CN108881353B

CN108881353B - Content pushing method and device and computer readable storage medium

Info

Publication number: CN108881353B
Application number: CN201710342522.3A
Authority: CN
Inventors: 黄思军
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2017-05-16
Filing date: 2017-05-16
Publication date: 2020-07-31
Anticipated expiration: 2037-05-16
Also published as: CN108881353A

Abstract

The application provides a content pushing method, which comprises the following steps: receiving user data sent by a first user terminal; storing the user data by using user information corresponding to the user data as an index; responding to a push request of a second user terminal, and searching user data which is stored by the second user terminal and corresponds to the user information according to the user information in the push request; generating a content push list according to the searched user data; and issuing the content push list to the second user terminal. The application also provides a corresponding device for pushing the content and a computer readable storage medium.

Description

Content pushing method and device and computer readable storage medium

Technical Field

The present application relates to the field of information technology, and in particular, to a content push method, an apparatus for executing the content push method, and a computer-readable storage medium.

Background

Currently, when a user turns on a television or other client device to watch multimedia or other programs, the television or other client device often recommends some programs and the like that may be of interest to the user, for example, recommending multimedia content based on past search records of the user, and the like. The pushing of the content can help the user to find the content in which the user is interested, and the processing efficiency of the client device and the network is improved.

Disclosure of Invention

The application example provides a content pushing method. The method comprises the following steps: receiving user data sent by a first user terminal; storing the user data by using user information corresponding to the user data as an index; responding to a push request of a second user terminal, and searching user data which is stored by the second user terminal and corresponds to the user information according to the user identity information in the push request; generating a content push list according to the searched user data; and issuing the content push list to the second user terminal.

The application example also provides a content pushing method. The method comprises the following steps: reading user data on the wearable intelligent device; and sending the user data to a server so that the server generates a content push list according to the user data.

The application example provides a server. The server includes:

The receiving module is used for receiving user data sent by a first user terminal and storing the user data by taking user information corresponding to the user data as an index;

The query module is used for responding to a push request of a second user terminal and querying user data which are stored in the query module and correspond to the user information according to the user identity information in the push request;

The generation module is used for generating a content push list according to the user data; and

And the sending module is used for sending the content push list to the second user terminal.

The embodiment of the application provides a user terminal. The user terminal includes:

The reading module is used for reading user data on the wearable intelligent equipment; and

And the sending module is used for sending the user data to a server so that the server generates a content push list according to the user data.

The present application also provides a computer-readable storage medium capable of implementing the content push method, where the computer instructions are stored thereon, and when executed by a processor, the computer instructions implement the steps of any one of the content push methods described above.

Through the technical scheme, the method can select the appropriate content for the user to popularize according to the user data acquired by the wearable intelligent device, and avoid unnecessary program switching operation, thereby improving the processing efficiency of the client device and the content server, reducing the power consumption and saving hardware and network resources.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.

FIG. 1 is a schematic diagram of a system architecture according to an example of the present application;

FIG. 2 is a flowchart illustrating a method for pushing content from a user terminal according to an embodiment of the present application;

FIG. 3 is a flow chart of a server-side content push method according to an embodiment of the present application;

FIG. 4 is a flow chart of a content push method according to an embodiment of the present application;

Fig. 5 is a flowchart of a method for establishing a correspondence between a public number of a target application and account information of target application software according to an embodiment of the present application;

FIG. 6 is a flow chart of a content push method according to an embodiment of the present application;

FIG. 7 is a flow chart of a content push method according to an embodiment of the present application;

Fig. 8 is a schematic structural diagram of a server of a content push method according to an example of the present application;

Fig. 9 is a schematic hardware structure diagram of a server of a content push method according to an example of the present application;

Fig. 10 is a schematic structural diagram of a user terminal of a content push method according to an example of the present application; and

Fig. 11 is a schematic hardware structure diagram of a user terminal of a content push method according to an example of the present application.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

For simplicity and clarity of description, the invention will be described below by describing several representative embodiments. The numerous details of the examples are merely provided to assist in understanding the inventive arrangements. It will be apparent, however, that the invention may be practiced without these specific details. Some embodiments are not described in detail, but rather are merely provided as frameworks, in order to avoid unnecessarily obscuring aspects of the invention. Hereinafter, "including" means "including but not limited to", "according to … …" means "at least according to … …, but not limited to … … only". When the number of one component is not particularly specified hereinafter, it means that the component may be one or more, or may be understood as at least one.

As described above, pushing of content can help a user find content of interest to him/her, and processing efficiency of a client device and a network is improved. However, in the current content push, pushed content is selected according to the use habits of users or keywords searched in the past, and the data collected by the content push is too single and does not make good use of other data of the users, so that the pushed content is not necessarily suitable for the users.

In order to solve the above problem, an example of the present application provides a content pushing method, which may obtain user data related to a user from a wearable smart device, and select a suitable content for the user to push according to the obtained user data. The user data is acquired by the wearable intelligent device, and can represent the data of the user characteristics, for example, the data can include body characteristic data such as heart rate, pulse, sleep quality, and even index of blood pressure and blood sugar of the user, or can be called physiological data; the system also can comprise movement data such as walking step number, movement duration, movement speed and the like; and the call data can also comprise call duration, call objects and the like. In the embodiment of the application, the data on which the pushed content selection is performed is more comprehensive, so that more suitable content can be provided for the user. On the other hand, the method can also improve the processing efficiency of the client device and the server, avoid frequent interaction between the user terminal and the server, and save hardware and power resources.

Fig. 1 is a schematic diagram of a system structure to which the content push method according to some examples of the present application is applied. As shown in fig. 1, the system of the present application includes at least: user terminal 11, wearable smart device 12, network 13, server 14 and database 15.

In some examples of the present application, the user terminal 11 may be an intelligent terminal device such as a smart television, a Personal Computer (PC), a notebook computer, or the like, or an intelligent mobile terminal device such as a smart phone, a PAD, or a tablet computer. In some examples of the present application, the user terminal 11 may include a short-range communication module, such as a bluetooth module 16 or the like. Through the short-range communication module, the user terminal 11 can directly communicate with other terminal devices in a short range, such as the wearable smart device 12. In other examples of the present application, the user terminal 11 may include a network communication module, such as a WiFi module or the like. Through the network communication module, the user terminal 11 can access a network to communicate with a server or other terminal devices in the network. In general, various application software may be installed on the user terminal 11, including application software that a user currently needs to use for watching videos such as movies, television programs, live programs, and the like, and text and/or picture contents such as news, hotspots, comments, and the like. In the following description, for convenience of description, the application software to be used or being used by the user is referred to as target application software.

