WO2016202200A1 - 数据校验方法、装置和智能电视系统 - Google Patents

数据校验方法、装置和智能电视系统 Download PDF

Info

Publication number
WO2016202200A1
WO2016202200A1 PCT/CN2016/085209 CN2016085209W WO2016202200A1 WO 2016202200 A1 WO2016202200 A1 WO 2016202200A1 CN 2016085209 W CN2016085209 W CN 2016085209W WO 2016202200 A1 WO2016202200 A1 WO 2016202200A1
Authority
WO
WIPO (PCT)
Prior art keywords
client
verification
service providing
request
random
Prior art date
Application number
PCT/CN2016/085209
Other languages
English (en)
French (fr)
Inventor
陈金虎
郑勇
范雷雷
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2016202200A1 publication Critical patent/WO2016202200A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/254—Management at additional data server, e.g. shopping server, rights management server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/239—Interfacing the upstream path of the transmission network, e.g. prioritizing client content requests
    • H04N21/2393—Interfacing the upstream path of the transmission network, e.g. prioritizing client content requests involving handling client requests
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/254—Management at additional data server, e.g. shopping server, rights management server
    • H04N21/2541—Rights Management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/258—Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
    • H04N21/25808—Management of client data
    • H04N21/25816—Management of client data involving client authentication