The wearable smart device 12 may be a wearable smart device such as a wrist type or a head type, for example, a smart band, a smart foot ring, a smart belt or a smart helmet. The wearable smart device 12 may collect and record various user data of the user, such as body characteristic data, exercise data, and call data, among others. Typically, the wearable smart device 12 may also connect to other devices in close proximity via a short-range communication module, such as the bluetooth module 16, and transmit user data. Of course, the wearable smart device 12 may also access the network and communicate with other devices through other communication methods.

The network 13 may include a wired network and a wireless network. As shown in fig. 1, on the access network side, a user terminal 11 may access a network 13 in a wireless manner or a wired manner; on the core network side, the server 14 is typically connected to the network 13 by wire. Of course, server 14 may also be connected to network 13 by wireless means.

The server 14 is a server of the above-described target application software, and may be, for example, a multimedia server such as a server of a penguin TV; it may also be a content server providing text and/or picture push content for the user, for example, an Tencent news server, etc. The server 14 provides services, such as video program push, text and/or picture content push, etc., for the user together with the user terminal 11.

The database 15 is used for storing data related to the target application software, such as account information of the user and user data of the user. Database 15 may be separate from server 14 in the manner shown in fig. 1, or may be integrated with server 14.

On the premise, based on the system structure shown in fig. 1, the example of the present application provides a content push method. Fig. 2 shows a flowchart of a content pushing method provided by an example of the present application. As shown in fig. 2, the method may be performed by the user terminal 11, comprising the steps of:

Step 201: the user terminal 11 reads user data on the wearable smart device 12.

In some examples, the user terminal 11 may establish a connection with the wearable smart device 12 through a short-range communication method such as bluetooth, and store the connection relationship with the wearable smart device 12. Therefore, the user terminal 11 can read the user data on the wearable smart device 12 through a short-distance communication mode such as bluetooth according to the connection relationship with the wearable smart device 12 stored by itself.

Specifically, an application client capable of reading user data on the wearable smart device 12 needs to be installed in advance on the user terminal 11, and the connected wearable smart device 12 is added to the application client. In the present application, the application client is referred to as an application client related to the wearable smart device. The Application client associated with the wearable smart device may call an operating system of the wearable smart device 12 to leave a specific Interface, such as an Application Programming Interface (API), and read the user data from the wearable smart device 12 through the Interface and a short-distance communication method such as bluetooth. The application client related to the wearable smart device may be an application developed for one or more wearable smart devices 12, such as some sports applications, for example, gurgling sports, Keep, and the like. The application client of the wearable smart device may also be a sub-function developed on the basis of other application programs, for example, a public number or an applet developed on a social application platform, such as wechat sports, microblog sports, and the like; or a sub-function which is developed on the basis of the target application and can read data of the wearable smart device, for example, a sports sub-function can be developed on the penguin TV, through which the wearable smart device connected to the user terminal can be bound and various data of the wearable smart device can be read, and the like. The user data may include heart rate, pulse, sleep quality, and even body characteristic data such as blood pressure and blood sugar of the user monitored by the wearable smart device 12; the user data can also comprise movement data such as walking step number, movement duration, movement speed and the like; in addition, the user data may also include call duration, call object, and other call data. The physical characteristic data and the sport host in the data can reflect the current physical state of the user, and the call data in the data can reflect the contact condition of the user and others, namely the partial social state.

In some instances, the user terminal 11 may communicate with the wearable smart device 12 on the premise that the two establish a connection. When the user terminal 11 needs to read user data on the wearable intelligent device 12, it may first determine whether a connection relationship has been established with a certain wearable intelligent device 12 according to a connection relationship stored by itself, and if so, read corresponding data through the established connection relationship; if not, the connection is established first, and then the corresponding data is read. Specifically, the user terminal 11 may determine whether the connection relationship stored in itself includes a connection relationship record with the wearable smart device 12, and if the connection relationship record with the wearable smart device 12 is included, determine that the wearable smart device 12 is already connected; if the connection relationship record of the wearable smart device 12 is not contained, it is determined that the wearable smart device 12 is not connected.

When it is determined that the wearable smart device 12 is not connected, if a connection is to be established with the wearable smart device 12, the user terminal 11 may actively search for nearby wearable smart devices through a short-range communication module such as bluetooth and turn on the wearable smart device with the short-range communication function, and make a selection by the user and determine whether to pair with a certain wearable smart device 12 to establish a connection. Or the user actively starts the short-distance communication module of the wearable intelligent device 12, and after the wearable intelligent device 12 searches the user terminal 11, the user selects and confirms to pair with the user terminal 11 to establish connection. Of course, the user terminal 11 may also search nearby wearable smart devices that support and open network communication functions through the network function module and make selections by the user and determine whether to pair with a certain wearable smart device 12 to establish a connection.

Step 202: the user terminal 11 transmits the user data to the server 14.

In some examples, as mentioned above, the user terminal 11 may read the user data on the wearable smart device through the application client associated with the wearable smart device, then read the user data from the application client associated with the wearable smart device through the target application client installed thereon, and finally send the user data to the server 14 through the target application client installed thereon. As mentioned above, the application client of the wearable smart device may be an independent application program or a public number or an applet developed on the social application platform and related to the wearable smart device. And the target application client may be a stand-alone target application client, for example, a penguin TV client. In this case, the user data may be marked with account information of the target application software on the user terminal 11 as an identifier to which user the user data corresponds. Alternatively, the target application client may be a target application public account or applet developed on the social application platform. At this time, the user data may use the user identifier of the target application public number on the user terminal 11 as an identifier to mark which user the user data corresponds to. As an example, after a user binds a certain smart band to a wechat sport public number, the wechat sport public number may read user data from the bound smart band at regular time or in response to a user request, and at this time, if the user also pays attention to the public number of the penguin TV on the wechat client, the public number of the penguin TV may read user data from the wechat sport public number at regular time or in response to a user request and upload the user data to the penguin TV server.

In some examples, after the user terminal 11 receives the user data, the user data may be sent to the server 14 by a Common Gateway Interface (CGI) provided by the server 14 through a target application client or a target application public number, together with account information of target application software on the user terminal 11 or a user identifier of the target application public number on the user terminal 11. In some examples of the present application, if the user data uses the user identifier of the target application public number on the user terminal 11 as an identifier, the user terminal 11 needs to configure a binding relationship between the user identifier of the target application public number and the account information of the target application software on the server 14 through the CGI interface in advance, that is, the user identifier of the target application public number and the account information of the target application software corresponding to the same user are simultaneously sent to the server 14, so as to establish a mapping relationship between the two in the server 14. The CGI interface CGI is an interface standard between an external application program (CGI program) and a web server, and is a process for transferring information between the CGI program and the web server. The CGI specification allows web servers to execute external programs and send their output to web browsers, which turn a simple set of static hypermedia documents of a web page into a complete new interactive media. The account information of the user terminal 11 may be a user login account of the target application software, such as a user login account in the form of a phone number, a mailbox, or a QQ number.

Further, after receiving the user data and the account information of the user terminal 11, the server 14 may store the user data to the database 15 by using the user information corresponding to the user data as an index, so that the server 14 can find the user data corresponding to the account information of the user terminal 11 through the user information in subsequent processing. In some examples of the present application, the user information may be account information of the target application software. In other examples of the present application, the user information may be a user identifier of a public number of the target application.

Step 203: the user terminal 11 requests content push to the server 14.

In some examples, when the user opens the target application software of the user terminal 11 to view a certain multimedia content, the user terminal 11 may send a multimedia playing request to the server 14, requesting the server 14 to issue the corresponding multimedia. The multimedia playing request includes user identity information of the user terminal 11, for example, account information of the target application software. At this time, the server 14 will issue the corresponding multimedia to the ue 11 according to the user id information in the request. Meanwhile, for the server 14, the multimedia playing request is further regarded as a push request, that is, the server 14 is requested to issue the content push list while issuing the specified multimedia. At this time, the server 14 further selects a suitable push content for the user according to the user data corresponding to the user identity information received from the user terminal 11, generates a content push list, and issues the content push list to the user terminal 11. Details regarding how server 14 selects content to be pushed will be described below.

In other examples, when the user opens the target application software of the user terminal 11 and does not select to view a certain multimedia content, the user terminal 11 may also send a push request to the server 14 to request the server 14 to send the content to be pushed. The push request includes user identity information of the user terminal 11, for example, account information of the target application software. At this time, the server 14 selects a suitable push content for the user according to the user data corresponding to the user identity information received from the user terminal 11, generates a content push list, and issues the content push list to the user terminal 11. Details regarding how server 14 selects content to be pushed will be described below.

Step 204: the user terminal 11 receives and displays the content push list sent by the server 14.

In some examples, after receiving the push content list sent by the server 14, the user terminal 11 may display the push content list in a single area at a preset position for the user to select, for example, display the push content list on the left side of the display window; or displaying the pushed content list in the whole display window. In some examples of the present application, if the server 14 issues the multimedia content requested by the user at the same time in addition to the push content list, the user terminal 11 will display the multimedia content requested by the user and the push content list issued by the server at the same time, for example, the multimedia content requested by the user is displayed on the left side of the display window, and the push content list is displayed on the right side of the display window.

Next, in response to the selection of the user, the user terminal 11 may acquire and play the push content selected by the user from the server 14.

In addition, in some examples of the present application, the user terminals 11 in the above steps 201 to 204 may be physically the same user terminal, but are not logically the same user terminal, for example, the user terminal 11 in 201 may be an application client related to a wearable smart device on a mobile terminal, for example, a sports-type application client or a wechat sports public number on a wechat, and in this case, the user terminal may be referred to as a first user terminal. The user terminal 11 in 202 may be a target application client on a mobile terminal, such as a penguin TV client or a penguin TV public number on a WeChat. The user terminal 11 in steps 203-204 may be a target application client on the mobile terminal, for example, an Tencent video client. At this time, the user terminal may be referred to as a second user terminal.

In other examples of the present application, the user terminal 11 in the steps 203 to 204 and the user terminal 11 in the steps 201 to 202 may not be the same user terminal physically. For example, the user terminal 11 in steps 201-202 may be a mobile terminal, such as a smart phone of a user. At this time, the user terminal may be referred to as a first user terminal. In some examples of the present application, the first user terminal may specifically refer to an application client or a target application client on a mobile terminal, which is related to a wearable smart device, for example, a penguin TV public number on a WeChat. And the user terminal 11 in steps 203-204 can be a client device, for example, a smart television of a user. At this time, the user terminal may be referred to as a second user terminal. In some examples of the present application, the second user terminal may also specifically refer to a target application client on a smart television, for example, a penguin TV client. That is, for example, an application client (a first user terminal) on a smart phone of a user uploads user data collected by a wearable smart device connected thereto to a server; then, the server selects the content to be pushed for the user according to the user data, generates a content pushing list, issues the content pushing list to a target application program client (a second user terminal) on the smart television of the user, and the smart television finishes pushing the content. Of course, in order to complete such content push, the server needs to establish an association relationship between the first user terminal and the second user terminal of the user in advance. The detailed description of how to establish the association relationship between the first mobile terminal and the second mobile terminal will be described below.

Fig. 3 shows a flowchart of a content pushing method provided by an example of the present application. As shown in fig. 3, the method may be performed by the server 14, comprising the steps of:

Step 301: the server 14 receives the user data transmitted from the user terminal 11.

In some examples, the user terminal 11 may use account information of the target application software on the user terminal 11 as an identifier of the user data and send the user data to the server.

In other examples, the user terminal 11 may use the user identifier of the target application public number on the user terminal 11 as the identifier of the user data and send the user data to the server. At this time, the server 14 will receive the user data sent by the first user terminal through the target application public number; wherein the user data is read from the wearable smart device by a target application client or a public number on the first user terminal through a client or a public number of an application related to the wearable smart device.

Step 302: the server stores the user data with the user information corresponding to the user data as an index.

In some examples, after receiving the user data and the information as its identification, the server 14 may determine the user information corresponding to the user data according to the information as its identification.

Specifically, in some examples, when the user terminal 11 uses the user account information of the target application software on the user terminal 11 as the identifier of the user data, the user information may be the user account information of the target application software. Alternatively, in another example, when the user terminal 11 uses the user identifier of the target application public number on the user terminal 11 as the identifier of the user data, the user information may be the user identifier of the target application public number. In another example, when the user terminal 11 uses the user identifier of the target application public number on the user terminal 11 as the identifier of the user data, the user information may be the user account information of the target application software corresponding to the user identifier of the target application public number. In this case, the server 14 will establish and store a correspondence between the user identification of the public number of the target application and the user account information of the target application software in advance. The method for establishing the above correspondence relationship will be described in detail below.

The main purpose of storing the user data in the database 15 using the user information as an index is that the server 14 can search the user data corresponding to the user through the user identification information such as the account number of the user terminal 11 in the subsequent processing.

Step 303: in response to the push request of the user terminal 11, the server 14 queries the user data stored in the server according to the user identity information in the push request, where the user data corresponds to the account information of the user terminal 11.