Definitions

  • the present application relates to the field of smart television technologies, and in particular, to a data verification method, apparatus, and smart television system.
  • a digital video conversion box which can also be called a set-top box or a set-top box, is a device that connects a television to an external signal source.
  • the digital video converter box converts the compressed digital signal into television content and displays it on the television.
  • the digital signal signals can be from cable cables, satellite antennas, broadband networks, terrestrial broadcasts, and the like.
  • the digital video converter box can also receive digital content, such as television program guides, Internet web pages, emails, and the like. Enables users to watch digital TV shows on existing TV sets and interactive digital entertainment, education and online shopping through the web.
  • the digital video conversion box or smart TV.
  • the development of Internet technology is changing with each passing day. It is constantly changing and changing.
  • more and more intelligent systems also bring many security risks.
  • the digital video converter box is vulnerable to network failure. Malicious attacks on them, or malicious login by hackers, illegally obtaining user data information, the security of user data is difficult to be guaranteed; on the other hand, the update and upgrade of digital video converter boxes cannot match this development and change, and cannot be Effectively meet the service needs of end users.
  • the present application provides a data verification method, device, and smart television system to solve the security problems such as the device being vulnerable to attacks and the user data information being easily leaked when using a device such as a digital video conversion box, and digital video.
  • the transform box cannot provide at least one of the problems that meet the end user's service needs.
  • the present application discloses a data verification method, and the method includes:
  • the locally stored random identifier is pre-assigned to the client, Information for identifying the client;
  • the locally stored random token is information pre-assigned to the client for verifying the validity of the connection between the client and the service providing device assigned to the client;
  • the random token and the random identifier carried in the verification request match the corresponding information stored in the locality, it is determined that the connection between the client requested by the verification request and the service providing device is legal.
  • the present application also discloses another data verification method, and the method includes:
  • connection request for requesting a connection
  • the connection request carries a random token of the client and a random identifier of the client
  • the random token of the client is used to indicate a server verification Determining the validity of the connection between the client and the service providing device allocated to the client; the random identifier of the client is used to identify the information of the client;
  • the verification request carries a random token of the client and a random identifier of the client;
  • the present application also discloses a data verification device, the device comprising:
  • a verification request receiving module configured to receive a verification request sent by the service providing device, where the verification request is used to request to verify whether the connection between the client and the service providing device is legal, and the verification request carries Describe a random token of the client and a random identifier of the client;
  • a verification module configured to verify the random token and the random identifier carried in the verification request according to the local random token and the random identifier; wherein the locally stored random identifier is pre-assigned to the local a client, information for identifying the client; the locally stored random token is pre-assigned to the client, and used to verify the connection between the client and a service providing device assigned to the client Information on effectiveness;
  • a determining module configured to determine, when the random token and the random identifier carried in the verification request match the corresponding information stored in the locality, that the connection between the client requested by the verification request and the service providing device is legal .
  • the present application also discloses another data verification device, which includes:
  • connection request receiving module configured to receive a connection request sent by the client for requesting a connection, where the connection request carries a random token of the client and a random identifier of the client, and the random order of the client
  • the card is used to instruct the server to verify the validity of the connection between the client and the service providing device allocated to the client; the random identifier of the client is used to identify the information of the client;
  • a verification request generating module configured to generate a verification request according to the connection request, and send the generated verification request to the server, where the verification request is used to request the server to verify the connection Requesting whether the requested connection is legal, and the verification request carries a random token of the client and a random identifier of the client;
  • the validity verification module is configured to determine, according to the verification result of the verification request returned by the server, whether the connection requested by the connection request is legal.
  • the present application also discloses a smart television system, the smart television system comprising: at least one server, at least one client, at least one service providing device; wherein the server is used to the client Allocating a service providing device; the client is disposed in a smart TV, and the service providing device is disposed on a network side for providing an Internet service for establishing a connected client through a network; wherein the server includes the claims 19 to 27
  • the data verification device according to any one of the preceding claims, wherein the service providing device comprises the data verification device according to any one of claims 28-33.
  • the present application includes the following advantages:
  • the service providing device allocated to the client when receiving the connection request of the client, does not directly establish a connection with the client in response to the connection request, but information related to the connection requested by the connection request. Carrying is sent to the server in the verification request, and the validity of the connection between the client requested by the connection request and the service providing device is verified by the server comparing the information in the verification request with the corresponding information saved locally by the server.
  • the service provider device establishes a connection with the client only after the verification is passed. Through the server's legality authentication of the connection between the client and the service providing device, the security of the smart television system is ensured, thereby avoiding the access of the illegal client, improving the security of the system, and avoiding leakage of user data information.
  • the device that provides services for the terminal is implemented by the service providing device on the network side, and the terminal only needs to have a basic decoding function to obtain the service from the network side, and no longer depends on or is subject to the digital video conversion box.
  • the services provided by the network side service providing device can be updated and upgraded in time, and the end user can ensure that the latest service provided by the end user is used, and the service demand of the end user is effectively met.
  • FIG. 1 is a flow chart showing the steps of a data verification method in Embodiment 1 of the present application.
  • FIG. 2 is a flow chart showing the steps of a data verification method in Embodiment 2 of the present application.
  • Embodiment 3 is a flow chart showing the steps of a data verification method in Embodiment 3 of the present application.
  • FIG. 4 is a flow chart showing the steps of a data verification method in Embodiment 4 of the present application.
  • FIG. 5 is a structural diagram of a smart television system in Embodiment 5 of the present application.
  • FIG. 6 is a flow chart of data verification in a smart television system according to Embodiment 5 of the present application.
  • FIG. 7 is a schematic diagram of data interaction in a smart television system according to Embodiment 5 of the present application.
  • FIG. 8 is a structural block diagram of a data verification apparatus in Embodiment 6 of the present application.
  • FIG. 9 is a structural block diagram of a data verification apparatus in Embodiment 7 of the present application.
  • the resource allocation method of the embodiment of the present application can be applied to a system including a client and a service providing device, wherein the service providing device can provide various services to the client.
  • a smart television system comprising: at least one server, at least one client, at least one service providing device; wherein the server is configured to allocate a service providing device to the client; the client The terminal is disposed in the smart TV, and the service providing device is disposed on the network side, and is configured to provide an Internet service for the connected client through the network.
  • the smart television system may further include at least one user data information storage device; the at least one user data information storage device includes: at least one user partition; wherein the at least one user partition is used to store different User data corresponding to the client.
  • the service providing device includes: a network set top box; the internet service includes at least one of the following: a live television, an audio and video service, a web service, and a game service.
  • FIG. 1 a flow chart of steps of a data verification method in Embodiment 1 of the present application is shown.
  • the data verification method of this embodiment is described in the perspective of a server in the above-described smart television system architecture.
  • the data verification method in this embodiment may specifically include the following steps:
  • Step 102 Receive a verification request sent by the service providing device.
  • the verification request is used to request that the connection between the client and the service providing device is valid.
  • the verification request carries the random token of the client and the random identifier of the client.
  • Step 104 Verify the random token and the random identifier carried in the verification request according to the local random token and the random identifier.
  • the locally stored random identifier is information pre-assigned to the client for identifying the client; the locally stored random token is pre-assigned to the client for verification Information about the validity of the connection between the client and the service providing device assigned to the client.
  • the server allocates a service providing device to the client, and generates a random token, and sends the generated random token to the client.
  • the generated random token is saved locally for subsequent verification.
  • the random token generated by the server according to the request of the client requesting the service providing device is different each time, and the random token has a certain timeliness, that is, it is valid for a certain period of time. In this way, even if the random token is used after being maliciously acquired, it will be invalidated due to the set time period, thereby effectively ensuring the security of the smart television system.
  • Step 106 If the random token and the random identifier carried in the verification request match the corresponding information stored in the locality, determine that the connection between the client requested by the verification request and the service providing device is legal.
  • the service providing device allocated to the client when receiving the connection request of the client, does not directly establish a connection with the client in response to the connection request, but carries information related to the connection requested by the connection request.
  • the verification request is sent to the server, and the validity of the connection between the client requested by the connection request and the service providing device is verified by the server comparing the information in the verification request with the corresponding information stored locally by the server, and only After the verification is passed, the service provider device establishes a connection with the client.
  • the server's legality authentication of the connection between the client and the service providing device the security of the smart television system is ensured, thereby avoiding the access of the illegal client, improving the security of the system, and avoiding leakage of user data information.
  • the device that provides services for the terminal is implemented by the service providing device on the network side, and the terminal only needs to have a basic decoding function to obtain the service from the network side, and no longer depends on or is subject to the digital video conversion box.
  • the services provided by the network side service providing device can be updated and upgraded in time, and the end user can ensure that the latest service provided by the end user is used, and the service demand of the end user is effectively met.
  • This embodiment is based on the data verification scheme of the first embodiment, and further optimizes the data verification scheme of the first embodiment.
  • FIG. 2 a flow chart of steps of a data verification method in Embodiment 2 of the present application is shown.
  • the data verification method of this embodiment is still described in the perspective of a server in the above-described smart television system architecture.
  • a plurality of related information involved in the data verification process of the present embodiment is first described in the form of a step, but in actual use, the information is not limited to the generation and acquisition modes in the embodiment, and is generated.
  • the steps of obtaining the related information There is no necessary order relationship between the steps of obtaining the related information, and those skilled in the art can refer to the introduction in this embodiment, and only use part of the related information to adopt the mode of the embodiment, and other information. In other suitable manners, the embodiments of the present invention do not limit this.
  • Step 202 The server sends a random identification password corresponding to the random identifier of the client to the client, and a random identification password corresponding to the random identifier of the client is sent to the client, in response to the registration request of the client, And storing the random identifier and the random identification password locally at the server.
  • the random identifier of the client is used to identify the client
  • the random identifier stored in the server is information that is allocated to the client and used to identify the client after receiving the registration request sent by the client.
  • the locally stored random identification password is a random identification password corresponding to the random identifier assigned to the client after receiving the registration request sent by the client, and being allocated to the client.
  • the random identifier and the random identification password of the above client are generated by the server and sent to the client each time the client registers with the server. Even for the same client, the server generates a random ID and a random ID password for the client each time it is registered.
  • Step 204 The server sends, to the client, a unique identification code and/or a random number of the service providing device that is allocated to the client to provide the service to the client, and saves locally at the server, in response to the client's allocation request.
  • the service provides a unique identification code and/or a random number of the device.
  • the client's allocation request is used to request the server to allocate a service providing device to the client.
  • the unique identification code and/or random number of the service providing device stored locally is allocated to the client after being allocated the request for the service providing device by receiving the request sent by the client.
  • steps 202 and 204 above does not have a necessary sequence relationship, and also requires steps.
  • Step 206 The server receives a verification request sent by the service providing device.
  • the verification request is used to request that the connection between the client and the service providing device is valid.
  • the verification request carries the random token of the client and the random identifier of the client.
  • the server can perform basic authentication on the legality of the connection between the client and the service providing device by using the received random token of the client and the random identifier of the client.
  • the verification request may further carry the verification information of the client.
  • the verification information of the client may be sent by the client to the service providing device, and the service providing device is carried in the verification request and sent to the server.
  • the verification information of the client may be generated according to a random identification password assigned by the server to the client.
  • the verification information of the client is generated according to at least one of a random identification password assigned by the server to the client, and the following information: a unique identification code of the service providing device allocated by the server to the client and/or a random allocation of the server to the client
  • the random identification password is information that the server pre-allocates to the client and corresponds to the random identifier of the client.
  • the verification request may further carry a unique identification code of the service providing device.
  • the unique identification code may be a unique identification code saved locally by the service providing device, and is carried in the verification request and sent to the server.
  • the verification information of the client and/or the unique identification code of the service providing device Through the verification information of the client and/or the unique identification code of the service providing device, the legality and security of the connection between the client and the service providing device can be further ensured.
  • Step 208 The server verifies the random token and the random identifier carried in the verification request according to the local random token and the random identifier.
  • the locally stored random identifier is information pre-assigned to the client for identifying the client; the locally stored random token is pre-assigned to the client for verification Information about the validity of the connection between the client and the service providing device assigned to the client.
  • the server will be based on the corresponding information stored locally. Verify the verification information.
  • the server needs to perform the verification information of the client carried in the verification request and the verification information of the client stored in the server. Comparing; wherein the verification information of the locally saved client is information pre-assigned to the client.
  • the verification information of the locally saved client may be generated according to the random identification password of the client stored locally, and the locally stored random identification password is pre-assigned to the client, and the The information corresponding to the random identifier of the client.
  • the verification information of the locally saved client is according to the locally saved a random identification password of the client, and at least one of the following information: a unique identification code and/or a random number of the service providing device stored locally; wherein the locally stored random identification password is pre-allocated Information corresponding to the client and the random identifier of the client.
  • the unique identification code and/or random number of the service providing device stored locally is allocated to the client after receiving the allocation request of the service providing device by the server after receiving the request sent by the client.
  • the server needs to use the unique identification code of the service providing device carried in the verification request and the unique identifier of the service providing device stored locally. The code is compared; wherein the unique identification code of the service providing device stored locally is a unique identification code of the service providing device pre-assigned to the client and serving the client.
  • Step 210 If the random token and the random identifier carried in the verification request match the corresponding information stored locally, the server determines that the connection between the client requested by the verification request and the service providing device is legal.
  • the verification request carries only the random token of the client and the random identifier of the client
  • the random identifier carried in the verification request matches the random identifier stored in the server, and according to The random token stored in the server determines that the random token carried in the verification request is valid, and the server determines that the connection between the client requested by the verification request and the service providing device is legal.
  • the server further needs to determine whether the verification information of the client carried in the verification request matches the verification information of the client stored locally.
  • the random identifier carried in the verification request is matched with the random identifier stored in the server, and the random token carried in the verification request is determined according to the random token stored in the server, and
  • the verification information of the client carried in the verification request matches the verification information of the client stored locally, and the server determines that the connection between the client requested by the verification request and the service providing device is legal.
  • the server When the verification request further carries the unique identification code of the service providing device, the server further needs to determine that the unique identification code of the service providing device carried in the verification request is unique to the local service providing device. Whether the identification code matches, if the random identifier carried in the verification request matches the random identifier stored in the server locality, and the random token carried in the verification request is determined according to the random token stored locally at the server Valid, and if the unique identification code of the service providing device carried in the verification request matches the unique identification code of the locally provided service providing device, the server determines the client requested to verify the verification request and The connection of the service provider device is legal.
  • the verification request carries the random token of the client, the random identifier of the client, the verification information of the client, and the unique identification code of the service providing device, if the random identifier carried in the verification request Matching with the random identifier stored in the server, and determining that the random token carried in the verification request is valid according to the random token stored in the server local, and if the client of the client carried in the verification request
  • the verification information matches the verification information of the locally stored client, and if the unique identification code of the service providing device carried in the verification request matches the unique identification code of the locally provided service providing device, the server determines The connection between the client requested to verify the request and the service providing device is legal.
  • the service providing device allocated to the client when receiving the connection request of the client, does not directly establish a connection with the client in response to the connection request, but carries information related to the connection requested by the connection request.
  • the verification request is sent to the server, and the validity of the connection between the client requested by the connection request and the service providing device is verified by the server comparing the information in the verification request with the corresponding information stored locally by the server, and only After the verification is passed, the service provider device establishes a connection with the client.
  • the server's legality authentication of the connection between the client and the service providing device the security of the smart television system is ensured, thereby avoiding the access of the illegal client, improving the security of the system, and avoiding leakage of user data information.
  • the device that provides services for the terminal is implemented by the service providing device on the network side, and the terminal only needs to have a basic decoding function to obtain the service from the network side, and no longer depends on or is subject to the digital video conversion box.
  • the services provided by the network side service providing device can be updated and upgraded in time, and the end user can ensure that the latest service provided by the end user is used, and the service demand of the end user is effectively met.
  • FIG. 3 a flow chart of steps of a data verification method in Embodiment 3 of the present application is shown.
  • the data verification method of this embodiment is described in the perspective of the service providing device in the smart TV system architecture.
  • the data verification method in this embodiment may specifically include the following steps:
  • Step 302 Receive a connection request sent by the client for requesting a connection.
  • connection request carries a random token of the client and a random identifier of the client, where the random token of the client is used to instruct the server to verify the client and the service providing device allocated to the client. The validity of the connection.
  • Step 304 Generate a verification request according to the connection request, and send the generated verification request to the server.
  • the verification request is used to request the server to check whether the connection requested by the connection request is legal.
  • the verification request carries a random token of the client and a random identifier of the client.
  • Step 306 Determine, according to the verification result of the verification request returned by the server, whether the connection requested by the connection request is legal.
  • the service providing device allocated to the client when receiving the connection request of the client, does not directly establish a connection with the client in response to the connection request, but carries information related to the connection requested by the connection request.
  • the verification request is sent to the server, and the validity of the connection between the client requested by the connection request and the service providing device is verified by the server comparing the information in the verification request with the corresponding information stored locally by the server, and only After the verification is passed, the service provider device establishes a connection with the client.
  • the server's legality authentication of the connection between the client and the service providing device the security of the smart television system is ensured, thereby avoiding the access of the illegal client, improving the security of the system, and avoiding leakage of user data information.
  • the device that provides services for the terminal is implemented by the service providing device on the network side, and the terminal only needs to have a basic decoding function to obtain the service from the network side, and no longer depends on or is subject to the digital video conversion box.
  • the services provided by the network side service providing device can be updated and upgraded in time, and the end user can ensure that the latest service provided by the end user is used, and the service demand of the end user is effectively met.
  • This embodiment is based on the data verification scheme of the third embodiment, and further optimizes the data verification scheme of the third embodiment.
  • FIG. 4 a flow chart of steps of a data verification method in Embodiment 4 of the present application is shown.
  • the data verification method of this embodiment is still described in the perspective of the service providing device in the above-mentioned smart television system architecture.
  • Step 402 The service providing device receives a connection request sent by the client for requesting the connection.
  • the connection request carries a random token of the client and a random identifier of the client, where the random token of the client is used to instruct the server to verify the client and the service providing device allocated to the client.
  • the validity of the connection, the random identifier of the client is used to identify the information of the client.
  • the basic information of the connection between the client and the service providing device can be characterized by the random token of the client and the random identifier of the client.
  • the verification request may also carry the report reported by the client.
  • the verification information of the client Preferably, the verification information of the client may be generated according to the random identification password of the client. Further preferably, the verification information of the client is generated according to at least one of the random identification password of the client and the following information: a unique identification code and/or a random number of the service providing device.
  • the random identifier of the client is used to identify that the client is the information that is allocated to the client after the server receives the registration request sent by the client, and is used to identify the client; After receiving the registration request sent by the client, the server assigns a random identification password corresponding to the random identifier assigned to the client and allocated to the client.
  • the random identifier and the random identification password of the above client are generated by the server and sent to the client each time the client registers with the server. Even for the same client, the server generates a random ID and a random ID password for the client each time it is registered.
  • the client sends an allocation request to the server when it needs to request the server to allocate a service providing device to the client.
  • the server allocates a service providing device to the client according to the allocation request, and generates a unique identification code and/or a random number of the service providing device to send to the client.
  • Step 404 The service providing device generates a verification request according to the connection request, and sends the generated verification request to the server.
  • the verification request is used to request the server to check whether the connection requested by the connection request is legal.
  • the verification request carries a random token of the client and a random identifier of the client.
  • the verification request further carries a unique identification code of the service providing device locally saved by the service providing device.
  • the verification request may further carry verification information of the client reported by the client.
  • Step 406 The service providing device determines, according to the verification result of the verification request returned by the server, whether the connection requested by the connection request is legal.
  • the service providing device receives a verification result returned by the server for the verification request, where the verification The result includes: a third verification result; wherein the third verification result is used to indicate whether the current connection requested by the client is valid, and the random identifier of the client carried in the verification request is saved in Whether the random identifier of the client in the server matches; wherein the random identifier of the client stored in the server is information pre-assigned to the client for identifying the client; the service providing device is according to the third school As a result of the test, it is determined whether the connection requested by the connection request is legal.
  • the verification result of the verification request returned by the server received by the service providing device further includes: a first verification result, where the first verification result is used to indicate verification information and save of the client carried in the verification request Whether the verification information of the client in the server matches; wherein the verification information stored in the server is information pre-allocated to the client; the service providing device further needs to determine, according to the first verification result, Whether the connection requested by the connection request is legal. That is, the service providing device further needs to determine whether the connection requested by the connection request is legal according to the first and third verification results.
  • the verification result of the verification request returned by the server received by the service providing device further includes: a second verification result, where the second verification result is used to indicate a unique identification code of the service providing device carried in the verification request and a unique identification code of the service providing device stored in the server Whether the matching is performed; wherein the unique identification code of the service providing device stored in the server is a unique identification code of the service providing device pre-allocated to the client and providing the service to the client; the service providing device also needs to be based on Determining the second verification result, determining whether the connection requested by the connection request is legal. That is, the service providing device further needs to determine whether the connection requested by the connection request is legal according to the second and third verification results.
  • the service providing device needs And determining, according to the first, second, and third verification results, whether the connection requested by the connection request is legal.
  • the service providing device allocated to the client when receiving the connection request of the client, does not directly establish a connection with the client in response to the connection request, but carries information related to the connection requested by the connection request.
  • the verification request is sent to the server, and the validity of the connection between the client requested by the connection request and the service providing device is verified by the server comparing the information in the verification request with the corresponding information stored locally by the server, and only After the verification is passed, the service provider device establishes a connection with the client.
  • the server's legality authentication of the connection between the client and the service providing device the security of the smart television system is ensured, thereby avoiding the access of the illegal client, improving the security of the system, and avoiding leakage of user data information.
  • the device that provides services for the terminal is implemented by the service providing device on the network side, and the terminal only needs to have a basic decoding function to obtain the service from the network side, and no longer depends on or is subject to the digital video conversion box.
  • the services provided by the network side service providing device can be updated and upgraded in time, and the end user can ensure that the latest service provided by the end user is used, and the service demand of the end user is effectively met.
  • a smart television system may be employed: the smart television system may include at least one client, at least one dispatch server, and at least one service providing device.
  • the client is a terminal that can use the APP application provided by the service providing device, such as a set top box, a smart mobile terminal, and a PAD (Portable). Android Device tablet, smart TV with decoding function, etc.
  • the service providing device can be set as a server in the cloud to remotely provide services for the client. After receiving the request of the client to apply for the service providing device, the scheduling server may select one of the plurality of service providing devices in the cloud to allocate to the client according to the set allocation policy.
  • the service providing device can be set in the cloud as a hardware device
  • the software (application) can be installed in the service providing device
  • the service providing device can be used in the cloud to set the user interface of various applications.
  • UI User Interface
  • the client has basic decoding capability to present the user interface of the application to the user, and realize operations on various applications.
  • the software (application) may not be installed in the set top box, may be installed in the service providing device, and provide services to the user through the service providing device. . Since the software can no longer be installed in the set top box, the set top box can no longer be set separately.
  • the smart mobile terminal (or a smart TV with decoding function) can be directly connected to the service providing device, and the user does not need to The purchase/set-up of the set-top box separately saves the user's cost; at the same time, the intelligent mobile terminal (or the smart TV with decoding function) directly interacts with the service providing device, thereby improving the interaction efficiency, reducing the maintenance steps for the set-top box, and reducing the maintenance steps. The occupation of resources.
  • the scheduling server may refer to a server, or may refer to a server group composed of multiple servers equivalent to the scheduling server function.
  • the user interface displayed on the client side is capable of providing various network services for the user, for example, the user interface may include various menu options or icons, such as: high-definition video, ultra-clear television. , software downloads, games, life services (such as payment, shopping, etc.), so that through the client, users can watch HD movies and TV, play somatosensory games, popular large 3D games, online shopping, pay for water and electricity costs on TV for free. And so on. After the user selects an icon or menu of a certain function, the user can continue to enter the corresponding UI interface to perform operations, such as local or network resources when playing HD video.
  • various menu options or icons such as: high-definition video, ultra-clear television. , software downloads, games, life services (such as payment, shopping, etc.), so that through the client, users can watch HD movies and TV, play somatosensory games, popular large 3D games, online shopping, pay for water and electricity costs on TV for free. And so on.
  • the user can continue to enter
  • the user can control through the external device of the remote controller, such as selecting a certain function and entering the next level interface, and the UI interface is displayed based on the transport stream of the service providing device. Therefore, the control response to the UI interface is also performed by the service providing device.
  • the service providing device virtualizes an input device in the user space, simulates a hardware input signal through the virtual input device, and injects an input signal of the user into the system to input an event and distribute the image, thereby realizing The service provides the device's response to user control.
  • the architecture of a preferred smart television system is as shown in FIG. 5.
  • the smart television system may specifically include: at least one device server (such as the device server 501 shown in FIG. 5), at least one scheduling server (such as the scheduling server 502 shown in FIG. 3), and at least one client. End (client 503 shown in Figure 5).
  • Each device server includes at least one service providing device (such as the service providing device 304 in the device server 501 shown in FIG. 5).
  • the smart television system may further include: at least one management server (such as the management server 505 shown in FIG. 5) and at least one user data storage device (such as the user data storage device 506 shown in FIG. 5).
  • the user data storage device is used to store user data, and one user may correspond to a dedicated user data storage device, and multiple users may share the same user data storage device, which is not limited in this embodiment.
  • the user data storage device may be a physical device, a logical device, or a combination of physical and logical devices.
  • the user data storage device may include at least one user partition (such as the user partition 507 shown in FIG. 5), and each user partition correspondingly stores user data of one user.
  • the client 503 may be a hardware device as described above, such as a set top box, a smart mobile terminal, a PAD, a smart TV with a decoding function, and the like.
  • the client 503 may also be in the form of a smart TV terminal, which may be presented in the form of an APP (Application) installed in the smart TV terminal.
  • the smart TV terminal herein may specifically include: a set top box and a mobile terminal. , smart TV, etc.
  • the client 503 can be used to play a user interface parsed by a transport stream (TS) sent by the service providing device 504, and play multimedia data (such as video signals, audio signals, etc.) acquired from other network servers.
  • TS transport stream
  • the client 503 can be used to listen to an input message generated by the user through an input device such as a remote controller, and send the input message to the service providing device 504 or the dispatch server 502.
  • an input device such as a remote controller
  • the client 503 only parses and displays, and the input message controlled by the client 503 to the user interface is also forwarded to the service providing device 504 to enable It adjusts the user interface accordingly.
  • the service providing device 504 is located at the network side, and each of the service providing devices may specifically include: a software module carried by the hardware board and the hardware board. It should be noted that, in this embodiment, various types of applications may be directly installed in the service providing device, and the user may perform the application in the service providing device 504 through the user interface corresponding to the application presented by the client 503. For the operation, it is no longer necessary to separately install the application program in the client 503, so that the technician can perform unified maintenance on the smart television system, thereby reducing the workload and improving the maintenance efficiency.
  • the user partition 507 is located on the network side. Generally, each user applies a user partition, and user data of each user is saved under the corresponding user partition. Further, each user partition has a unique address information, The address information may indicate a specific address of the corresponding user partition, and the user information may be quickly found through the address information to complete the calling of the user data. In other words, the dispatch server 502 (or the management server 505) can perform maintenance only on address information (small data amount) without maintaining the entire user data (large amount of data), reducing the amount of data maintained. , reducing resource occupation, improving system running speed, and user data is easy to find.
  • the scheduling server 502 is located on the network side, and is mainly configured to allocate an idle, good-quality service providing device 504 to the client 503 according to the request message sent by the client 503.
  • the user partition corresponding to the user ID may be mounted to the The assigned service providing device 504, that is, each user partition may correspond to a unique user ID, such as user partition A corresponding to user A, etc., such that user A is at client 503 with the last assigned, After the service provider device with the number 001 is disconnected, even if the service provider device with the number 002 is connected next time, the user A can still use the user partition A, and can use data such as the previous history.
  • the management server 505 is located on the network side and can be used to manage all the service providing devices.
  • the management may include: status reporting, heartbeat management, setting attributes, obtaining attributes, network wake-up, soft restart, hard restart, etc.; visible, management
  • the server 505 can be used as a remote server to implement network wake-up of the service providing device in the wide area network by using the technical solution of the present application.
  • the service providing device adopts a reusable mechanism, that is, one service providing device serves to continue servicing another client after the client resets. That is, after the service providing device establishes a connection with the client, the two are the only corresponding interaction relationship, and when the completion of the service is disconnected, the service providing device does not have a direct correspondence with the client, but waits for the system to be It allocates other clients. Therefore, the service providing device can serve one client at a time, and if the service providing device is not used for a set length of time, it will enter a power-saving sleep state.
  • the Idle state that is, the idle state, the service providing device in the state can be directly allocated to the required client;
  • the Busy state that is, the busy state, the service providing device in this state has been connected to the client and is in the service client, and can no longer be allocated;
  • Sleep state that is, a sleep state, when a service providing device having no redundant idle state in the system can be allocated, the system can wake up the service providing device in the state and assign it to the client;
  • the Exception state that is, the exception state, in which the allocation cannot be made
  • the management state that is, the management state, indicates that the service providing device is in the server management state and cannot be allocated.
  • the resource allocation method in the smart television system is taken as an example to describe the resource allocation method in detail. In the case of no contradiction, the method can be combined with the method in the above embodiment.
  • the resource allocation method described in this embodiment will be specifically described below.
  • the data verification method includes:
  • Step 602 The scheduling server determines that the client is legal according to the request information that is sent by the client for requesting the service providing device.
  • the client that requests the service providing device from the scheduling server may be the client that has already completed the registration. If the client is still not registered, the registration of the client may be completed by the following steps: Step 616, The scheduling server receives the registration request sent by the client, randomly assigns a random identifier and a random identification password to the client, and performs the assigned random identifier and the random identifier password as the second random identifier and the second random identifier password. save.
  • the random identification password may be an identification password randomly assigned by the scheduling server to the client when the client registers, and may be used for identifying the client and/or verifying the validity of the client.
  • Step 618 The scheduling server sends the assigned random identifier and the random identifier password to the client, and the first random identifier and the first random identifier password are saved in the client for legality authentication of the client.
  • the client requesting the service providing device from the scheduling server may also be an unregistered client.
  • the scheduling server may be the client.
  • steps 616 and 618 may be performed before the step 602 above, or may be performed after receiving the re-registration request of the user after the step 602.
  • the scheduling server may further allocate a user data partition to the client, where the user data partition uniquely corresponds to the client, and may be used to store the client. Corresponding user data information.
  • a correspondence between the random identifier and the user data partition may be established, and the corresponding user data partition may be quickly found by using the random identifier, thereby improving data processing efficiency.
  • a person skilled in the art can determine whether the client is legal in any suitable manner.
  • a feasible way to determine the validity of the client may be as follows: the scheduling server determines the scheduling server Whether there is a second random identifier that matches the first random identifier carried in the request information; if yes, it is determined that the client is legal.
  • the third verification carried in the request information may be further verified. Whether the information matches the fourth verification information in the scheduling server, specifically: the scheduling server determines whether the third verification information carried in the request information reported by the client is compared with the fourth verification information in the scheduling server. Matching; if the third verification information matches the fourth verification information, determining that the client is legal.
  • the third verification information may be verification information generated by the client according to the first random identifier and/or the first random identifier password according to a third setting rule, and carried in the request information.
  • the fourth verification information may be generated by the scheduling server according to the second random identifier and/or the second random identification password according to a fourth setting rule.
  • the third setting rule and the fourth setting rule are the same setting rule; the first second here is only for convenience of description and does not play any limiting role.
  • the third verification information may be generated according to the third setting encryption algorithm according to at least one of the first random identifier, the first random identifier password, the device address of the client, and the timestamp.
  • the scheduling server may be configured according to the second random identifier, the second random identifier password, the received device address sent by the client, and the received timestamp sent by the client.
  • At least one of the fourth verification information is generated according to a fourth setting encryption algorithm.
  • the third setting encryption algorithm is the same as the fourth setting encryption algorithm.
  • the client when the scheduling server registers with the client, the client is assigned a random identifier Key and a random identifier password Secret.
  • the random identifier and the random identification password sent and stored in the client are respectively recorded as Key1 and Srcret1, and the random identifier and the random identification password stored in the dispatch server are respectively recorded as Key2 and Secret2.
  • the time Time corresponding to when the client sends the request information may be used as the timestamp; the timestamp stored in the client is recorded as Time1; the request information is separately sent to the scheduling server and saved in the scheduling server.
  • the timestamp is recorded as Time2.
  • the client may carry its own device information, a Mac address (Media Access Control address, hardware address), in the request information or directly and independently to the dispatching server, where the device information saved in the client is recorded as Mac1, the device information received and saved by the dispatch server is recorded as Mac2.
  • a Mac address Media Access Control address, hardware address
  • Step 604 The scheduling server allocates a service providing device to the client determined to be legal, acquires device information of the allocated service providing device, and generates a random token that satisfies the set aging.
  • the service providing device may be allocated to the client in a feasible manner: the scheduling server acquires the information of the client from the request information, determines the terminal type of the client according to the information, and then determines the terminal type of the client, and then Selecting a service providing device to allocate the client from a distributed queue matching the determined terminal type; and matching the selected service providing device to the client before assigning the selected service providing device to the client Obtaining user data in the user data partition; notifying the selected service providing device to perform initial configuration according to the acquired user data, and then assigning the service providing device that successfully initializes the configuration to the client.
  • the device information of the service providing device acquired by the scheduling server and the generated random token may be used for verification of the legality of the connection between the client and the service providing device.
  • the scheduling server may save the acquired device information of the service providing device and the generated random token as the second device information and the second random token, respectively; and send the acquired device information and the generated random token.
  • the first device information and the first random token are respectively saved in the client, and the client may generate, according to the first device information and/or the first random token, a request for performing with the service providing device. Connected connection request.
  • the device information of the service providing device acquired by the scheduling server includes, but is not limited to, an IP address of the service providing device, a port address of the service providing device, a UUID of the service providing device, a version number and a version of the service providing device. Describe application information and so on.
  • the scheduling server sends the acquired device information of the service providing device to the client, and the client may provide device information of the device according to the received service (the IP address of the service providing device, the port address of the service providing device, and the service providing device)
  • the UUID, the version number of the service providing device, and the application information, etc.) request to establish a connection with the service providing device.
  • the client does not establish a formal connection with the service providing device, that is, the service providing device cannot provide the service to the client normally, and the connection request sent by the client needs to be verified for legality.
  • the service providing device establishes a formal connection with the client and provides a service for the client.
  • the service providing device may generate a verification request according to the device information of the service providing device, the random token, and the connection request, to request verification of the client. Whether the connection between the terminal and the service providing device is legal.
  • Step 606 The scheduling server receives the request for verifying the client and the service providing device that is reported by the service providing device. Whether the backup connection is a valid verification request.
  • Step 608 The scheduling server acquires the second verification information and the first verification information carried in the verification request.
  • the second verification information may be generated by the scheduling server according to the second setting rule according to the second device information and/or the second random identification password stored in the scheduling server;
  • the verification information may be generated by the client according to the first setting rule according to the first device information and/or the first random identification password stored in the client.
  • the first verification information may be generated by the client by using a first setting rule according to: a first unique identification code UUID1, the first random identification password Secret1, and a random number in the first device information.
  • Step 610 The scheduling server determines, according to the comparison result of the first verification information and the second verification information, whether the connection between the client requested by the verification request and the service providing device is legal.
  • the service providing device may generate the verification request according to the third device information, the third random token, and the third random identifier.
  • the third device information, the third random token, and the third random identifier may be the first device information, the first random token, and the first one that are sent in the connection request and are saved in the client. Random identification.
  • the first device information carried in the connection request sent by the client to the service providing device may be used as the third device information; the client will be sent to the service.
  • the first device information, the first random token, and the first random identifier may be actively reported by the client to the service providing device, as the third device information, the third random token, and the third Three random identifiers.
  • the client may send the first device information, the first random token, and the first random identifier directly to the service providing device after receiving the obtaining request of the service providing device, which is used in this embodiment. No restrictions.
  • the following steps may be performed:
  • Step 612 The scheduling server determines whether the third device information carried in the verification request matches the second device information, and determines a third random token carried in the verification request and the second random Whether the tokens match, the first judgment result is obtained; and determining, according to the first judgment result, whether the connection between the client requested by the verification request and the service providing device is legal.
  • the unique identifier code UUID in the device information is used as an example, if the third unique identifier code UUID3 in the third device information matches the second unique identifier code UUID2 in the second device information, and the third random order The card Token3 matches the second random token Token2, and then determines that the connection between the client requested by the verification request and the service providing device is legal.
  • the random token has timeliness. If the set time interval is exceeded, the random token will be invalid, and the validity of the connection for the connection between the client and the service providing device cannot be determined. . If the random token has expired during the verification of the legality of the connection between the client and the service providing device, the connection between the client and the service providing device may be directly determined to be invalid (the random token exceeds the time limit identifier, possibly It has been maliciously obtained), or the dispatch server regenerates a random token and then uses the newly generated random token for verification.
  • the following steps may be performed:
  • Step 614 The scheduling server determines whether the third random identifier carried in the verification request matches the second random identifier, and obtains a second determination result; and determines, according to the second determination result, that the verification request is requested Is the connection between the client and the service provider device legal?
  • the third random identifier Key3 matches the second random identifier Key2, it is determined whether the connection between the client requested by the verification request and the service providing device is legal.
  • the verification request is one of the implementation schemes of whether the connection between the client requested by the verification and the service providing device box is legal. A person skilled in the art can select at least one according to actual conditions to judge the legality of the connection between the client and the service providing device.
  • the smart television system in this example includes at least a client, a service providing device, and a server (eg, Can be a scheduling server).
  • the interaction process can include:
  • Step S10 The client sends a registration request to the server, where the registration request carries at least the MAC address information of the client.
  • Step S20 The server receives the registration request of the client, generates a pair of key/secret (ie, the random identifier and the random identification password of the client) for the client, and records the correspondence between the client information and the key/secret in the database.
  • a pair of key/secret ie, the random identifier and the random identification password of the client
  • the client Each time the client registers, it will generate different key/secret (even if the information carried in the registration request is the same), so that even if the hacker or illegal user simulates someone else's client to register, the client's key/secret is not obtained, which is convenient.
  • the server determines that it is a different or illegal client.
  • Step S30 The server sends the key/secret to the client.
  • Step S40 The client saves the key/secret returned by the server, and saves it as key1/secret1.
  • Step S50 The client generates sign1 (for verifying whether the client is legal) according to key1, secret1, mac1 (that is, the locally saved mac address), and time1 (that is, the locally generated timestamp).
  • sign1 for verifying whether the client is legal
  • key1, secret1, mac1 that is, the locally saved mac address
  • time1 that is, the locally generated timestamp
  • Step S60 The client sends request information to the server, where the request information carries key1, mac1, sign1, and time1.
  • Step S70 The server receives the request information sent by the client, and verifies whether the key1 exists locally in the server.
  • the request information is considered to be an illegal request.
  • step S80 If it exists, use the key1 to find the corresponding secret and mac saved in the server, and find the secret and mac as secret2 and mac2; verify whether sign1 and sign2 are consistent, where sign2 is determined by the server according to key1, mac2, secret2 and time1 , generated by the same algorithm as the client generates sign1. If sign1 and sign2 do not match, it is determined that the request information is an illegal request; if sign1 and sign2 are consistent, step S80 is performed.
  • Step S80 The server selects an idle service providing device for the client (the UUID of the service providing device is recorded as UUID1).
  • Step S90 The server allocates the selected service providing device to the client, and generates a token1, a random number random1, and a salt1 for the client.
  • token1 is a string of random strings, which can be about 32 bits in length but not limited to 32 bits.
  • a certain algorithm, such as md5, encrypts a string to generate a value of salt: Salt MD5(secret+uuid1+random1) is stored in the server and recorded as salt1; the server records the correspondence between key1, uuid1, token1, and salt1, and is not permanently saved (for example, it will expire after a certain period of time, such as more than 5 minutes). ).
  • Step S100 The server returns uuid1, token1, random1, and the IP address of the service providing device and the PORT to the client.
  • the server is configured to allocate a service providing device for the client.
  • Step S110 The client generates the salt2 by using the same algorithm as the server.
  • the client saves the received token1 locally and records it as token2.
  • Step S120 The client sends a connection request to the service providing device, where the connection request carries token2, key2, and salt2.
  • Step S130 The service providing device receives the connection request, obtains corresponding information therefrom, and determines whether to request the server to determine whether the connection requested by the connection request is legal.
  • Step S140 The service providing device sends a verification request to the server, where the verification request carries the token2, the key2, the salt2, and the uuid of the service providing device itself.
  • Step S150 The server verifies whether the connection requested by the connection request is legal.
  • the server verifies the locally saved key1, uuid1, token1, and salt1, and is consistent with the key2, uuid, token2, and salt2; if not, the connection requested by the connection request is considered illegal; if they are consistent, the connection request is considered The requested connection is legal.
  • Step S160 The server returns the verification result to the service providing device.
  • the server verifies the validity of the connection between the client and the service providing device.
  • Step S170 If the service providing device determines that the connection requested by the connection request is legal according to the verification result, establish a connection with the client, and send a ts stream to the client; otherwise, disconnect the client.
  • the scheduling server in the smart television system receives a verification request reported by the service providing device for requesting verification of whether the connection between the client and the service providing device is legal;
  • the comparison result of the first verification information and the second verification information determines whether the connection between the client requested by the verification request and the service providing device is legal. It can be seen that, in this embodiment, before the client and the service providing device are connected, The validity of the connection between the client and the service providing device needs to be determined by the scheduling server.
  • the client When the connection between the client and the service providing device is legal, the client establishes a formal connection with the service providing device, and the scheduling server And the service providing device provides services for the client, ensures the security of the smart television system, thereby avoiding the access of the illegal client, improving the security of the system, and avoiding leakage of user data information.
  • the present embodiment implements the function of providing services for the client by the service providing device, and can perform maintenance on the service providing device (such as software update or hardware upgrade) in the cloud, thereby avoiding manual update operation by the user, and saving User time reduces user costs.
  • the scheduling server may first determine the validity of the client after receiving the verification request, and after determining that the client is legal, the client may send a connection request to the service providing device, further improving the smart television system. safety.
  • the smart TV can be directly provided by the service providing device, and the set-top box is no longer required to be separately set, thereby reducing the maintenance steps of the user on the set-top box. , reducing the occupation of resources while saving user costs.
  • the smart TV with basic decoding function is more independent than the traditional set top box, and the malicious program is difficult to implement the attack on the smart TV with the basic decoding function through the network, and the system is more secure.
  • the embodiment of the present invention further provides a data verification device.
  • the server in the smart television system described in the foregoing embodiment may include the data verification device, that is, the data verification device may be used to implement the foregoing.
  • Method embodiments therefore, the features in the above method embodiments can be applied to the embodiment.
  • the data verification device may specifically include:
  • the verification request receiving module 702 is configured to receive a verification request sent by the service providing device.
  • the verification request is used to request whether the connection between the client and the service providing device is valid.
  • the verification request carries the random token of the client and the random identifier of the client.
  • the verification module 704 is configured to verify the random token and the random identifier carried in the verification request according to the local random token and the random identifier.
  • the locally stored random identifier is information that is pre-assigned to the client for identifying the client; the locally stored random token is pre-assigned to the client, Information for verifying the validity of the connection between the client and the service providing device assigned to the client.
  • a determining module 706, configured to store the random token and the random identifier carried in the verification request and save the local When the corresponding information is matched, it is determined that the connection between the client requested by the verification request and the service providing device is legal.
  • the determining module 606 may be configured to: the random identifier carried in the verification request matches the random identifier stored locally, and according to the random order saved locally When the card determines that the random token carried in the verification request is valid, it determines that the connection between the client requested by the verification request and the service providing device is legal.
  • the verification request may further carry the verification information of the client.
  • the device may further include: a first comparison module, configured to compare the verification information of the client carried in the verification request with the verification information of the client stored locally; wherein the saving The verification information of the local client is information pre-allocated to the client; and when the verification information of the client carried in the verification request matches the verification information of the client stored locally, determining the The connection between the client requesting verification and the service providing device is valid.
  • the verification information of the locally saved client is generated according to the random identification password of the client stored locally; wherein the locally stored random identification password is pre-assigned to the client, and Information corresponding to the random identifier of the client.
  • the verification information of the locally saved client is generated according to at least one of a random identification password of the client stored locally, and the following information: a unique identifier of the service providing device saved locally a code and/or a random number; wherein the locally stored random identification password is information pre-assigned to the client and corresponding to the random identifier of the client.
  • the verification request may further carry a unique identification code of the service providing device.
  • the apparatus may further include: a second comparison module, configured to compare the unique identification code of the service providing device carried in the verification request with a unique identification code of the service providing device stored locally;
  • the unique identification code of the service providing device stored locally is a unique identification code of the service providing device pre-allocated to the client and providing the service to the client; and the service carried in the verification request.
  • the locally stored random identifier may be information that is allocated to the client and used to identify the client after receiving the registration request sent by the client.
  • the device may further include: a first response module, configured to send, to the client, a random identifier that is allocated to the client for identifying the client, in response to the registration request of the client.
  • the locally stored random identification password is a random identifier assigned to the client after receiving the registration request sent by the client, and being allocated to the client.
  • Corresponding Machine identification password may further include: a second response module, configured to respond to the registration request of the client, to assign a random identifier to the client, to identify the client, and correspond to a random identifier of the client The random identification password is sent to the client.
  • the unique identification code and/or random number of the service providing device stored locally may be an allocation request for allocating a service providing device to the request sent by the client. a unique identification code and/or a random number of the service providing device that is assigned to the client and provides the service to the client; wherein the allocation request carries a pre-allocation to the client for identifying the location The random identifier of the client.
  • the apparatus may further include: a third response module, configured to send, to the allocation request, a unique identification code and/or a random number of the service providing device allocated to the client to serve the client The client.
  • the service providing device allocated to the client when receiving the connection request of the client, does not directly establish a connection with the client in response to the connection request, but carries information related to the connection requested by the connection request.
  • the verification request is sent to the server, and the validity of the connection between the client requested by the connection request and the service providing device is verified by the server comparing the information in the verification request with the corresponding information stored locally by the server, and only After the verification is passed, the service provider device establishes a connection with the client.
  • the server's legality authentication of the connection between the client and the service providing device the security of the smart television system is ensured, thereby avoiding the access of the illegal client, improving the security of the system, and avoiding leakage of user data information.
  • the device that provides services for the terminal is implemented by the service providing device on the network side, and the terminal only needs to have a basic decoding function to obtain the service from the network side, and no longer depends on or is subject to the digital video conversion box.
  • the services provided by the network side service providing device can be updated and upgraded in time, and the end user can ensure that the latest service provided by the end user is used, and the service demand of the end user is effectively met.
  • the embodiment of the present invention further provides a data verification device, where the service providing device in the smart television system described in the foregoing embodiment may include the data verification device, that is, the data verification device may be used for
  • the data verification device may be used for
  • the data verification device may specifically include:
  • the connection request receiving module 802 is configured to receive a connection request sent by the client for requesting the connection.
  • the connection request carries a random token of the client and a random identifier of the client, where the random token of the client is used to instruct the server to verify the client and allocate to the client.
  • the service of the end provides the connection validity of the device; the random identifier of the client is used to identify the information of the client.
  • the verification request generating module 804 is configured to generate a verification request according to the connection request, and send the generated verification request to the server.
  • the verification request is used to request the server to verify whether the connection requested by the connection request is legal, and the verification request carries the random token of the client and the client. Random identification.
  • the validity verification module 806 is configured to determine, according to the verification result of the verification request returned by the server, whether the connection requested by the connection request is legal.
  • the verification request may further carry the verification information of the client reported by the client.
  • the validity verification module 706 is specifically configured to receive a verification result of the verification request returned by the server, where the verification result may include: a first verification result, where The first verification result is used to indicate whether the verification information of the client carried in the verification request matches the verification information of the client stored in the server; wherein the verification is saved in the server The information is information pre-assigned to the client; and, based on the first verification result, determining whether the connection requested by the connection request is legal.
  • the verification information of the client may be generated according to the random identification password of the client.
  • the verification information of the client may be generated according to at least one of a random identification password of the client and the following information: a unique identification code and/or a random number of the service providing device.
  • the verification request may further carry a locally stored unique identification code of the service providing device.
  • the validity verification module 706 is specifically configured to receive a verification result of the verification request returned by the server.
  • the verification result includes: a second verification result, where the second verification result is used to indicate that the unique identification code of the service providing device carried in the verification request is saved in a server. Whether the unique identification code of the service providing device matches; wherein the unique identification code of the service providing device stored in the server is a unique identifier of the service providing device pre-allocated to the client and providing the service for the client And determining, according to the second verification result, whether the connection requested by the connection request is legal.
  • the validity verification module 706 is specifically configured to receive a verification result of the verification request returned by the server, where the verification result includes: a result of the verification; wherein the third verification result is used to indicate whether the current connection requested by the client is valid, and the random identifier of the client carried in the verification request is saved by the client stored in the server Whether the random identifier matches; wherein the random identifier of the client stored in the server is information pre-assigned to the client for identifying the client; and, according to the third verification result, determining the Whether the connection requested by the connection request is legal.
  • the service providing device allocated to the client when receiving the connection request of the client, does not directly establish a connection with the client in response to the connection request, but carries information related to the connection requested by the connection request.
  • the verification request is sent to the server, and the validity of the connection between the client requested by the connection request and the service providing device is verified by the server comparing the information in the verification request with the corresponding information stored locally by the server, and only After the verification is passed, the service provider device establishes a connection with the client.
  • the server's legality authentication of the connection between the client and the service providing device the security of the smart television system is ensured, thereby avoiding the access of the illegal client, improving the security of the system, and avoiding leakage of user data information.
  • the device that provides services for the terminal is implemented by the service providing device on the network side, and the terminal only needs to have a basic decoding function to obtain the service from the network side, and no longer depends on or is subject to the digital video conversion box.
  • the services provided by the network side service providing device can be updated and upgraded in time, and the end user can ensure that the latest service provided by the end user is used, and the service demand of the end user is effectively met.
  • the embodiment of the invention further discloses a smart television system, comprising: at least one server, at least one client, at least one service providing device; wherein the server is configured to allocate a service providing device to the client; the client The terminal is disposed in the smart TV, and the service providing device is disposed on the network side, and is configured to provide an Internet service for the established client through the network;
  • the server may include the data verification device according to the sixth embodiment, and the service providing device may include the data verification device according to the seventh embodiment.
  • the system further includes: one less user data information storage device; the at least one user data information storage device includes: at least one user partition; wherein the at least one user partition is respectively configured to store user data corresponding to different clients .
  • the service providing device includes: a network set top box; the internet service includes at least one of the following: a live television, an audio and video service, a web service, and a game service.
  • the smart television system is basically the same as the system described in FIG. 5 above, and therefore will not be described again.
  • This application can be used in a variety of general purpose or special purpose computing system environments or configurations.
  • the application can be described in the general context of computer-executable instructions executed by a computer, such as a program module.
  • program modules include routines, programs, objects, components, data structures, and the like that perform particular tasks or implement particular abstract data types.
  • the present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are connected through a communication network.
  • program modules can be located in both local and remote computer storage media including storage devices.
  • a component can be, but is not limited to being, a process running on a processor, a processor, an object, an executable component, a thread of execution, a program, and/or a computer.
  • an application or script running on a server, or a server can be a component.
  • One or more components can be executed in a process and/or thread, and the components can be localized on a single computer and/or distributed between two or more computers and can be run by various computer readable media. .
  • the component may also pass signals based on data having one or more data packets, for example, from a signal interacting with another component in the local system, the distributed system, and/or interacting with other systems over the network of the Internet. Local and/or remote processes to communicate.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Graphics (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

本申请提供了一种数据校验方法、装置和智能电视系统。其中，所述数据校验方法接收服务提供设备发送的校验请求，其中，所述校验请求用于请求校验客户端与服务提供设备的连接是否合法，所述校验请求中携带有所述客户端的随机令牌和所述客户端的随机标识；根据保存在本地的随机令牌和随机标识，对所述校验请求中携带的随机令牌和随机标识进行验证；若所述校验请求中携带的随机令牌和随机标识与保存在本地的对应信息匹配，则确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。通过本申请，保证了智能电视系统的安全性。

Description

数据校验方法、装置和智能电视系统
本申请要求2015年06月17日递交的申请号为201510338173.9、发明名称为“数据校验方法、装置和智能电视系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及智能电视技术领域，具体涉及一种数据校验方法、装置和智能电视系统。
背景技术
随着互联网技术的发展，智能电视、数字视频变换盒的出现，使得电视节目系统也越来越智能化，除了传统的电视节目的播出之外，还可以进行互联网活动。
以数字视频变换盒为例，数字视频变换盒(Set Top Box，简称STB)，通常也可以称作机顶盒或机上盒，是一个连接电视机与外部信号源的设备。数字视频变换盒可以将压缩的数字信号转成电视内容，并在电视机上显示出来。所述数字信号信号可以来自有线电缆、卫星天线、宽带网络以及地面广播等等。数字视频变换盒除了可以接收上述可以转换为电视内容的数字信号之外，还可以接收数字内容，例如，电视节目指南、因特网网页、电子邮件等等。使用户能在现有电视机上观看数字电视节目，并可以通过网络进行交互式数字化娱乐、教育和网络购物等活动。
由上可见，上述数字电视节目的播出、交互式数字化娱乐、教育和网络购物等活动都需要通过所述数字视频变换盒(或智能电视)实现。而互联网技术的发展是日新月异的、是不断地在更新变化的，一方面，越来越智能化的系统也带来的了诸多安全隐患，例如，所述数字视频变换盒很容易遭到来自网络上的恶意攻击，或者被黑客恶意登录，非法获取用户数据信息，用户数据的安全性难以得到保障；另一方面，数字视频变换盒的更新和升级也无法与这一发展和变化相匹配，无法有效满足终端用户的服务需求。
发明内容
本申请提供了一种数据校验方法、装置和智能电视系统，以解决目前在使用数字视频变换盒等设备时，设备容易遭到攻击、用户数据信息易泄露等安全性问题，以及，数字视频变换盒无法提供满足终端用户的服务需求的问题中的至少一个。
为了解决上述问题，本申请公开了一种数据校验方法，所述方法包括：
接收服务提供设备发送的校验请求，其中，所述校验请求用于请求校验客户端与服务提供设备的连接是否合法，所述校验请求中携带有所述客户端的随机令牌和所述客户端的随机标识；
根据保存在本地的随机令牌和随机标识，对所述校验请求中携带的随机令牌和随机标识进行验证；其中，所述保存在本地的随机标识为预先分配给所述客户端、用于标识所述客户端的信息；所述保存在本地的随机令牌为预先分配给所述客户端、用于验证所述客户端与分配给所述客户端的服务提供设备的连接有效性的信息；
若所述校验请求中携带的随机令牌和随机标识与保存在本地的对应信息匹配，则确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
为了解决上述问题，本申请还公开了另一种数据校验方法，所述方法包括：
接收客户端发送的用于请求连接的连接请求，其中，所述连接请求中携带有所述客户端的随机令牌和所述客户端的随机标识，所述客户端的随机令牌用于指示服务器验证所述客户端与分配给所述客户端的服务提供设备的连接有效性；所述客户端的随机标识用于标识所述客户端的信息；
根据所述连接请求生成校验请求，并向所述服务器发送生成的所述校验请求，其中，所述校验请求用于请求所述服务器校验所述连接请求所请求的连接是否合法，所述校验请求中携带有所述客户端的随机令牌和所述客户端的随机标识；
根据所述服务器返回的对所述校验请求的校验结果，确定所述连接请求所请求的连接是否合法。
为了解决上述问题，本申请还公开了一种数据校验装置，所述装置包括：
校验请求接收模块，用于接收服务提供设备发送的校验请求，其中，所述校验请求用于请求校验客户端与服务提供设备的连接是否合法，所述校验请求中携带有所述客户端的随机令牌和所述客户端的随机标识；
验证模块，用于根据保存在本地的随机令牌和随机标识，对所述校验请求中携带的随机令牌和随机标识进行验证；其中，所述保存在本地的随机标识为预先分配给所述客户端、用于标识所述客户端的信息；所述保存在本地的随机令牌为预先分配给所述客户端、用于验证所述客户端与分配给所述客户端的服务提供设备的连接有效性的信息；
确定模块，用于在所述校验请求中携带的随机令牌和随机标识与保存在本地的对应信息匹配时，确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
为了解决上述问题，本申请还公开了另一种数据校验装置，所述装置包括：
连接请求接收模块，用于接收客户端发送的用于请求连接的连接请求，其中，所述连接请求中携带有所述客户端的随机令牌和所述客户端的随机标识，所述客户端的随机令牌用于指示服务器验证所述客户端与分配给所述客户端的服务提供设备的连接有效性；所述客户端的随机标识用于标识所述客户端的信息；
校验请求生成模块，用于根据所述连接请求生成校验请求，并向所述服务器发送生成的所述校验请求，其中，所述校验请求用于请求所述服务器校验所述连接请求所请求的连接是否合法，所述校验请求中携带有所述客户端的随机令牌和所述客户端的随机标识；
合法性验证模块，用于根据所述服务器返回的对所述校验请求的校验结果，确定所述连接请求所请求的连接是否合法。
为了解决上述问题，本申请还公开了一种智能电视系统，所述智能电视系统包括：至少一个服务器、至少一个客户端、至少一个服务提供设备；其中，所述服务器用于向所述客户端分配服务提供设备；所述客户端设置在智能电视中，所述服务提供设备设置在网络侧，用于通过网络为建立连接的客户端提供互联网服务；其中，所述服务器包括权利要求19至27任一项所述的数据校验装置，所述服务提供设备包括权利要求28-33任一项所述的数据校验装置。
与现有技术相比，本申请包括以下优点：
在本申请实施例中，分配给客户端的服务提供设备在接收到客户端的连接请求时，并不直接响应该连接请求与客户端建立连接，而是将与该连接请求所请求的连接有关的信息携带在校验请求中发送给服务器，通过服务器比对校验请求中的信息和服务器本地保存的对应信息，对所述连接请求所请求的客户端与服务提供设备之间的连接进行合法性验证，只有验证通过后，服务提供设备才与客户端建立连接。通过服务器对客户端与服务提供设备的连接的合法性认证，保证了智能电视系统的安全性，进而避免了非法客户端的接入，提高了系统的安全性，避免了用户数据信息的泄露。
此外，为终端提供服务的设备由网络侧的服务提供设备实现，终端只需具有基本的解码功能，即可从网络侧获取服务，不再依赖或受制于数字视频变换盒。网络侧服务提供设备所提供的服务能够及时进行更新和升级，可以保证终端用户使用到当前提供的最新的服务，有效满足了终端用户的服务需求。
附图说明
图1是本申请实施例一中一种数据校验方法的步骤流程图；
图2是本申请实施例二中一种数据校验方法的步骤流程图；
图3是本申请实施例三中一种数据校验方法的步骤流程图；
图4是本申请实施例四中一种数据校验方法的步骤流程图；
图5是本申请实施例五中的一种智能电视系统的架构图；
图6是本申请实施例五中一种智能电视系统中的数据校验的流程图；
图7是本申请实施例五中的一种智能电视系统中的数据交互的示意图；
图8是本申请实施例六中一种数据校验装置的结构框图；
图9是本申请实施例七中一种数据校验装置的结构框图。
具体实施方式
为使本申请的上述目的、特征和优点能够更加明显易懂，下面结合附图和具体实施方式对本申请作进一步详细的说明。
本申请实施例的资源分配方法可以应用于包括客户端以及服务提供设备的系统中，其中，服务提供设备可以向客户端提供各类服务。例如，智能电视系统；其中，所述智能电视系统包括：至少一个服务器、至少一个客户端、至少一个服务提供设备；其中，所述服务器用于向所述客户端分配服务提供设备；所述客户端设置在智能电视中，所述服务提供设备设置在网络侧，用于通过网络为建立连接的客户端提供互联网服务。
可选地，所述智能电视系统，还可以包括至少一个用户数据信息存储设备；所述至少一个用户数据信息存储设备包括：至少一个用户分区；其中，所述至少一个用户分区分别用于存储不同客户端对应的用户数据。
可选地，所述服务提供设备包括：网络机顶盒；所述互联网服务，包括如下中的至少一个：电视直播、音视频服务、网页服务、游戏服务。
以下，基于上述智能电视系统架构，对本申请实施例中的设备连接方案进行说明。但本领域技术人员应当明了，在实际使用中，本领域技术人员根据实际需要，依照上述智能电视系统架构所做的等同替换或容易想到的改变，均在本发明的保护范围内。
实施例一
参照图1，示出了本申请实施例一中一种数据校验方法的步骤流程图。
在本实施例中，以上述智能电视系统架构中的服务器的角度，对本实施例的数据校验方法进行说明。本实施例的数据校验方法具体可以包括如下步骤：
步骤102，接收服务提供设备发送的校验请求。
其中，所述校验请求用于请求校验客户端与服务提供设备的连接是否合法，所述校验请求中携带有所述客户端的随机令牌和所述客户端的随机标识。
步骤104，根据保存在本地的随机令牌和随机标识，对所述校验请求中携带的随机令牌和随机标识进行验证。
其中，所述保存在本地的随机标识为预先分配给所述客户端、用于标识所述客户端的信息；所述保存在本地的随机令牌为预先分配给所述客户端、用于验证所述客户端与分配给所述客户端的服务提供设备的连接有效性的信息。
为了保证连接的安全，服务器在收到客户端请求服务提供设备的请求后，会为该客户端分配服务提供设备，同时生成一个随机令牌，一方面将生成的随机令牌发送给客户端，一方面将生成的随机令牌保存在本地，以便后续验证使用。服务器根据客户端请求服务提供设备的请求生成的随机令牌每次都不相同，该随机令牌具有一定的时效性，也即，在一定时间段内有效。这样，即使该随机令牌被恶意获取后使用，也会因为过了设定时间段而失效，从而有效保证智能电视系统的安全性。
步骤106，若所述校验请求中携带的随机令牌和随机标识与保存在本地的对应信息匹配，则确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
通过本实施例，分配给客户端的服务提供设备在接收到客户端的连接请求时，并不直接响应该连接请求与客户端建立连接，而是将与该连接请求所请求的连接有关的信息携带在校验请求中发送给服务器，通过服务器比对校验请求中的信息和服务器本地保存的对应信息，对所述连接请求所请求的客户端与服务提供设备之间的连接进行合法性验证，只有验证通过后，服务提供设备才与客户端建立连接。通过服务器对客户端与服务提供设备的连接的合法性认证，保证了智能电视系统的安全性，进而避免了非法客户端的接入，提高了系统的安全性，避免了用户数据信息的泄露。
此外，为终端提供服务的设备由网络侧的服务提供设备实现，终端只需具有基本的解码功能，即可从网络侧获取服务，不再依赖或受制于数字视频变换盒。网络侧服务提供设备所提供的服务能够及时进行更新和升级，可以保证终端用户使用到当前提供的最新的服务，有效满足了终端用户的服务需求。
实施例二
本实施例基于上述实施例一的数据校验方案，并对实施例一的数据校验方案进行了进一步的优化。
参照图2，示出了本申请实施例二中一种数据校验方法的步骤流程图。
在本实施例中，仍以上述智能电视系统架构中的服务器的角度，对本实施例的数据校验方法进行说明。本实施例中，首先以步骤的形式对本实施例的数据校验过程中涉及到的多个相关信息进行说明，但在实际使用中，这些信息不限于本实施例中的生成和获取方式，生成和获取这些相关信息的步骤之间也没有必然的顺序关系，而且，本领域技术人员可以参照本实施例中的介绍，仅对这些相关信息中的部分信息采用本实施例的方式，而其它信息采用其它适当方式，本发明实施例对此不作限制。
本实施例的数据校验方法具体可以包括如下步骤：
步骤202：服务器响应于客户端的注册请求，将分配给所述客户端、用于标识所述客户端的随机标识，以及，与所述客户端的随机标识对应的随机标识密码发送给所述客户端，并且在服务器本地保存所述随机标识和所述随机标识密码。
可见，客户端的随机标识用于标识所述客户端，保存在服务器本地的随机标识为在接收到所述客户端发送的注册请求后、分配给所述客户端、用于标识所述客户端的信息；所述保存在本地的随机标识密码为在接收到所述客户端发送的注册请求后、分配给所述客户端、且与分配给所述客户端的随机标识对应的随机标识密码。
上述客户端的随机标识和随机标识密码在客户端每次向服务器注册时，由服务器生成并发送给客户端。即使对于同一个客户端，每次注册时服务器生成的客户端的随机标识和随机标识密码都不相同。
步骤204：服务器响应于客户端的分配请求，将分配给所述客户端为所述客户端提供服务的服务提供设备的唯一标识码和/或随机数发送给所述客户端，并且在服务器本地保存所述服务提供设备的唯一标识码和/或随机数。
其中，客户端的分配请求用于请求服务器为客户端分配服务提供设备。所述保存在本地的所述服务提供设备的唯一标识码和/或随机数，为在接收到所述客户端发送的请求分配服务提供设备的分配请求后、分配给所述客户端且为所述客户端提供服务的服务提供设备的唯一标识码和/或随机数；其中，所述分配请求中携带预先分配给所述客户端、用于标识所述客户端的随机标识。
如前所述，上述步骤202和204之间的执行没有必然的先后顺序关系，并且，也并且必需步骤。
步骤206：服务器接收服务提供设备发送的校验请求。
其中，所述校验请求用于请求校验客户端与服务提供设备的连接是否合法，所述校验请求中携带有客户端的随机令牌和客户端的随机标识。
服务器通过接收到的客户端的随机令牌和客户端的随机标识，可以实现对客户端与服务提供设备之间的连接的合法性进行基本的认证。
但可选地，所述校验请求中还可以携带有客户端的校验信息。客户端的校验信息可以由客户端发送给服务提供设备，服务提供设备携带在校验请求中发送给服务器。可选地，客户端的检验信息可以根据服务器分配给客户端的随机标识密码生成。优选地，客户端的校验信息根据服务器分配给客户端的随机标识密码，以及，以下信息中的至少一种生成：服务器分配给客户端的服务提供设备的唯一标识码和/或服务器分配给客户端的随机数；其中，所述随机标识密码为服务器预先分配给所述客户端、且与所述客户端的随机标识对应的信息。
又一可选地，所述校验请求中还可以携带有服务提供设备的唯一标识码。该唯一标识码可以为服务提供设备本地保存的唯一标识码，携带在校验请求中发送给服务器。
通过客户端的检验信息和/或服务提供设备的唯一标识码，可以对客户端与服务提供设备之间的连接合法性和安全性提供更进一步的保障。
步骤208：服务器根据保存在本地的随机令牌和随机标识，对所述校验请求中携带的随机令牌和随机标识进行验证。
其中，所述保存在本地的随机标识为预先分配给所述客户端、用于标识所述客户端的信息；所述保存在本地的随机令牌为预先分配给所述客户端、用于验证所述客户端与分配给所述客户端的服务提供设备的连接有效性的信息。
可选地，如步骤206中所述，若校验信息中还包括上述客户端的校验信息和服务提供设备的唯一标识码中的至少一种，则服务器将根据保存在本地的对应的信息，对校验信息进行验证。
也即，若所述校验请求中还携带有所述客户端的校验信息，则服务器需要将所述校验请求中携带的客户端的校验信息与保存在服务器本地的客户端的校验信息进行比较；其中，所述保存在本地的客户端的校验信息为预先分配给所述客户端的信息。其中，所述保存在本地的客户端的校验信息可以根据保存在本地的所述客户端的随机标识密码生成，所述保存在本地的随机标识密码为预先分配给所述客户端、且与所述客户端的随机标识对应的信息。优选地，所述保存在本地的客户端的校验信息根据保存在本地的所述 客户端的随机标识密码，以及，以下信息中的至少一种生成：保存在本地的所述服务提供设备的唯一标识码和/或随机数；其中，所述保存在本地的随机标识密码为预先分配给所述客户端、且与所述客户端的随机标识对应的信息。优选地，所述保存在本地的所述服务提供设备的唯一标识码和/或随机数，为服务器在接收到所述客户端发送的请求分配服务提供设备的分配请求后、分配给所述客户端且为所述客户端提供服务的服务提供设备的唯一标识码和/或随机数；其中，所述分配请求中携带预先分配给所述客户端、用于标识所述客户端的随机标识。
若所述校验请求中还携带有所述服务提供设备的唯一标识码，则服务器需要将所述校验请求中携带的服务提供设备的唯一标识码与保存在本地的服务提供设备的唯一标识码进行比较；其中，保存在本地的服务提供设备的唯一标识码为预先分配给所述客户端、且为所述客户端提供服务的服务提供设备的唯一标识码。
步骤210：若所述校验请求中携带的随机令牌和随机标识与保存在本地的对应信息匹配，则服务器确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
如前所述，当所述校验请求中仅携带有客户端的随机令牌和客户端的随机标识时，若所述校验请求中携带的随机标识与保存在服务器本地的随机标识匹配、且根据保存在服务器本地的所述随机令牌确定所述校验请求中携带的随机令牌有效，则服务器确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
当所述校验请求中还携带有所述客户端的校验信息时，服务器还需要判断所述校验请求中携带的客户端的校验信息与保存在本地的客户端的校验信息是否匹配，若所述校验请求中携带的随机标识与保存在服务器本地的随机标识匹配、且根据保存在服务器本地的所述随机令牌确定所述校验请求中携带的随机令牌有效，且，若所述校验请求中携带的客户端的校验信息与保存在本地的客户端的校验信息匹配，则服务器确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
当所述校验请求中还携带有所述服务提供设备的唯一标识码，则服务器还需要判断所述校验请求中携带的服务提供设备的唯一标识码与保存在本地的服务提供设备的唯一标识码是否匹配，若所述校验请求中携带的随机标识与保存在服务器本地的随机标识匹配、且根据保存在服务器本地的所述随机令牌确定所述校验请求中携带的随机令牌有效，且，若所述校验请求中携带的服务提供设备的唯一标识码与保存在本地的服务提供设备的唯一标识码匹配，则服务器确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
依次类推，当所述校验请求中同时携带有客户端的随机令牌、客户端的随机标识、客户端的校验信息和服务提供设备的唯一标识码时，若所述校验请求中携带的随机标识与保存在服务器本地的随机标识匹配、且根据保存在服务器本地的所述随机令牌确定所述校验请求中携带的随机令牌有效，且，若所述校验请求中携带的客户端的校验信息与保存在本地的客户端的校验信息匹配，且，若所述校验请求中携带的服务提供设备的唯一标识码与保存在本地的服务提供设备的唯一标识码匹配，则服务器确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
通过本实施例，分配给客户端的服务提供设备在接收到客户端的连接请求时，并不直接响应该连接请求与客户端建立连接，而是将与该连接请求所请求的连接有关的信息携带在校验请求中发送给服务器，通过服务器比对校验请求中的信息和服务器本地保存的对应信息，对所述连接请求所请求的客户端与服务提供设备之间的连接进行合法性验证，只有验证通过后，服务提供设备才与客户端建立连接。通过服务器对客户端与服务提供设备的连接的合法性认证，保证了智能电视系统的安全性，进而避免了非法客户端的接入，提高了系统的安全性，避免了用户数据信息的泄露。
此外，为终端提供服务的设备由网络侧的服务提供设备实现，终端只需具有基本的解码功能，即可从网络侧获取服务，不再依赖或受制于数字视频变换盒。网络侧服务提供设备所提供的服务能够及时进行更新和升级，可以保证终端用户使用到当前提供的最新的服务，有效满足了终端用户的服务需求。
实施例三
参照图3，示出了本申请实施例三中一种数据校验方法的步骤流程图。
在本实施例中，以上述智能电视系统架构中的服务提供设备的角度，对本实施例的数据校验方法进行说明。本实施例的数据校验方法具体可以包括如下步骤：
步骤302：接收客户端发送的用于请求连接的连接请求。
其中，所述连接请求中携带有所述客户端的随机令牌和所述客户端的随机标识，所述客户端的随机令牌用于指示服务器验证所述客户端与分配给所述客户端的服务提供设备的连接有效性。
步骤304：根据所述连接请求生成校验请求，并向所述服务器发送生成的所述校验请求。
其中，所述校验请求用于请求所述服务器校验所述连接请求所请求的连接是否合法，所述校验请求中携带有所述客户端的随机令牌和所述客户端的随机标识。
步骤306：根据所述服务器返回的对所述校验请求的校验结果，确定所述连接请求所请求的连接是否合法。
通过本实施例，分配给客户端的服务提供设备在接收到客户端的连接请求时，并不直接响应该连接请求与客户端建立连接，而是将与该连接请求所请求的连接有关的信息携带在校验请求中发送给服务器，通过服务器比对校验请求中的信息和服务器本地保存的对应信息，对所述连接请求所请求的客户端与服务提供设备之间的连接进行合法性验证，只有验证通过后，服务提供设备才与客户端建立连接。通过服务器对客户端与服务提供设备的连接的合法性认证，保证了智能电视系统的安全性，进而避免了非法客户端的接入，提高了系统的安全性，避免了用户数据信息的泄露。
此外，为终端提供服务的设备由网络侧的服务提供设备实现，终端只需具有基本的解码功能，即可从网络侧获取服务，不再依赖或受制于数字视频变换盒。网络侧服务提供设备所提供的服务能够及时进行更新和升级，可以保证终端用户使用到当前提供的最新的服务，有效满足了终端用户的服务需求。
实施例四
本实施例基于上述实施例三的数据校验方案，并对实施例三的数据校验方案进行了进一步的优化。
参照图4，示出了本申请实施例四中一种数据校验方法的步骤流程图。
在本实施例中，仍以上述智能电视系统架构中的服务提供设备的角度，对本实施例的数据校验方法进行说明。
本实施例的数据校验方法具体可以包括如下步骤：
步骤402：服务提供设备接收客户端发送的用于请求连接的连接请求。
其中，所述连接请求中携带有所述客户端的随机令牌和所述客户端的随机标识，所述客户端的随机令牌用于指示服务器验证所述客户端与分配给所述客户端的服务提供设备的连接有效性，所述客户端的随机标识用于标识所述客户端的信息。
通过所述客户端的随机令牌和所述客户端的随机标识，即可表征客户端与服务提供设备之间的连接的基本信息。但为了进一步提高对客户端与服务提供设备之间的连接的合法性的认证准确性和效率，在一可选方案中，所述校验请求中还可以携带有由所述客户端上报的所述客户端的校验信息。优选地，所述客户端的校验信息可以根据所述客户端的随机标识密码生成。进一步优选地，所述客户端的校验信息根据所述客户端的随机标识密码，以及，以下信息中的至少一种生成：服务提供设备的唯一标识码和/或随机数。
其中，客户端的随机标识用于标识所述客户端为服务器在接收到所述客户端发送的注册请求后、分配给所述客户端、用于标识所述客户端的信息；所述随机标识密码为服务器在接收到所述客户端发送的注册请求后、分配给所述客户端、且与分配给所述客户端的随机标识对应的随机标识密码。
上述客户端的随机标识和随机标识密码在客户端每次向服务器注册时，由服务器生成并发送给客户端。即使对于同一个客户端，每次注册时服务器生成的客户端的随机标识和随机标识密码都不相同。
客户端在需要请求服务器为客户端分配服务提供设备时，向服务器发送分配请求。服务器根据该分配请求为客户端分配服务提供设备，并生成所述服务提供设备的唯一标识码和/或随机数向客户端发送。
步骤404：服务提供设备根据所述连接请求生成校验请求，并向所述服务器发送生成的所述校验请求。
其中，所述校验请求用于请求所述服务器校验所述连接请求所请求的连接是否合法，所述校验请求中携带有所述客户端的随机令牌和所述客户端的随机标识。
在一可选方案中，所述校验请求中还携带有服务提供设备本地保存的所述服务提供设备的唯一标识码。
在又一可选方案中，所述校验请求中还可以携带有由所述客户端上报的所述客户端的校验信息。
步骤406：服务提供设备根据所述服务器返回的对所述校验请求的校验结果，确定所述连接请求所请求的连接是否合法。
当校验请求中仅携带有所述客户端的随机令牌和所述客户端的随机标识时，服务提供设备接收所述服务器返回的对所述校验请求的校验结果，其中，所述校验结果包括：第三校验结果；其中，所述第三校验结果用于指示所述客户端请求的本次连接是否有效，以及，所述校验请求中携带的客户端的随机标识与保存在服务器中的客户端的随机标识是否匹配；其中，所述保存在服务器中的客户端的随机标识为预先分配给所述客户端、用于标识所述客户端的信息；服务提供设备根据所述第三校验结果，确定所述连接请求所请求的连接是否合法。
当所述校验请求中还携带有由所述客户端上报的所述客户端的校验信息时，服务提供设备接收的所述服务器返回的对所述校验请求的校验结果中还包括：第一校验结果，其中，所述第一校验结果用于指示所述校验请求中携带的所述客户端的校验信息与保存 在服务器中的所述客户端的校验信息是否匹配；其中，保存在服务器中的校验信息为预先分配给所述客户端的信息；服务提供设备还需要根据所述第一校验结果，确定所述连接请求所请求的连接是否合法。也即，服务提供设备还需要根据所述第一和第三校验结果，确定所述连接请求所请求的连接是否合法。
所述校验请求中还携带有服务提供设备本地保存的所述服务提供设备的唯一标识码时，服务提供设备接收的所述服务器返回的对所述校验请求的校验结果中还包括：第二校验结果；其中，所述第二校验结果用于指示所述校验请求中携带的所述服务提供设备的唯一标识码与保存在服务器中的所述服务提供设备的唯一标识码是否匹配；其中，保存在服务器中的服务提供设备的唯一标识码为预先分配给所述客户端、且为所述客户端提供服务的服务提供设备的唯一标识码；服务提供设备还需要根据所述第二校验结果，确定所述连接请求所请求的连接是否合法。也即，服务提供设备还需要根据所述第二和第三校验结果，确定所述连接请求所请求的连接是否合法。
依此类推，当校验请求中同时携带有所述客户端的随机令牌、所述客户端的随机标识、所述服务提供设备的唯一标识码和所述客户端的校验信息时，服务提供设备需要根据所述第一、第二和第三校验结果，确定所述连接请求所请求的连接是否合法。
通过本实施例，分配给客户端的服务提供设备在接收到客户端的连接请求时，并不直接响应该连接请求与客户端建立连接，而是将与该连接请求所请求的连接有关的信息携带在校验请求中发送给服务器，通过服务器比对校验请求中的信息和服务器本地保存的对应信息，对所述连接请求所请求的客户端与服务提供设备之间的连接进行合法性验证，只有验证通过后，服务提供设备才与客户端建立连接。通过服务器对客户端与服务提供设备的连接的合法性认证，保证了智能电视系统的安全性，进而避免了非法客户端的接入，提高了系统的安全性，避免了用户数据信息的泄露。
此外，为终端提供服务的设备由网络侧的服务提供设备实现，终端只需具有基本的解码功能，即可从网络侧获取服务，不再依赖或受制于数字视频变换盒。网络侧服务提供设备所提供的服务能够及时进行更新和升级，可以保证终端用户使用到当前提供的最新的服务，有效满足了终端用户的服务需求。
实施例五
在本实施例中，可以采用如下的智能电视系统：该智能电视系统可以包括：至少一个客户端、至少一个调度服务器和至少一个服务提供设备。其中，客户端是一种可以使用服务提供设备提供的APP应用程序的终端，如，机顶盒、智能移动终端、PAD(Portable  Android Device平板电脑)、具有解码功能的智能电视等。所述服务提供设备可以作为服务端设置在云端，远程为所述客户端提供服务。调度服务器在接收到客户端申请服务提供设备的请求之后，可以根据设定分配策略从云端的多个服务提供设备中选择一个服务提供设备分配给所述客户端。
这里需要说明的是，在本实施例中，服务提供设备可以作为硬件设备设置在云端，软件(应用程序)可以安装在服务提供设备中，服务提供设备可以在云端将各类应用程序的用户界面(User Interface，UI)进行压缩编码，客户端有基本解码能力即可向用户展现应用程序的用户界面，实现对各类应用程序的操作。换而言之，与传统的智能电视系统所不同的是，在本实施例中，软件(应用程序)可以不安装在机顶盒中，可以安装在服务提供设备中，通过服务提供设备为用户提供服务。由于可以不再需要将软件安装在机顶盒中，故可以不再单独设置机顶盒。例如，若所述客户端为智能移动终端、或具有解码功能的智能电视时，则可以直接将智能移动终端(或具有解码功能的智能电视)与所述服务提供设备进行连接，用户可以不需要单独购买/设置机顶盒，节约了用户成本；同时，智能移动终端(或具有解码功能的智能电视)与所述服务提供设备直接进行交互，提高了交互效率，减少了对机顶盒的维护步骤，降低了对资源的占用。当然，对有现有机顶盒来说，其具有基本解码能力，本发明的方案也仍然适用。进一步地，所述调度服务器可以是指一个服务器，也可以是指等同于所述调度服务器功能的多个服务器组成的服务器群组。
本申请实施例中，客户端侧所显示的用户界面是能够为用户提供各种网络服务，例如在用户界面上可以包括各种菜单选项或图标等服务功能，例如包括：高清视频，超清电视、软件下载、游戏、生活服务(如缴费、购物等)等，从而通过该客户端，用户可在电视上免费观看高清电影电视、玩体感游戏、热门大型3D游戏、网络购物、支付水电煤费用等等功能。在用户选择某一功能的图标或菜单后，可以继续进入相应的UI界面执行操作，例如播放高清视频时可以选择本地或网络资源等。
针对客户端所显示的UI界面，用户可以通过遥控器的外置设备进行控制，如选择某个功能，进入下一级界面等，而由于UI界面是基于服务提供设备的传送流解析显示的，因此对UI界面的控制响应也由服务提供设备执行。本实施例中服务提供设备在与客户端建立连接后，预先在用户空间虚拟一输入设备，通过该虚拟输入设备模拟硬件输入信号，在系统注入用户的输入信号对应输入事件并进行分发，从而实现服务提供设备对用户控制的响应。
本实施例中，一种优选的智能电视系统的架构如图5所示。在本实施例中，所述智能电视系统具体可以包括：至少一个设备服务器(如图5所示的设备服务器501)、至少一个调度服务器(如图3所示的调度服务器502)和至少一个客户端(如图5所示的客户端503)。其中，每个设备服务器中包括至少一个服务提供设备(如图5所示的设备服务器501中的服务提供设备304)。
此外，优选地，所述智能电视系统还可以包括：至少一个管理服务器(如图5所示的管理服务器505)和至少一个用户数据存储设备(如图5所示的用户数据存储设备506)。需要说明的是，所述用户数据存储设备用于存储用户数据，一个用户可以对应一个专用的用户数据存储设备，多个用户也可以共有同一个用户数据存储设备，本实施例对此不作限制。其中，所述用户数据存储设备可以是物理设备，也可以是逻辑设备，还可以是物理和逻辑相结合的设备。例如，所述用户数据存储设备中可以包括至少一个用户分区(如图5所示的用户分区507)，每个用户分区对应存储一个用户的用户数据。
在本实施例中，客户端503可以是如上所述的硬件设备，如，机顶盒、智能移动终端、PAD、具有解码功能的智能电视等。优选地，所述客户端503也可以是位于智能电视终端侧，其可以呈现为智能电视终端中装载的APP(应用程序，Application)的形式，这里的智能电视终端具体可以包括：机顶盒、移动终端、智能电视机等。一方面，客户端503可用于播放服务提供设备504发送的传送流(Transport Stream，TS)所解析出的用户界面，以及播放从其他网络服务器中获取的多媒体数据(如视频信号、音频信号等)；另一方面，客户端503可用于监听用户通过遥控器等输入装置产生的输入消息，并将该输入消息发送给服务提供设备504或者调度服务器502。从而客户端503所显示的用户界面由服务提供设备504推送，客户端503仅解析并显示，且客户端503所接收的用户对用户界面控制的输入消息，也会转发给服务提供设备504以使其据此调整用户界面。
服务提供设备504位于网络侧，其中，每个服务提供设备具体可以包括：硬件板卡和硬件板卡所承载的软件模块。需要说明的是，在本实施例中，各类应用程序可以直接安装在服务提供设备中，用户可以通过客户端503展现的应用程序对应的用户界面，对服务提供设备504中的应用程序进行各项操作，不再需要在客户端503中单独安装应用程序，便于技术人员对所述智能电视系统进行统一维护，减少了工作量，提高了维护效率。
用户分区507位于网络侧，一般地，每个用户对应用一个用户分区，各个用户的用户数据被保存在对应的用户分区下。进一步地，每个用户分区具有唯一一个地址信息， 所述地址信息可以指示对应的用户分区的具体地址，通过所述地址信息可以快速查找到用户分区，完成用户数据的调用。换而言之，调度服务器502(或，管理服务器505)可以仅对地址信息(数据量较小)进行维护，而不用对整个用户数据(数据量较大)进行维护，降低了维护的数据量，减少了资源占用，提高了系统运行速度，且，用户数据便于查找。
调度服务器502位于网络侧，主要用于依据客户端503发送的请求消息，分配一个空闲的、状态良好的服务提供设备504与客户端503对接；同时，可以将用户ID对应的用户分区挂载到所分配的服务提供设备504上，也即，每个用户分区可以与唯一的用户ID相对应，如用户分区A对应用户A等等，这样，用户A在客户端503在与上次分配的、编号为001的服务提供设备断开连接后，即使下次连接的是编号为002的服务提供设备，用户A仍然可以使用用户分区A，并且可以使用之前的历史记录等数据。
管理服务器505位于网络侧，可用于对所有的服务提供设备进行管理，所述管理具体可以包括：状态上报、心跳管理、设置属性、获取属性、网络唤醒、软重启、硬重启等；可见，管理服务器505可以作为远程服务器，采用本申请的技术方案在广域网实现对服务提供设备的网络唤醒。
需要说明的是，本实施例所述的资源分配方法可以应用于基于图5中所示的智能电视系统中。但本领域技术人员应当明了，任意需要类似设备连接的系统或服务器，均可参照本实施例实现设备连接的方案，而不仅限于上述架构下的应用场景。
本实施例中，在智能电视系统中，服务提供设备采用的是可复用机制，即是一个服务提供设备服务完一个客户端重置后继续服务另一个客户端。即在服务提供设备与客户端建立连接后二者是唯一对应交互的关系，而当完成服务两者断开后，服务提供设备与客户端并不具有直接的对应关系，而是要等待系统为其分配其他客户端。因此，服务提供设备同一时间能服务一个客户端，如果服务提供设备在设定时间长度内未被使用，将进入省电休眠状态。
基于服务提供设备的上述特征，可以为服务提供设备设定几个状态以进行管理分配：
Idle状态，即空闲状态，处于该状态的服务提供设备可被直接分配给需要的客户端；
Busy状态，即忙碌状态，处于该状态的服务提供设备已经与客户端连接并在服务客户端，无法再进行分配；
Sleep状态，即睡眠状态，当系统中没有多余空闲状态的服务提供设备可分配时，系统可唤醒处于该状态的服务提供设备并将其分配给客户端；
Exception状态，即异常状态，处于该异常状态无法进行分配；
Management状态，即管理状态，表征该服务提供设备处在被服务器管理状态，无法进行分配。
结合前述实施例，本实施例以对智能电视系统中的资源分配为例，对所述资源分配方法进行详细说明。在不矛盾的情况下，该方法可以和上述实施例中的方法相结合。下面对本实施例所述的资源分配方法进行具体说明。
参照图6，示出了本申请实施例五中一种数据校验方法的步骤流程图。在本实施例中，所述数据校验方法包括：
步骤602，调度服务器根据接收到客户端上报的用于请求服务提供设备的请求信息，确定所述客户端合法。
在本实施例中，优选地，向调度服务器请求服务提供设备的客户端可以是已经完成注册的客户端，若客户端还是未注册客户端，则可以通过如下步骤完成客户端的注册：步骤616，调度服务器接收所述客户端发送的注册请求，为所述客户端随机分配一个随机标识和一个随机标识密码，并将分配的随机标识和随机标识密码作为第二随机标识和第二随机标识密码进行保存。
随机标识密码可以是调度服务器在客户端进行注册时为所述客户端随机分配的一个标识密码，可以用于对客户端进行识别、和/或进行合法性验证。
步骤618，调度服务器将分配的随机标识和随机标识密码发送至所述客户端，作为第一随机标识和第一随机标识密码保存在所述客户端，用于所述客户端的合法性认证。
本领域技术人员应当明了的是，向调度服务器请求服务提供设备的客户端也可以是未注册的客户端，当所述客户端是未注册的客户端端时，调度服务器可以为所述客户端临时分配一个随机标识和随机标识密码，用于对未注册客户端进行标识和验证。
需要说明的是，上述步骤616和步骤618可以在上述步骤602之前执行，或者也可以在上述步骤602之后，当接收到用户的重注册请求时执行。
此外，在接收到客户端的注册请求时，所述调度服务器还可以为所述客户端分配一个用户数据分区，所述用户数据分区与所述客户端唯一对应，可以用于存储所述客户端所对应的用户数据信息。优选地，可以建立所述随机标识与所述用户数据分区之间的对应关系，通过所述随机标识即可快速查找到对应的用户数据分区，提高了数据处理效率。
在本实施例中，本领域技术人员可以采用任意一种适当的方式确定客户端是否合法。优选地，一种可行的确定客户端合法的方式可以如下：调度服务器判断所述调度服务器 中是否存在与所述请求信息中携带的第一随机标识相匹配的第二随机标识；若存在，则确定所述客户端合法。
更优选地，为了保证验证结果的准确性，在确定客户端合法之前，除了验证第一随机标识与所述第二随机标识是否匹配外，还可以进一步验证所述请求信息中携带的第三验证信息与所述调度服务器中的第四验证信息是否相匹配，具体地：调度服务器判断所述客户端上报的请求信息中携带的第三验证信息是否与所述调度服务器中的第四验证信息相匹配；若所述第三验证信息与所述第四验证信息匹配，则确定所述客户端合法。
其中，所述第三验证信息可以是由所述客户端根据所述第一随机标识和/或第一随机标识密码按照第三设定规则生成的验证信息，并携带在所述请求信息中发送至所述调度服务器；或者，也可以直接单独发送给所述调度服务器。所述第四验证信息则可以是由所述调度服务器根据所述第二随机标识和/或第二随机标识密码按照第四设定规则生成。其中，所述第三设定规则与所述第四设定规则为同一设定规则；这里的第一个第二只是为了便于描述，并不起任何限定作用。
例如，可以根据所述第一随机标识、第一随机标识密码、客户端的设备地址、时间戳中的至少一种，按照第三设定加密算法生成所述第三验证信息。与之相对应地，调度服务器可以根据所述第二随机标识、第二随机标识密码、接收到的由所述客户端发送的设备地址、接收到的由所述客户端发送的时间戳中的至少一种，按照第四设定加密算法生成所述第四验证信息。其中，所述第三设定加密算法与所述第四设定加密算法相同。
举例来说，调度服务器在客户端注册时，为客户端分配了随机标识Key和随机标识密码Secret。将发送并保存在客户端中的随机标识和随机标识密码分别记作Key1和Srcret1，将保存在调度服务器中的随机标识和随机标识密码分别记作Key2和Secret2。优选地，可以将客户端发送请求信息时所对应的时间Time作为所述时间戳；保存在客户端的时间戳记作Time1；将通过所述请求信息或独立发送至调度服务器、并保存在调度服务器中的时间戳记作Time2。更优选地，客户端可以将自身的设备信息Mac地址(Media Access Control地址，硬件地址)携带在所述请求信息中或直接独立的发送至调度服务器，其中，客户端中保存的设备信息记作Mac1，调度服务器接收并保存的设备信息记作Mac2。
则，第三验证信息Sign1＝MD5(Key1+Mac1+Time1+Secret1)；对应地，第四验证信息Sign2＝MD5(Key2+Mac2+Time2+Secret2)。若Key1＝Key2，且，Sign1＝Sign2，则可以确定客户端合法。
本领域技术人员应当明了的是，客户端合法性的验证并不仅限于上述实施例中所述的方式，例如，也可以根据Mac来判断客户端的合法性。
步骤604，调度服务器为确定为合法的客户端分配服务提供设备，并获取分配的服务提供设备的设备信息，以及生成一个满足设定时效的随机令牌。
优选地，在确定客户端合法之后，可以通过如下一种可行的方式为客户端分配服务提供设备：调度服务器从请求信息中获取客户端的信息，根据所述信息确定所述客户端的终端类型，然后从与所述确定的终端类型相匹配的分布式队列中选择一个服务提供设备分配个所述客户端；在将选择的服务提供设备分配给客户端之前，还可以从与所述客户端相匹配的用户数据分区中获取用户数据；通知所述选择的服务提供设备根据获取的用户数据进行初始化配置，然后将初始化配置成功的服务提供设备分配给所述客户端。
在本实施例中，调度服务器获取的服务提供设备的设备信息和生成的随机令牌可以用于对客户端与服务提供设备连接的合法性的验证。优选地，调度服务器可以将获取的服务提供设备的设备信息和生成的随机令牌分别作为第二设备信息和第二随机令牌进行保存；以及，将获取的设备信息和生成的随机令牌发送至所述客户端，分别作为第一设备信息和第一随机令牌保存在客户端，客户端可以根据所述第一设备信息和/或第一随机令牌生成用于请求与服务提供设备进行连接的连接请求。
在本实施例中，调度服务器获取的服务提供设备的设备信息中包括但不仅限于：服务提供设备的IP地址、服务提供设备的端口地址和服务提供设备的UUID、服务提供设备的版本号和所述应用信息等。调度服务器将获取的服务提供设备的设备信息发送至所述客户端，客户端可以根据接收到的服务提供设备的设备信息(服务提供设备的IP地址、服务提供设备的端口地址和服务提供设备的UUID、服务提供设备的版本号和所述应用信息等)请求与所述服务提供设备建立连接。当然，此时客户端与服务提供设备并未建立正式的连接，也即，此时服务提供设备还不能正常为所述客户端提供服务，需要对所述客户端发送的连接请求进行合法性验证，当确定所述连接请求所请求的客户端与服务提供设备之间的连接合法时，所述服务提供设备才与所述客户端建立正式连接，并为所述客户端提供服务。
优选地，在本实施例中，服务提供设备在接收到客户端发送的连接请求之后，可以根据服务提供设备地设备信息、随机令牌和所述连接请求生成校验请求，以请求校验客户端与服务提供设备的连接是否合法。
步骤606，调度服务器接收服务提供设备上报的用于请求校验客户端与服务提供设 备的连接是否合法的校验请求。
步骤608，调度服务器获取第二验证信息和所述校验请求中携带的第一验证信息。
在本实施例中，所述第二验证信息可以由所述调度服务器根据保存在所述调度服务器的第二设备信息和/或第二随机标识密码按照第二设定规则生成；所述第一验证信息可以由所述客户端根据保存在所述客户端的第一设备信息和/或第一随机标识密码按照第一设定规则生成。
优选地，所述第一验证信息可以由所述客户端通过如下第一设定规则生成：根据所述第一设备信息中的第一唯一标识码UUID1、所述第一随机标识密码Secret1和随机生成的一个随机密钥Random_num，按照第一设定加密算法生成所述第一验证信息Salt1。例如：Salt1＝MD5(Secret1+UUID1+(Random_num+1))。
所述第二验证信息可以由调度服务器通过如下第二设定规则生成：根据所述第二设备信息中的第二唯一标识码UUID2、所述第二随机标识密码Secret2和所述随机密钥Random_num，按照第二设定加密算法生成所述第二验证信息Salt2。例如：Salt2＝MD5(Secret2+UUID2+(Random_num+1))。
步骤610，调度服务器根据所述第一验证信息与所述第二验证信息的比较结果确定所述校验请求所请求校验的客户端与服务提供设备的连接是否合法。
在本实施例中，若Salt1＝Salt2，则确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
在本实施例中，优选地，服务提供设备可以根据第三设备信息、第三随机令牌和第三随机标识生成所述校验请求。其中，第三设备信息、第三随机令牌和第三随机标识可以是携带在所述连接请求中发送的、保存在所述客户端中的第一设备信息、第一随机令牌和第一随机标识。换而言之，为了便于描述，可以将由所述客户端发送至所述服务提供设备的连接请求中携带的第一设备信息作为所述第三设备信息；将由所述客户端发送至所述服务提供设备的连接请求中携带的第一随机令牌作为所述第三随机令牌；将由所述客户端发送至所述服务提供设备的连接请求中携带的第一随机标识作为所述第三随机标识。
当然，所述第一设备信息、第一随机令牌和第一随机标识也可以是由所述客户端主动上报给所述服务提供设备，分别作为第三设备信息、第三随机令牌和第三随机标识。或者，也可以是客户端在接收到服务提供设备的获取请求之后，将所述第一设备信息、第一随机令牌和第一随机标识直接发送给所述服务提供设备，本实施例对此不作限制。
如上所示，一优选地，在确定所述校验请求所请求校验的客户端与服务提供设备的连接合法之前，还可以执行如下步骤：
步骤612，调度服务器判断所述校验请求中携带的第三设备信息与所述第二设备信息是否匹配；以及，判断所述校验请求中携带的第三随机令牌与所述第二随机令牌是否匹配，得到第一判断结果；并根据所述第一判断结果确定所述校验请求所请求校验的客户端与服务提供设备的连接是否合法。
以设备信息中的唯一标识码UUID为例进行说明，若第三设备信息中的第三唯一标识码UUID3与第二设备信息中的第二唯一标识码UUID2匹配，且，所述第三随机令牌Token3与所述第二随机令牌Token2匹配，则确定所述验请求所请求校验的客户端与服务提供设备的连接合法。
需要说明的是，所述随机令牌具有时效性，若超过设定的时间间隔，所述随机令牌将失效，不能在用于对所述客户端与服务提供设备的连接的合法性的判断。若在对客户端与服务提供设备之间的连接的合法性的验证过程中，随机令牌已失效，则可以直接判断客户端与服务提供设备的连接不合法(随机令牌超过时限标识，可能已被恶意获取)，或者，调度服务器重新生成一个随机令牌，然后使用新生成的随机令牌进行验证。
另一优选地，在确定所述校验请求所请求校验的客户端与服务提供设备的连接合法之前，还可以执行如下步骤：
步骤614，调度服务器判断所述校验请求中携带的第三随机标识与所述第二随机标识是否匹配，得到第二判断结果；根据所述第二判断结果确定所述校验请求所请求校验的客户端与服务提供设备的连接是否合法。
在本实施例中，若所述第三随机标识Key3与所述第二随机标识Key2匹配，则确定所述校验请求所请求校验的客户端与服务提供设备的连接是否合法。
本领域技术人员应当明了的是，所述步骤610、步骤612和步骤614之间并不存在必然的先后顺序，可以同时执行，也可以按照任意适当的顺序依次执行。换而言之，第一验证信息与第二验证信息的比较、第三唯一标识码UUID3与第二唯一标识码UUID2的比较、Token3与Token2的比较、以及Key3与Key2的比较均是用于确定所述校验请求所请求校验的客户端与服务提供设备盒的连接是否合法的实现方案中的一种。本领域技术人员可以根据实际情况从中选择至少一个，以对所述客户端与服务提供设备的连接的合法性进行判断。
以下，基于本实施例中的上述描述，以一个具体实例的形式，从数据交互的整体过 程角度对本申请的数据校验方案进行说明。如图7所示，示出了本实施例中的一种智能电视系统中的数据交互的过程，由图7可见，本实例中的智能电视系统至少包括客户端、服务提供设备和服务器(如可以为调度服务器)。该交互过程可以包括：
步骤S10：客户端向服务器发送注册请求，其中，所述注册请求至少携带有客户端的MAC地址信息。
步骤S20：服务器接收到客户端的注册请求，为客户端生成一对key/secret(即客户端的随机标识和随机标识密码)，并把客户端信息与key/secret的对应关系记录在数据库中。
客户端每次注册都会生成不同的key/secret(即使注册请求中携带的信息相同)，这样，即使黑客或非法用户模拟别人的客户端来注册，也拿不到客户端的key/secret，从而便于服务器确定其为其他的或非法的客户端。
步骤S30：服务器将key/secret发送给客户端。
步骤S40：客户端保存服务器返回的key/secret，并保存，记为key1/secret1。
通过上述步骤S10-S40，实现了客户端向服务器的注册。
步骤S50：客户端根据key1、secret1、mac1(即本地保存的mac地址)、和time1(即本地生成的时间戳)，生成sign1(用于验证客户端是否合法)。客户端在需要向服务器请求服务提供设备时，根据key1、mac1、sign1和time1生成请求信息。
步骤S60：客户端向服务器发送请求信息，该请求信息中携带有key1、mac1、sign1和time1。
步骤S70：服务器接收客户端发送的请求信息，验证服务器本地是否存在key1。
若不存在，则认为该请求信息为非法请求。
若存在，则通过key1查找服务器中保存的对应的secret和mac，将找出的secret和mac记为secret2和mac2；验证sign1与sign2是否一致，其中，sign2由服务器根据key1、mac2、secret2和time1，采用与客户端生成sign1相同的算法生成。若sign1与sign2不一致，则认定所述请求信息为非法请求；若sign1与sign2一致，则执行步骤S80。
步骤S80：服务器为客户端选择一个空闲服务提供设备(该服务提供设备的UUID记为UUID1)。
步骤S90：服务器将选择的服务提供设备分配给客户端，同时为客户端生成token1、随机数random1、和salt1。其中，token1为一串随机字符串，其长度可以为32位左右但不限于32位左右；通过一定的算法，如md5对一下字符串加密生成一个值salt：如 salt＝MD5(secret+uuid1+random1)保存在服务器，记为salt1；服务器记录key1、uuid1、token1、和salt1的对应关系，并且非永久保存(如，超过一定时间后会过期，如超过5分钟)。
步骤S100：服务器将uuid1、token1、random1，以及，服务提供设备的IP地址和PORT返回给客户端。
通过上述步骤S50-S100，实现了服务器为客户端分配服务提供设备。
步骤S110：客户端采用与服务器相同的算法生成salt2。
此外，客户端将接收的token1保存在本地，并记为token2。
步骤S120：客户端向服务提供设备发送连接请求，该连接请求中携带有token2、key2、和salt2。
其中，key2为客户端自身的key，key2＝key1，salt2＝MD5(secret1+uuid1+random1)，也即，客户端在本地采用与服务器相同的算法生成salt2。
步骤S130：服务提供设备接收连接请求，从中获取相应的信息，并确定向服务器请求判断该连接请求所请求的连接是否合法。
步骤S140：服务提供设备向服务器发送校验请求，该校验请求中携带有token2、key2、salt2和服务提供设备自身的uuid。
步骤S150：服务器验证所述连接请求所请求的连接是否合法。
包括：服务器验证本地保存的key1、uuid1、token1、salt1，与key2、uuid、token2、salt2是否一致；若不一致，则认为所述连接请求所请求的连接非法；若一致，则认为所述连接请求所请求的连接合法。
步骤S160：服务器向服务提供设备返回验证结果。
通过上述步骤S110-S160，实现了服务器对客户端和服务提供设备之间连接合法性的验证。
步骤S170：服务提供设备若根据验证结果确定所述连接请求所请求的连接合法，则与客户端建立连接，并向客户端发送ts流；否则，与客户端断开连接。
综上所述，在本实施例中，所述智能电视系统中的调度服务器接收服务提供设备上报的用于请求校验客户端与服务提供设备的连接是否合法的校验请求；然后根据所述第一验证信息与所述第二验证信息的比较结果确定所述校验请求所请求校验的客户端与服务提供设备的连接是否合法。可见，在本实施例中，客户端与服务提供设备在连接之前， 需要通过调度服务器对所述客户端与服务提供设备的连接的合法性进行判断，当所述客户端与服务提供设备的连接合法时，客户端与服务提供设备才建立正式连接，所述调度服务器和服务提供设备为所述客户端提供服务，保证了智能电视系统的安全性，进而避免了非法客户端的接入，提高了系统的安全性，避免了用户数据信息的泄露。
进一步地，通过本实施例实现了由服务提供设备为客户端提供服务的功能，可以在云端对服务提供设备进行维护(如，软件更新或硬件升级等)，避免了用户手动更新操作，节约了用户时间，降低了用户成本。
此外，调度服务器在接收校验请求之后可以先对客户端的合法性进行判断，在确定客户端合法之后，客户端才可以向所述服务提供设备发送连接请求，进一步提高了所述智能电视系统的安全性。
更进一步地，若采用具有基本的解码功能的智能电视作为所述客户端，则可以通过服务提供设备直接为所述智能电视提供服务，不再需要单独设置机顶盒，减少了用户对机顶盒的维护步骤，减少了对资源的占用，同时节约了用户成本。而且具有基本的解码功能的智能电视相对传统的机顶盒更加独立，恶意程序难以通过网络实现对所述具有基本的解码功能的智能电视的攻击，系统更加安全。
实施例六
本发明实施例还提供了一种数据校验装置，上述实施例中所述的智能电视系统中的服务器可以包括所述数据校验装置，也即，所述数据校验装置可以用于实现上述方法实施例，故，上述方法实施例中的特征都可以应用到本实施例中。
参照图8，示出了本发明实施例六中一种数据校验装置的结构框图。在本实施例中，所述数据校验装置具体可以包括：
校验请求接收模块702，用于接收服务提供设备发送的校验请求。
在本实施例中，所述校验请求用于请求校验客户端与服务提供设备的连接是否合法，所述校验请求中携带有所述客户端的随机令牌和所述客户端的随机标识。
验证模块704，用于根据保存在本地的随机令牌和随机标识，对所述校验请求中携带的随机令牌和随机标识进行验证。
在本实施例中，所述保存在本地的随机标识为预先分配给所述客户端、用于标识所述客户端的信息；所述保存在本地的随机令牌为预先分配给所述客户端、用于验证所述客户端与分配给所述客户端的服务提供设备的连接有效性的信息。
确定模块706，用于在所述校验请求中携带的随机令牌和随机标识与保存在本地的 对应信息匹配时，确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
在本实施例的一优选方案中，所述确定模块606，具体可以用于在所述校验请求中携带的随机标识与保存在本地的随机标识匹配、且根据保存在本地的所述随机令牌确定所述校验请求中携带的随机令牌有效时，确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
在本实施例的一优选方案中，所述校验请求中还可以携带有所述客户端的校验信息。进一步优选地，所述装置还可以包括：第一比较模块，用于将所述校验请求中携带的客户端的校验信息与保存在本地的客户端的校验信息进行比较；其中，所述保存在本地的客户端的校验信息为预先分配给所述客户端的信息；以及，在所述校验请求中携带的客户端的校验信息与保存在本地的客户端的校验信息匹配时，确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。优选地，所述保存在本地的客户端的校验信息根据保存在本地的所述客户端的随机标识密码生成；其中，所述保存在本地的随机标识密码为预先分配给所述客户端、且与所述客户端的随机标识对应的信息。优选地，所述保存在本地的客户端的校验信息根据保存在本地的所述客户端的随机标识密码，以及，以下信息中的至少一种生成：保存在本地的所述服务提供设备的唯一标识码和/或随机数；其中，所述保存在本地的随机标识密码为预先分配给所述客户端、且与所述客户端的随机标识对应的信息。
在本实施例的一优选方案中，所述校验请求中还可以携带有所述服务提供设备的唯一标识码。进一步优选地，所述装置还可以包括：第二比较模块，用于将所述校验请求中携带的服务提供设备的唯一标识码与保存在本地的服务提供设备的唯一标识码进行比较；其中，保存在本地的服务提供设备的唯一标识码为预先分配给所述客户端、且为所述客户端提供服务的服务提供设备的唯一标识码；以及，在所述校验请求中携带的服务提供设备的唯一标识码与保存在本地的服务提供设备的唯一标识码匹配时，确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
在本实施例的一优选方案中，保存在本地的随机标识可以为在接收到所述客户端发送的注册请求后、分配给所述客户端、用于标识所述客户端的信息。所述装置还可以包括：第一响应模块，用于响应于所述客户端的注册请求，将分配给所述客户端、用于标识所述客户端的随机标识发送给所述客户端。
在本实施例的一优选方案中，所述保存在本地的随机标识密码为在接收到所述客户端发送的注册请求后、分配给所述客户端、且与分配给所述客户端的随机标识对应的随 机标识密码。所述装置还可以包括：第二响应模块，用于响应于所述客户端的注册请求，将分配给所述客户端、用于标识所述客户端的随机标识、以及与所述客户端的随机标识对应的随机标识密码发送给所述客户端。
在本实施例的一优选方案中，所述保存在本地的所述服务提供设备的唯一标识码和/或随机数，可以为在接收到所述客户端发送的请求分配服务提供设备的分配请求后、分配给所述客户端且为所述客户端提供服务的服务提供设备的唯一标识码和/或随机数；其中，所述分配请求中携带预先分配给所述客户端、用于标识所述客户端的随机标识。所述装置还可以包括：第三响应模块，用于响应于所述分配请求，将分配给所述客户端为所述客户端提供服务的服务提供设备的唯一标识码和/或随机数发送给所述客户端。
通过本实施例，分配给客户端的服务提供设备在接收到客户端的连接请求时，并不直接响应该连接请求与客户端建立连接，而是将与该连接请求所请求的连接有关的信息携带在校验请求中发送给服务器，通过服务器比对校验请求中的信息和服务器本地保存的对应信息，对所述连接请求所请求的客户端与服务提供设备之间的连接进行合法性验证，只有验证通过后，服务提供设备才与客户端建立连接。通过服务器对客户端与服务提供设备的连接的合法性认证，保证了智能电视系统的安全性，进而避免了非法客户端的接入，提高了系统的安全性，避免了用户数据信息的泄露。
此外，为终端提供服务的设备由网络侧的服务提供设备实现，终端只需具有基本的解码功能，即可从网络侧获取服务，不再依赖或受制于数字视频变换盒。网络侧服务提供设备所提供的服务能够及时进行更新和升级，可以保证终端用户使用到当前提供的最新的服务，有效满足了终端用户的服务需求。
实施例七
本发明实施例还提供了一种数据校验装置，上述实施例中所述的智能电视系统中的服务提供设备可以包括所述数据校验装置，也即，所述数据校验装置可以用于实现上述方法实施例，故，上述方法实施例中的特征都可以应用到本实施例中。
参照图9，示出了本发明实施例七中一种数据校验装置的结构框图。在本实施例中，所述数据校验装置具体可以包括：
连接请求接收模块802，用于接收客户端发送的用于请求连接的连接请求。
在本实施例中，所述连接请求中携带有所述客户端的随机令牌和所述客户端的随机标识，所述客户端的随机令牌用于指示服务器验证所述客户端与分配给所述客户端的服务提供设备的连接有效性；所述客户端的随机标识用于标识所述客户端的信息。
校验请求生成模块804，用于根据所述连接请求生成校验请求，并向所述服务器发送生成的所述校验请求。
在本实施例中，所述校验请求用于请求所述服务器校验所述连接请求所请求的连接是否合法，所述校验请求中携带有所述客户端的随机令牌和所述客户端的随机标识。
合法性验证模块806，用于根据所述服务器返回的对所述校验请求的校验结果，确定所述连接请求所请求的连接是否合法。
在本实施例的一优选方案中，所述校验请求中还可以携带有由所述客户端上报的所述客户端的校验信息。优选地，所述合法性验证模块706，具体可以用于接收所述服务器返回的对所述校验请求的校验结果，其中，所述校验结果可以包括：第一校验结果，其中，所述第一校验结果用于指示所述校验请求中携带的所述客户端的校验信息与保存在服务器中的所述客户端的校验信息是否匹配；其中，保存在服务器中的校验信息为预先分配给所述客户端的信息；以及，根据所述第一校验结果，确定所述连接请求所请求的连接是否合法。
优选地，所述客户端的校验信息可以根据所述客户端的随机标识密码生成。
优选地，所述客户端的校验信息可以根据所述客户端的随机标识密码，以及，以下信息中的至少一种生成：服务提供设备的唯一标识码和/或随机数。
在本实施例的一优选方案中，所述校验请求中还可以携带有本地保存的所述服务提供设备的唯一标识码。优选地，所述合法性验证模块706，具体可以用于接收所述服务器返回的对所述校验请求的校验结果。其中，所述校验结果包括：第二校验结果；其中，所述第二校验结果用于指示所述校验请求中携带的所述服务提供设备的唯一标识码与保存在服务器中的所述服务提供设备的唯一标识码是否匹配；其中，保存在服务器中的服务提供设备的唯一标识码为预先分配给所述客户端、且为所述客户端提供服务的服务提供设备的唯一标识码；以及，根据所述第二校验结果，确定所述连接请求所请求的连接是否合法。
在本实施例的一优选方案中，所述合法性验证模块706，具体可以用于接收所述服务器返回的对所述校验请求的校验结果，其中，所述校验结果包括：第三校验结果；其中，所述第三校验结果用于指示所述客户端请求的本次连接是否有效，以及，所述校验请求中携带的客户端的随机标识与保存在服务器中的客户端的随机标识是否匹配；其中，所述保存在服务器中的客户端的随机标识为预先分配给所述客户端、用于标识所述客户端的信息；以及，根据所述第三校验结果，确定所述连接请求所请求的连接是否合法。
通过本实施例，分配给客户端的服务提供设备在接收到客户端的连接请求时，并不直接响应该连接请求与客户端建立连接，而是将与该连接请求所请求的连接有关的信息携带在校验请求中发送给服务器，通过服务器比对校验请求中的信息和服务器本地保存的对应信息，对所述连接请求所请求的客户端与服务提供设备之间的连接进行合法性验证，只有验证通过后，服务提供设备才与客户端建立连接。通过服务器对客户端与服务提供设备的连接的合法性认证，保证了智能电视系统的安全性，进而避免了非法客户端的接入，提高了系统的安全性，避免了用户数据信息的泄露。
此外，为终端提供服务的设备由网络侧的服务提供设备实现，终端只需具有基本的解码功能，即可从网络侧获取服务，不再依赖或受制于数字视频变换盒。网络侧服务提供设备所提供的服务能够及时进行更新和升级，可以保证终端用户使用到当前提供的最新的服务，有效满足了终端用户的服务需求。
实施例八
本发明实施例还公开了一种智能电视系统，包括：至少一个服务器、至少一个客户端、至少一个服务提供设备；其中，所述服务器用于向所述客户端分配服务提供设备；所述客户端设置在智能电视中，所述服务提供设备设置在网络侧，用于通过网络为建立连接的客户端提供互联网服务；
其中，所述服务器可以包括上述实施例六所述的数据校验装置，所述服务提供设备可以包括所述实施例七所述的数据校验装置。
所述的系统还包括：少一个用户数据信息存储设备；所述至少一个用户数据信息存储设备包括：至少一个用户分区；其中，所述至少一个用户分区分别用于存储不同客户端对应的用户数据。
所述服务提供设备包括：网络机顶盒；所述互联网服务，包括如下中的至少一个：电视直播、音视频服务、网页服务、游戏服务。
其中，该智能电视系统与上述图5所述的系统基本一致，因此不再赘述。
对于上述一种调度服务器的装置实施例而言，由于其与方法实施例基本相似，所以描述的比较简单，相关之处参见上述方法实施例的部分说明即可。
本说明书中的各个实施例均采用递进的方式描述，每个实施例重点说明的都是与其他实施例的不同之处，各个实施例之间相同相似的部分互相参见即可。
本领域技术人员易于想到的是：上述各个实施例的任意组合应用都是可行的，故上 述各个实施例之间的任意组合都是本申请的实施方案，但是由于篇幅限制，本说明书在此就不一一详述了。
本申请可用于众多通用或专用的计算系统环境或配置中。例如：个人计算机、服务器计算机、手持设备或便携式设备、平板型设备、多处理器系统、基于微处理器的系统、置顶盒、可编程的消费电子设备、网络PC、小型计算机、大型计算机、包括以上任何系统或设备的分布式计算环境等等。
本申请可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本申请，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
在本申请中，“组件”、“装置”、“系统”等等指应用于计算机的相关实体，如硬件、硬件和软件的组合、软件或执行中的软件等。详细地说，例如，组件可以、但不限于是运行于处理器的过程、处理器、对象、可执行组件、执行线程、程序和/或计算机。还有，运行于服务器上的应用程序或脚本程序、服务器都可以是组件。一个或多个组件可在执行的过程和/或线程中，并且组件可以在一台计算机上本地化和/或分布在两台或多台计算机之间，并可以由各种计算机可读介质运行。组件还可以根据具有一个或多个数据包的信号，例如，来自一个与本地系统、分布式系统中另一组件交互的，和/或在因特网的网络通过信号与其它系统交互的数据的信号通过本地和/或远程过程来进行通信。
最后，还需要说明的是，在本文中，诸如第一和第二等之类的关系术语仅仅用来将一个实体或者操作与另一个实体或操作区分开来，而不一定要求或者暗示这些实体或操作之间存在任何这种实际的关系或者顺序。而且，术语“包括”、“包含”，不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括……”限定的要素，并不排除在包括所述要素的过程、方法、物品或者设备中还存在另外的相同要素。
而且，上文中的“和/或”表示本文既包含了“和”的关系，也包含了“或”的关系，其中：如果方案A与方案B是“和”的关系，则表示某实施例中可以同时包括方案A和方案B；如果方案A与方案B是“或”的关系，则表示某实施例中可以单独包括方案A，或者单独包括方案B。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序 产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例做出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
以上对本申请所提供的一种数据校验方法、装置和智能电视系统，进行了详细介绍，本文中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想；同时，对于本领域的一般技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本申请的限制。

Claims (36)

  1. 一种数据校验方法，其特征在于，所述方法包括：
    接收服务提供设备发送的校验请求，其中，所述校验请求用于请求校验客户端与服务提供设备的连接是否合法，所述校验请求中携带有所述客户端的随机令牌和所述客户端的随机标识；
    根据保存在本地的随机令牌和随机标识，对所述校验请求中携带的随机令牌和随机标识进行验证；其中，所述保存在本地的随机标识为预先分配给所述客户端、用于标识所述客户端的信息；所述保存在本地的随机令牌为预先分配给所述客户端、用于验证所述客户端与分配给所述客户端的服务提供设备的连接有效性的信息；
    若所述校验请求中携带的随机令牌和随机标识与保存在本地的对应信息匹配，则确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
  2. 如权利要求1所述的方法，其特征在于，若所述校验请求中携带的随机令牌和随机标识与保存在本地的对应信息匹配，则确定所述校验请求所请求校验的客户端与服务提供设备的连接合法的步骤，包括：
    若所述校验请求中携带的随机标识与保存在本地的随机标识匹配、且根据保存在本地的所述随机令牌确定所述校验请求中携带的随机令牌有效，则确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
  3. 如权利要求1所述的方法，其特征在于，所述校验请求中还携带有所述客户端的校验信息；
    所述方法还包括：
    将所述校验请求中携带的客户端的校验信息与保存在本地的客户端的校验信息进行比较；其中，所述保存在本地的客户端的校验信息为预先分配给所述客户端的信息；
    若所述校验请求中携带的客户端的校验信息与保存在本地的客户端的校验信息匹配，则执行确定所述校验请求所请求校验的客户端与服务提供设备的连接合法的步骤。
  4. 如权利要求3所述的方法，其特征在于，所述保存在本地的客户端的校验信息根据保存在本地的所述客户端的随机标识密码生成；其中，所述保存在本地的随机标识密码为预先分配给所述客户端、且与所述客户端的随机标识对应的信息。
  5. 如权利要求3所述的方法，其特征在于，所述保存在本地的客户端的校验信息根据保存在本地的所述客户端的随机标识密码，以及，以下信息中的至少一种生成：保存在本地的所述服务提供设备的唯一标识码和/或随机数；其中，所述保存在本地的随机 标识密码为预先分配给所述客户端、且与所述客户端的随机标识对应的信息。
  6. 如权利要求1所述的方法，其特征在于，所述校验请求中还携带有所述服务提供设备的唯一标识码；
    所述方法还包括：
    将所述校验请求中携带的服务提供设备的唯一标识码与保存在本地的服务提供设备的唯一标识码进行比较；其中，保存在本地的服务提供设备的唯一标识码为预先分配给所述客户端、且为所述客户端提供服务的服务提供设备的唯一标识码；
    若所述校验请求中携带的服务提供设备的唯一标识码与保存在本地的服务提供设备的唯一标识码匹配，则执行确定所述校验请求所请求校验的客户端与服务提供设备的连接合法的步骤。
  7. 如权利要求1-6任一项所述的方法，其特征在于，保存在本地的随机标识为在接收到所述客户端发送的注册请求后、分配给所述客户端、用于标识所述客户端的信息；
    所述方法还包括：
    响应于所述客户端的注册请求，将分配给所述客户端、用于标识所述客户端的随机标识发送给所述客户端。
  8. 如权利要求4或5所述的方法，其特征在于，所述保存在本地的随机标识密码为在接收到所述客户端发送的注册请求后、分配给所述客户端、且与分配给所述客户端的随机标识对应的随机标识密码；
    所述方法还包括：
    响应于所述客户端的注册请求，将分配给所述客户端、用于标识所述客户端的随机标识、以及与所述客户端的随机标识对应的随机标识密码发送给所述客户端。
  9. 如权利要求5所述的方法，其特征在于，所述保存在本地的所述服务提供设备的唯一标识码和/或随机数，为在接收到所述客户端发送的请求分配服务提供设备的分配请求后、分配给所述客户端且为所述客户端提供服务的服务提供设备的唯一标识码和/或随机数；其中，所述分配请求中携带预先分配给所述客户端、用于标识所述客户端的随机标识；
    所述方法还包括：
    响应于所述分配请求，将分配给所述客户端为所述客户端提供服务的服务提供设备的唯一标识码和/或随机数发送给所述客户端。
  10. 根据权利要求1-6任一权利要求所述的方法，其特征在于，所述数据校验方法 应用于智能电视系统；其中，所述智能电视系统包括：至少一个服务器、至少一个客户端、至少一个服务提供设备；其中，所述服务器用于向所述客户端分配服务提供设备；所述客户端设置在智能电视中，所述服务提供设备设置在网络侧，用于通过网络为建立连接的客户端提供互联网服务。
  11. 根据权利要求10所述的方法，其特征在于，所述智能电视系统，还包括至少一个用户数据信息存储设备；所述至少一个用户数据信息存储设备包括：至少一个用户分区；其中，所述至少一个用户分区分别用于存储不同客户端对应的用户数据。
  12. 根据权利要求11所述的方法，其特征在于，所述服务提供设备包括：网络机顶盒；所述互联网服务，包括如下中的至少一个：
    电视直播、音视频服务、网页服务、游戏服务。
  13. 一种数据校验方法，其特征在于，所述方法包括：
    接收客户端发送的用于请求连接的连接请求，其中，所述连接请求中携带有所述客户端的随机令牌和所述客户端的随机标识，所述客户端的随机令牌用于指示服务器验证所述客户端与分配给所述客户端的服务提供设备的连接有效性；所述客户端的随机标识用于标识所述客户端的信息；
    根据所述连接请求生成校验请求，并向所述服务器发送生成的所述校验请求，其中，所述校验请求用于请求所述服务器校验所述连接请求所请求的连接是否合法，所述校验请求中携带有所述客户端的随机令牌和所述客户端的随机标识；
    根据所述服务器返回的对所述校验请求的校验结果，确定所述连接请求所请求的连接是否合法。
  14. 如权利要求13所述的方法，其特征在于，所述校验请求中还携带有由所述客户端上报的所述客户端的校验信息；
    根据所述服务器返回的对所述校验请求的校验结果，确定所述连接请求所请求的连接是否合法的步骤，包括：
    接收所述服务器返回的对所述校验请求的校验结果，其中，所述校验结果包括：第一校验结果，其中，所述第一校验结果用于指示所述校验请求中携带的所述客户端的校验信息与保存在服务器中的所述客户端的校验信息是否匹配；其中，保存在服务器中的校验信息为预先分配给所述客户端的信息；
    根据所述第一校验结果，确定所述连接请求所请求的连接是否合法。
  15. 如权利要求14所述的方法，其特征在于，所述客户端的校验信息根据所述客户端的随机标识密码生成。
  16. 如权利要求15所述的方法，其特征在于，所述客户端的校验信息根据所述客户端的随机标识密码，以及，以下信息中的至少一种生成：服务提供设备的唯一标识码和/或随机数。
  17. 如权利要求13所述的方法，其特征在于，所述校验请求中还携带有本地保存的所述服务提供设备的唯一标识码；
    根据所述服务器返回的对所述校验请求的校验结果，确定所述连接请求所请求的连接是否合法的步骤，包括：
    接收所述服务器返回的对所述校验请求的校验结果，其中，所述校验结果包括：第二校验结果；其中，所述第二校验结果用于指示所述校验请求中携带的所述服务提供设备的唯一标识码与保存在服务器中的所述服务提供设备的唯一标识码是否匹配；其中，保存在服务器中的服务提供设备的唯一标识码为预先分配给所述客户端、且为所述客户端提供服务的服务提供设备的唯一标识码；
    根据所述第二校验结果，确定所述连接请求所请求的连接是否合法。
  18. 如权利要求13所述的方法，其特征在于，根据所述服务器返回的对所述校验请求的校验结果，确定所述连接请求所请求的连接是否合法的步骤，包括：
    接收所述服务器返回的对所述校验请求的校验结果，其中，所述校验结果包括：第三校验结果；其中，所述第三校验结果用于指示所述客户端请求的本次连接是否有效，以及，所述校验请求中携带的客户端的随机标识与保存在服务器中的客户端的随机标识是否匹配；其中，所述保存在服务器中的客户端的随机标识为预先分配给所述客户端、用于标识所述客户端的信息；
    根据所述第三校验结果，确定所述连接请求所请求的连接是否合法。
  19. 一种数据校验装置，其特征在于，所述装置包括：
    校验请求接收模块，用于接收服务提供设备发送的校验请求，其中，所述校验请求用于请求校验客户端与服务提供设备的连接是否合法，所述校验请求中携带有所述客户端的随机令牌和所述客户端的随机标识；
    验证模块，用于根据保存在本地的随机令牌和随机标识，对所述校验请求中携带的随机令牌和随机标识进行验证；其中，所述保存在本地的随机标识为预先分配给所述客 户端、用于标识所述客户端的信息；所述保存在本地的随机令牌为预先分配给所述客户端、用于验证所述客户端与分配给所述客户端的服务提供设备的连接有效性的信息；
    确定模块，用于在所述校验请求中携带的随机令牌和随机标识与保存在本地的对应信息匹配时，确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
  20. 如权利要求19所述的装置，其特征在于，所述确定模块，用于在所述校验请求中携带的随机标识与保存在本地的随机标识匹配、且根据保存在本地的所述随机令牌确定所述校验请求中携带的随机令牌有效时，确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
  21. 如权利要求19所述的装置，其特征在于，所述校验请求中还携带有所述客户端的校验信息；
    所述装置还包括：
    第一比较模块，用于将所述校验请求中携带的客户端的校验信息与保存在本地的客户端的校验信息进行比较；其中，所述保存在本地的客户端的校验信息为预先分配给所述客户端的信息；以及，
    在所述校验请求中携带的客户端的校验信息与保存在本地的客户端的校验信息匹配时，确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
  22. 如权利要求21所述的装置，其特征在于，所述保存在本地的客户端的校验信息根据保存在本地的所述客户端的随机标识密码生成；其中，所述保存在本地的随机标识密码为预先分配给所述客户端、且与所述客户端的随机标识对应的信息。
  23. 如权利要求21所述的装置，其特征在于，所述保存在本地的客户端的校验信息根据保存在本地的所述客户端的随机标识密码，以及，以下信息中的至少一种生成：保存在本地的所述服务提供设备的唯一标识码和/或随机数；其中，所述保存在本地的随机标识密码为预先分配给所述客户端、且与所述客户端的随机标识对应的信息。
  24. 如权利要求19所述的装置，其特征在于，所述校验请求中还携带有所述服务提供设备的唯一标识码；
    所述装置还包括：
    第二比较模块，用于将所述校验请求中携带的服务提供设备的唯一标识码与保存在本地的服务提供设备的唯一标识码进行比较；其中，保存在本地的服务提供设备的唯一标识码为预先分配给所述客户端、且为所述客户端提供服务的服务提供设备的唯一标识码；以及，
    在所述校验请求中携带的服务提供设备的唯一标识码与保存在本地的服务提供设备的唯一标识码匹配时，确定所述校验请求所请求校验的客户端与服务提供设备的连接合法。
  25. 如权利要求19-24任一项所述的装置，其特征在于，保存在本地的随机标识为在接收到所述客户端发送的注册请求后、分配给所述客户端、用于标识所述客户端的信息；
    所述装置还包括：
    第一响应模块，用于响应于所述客户端的注册请求，将分配给所述客户端、用于标识所述客户端的随机标识发送给所述客户端。
  26. 如权利要求22或23所述的装置，其特征在于，所述保存在本地的随机标识密码为在接收到所述客户端发送的注册请求后、分配给所述客户端、且与分配给所述客户端的随机标识对应的随机标识密码；
    所述装置还包括：
    第二响应模块，用于响应于所述客户端的注册请求，将分配给所述客户端、用于标识所述客户端的随机标识、以及与所述客户端的随机标识对应的随机标识密码发送给所述客户端。
  27. 如权利要求23所述的装置，其特征在于，所述保存在本地的所述服务提供设备的唯一标识码和/或随机数，为在接收到所述客户端发送的请求分配服务提供设备的分配请求后、分配给所述客户端且为所述客户端提供服务的服务提供设备的唯一标识码和/或随机数；其中，所述分配请求中携带预先分配给所述客户端、用于标识所述客户端的随机标识；
    所述装置还包括：
    第三响应模块，用于响应于所述分配请求，将分配给所述客户端为所述客户端提供服务的服务提供设备的唯一标识码和/或随机数发送给所述客户端。
  28. 一种数据校验装置，其特征在于，所述装置包括：
    连接请求接收模块，用于接收客户端发送的用于请求连接的连接请求，其中，所述连接请求中携带有所述客户端的随机令牌和所述客户端的随机标识，所述客户端的随机令牌用于指示服务器验证所述客户端与分配给所述客户端的服务提供设备的连接有效性；所述客户端的随机标识用于标识所述客户端的信息；
    校验请求生成模块，用于根据所述连接请求生成校验请求，并向所述服务器发送生成的所述校验请求，其中，所述校验请求用于请求所述服务器校验所述连接请求所请求的连接是否合法，所述校验请求中携带有所述客户端的随机令牌和所述客户端的随机标识；
    合法性验证模块，用于根据所述服务器返回的对所述校验请求的校验结果，确定所述连接请求所请求的连接是否合法。
  29. 如权利要求28所述的装置，其特征在于，所述校验请求中还携带有由所述客户端上报的所述客户端的校验信息；
    所述合法性验证模块，用于接收所述服务器返回的对所述校验请求的校验结果，其中，所述校验结果包括：第一校验结果，其中，所述第一校验结果用于指示所述校验请求中携带的所述客户端的校验信息与保存在服务器中的所述客户端的校验信息是否匹配；其中，保存在服务器中的校验信息为预先分配给所述客户端的信息；以及，
    根据所述第一校验结果，确定所述连接请求所请求的连接是否合法。
  30. 如权利要求29所述的装置，其特征在于，所述客户端的校验信息根据所述客户端的随机标识密码生成。
  31. 如权利要求30所述的装置，其特征在于，所述客户端的校验信息根据所述客户端的随机标识密码，以及，以下信息中的至少一种生成：服务提供设备的唯一标识码和/或随机数。
  32. 如权利要求28所述的装置，其特征在于，所述校验请求中还携带有本地保存的所述服务提供设备的唯一标识码；
    所述合法性验证模块，用于接收所述服务器返回的对所述校验请求的校验结果，其中，所述校验结果包括：第二校验结果；其中，所述第二校验结果用于指示所述校验请求中携带的所述服务提供设备的唯一标识码与保存在服务器中的所述服务提供设备的唯一标识码是否匹配；其中，保存在服务器中的服务提供设备的唯一标识码为预先分配给所述客户端、且为所述客户端提供服务的服务提供设备的唯一标识码；以及，
    根据所述第二校验结果，确定所述连接请求所请求的连接是否合法。
  33. 如权利要求28所述的装置，其特征在于，所述合法性验证模块，用于接收所述服务器返回的对所述校验请求的校验结果，其中，所述校验结果包括：第三校验结果；其中，所述第三校验结果用于指示所述客户端请求的本次连接是否有效，以及，所述校验请求中携带的客户端的随机标识与保存在服务器中的客户端的随机标识是否匹配；其 中，所述保存在服务器中的客户端的随机标识为预先分配给所述客户端、用于标识所述客户端的信息；以及，
    根据所述第三校验结果，确定所述连接请求所请求的连接是否合法。
  34. 一种智能电视系统，其特征在于，所述智能电视系统包括：至少一个服务器、至少一个客户端、至少一个服务提供设备；其中，所述服务器用于向所述客户端分配服务提供设备；所述客户端设置在智能电视中，所述服务提供设备设置在网络侧，用于通过网络为建立连接的客户端提供互联网服务；
    其中，所述服务器包括权利要求19至27任一项所述的数据校验装置，所述服务提供设备包括权利要求28-33任一项所述的数据校验装置。
  35. 根据权利要求34所述的智能电视系统，其特征在于，所述智能电视系统，还包括至少一个用户数据信息存储设备；所述至少一个用户数据信息存储设备包括：至少一个用户分区；其中，所述至少一个用户分区分别用于存储不同客户端对应的用户数据。
  36. 根据权利要求34所述的智能电视系统，其特征在于，所述服务提供设备包括：网络机顶盒；所述互联网服务，包括如下中的至少一个：
    电视直播、音视频服务、网页服务、游戏服务。
PCT/CN2016/085209 2015-06-17 2016-06-08 数据校验方法、装置和智能电视系统 WO2016202200A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510338173.9 2015-06-17
CN201510338173.9A CN106331772A (zh) 2015-06-17 2015-06-17 数据校验方法、装置和智能电视系统

Publications (1)

Publication Number Publication Date
WO2016202200A1 true WO2016202200A1 (zh) 2016-12-22

Family

ID=57544880

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/085209 WO2016202200A1 (zh) 2015-06-17 2016-06-08 数据校验方法、装置和智能电视系统

Country Status (2)

Country Link
CN (1) CN106331772A (zh)
WO (1) WO2016202200A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112598400A (zh) * 2020-12-31 2021-04-02 青岛海尔科技有限公司 一种通行校验方法及装置、电子设备
CN113254893A (zh) * 2020-02-13 2021-08-13 百度在线网络技术（北京）有限公司 一种身份校验方法、装置、电子设备及存储介质

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108712657B (zh) * 2018-04-10 2020-09-04 武汉斗鱼网络科技有限公司 一种弹幕验证方法、计算机设备和存储介质
CN108897615B (zh) * 2018-05-31 2023-06-13 康键信息技术（深圳）有限公司 秒杀请求处理方法、应用服务器集群及存储介质
CN110868374A (zh) 2018-08-27 2020-03-06 京东方科技集团股份有限公司 安全认证方法、服务器及客户端设备
CN110233836B (zh) * 2019-05-31 2021-06-08 顾宏超 一种通讯验证方法、设备、系统及计算机可读存储介质
CN112533055A (zh) * 2019-09-17 2021-03-19 青岛海信传媒网络技术有限公司 一种终端交互方法、装置、视频播放设备和存储介质
CN111132076B (zh) * 2019-12-31 2024-04-09 斑马网络技术有限公司 车机通信方法、装置、车机及终端
CN111431726B (zh) * 2020-06-11 2020-09-18 深圳市友杰智新科技有限公司 算法授权方法、装置、计算机设备和存储介质
CN113497950B (zh) * 2021-06-15 2023-03-17 杭州华橙软件技术有限公司 一种流媒体直播的方法、装置及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070022473A1 (en) * 2005-07-21 2007-01-25 Arcot Systems, Inc. Server-token lockstep systems and methods
CN101527818A (zh) * 2009-04-23 2009-09-09 天柏宽带网络科技（北京）有限公司 交互式网络电视数字版权管理系统许可证管理方法
CN102378170A (zh) * 2010-08-27 2012-03-14 中国移动通信有限公司 一种鉴权及业务调用方法、装置和系统
CN103905920A (zh) * 2012-12-26 2014-07-02 中国电信股份有限公司 基于以太网动态地址接入的网络电视开通配置方法与系统
CN104113549A (zh) * 2014-07-28 2014-10-22 百度在线网络技术（北京）有限公司 一种平台授权方法、平台服务端及应用客户端和系统

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8386776B2 (en) * 2007-09-25 2013-02-26 Nec Corporation Certificate generating/distributing system, certificate generating/distributing method and certificate generating/distributing program
CN101222335A (zh) * 2008-02-02 2008-07-16 国电信息中心 一种应用系统间的级联认证方法及装置
CN102201915B (zh) * 2010-03-22 2014-05-21 中国移动通信集团公司 一种基于单点登录的终端认证方法和装置
CN104268457B (zh) * 2014-09-22 2017-07-25 联想(北京)有限公司 信息处理方法、电子设备和服务器

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070022473A1 (en) * 2005-07-21 2007-01-25 Arcot Systems, Inc. Server-token lockstep systems and methods
CN101527818A (zh) * 2009-04-23 2009-09-09 天柏宽带网络科技（北京）有限公司 交互式网络电视数字版权管理系统许可证管理方法
CN102378170A (zh) * 2010-08-27 2012-03-14 中国移动通信有限公司 一种鉴权及业务调用方法、装置和系统
CN103905920A (zh) * 2012-12-26 2014-07-02 中国电信股份有限公司 基于以太网动态地址接入的网络电视开通配置方法与系统
CN104113549A (zh) * 2014-07-28 2014-10-22 百度在线网络技术（北京）有限公司 一种平台授权方法、平台服务端及应用客户端和系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113254893A (zh) * 2020-02-13 2021-08-13 百度在线网络技术（北京）有限公司 一种身份校验方法、装置、电子设备及存储介质
CN113254893B (zh) * 2020-02-13 2023-09-19 百度在线网络技术（北京）有限公司 一种身份校验方法、装置、电子设备及存储介质
CN112598400A (zh) * 2020-12-31 2021-04-02 青岛海尔科技有限公司 一种通行校验方法及装置、电子设备

Also Published As

Publication number Publication date
CN106331772A (zh) 2017-01-11

Similar Documents

Publication Publication Date Title
WO2016202200A1 (zh) 数据校验方法、装置和智能电视系统
CN108540433B (zh) 用户身份校验方法及装置
WO2016197862A1 (zh) 一种数据传输方法、装置和智能电视系统
US20200376374A1 (en) Dynamic network storage for cloud console server
CN109951488B (zh) 内容分发网络的服务实现方法、装置、设备及存储介质
CN106301865B (zh) 应用于服务提供设备的数据处理方法和设备
CN108055575B (zh) 一种面向小区基于模拟投屏的网络视频共享系统
US9473940B2 (en) Authenticating a browser-less data streaming device to a network with an external browser
JP2013137741A (ja) アセットリース管理のためのシステム及び方法
US11889133B2 (en) Burst traffic processing method, computer device and readable storage medium
CN111643889A (zh) 一种游戏控制方法、装置、存储介质和电子设备
JP2009273105A (ja) 音声／映像ストリーム信号提供方法及び共有システム
US11743101B2 (en) Techniques for accessing logical networks via a virtualized gateway
CN105282624A (zh) 桌面云视频的播放处理方法及装置
KR20060014354A (ko) 기기 간 인증 시스템 및 기기 간 인증 방법, 통신 장치,및 컴퓨터 프로그램
CN107332894B (zh) 直播方法、装置及系统、服务器、存储介质
US8763056B2 (en) Bandwidth management for packet-based program service
KR20060008270A (ko) 기기간 인증 시스템 및 기기간 인증 방법, 통신 기기 및컴퓨터 프로그램
KR101325025B1 (ko) 셋톱박스 기반의 클라우드 서비스 방법 및 이를 위한 컴퓨터로 판독가능한 기록매체
WO2016202202A1 (zh) 设备连接的方法和装置、以及智能电视系统
US20140096154A1 (en) Integrated broadcasting communications receiver and resource managing device
WO2016202203A1 (zh) 设备连接方法、装置和智能电视系统
CN105847884B (zh) 一种控制电视用户使用电视的方法和装置
JP5941356B2 (ja) 放送通信連携受信装置、アプリケーション認証プログラム及び放送通信連携システム
CN117650903A (zh) 被控设备和设备授权管理方法、及存储介质

Legal Events

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

Ref document number: 16810941

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16810941

Country of ref document: EP

Kind code of ref document: A1