In some examples, the push request may refer to a multimedia play request of a user. When the server 14 receives the multimedia playing request sent by the user terminal 11, the storage address of the corresponding multimedia is obtained and fed back to the user terminal 11. Meanwhile, the server 14 will further query the user data stored in itself and corresponding to the user identity information according to the user identity information carried in the multimedia playing request.

In some examples, the push request may refer to a push request of a user. When the server 14 receives the push request sent by the user terminal 11, it will query the user data corresponding to the account information of the user terminal stored in itself according to the user identity information carried in the multimedia play request.

In some examples of the present application, the user identity information may be account information of the target application software. When the server 14 stores the user data by using the account information of the target application software as an index, the server 14 may directly search the user data corresponding to the account information of the target application software in the push request. When the server 14 stores the user data by using the user identifier of the target application public number as an index, the server 14 determines the account information of the target application software corresponding to the user identifier of the target application public number in the push request according to the corresponding relationship between the account information of the target application software stored by the server 14 and the user identifier of the target application public number, and searches the user data corresponding to the determined account information of the target application software.

Step 304: the server 14 generates a content push list based on the determined user data.

In some examples, after the server 14 finds the user data according to the account information of the user terminal 11, a data adaptation algorithm is started, and a content push list is generated according to the determined user data. The algorithm is mainly used for calculating various contents of the user data, such as heart rate, pulse, sleep quality, blood pressure, blood sugar and the like, through a preset calculation formula to obtain specific numerical values. This specific numerical value is referred to as a physical characteristic value in the present application. And then, generating a content push list according to the numerical range of the body characteristic value. Still further, in addition to the physical characteristic value, the server 14 may further generate a content push list according to the current time and the multimedia channel currently viewed by the user.

For example, the threshold value of the body feature value is set to 80, and if the threshold value is greater than 80, the body feature value is higher. If the user is in the morning and the body characteristic value calculated according to the above adaptation algorithm is high, it indicates that the user may not be in good sleep quality and the heart rate, pulse and blood pressure may be high. At this time, if the user stays in the selected channel, the server 14 recommends some multimedia that is more leisure, health preserving, or comfortable and more suitable for the current state of the user to the user, such as entertainment programs, diet programs, health preserving medical programs, and the like, to help the user relax the mood.

For another example, the threshold value of the body feature value is set to 80, and if greater than 80, the body feature value is higher. If it is night and the body characteristic value calculated according to the above-mentioned fitting algorithm is high, it indicates that the user may be tired currently and the heart rate, pulse and blood pressure may be high. If the user is staying in the movie channel, the server 14 will recommend a relatively easy and leisure movie suitable for the current status of the user, such as comedy or love, to the user to help the user relax the mood.

Step 305: the server 14 issues the generated content push list to the user terminal 11.

In addition, in some examples of the present application, the user terminal 11 in the above steps 302-304 and the user terminal 11 in the above step 301 may be physically the same user terminal.

In other examples of the present application, the user terminal 11 in the above steps 302 to 304 and the user terminal 11 in the above step 301 may not be the same user terminal physically. For example, the user terminal 11 in step 301 may be a mobile terminal, such as a smartphone of the user. At this time, the user terminal may be referred to as a first user terminal. And the user terminal 11 in steps 302-304 can be a client device, such as a smart television of a user. At this time, the user terminal may be referred to as a second user terminal. That is, for example, a smart phone (a first user terminal) of a user uploads user data collected by a wearable smart device connected thereto to a server; then, the server selects the content to be pushed for the user according to the user data, generates a content pushing list, issues the content pushing list to the smart television (a second user terminal) of the user, and the smart television finishes pushing the content. As described above, in order to complete such content push, the server needs to establish an association relationship between the first user terminal and the second user terminal of the user in advance. The detailed description of how to establish the association relationship between the first mobile terminal and the second mobile terminal will be described below.

Through the method, the server 14 can determine the current state of the user by fully utilizing the user data related to the user and collected by the wearable intelligent device 12, and recommend the content suitable for the current state of the user according to different states of different users, so that the accurate delivery of the content can be realized. In addition, on one hand, the method can enhance human-computer interaction and improve user experience; on the other hand, frequent interaction between the user terminal and the server can be avoided, so that the processing efficiency of the user terminal and the server and the utilization rate of the network are improved, the power consumption is reduced, the resources are saved, and the like.

Specifically, in some examples of the present application, the user terminal 11 may be a mobile terminal, such as a portable mobile device, such as a smart phone, a tablet computer, and a PAD. In some examples of the present application, the user terminal 11 may also be a client device such as a smart tv, a personal computer, or the like. Of course, a combination of a mobile terminal and a client device is also possible. When the user terminal 11 is a different intelligent device, the implementation details of the multimedia data synchronization method shown in fig. 2 may be different. The content push methods provided by some examples of the present application are further described below in conjunction with various examples.

Example one: in this example, the user terminal 11 is implemented by two terminal devices, a mobile terminal and a client device. Fig. 4 is a schematic diagram of a system structure to which the content push method according to this example is applied. As shown in fig. 4, the current system includes: mobile terminal, wearable intelligent device, server and customer end equipment. In this example, a mobile terminal as the first terminal is connected to the wearable intelligent device 12 in a short-distance communication manner to obtain user data; the client device, as the second terminal, requests the server 14 to issue the multimedia data content and display the multimedia data content.

In some examples of the present application, fig. 4 shows a flow chart of a content push method according to an example of the present application. As shown in fig. 4, the method may include the steps of:

Step 401: the mobile terminal reads the user data on the wearable smart device 12.

In view of the connection mode, in some examples, the mobile terminal may establish connection with the wearable smart device 12 through short-range communication modes such as bluetooth, and further may read user data obtained by monitoring the wearable smart device 12 through short-range communication modes such as bluetooth according to a connection relationship stored in the mobile terminal and the wearable smart device 12, where the user data may include body characteristic data, motion data, call data, and the like of the user.

From an application level, in particular, in some examples, the mobile terminal may read the user data from the wearable smart device 12 through an application client (e.g., a sports application or a public account or applet of a sports class on a social platform) associated with the wearable smart device. At this time, a target application client (e.g., a target application or a target application public number or an applet on the social platform) on the mobile terminal may further read the user data from an application client associated with the wearable smart device. This is shown in step 401a, shown in dashed lines in figure 4.

For example, the mobile terminal may call a plug-in or a public number of a certain social platform (or other public platforms) to read the user data from the wearable smart device 12, for example, read body feature data, motion data, and call data on a smart bracelet connected to itself through a wechat sport public number of a wechat platform or a surf sport plug-in of a surf microblog platform. The public number can be an application account number applied by a developer or a merchant on a public platform and is displayed in a webpage form, such as an H5 page form, and through the public number, the merchant can realize all-round communication and interaction with characters, pictures, voice and videos of a specific group on the public platform. For example, the wechat sport public number is an application account number applied on the wechat public platform, and a wechat user can check the number of steps of walking per day by paying attention to the wechat sport public number, and can compare the amount of exercise with other users or approve the exercise. Then, the mobile terminal can also read the user data from the related public account at preset time intervals through the public number of the target application on the public platform. For example, the mobile terminal reads user data from the WeChat sports public number on the WeChat platform every 5 seconds through the public number of the penguin TV on the WeChat platform.

In other examples, the client software of the target application may be developed secondarily to extend the function of reading the user data on the wearable smart device 12 connected to the mobile terminal, for example, to extend the function of the penguin TV, so that the user data on the wearable smart device 12 connected to the mobile terminal may be directly read. In this case, the user terminal may directly read the user data through the client of the target application and upload the user data to the server through the client of the target application.

Step 402: the mobile terminal transmits the user data to the server 14.

The implementation method of step 402 can refer to step 202. Specifically, the mobile terminal may upload the user data to the server 14 through a CGI interface provided by the server 14 to the public platform using the public number of the target application. The user data may use a user identifier of the target application public number as an identifier to distinguish which user the user data corresponds to.

Step 403: the server 14 stores user data from the mobile terminal.

In some examples, after receiving the user data and the user identifier of the target application public number, the server 14 finds the account information of the target application software corresponding to the user identifier of the target application public number as the user data identifier through the correspondence between the user identifier of the target application public number stored in the server 14 and the account information of the target application software, and stores the user data to the database 15 by using the account information of the target application software as an index, so that the server 14 can find the user data under the account through the account information of the target application software in subsequent processing. The account information of the target application software may be a user login account of the target application software installed on the client device, such as a user login account in the form of a phone number, a mailbox, or a QQ number.

the target application public number is an application account number applied by the target application software on a public platform of the social application, the application account number is an identifier of the target application public number, and the identifier of the target application public number may be a home page UR L.

The method for establishing the corresponding relationship between the user identifier of the target application public number and the account information of the target application software is described in detail below.

Step 404: the client device requests a content push from the server 14.

In some examples, the client device may be a smart television, a personal computer, or the like. The push request may include user identity information, for example, account information of the target application software. The implementation method of step 404 may refer to step 203.

Step 405: in response to a request by the client device, the server 14 generates a content push list from its stored user data.

The implementation method of step 405 above may refer to

steps

302 and 303 above.

Step 406: the server 14 issues the generated content push list to the client device.

Step 407: and the client equipment receives and displays the conventional multimedia and recommended multimedia content push list for the user to select.

The implementation method of step 407 may refer to step 204.

Thereafter, the client device may request the corresponding content from the server 14 in response to the push content selected by the user.

A method for establishing a correspondence relationship between a user identifier of a target application public number and account information of target application software will be described in detail with reference to examples.

Fig. 5 shows a flowchart of a method for establishing a correspondence between a user identifier of a target application public number and account information of target application software. As shown in fig. 5, the method comprises the steps of:

Step 501: in response to the user's binding request, the client device exposes a binding interface and sends a binding request to the server 14.

in some examples, the binding interface may be a web page, such as a H5 page, the client device configures user information, such as a device identifier of the client device and account information of the target application software, in a Uniform Resource locator UR L (Uniform Resource L adapter) address for accessing the binding interface, adds the user information, such as the device identifier of the client device and the account information of the target application software, to a tail of the UR L of the binding interface, and sends the UR L of the binding interface to the server 14 as a binding request parameter.

Step 502: the server 14 generates an e-code according to the binding request and sends the e-code to the client device for presentation.

in some examples of the present application, the electronic code may be a bar code, a two-dimensional code, or other graphic identification code, and the UR L of the binding interface is included in the electronic code, that is, the UR L of the binding interface includes user information such as a device identifier of the client device and account information of the client device side of the target application software.

Step 503: and the client equipment receives and displays the electronic code.

In some examples of the present application, after receiving an electronic code issued by a server, a client device displays the electronic code through its own display device.

and 504, the mobile terminal scans the electronic code, obtains the UR L of the binding interface according to the electronic code, jumps to the binding interface provided by the public number of the target application according to the UR L of the binding interface to obtain the device identification of the client device, the account information of the target application software and other user information, and prompts the user to bind.

in some examples, the premise that the social application client of the mobile terminal directly jumps to the binding interface provided by the target application public number according to the UR L of the binding interface is that a user account of the social application of the mobile terminal user concerns the public number of the target application, if the user account does not concern the public number of the target application, the user is prompted to pay attention by directly jumping to a home page of the public number of the target application, and if the user account concerns the public number of the target application, the user information such as the device identification of the client device and the account information on the device side of the target application software client is obtained by directly jumping to the binding interface provided by the public number of the target application, and the user binding is prompted.

for example, the social application is a WeChat client, the target application software is a penguin TV, the target application public number is an application account number applied by the penguin TV on a WeChat public platform, and the application account number is identified as a penguin public number first page UR L, then if the user account number of the WeChat client of the mobile terminal user does not pay attention to the public number of the penguin TV, the WeChat client of the mobile terminal jumps to the first page of the penguin public number first to prompt the user to pay attention, and if the user account number of the WeChat client of the mobile terminal user pays attention to the public number of the penguin TV, the WeChat client jumps directly to a binding interface provided by the target application public number to acquire user information such as a device identifier of the client device and account information on the target application software client device side included in the binding interface and prompts.

Step 505: and responding to the binding operation of the user, and binding the target application public number identification and the target application software client side account information through the social application client on the mobile terminal.

In some examples, the target application public number of the social application client may add account information of the target application software client device side to an account management list corresponding to the target application public number identifier to implement binding on the mobile terminal side.

Step 506: the social application client on the mobile terminal generates a user identifier of the target application public number according to the user identifier of the target application public number and the user account of the social application client, adds the user identifier of the target application public number and the account information of the target application software into a binding success notification, and sends the binding success notification to the server 14.

in a specific example, the target application public number is a penguin TV public number, the target application public number identifier may be a penguin TV public number home page UR L, and the user account of the social application client is a user account of the wechat client, so the user account of the wechat client may be added to the end of the penguin TV public number home page UR L to generate the user identifier of the penguin TV public number, that is, the user account of the penguin TV public number home page UR L + the wechat client is used as the user identifier of the penguin TV public number.

Step 507: the server 14 receives the binding success notification from the social application client, and establishes a corresponding relationship between the account information of the target application software and the user identifier of the target application public number, that is, establishes a binding relationship.

It should be noted that fig. 5 shows a method for establishing a correspondence between a user identifier of a public number of a target application and account information of target application software. By the method, the mobile terminal and the client equipment can be associated at the server, so that after the server receives the user data of the target application public number from the mobile terminal and generates the content promotion list according to the user data, the account information of the target application client equipment corresponding to the user identification of the target application public number on the mobile terminal can be found according to the established corresponding relation, and the generated content promotion list is issued to the corresponding client equipment according to the account information.

In some examples of the present application, the server may also establish a correspondence between the mobile terminal and the client device in other manners. For example, the server may directly establish the correspondence between the device identifications. For example, the server establishes a correspondence between the device identification of the mobile terminal and the device identification of the client device. Thus, after the server receives the user data from the mobile terminal and generates the content promotion list according to the user data, the server can also find the equipment identifier of the client equipment corresponding to the equipment identifier of the mobile terminal according to the established corresponding relation, and issue the generated content promotion list to the corresponding client equipment according to the equipment identifier of the client equipment.

Or the server directly completes the association between the mobile terminal and the client device through the account information of the target application software. For example, the server establishes a correspondence between the mobile terminal and the client device that log in through the same account. Thus, after the server receives the user data from the mobile terminal and generates the content promotion list according to the user data, the server can find the client device which logs in the server by using the same account number as the mobile terminal according to the established corresponding relation, and send the generated content promotion list to the corresponding client device.

Example two: in this example, the user terminal 11 is a mobile terminal. In this example, the mobile terminal and the wearable smart device 12 are connected to obtain user data, and the mobile terminal requests the server 14 to issue multimedia data content and display the multimedia data content.

In some examples of the present application, fig. 6 shows a specific implementation flow when the user terminal 11 is a mobile terminal. As shown in fig. 6, the method may include the steps of:

Step 601: the mobile terminal reads the user data on the wearable smart device 12.

Specifically, the step 401 may be referred to as an implementation method of the step 601.

Step 602: the mobile terminal transmits the user data to the server 14.

The implementation method of step 602 above may refer to step 402 above.

Step 603: the server 14 stores user data from the mobile terminal.

The implementation method of step 603 may refer to step 403.

Step 604: the mobile terminal requests a content push from the server 14.

The implementation method of step 604 may refer to step 404.

Step 605: in response to the request of the mobile terminal, the server 14 generates a content push list from the user data stored in itself.

The implementation method of step 605 may refer to step 405.

Step 606: the server 14 issues the generated content push list to the mobile terminal.

Step 607: and the mobile terminal receives and displays the conventional multimedia and recommended multimedia content push list for the user to select.

The implementation method of step 607 above may refer to step 407 above.

Thereafter, the mobile terminal may request the corresponding content from the server 14 in response to the push content selected by the user.

Example three: in this example, the user terminal 11 is a client device. In this example, the client device and the wearable smart device 12 are connected to obtain user data, and the client device requests the server 14 to issue and present multimedia data content.

In some examples of the present application, fig. 7 shows a specific implementation flow when the user terminal 11 is a client device. As shown in fig. 7, the method may include the steps of:

Step 701: the client device reads the user data on the wearable smart device 12.

In this example, the client device may communicate with the wearable smart device 12 via a short-range communication module such as bluetooth.

The implementation method of the step 701 may refer to the step 201.

Specifically, the secondary development may be performed on the client of the target application software, so as to extend the function of reading the user data on the wearable smart device 12 connected to the mobile terminal, for example, the function of extending the penguin TV, so that the user data on the wearable smart device 12 connected to the mobile terminal may be read.

Step 702: the client device sends the user data to the server 14.

The implementation method of step 702 may refer to step 202.

Specifically, the client device may send the user data and account information of the client device side of the target application software to the server 14 in a network interaction mode by using the target application software installed in the client device.

Step 703: the server 14 stores user data from the client devices.

In some examples, after receiving the user data and the account information of the target application client device side, the server 14 may store the user data to the database 15 by using the account information of the target application client device side as an index, so that the server 14 can find the user data corresponding to the account information of the target application client device side through the account information of the target application client device side in subsequent processing.

Step 704: the client device requests a content push from the server 14.

The implementation method of step 704 may refer to step 203.

Step 705: in response to a request by the client device, the server 14 generates a content push list from its stored user data.

The implementation method of step 705 above can refer to step 605 above.

Step 706: the server 14 issues the generated content push list to the client device.

Step 707: and the client equipment receives and displays the conventional multimedia and recommended multimedia content push list for the user to select.

The implementation method of step 707 above may refer to step 607 above.

By any of the above methods, the server 14 can recommend the content suitable for the current state of the user by making full use of the user data related to the user collected by the wearable smart device 12, so that the accurate delivery of the content can be realized. In addition, on one hand, the method can enhance human-computer interaction and improve user experience; on the other hand, frequent interaction between the user terminal and the server can be avoided, so that the processing efficiency of the user terminal and the server and the utilization rate of the network are improved, the power consumption is reduced, the resources are saved, and the like.

Corresponding to the content push method, the application also provides a content push server 800 and a user terminal 1000 for implementing the method.

In some examples of the present application, the server 800 implementing the content push method may be implemented by a structure diagram shown in fig. 8, and includes a receiving module 801, a querying module 802, a generating module 803, and a sending module 804, where functions of the modules are as follows:

A receiving module 801, configured to receive user data sent by a first user terminal and store the user data with user information corresponding to the user data as an index;

The query module 802 is configured to respond to a push request of a second user terminal, and query user data corresponding to user information stored in the query module according to the user identity information in the push request;

A generating module 803, configured to generate a content push list according to the user data; and

A sending module 804, configured to issue the content push list to the second user terminal.

In some examples, the receiving module 801 is configured to save the user data to a database with account information of the target application software as an index; or the user data is stored in a database by taking the user identification of the target application public number as an index.

In some examples, the generating module 803 calculates each item of content of the user data by a preset calculation formula to obtain a physical characteristic value; and generating a content push list according to the numerical range of the physical characteristic numerical value. In other examples, the generation module 803 may further generate the content push list according to one or a combination of the current time and the current channel.

In order to make the content push server 800 have the binding function, the content push server 800 further includes:

the receiving module 801 further receives a binding request sent by the second terminal, wherein the binding request is a UR L address configured with a device identifier of the second terminal and account information of target application software;

The generating module 803 further generates an electronic code according to the binding request, and sends the electronic code to the second terminal for displaying;

The receiving module 801 further receives a binding success notification sent by the first terminal after scanning the electronic code; the binding notification is configured with a user identifier of the target application public number and account information of the target application software; and

The server further comprises: the establishing module 805 is configured to establish a corresponding relationship between the user identifier of the target application public number and the account information of the target application software.

Fig. 9 shows a block diagram of a computing device 900 in which the content push server 800 is located. As shown in fig. 9, the computing device includes one or more processors (CPUs) 902, a communications module 904, a memory 906, a user interface 910, and a communications bus 908 for interconnecting these components.

The processor 902 can receive and transmit data via the communication module 904 to enable network communications and/or local communications.

User interface 910 includes one or more output devices 912 including one or more speakers and/or one or more visual displays. The user interface 910 also includes one or more input devices 914, including, for example, a keyboard, a mouse, a voice command input unit or microphone, a touch screen display, a touch-sensitive tablet, a gesture-capture camera or other input buttons or controls, and the like.

The memory 906 may be a high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; or non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices.

The memory 906 stores a set of instructions executable by the processor 902, including:

An operating system 916 including programs for handling various basic system services and for performing hardware related tasks;

The application 918 includes various application programs for content push, and such application programs can implement the processing flows in the above examples, and for example, may include some or all of the units in the content push server 800 shown in fig. 8. At least one of the units or modules 801-805 may store machine-executable instructions. The processor 902 is able to carry out the functions of at least one of the modules 801-805 described above by executing machine executable instructions in at least one of the modules 801-805 in the memory 906.

In some examples of the present application, the user terminal 1000 for implementing content push may be implemented by a structure diagram shown in fig. 10, and includes a reading module 1001 and a sending module 1002, where functions of the modules are as follows:

The reading module 1001 reads user data on the wearable intelligent device;

The sending module 1002 is configured to send the user data to a server, so that the server generates a content push list according to the user data.

In some examples, the user terminal 1000 for implementing content push further includes a connection module 1003, configured to determine whether a connection relationship with the wearable smart device has been established according to a connection relationship stored in the connection module, and if the connection relationship with the wearable smart device has not been established, establish a connection with the wearable smart device through a short-distance communication manner such as bluetooth, and store the connection relationship with the wearable smart device.

In some examples, the reading module 1001 reads the user data from the wearable smart device through a target application or public number.

In some examples, the sending module 1002 sends the user data to the server by using user account information as an identifier through a Common Gateway Interface (CGI) provided by the server.

In some examples, the sending module 1002 further sends the user data to the server through a CGI interface provided by the server using a public number of a target application or target application software.

The user data sent by the sending module 1002 may use account information of the target application software as an identifier or use a user identifier of a public number of the target application as an identifier.

In order to make the content push user terminal 1000 have the binding function, the content push user terminal 1000 further includes:

A scanning module 1004, configured to scan an electronic code, which is issued by the server and is displayed by the second terminal in response to the binding request of the second terminal;

the binding module 1005 is used for obtaining a UR L of a binding interface displayed by the second terminal according to the electronic code, wherein the UR L of the binding interface is configured with the equipment identifier of the second terminal and account information of target application software;

The sending module 1002 further adds the user identifier of the target application public number to a binding success notification, and sends the binding success notification to the server.

The user terminal 1000 may further include:

The second sending module is used for sending a content pushing request to the server; wherein, the push request comprises user identity information;

The receiving module is used for receiving the content push list generated by the server; and

And the display device is used for displaying the content push list.

Fig. 11 shows a block diagram of a computing device 1100 in which the content push user terminal 1000 is located. As shown in fig. 11, the computing device includes one or more processors (CPUs) 1102, a communications module 1104, a memory 1106, a user interface 1110, and a communications bus 1108 for interconnecting these components.

The processor 1102 may receive and transmit data via the communication module 1104 to enable network communications and/or local communications.

The user interface 1110 includes one or more output devices 1112, including one or more speakers and/or one or more visual displays. The user interface 1110 also includes one or more input devices 1114, including, for example, a keyboard, a mouse, a voice command input unit or microphone, a touch screen display, a touch-sensitive input pad, a gesture-capture camera or other input buttons or controls, and the like.

Memory 1106 may be high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid state memory devices; or non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices.

The memory 1106 stores a set of instructions executable by the processor 1102, including:

An operating system 1116, including programs for handling various basic system services and for performing hardware-related tasks;

The application 1118 includes various application programs for content push, which can implement the processing flows in the above examples, and may include some or all of the units in the content push user terminal 1000 shown in fig. 10, for example. At least one of the units or modules 1001-1005 may store machine-executable instructions. The processor 1102 may be configured to implement the functionality of at least one of the modules 1001-1005 described above by executing machine-executable instructions within at least one of the modules 1001-1005 of the memory 1106.

It should be noted that not all steps and modules in the above flows and structures are necessary, and some steps or modules may be omitted according to actual needs. The execution order of the steps is not fixed and can be adjusted as required. The division of each module is only for convenience of describing adopted functional division, and in actual implementation, one module may be divided into multiple modules, and the functions of multiple modules may also be implemented by the same module, and these modules may be located in the same device or in different devices.

The hardware modules in the embodiments may be implemented in hardware or a hardware platform plus software. The software includes machine-readable instructions stored on a non-volatile storage medium. Thus, embodiments may also be embodied as software products.

Accordingly, some examples of the present application also provide a computer-readable storage medium having computer instructions stored thereon, wherein the computer instructions, when executed by a processor, implement the steps of the method of any of the above-described figures 2-7.

In various examples, the hardware may be implemented by specialized hardware or hardware executing machine-readable instructions. For example, the hardware may be specially designed permanent circuits or logic devices (e.g., special purpose processors, such as FPGAs or ASICs) for performing the specified operations. Hardware may also include programmable logic devices or circuits temporarily configured by software (e.g., including a general purpose processor or other programmable processor) to perform certain operations.

In addition, each example of the present application can be realized by a data processing program executed by a data processing apparatus such as a computer. It is clear that a data processing program constitutes the present application. Further, the data processing program, which is generally stored in one storage medium, is executed by directly reading the program out of the storage medium or by installing or copying the program into a storage device (such as a hard disk and/or a memory) of the data processing device. Such a storage medium therefore also constitutes the present application, which also provides a non-volatile storage medium in which a data processing program is stored, which data processing program can be used to carry out any one of the above-mentioned method examples of the present application.

Machine-readable instructions corresponding to the modules in fig. 8 and 10 may cause an operating system or the like operating on the computer to perform some or all of the operations described herein. The nonvolatile computer-readable storage medium may be a memory provided in an expansion board inserted into the computer or written to a memory provided in an expansion unit connected to the computer. A CPU or the like mounted on the expansion board or the expansion unit may perform part or all of the actual operations according to the instructions.

In addition, the devices and modules in the examples of the present application may be integrated into one processing unit, or each module may exist alone physically, or two or more devices or modules may be integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.

Claims

1. A content push method, wherein the method comprises:

Receiving user data sent by a first user terminal; storing the user data by using user information corresponding to the user data as an index;

Responding to a push request of a second user terminal, and searching user data which is stored by the second user terminal and corresponds to the user information according to the user identity information in the push request;

Generating a content push list according to the searched user data; and

Issuing the content push list to the second user terminal;

Wherein the method further comprises:

receiving a binding request sent by the second user terminal, wherein the binding request is a uniform resource locator UR L address configured with a device identifier of the second user terminal and account information of target application software;

Generating an electronic code according to the binding request, and sending the electronic code to the second user terminal for displaying;

Receiving a binding success notification sent by the first user terminal after scanning the electronic code; the binding notification is configured with a user identifier of the target application public number and account information of the target application software; and

And establishing a corresponding relation between the user identification of the target application public number and the account information of the target application software.

2. The method of claim 1, wherein the receiving user data transmitted by a first user terminal comprises:

Receiving user data sent by a first user terminal through a target application client; wherein the user data is read from the wearable smart device by a target application client on the first user terminal through an application client associated with the wearable smart device.

3. The method of claim 1, wherein the receiving user data sent by the first user terminal through the target application client comprises:

Receiving user data sent by a first user terminal through a target application public number; wherein the user data is read from the wearable smart device by a target application public number on the first user terminal through an application public number associated with the wearable smart device.

4. The method of claim 2, wherein the user information is account information of the target application software; the user identity information is account information of the target application software;

The first user terminal takes account information of target application software corresponding to user data as an identifier through the user data sent by a target application client;

The storing the user data with the user information corresponding to the user data as an index includes: and storing the user data by taking account information of the target application software corresponding to the user data as an index.

5. The method of claim 3, wherein the user information is a user identification of a target application public number; the user identity information is account information of the target application software;

The first user terminal takes a user identifier of a target application public number corresponding to user data as an identifier through user data sent by the target application public number;

Wherein the method further comprises:

Searching account information of the target application software corresponding to the user identification of the target application public number through the corresponding relation between the user identification of the target application public number stored in the corresponding relation and the account information of the target application software; and

And taking the found account information of the target application software as the user information corresponding to the user data.

6. The method of claim 3, wherein the user information is a user identification of a target application public number; the user identity information is account information of the target application software;

The first user terminal takes a user identifier of a target application public number corresponding to user data as an identifier through user data sent by the target application public number; and

The searching of the user data corresponding to the user information stored in the push request according to the user identity information in the push request comprises:

Searching the user identification of the target application public number corresponding to the account information of the target application software in the push request according to the corresponding relation between the user identification of the target application public number stored in the user identification of the target application public number and the account information of the target application software; and searching user data corresponding to the user identification of the target application public number in user data stored in the user data storage device.

7. The method of claim 1, wherein the generating a content push list according to the found user data comprises:

Calculating each content of the user data through a preset calculation formula to obtain a body characteristic value; and

And generating a content push list according to the numerical range of the physical characteristic numerical value.

8. The method of claim 1, wherein the generating a content push list according to the found user data comprises:

And generating a content push list according to one or a combination of the current time and the current channel and the value range of the physical characteristic value.

9. A content push method, wherein the method is performed by a first user terminal, comprising:

Reading user data collected by the wearable intelligent equipment through an application client related to the wearable intelligent equipment;

Reading the user data from the application client related to the wearable smart device through a target application client;

Sending the user data to a server through a target application client so that the server generates a content push list according to the user data;

Wherein the method further comprises:

Scanning the electronic code displayed by the second user terminal;

acquiring a UR L of a binding interface displayed by the second user terminal according to the electronic code, wherein the UR L of the binding interface is configured with a device identifier of the second user terminal and account information of target application software;

skipping to a binding interface provided by a target application public number according to the UR L of the binding interface to prompt a user to bind;

Responding to the binding operation of the user, and binding the identification of the target application public number and the user account information;

Generating a user identifier of the target application public number according to the target application public number identifier and the account of the social application; and

And adding the user identification of the target application public number into a binding success notice, and sending the binding success notice to the server.

10. The method of claim 9, wherein the application client associated with the wearable smart device is a public number associated with the wearable smart device on a social application platform;

The target application client is a target application public number on the social application platform;

The sending the user data to the server by the target application client comprises: and sending the user data to a server by taking the user identification of the target application public number as an identification.

11. A server, wherein the server comprises:

The sending module is used for sending the content push list to the second user terminal;

the receiving module is further used for receiving a binding request sent by the second user terminal, wherein the binding request is a UR L address configured with a device identifier of the second user terminal and account information of target application software;

The generating module is further used for generating an electronic code according to the binding request and sending the electronic code to the second user terminal for displaying;

The receiving module is further configured to receive a binding success notification sent by the first user terminal after scanning the electronic code; the binding notification is configured with a user identifier of the target application public number and account information of the target application software; and

The server further comprises: and the establishing module is used for establishing the corresponding relation between the user identification of the target application public number and the account information of the target application software.

12. A first user terminal, wherein the first user terminal comprises:

The reading module is used for reading user data collected by the wearable intelligent equipment through an application client side related to the wearable intelligent equipment and reading the user data from the application client side related to the wearable intelligent equipment through a target application client side; and

The sending module is used for sending the user data to a server through a target application client so that the server generates a content push list according to the user data;

The first user terminal further comprises: the scanning module is used for scanning an electronic code which is displayed by a second user terminal and issued by the server in response to the binding request of the second user terminal;

the binding module is used for obtaining a UR L of a binding interface displayed by the second user terminal according to the electronic code, wherein the UR L of the binding interface is configured with an equipment identifier of the second user terminal and account information of target application software;

The sending module is further configured to add the user identifier of the target application public account to a binding success notification, and send the binding success notification to the server.

13. A computer readable storage medium having computer instructions stored thereon, wherein the computer instructions, when executed by a processor, implement the steps of the method of any of claims 1 to 9.

14. A computing device comprising a memory, a processor, and a computer program stored on the memory and run on the processor; the processor, when executing the computer program, implements the method of any of claims 1-9.