WO2015180567A1 - 一种智能显示终端与体感设备实现数据交互的方法及装置 - Google Patents

一种智能显示终端与体感设备实现数据交互的方法及装置 Download PDF

Info

Publication number
WO2015180567A1
WO2015180567A1 PCT/CN2015/078917 CN2015078917W WO2015180567A1 WO 2015180567 A1 WO2015180567 A1 WO 2015180567A1 CN 2015078917 W CN2015078917 W CN 2015078917W WO 2015180567 A1 WO2015180567 A1 WO 2015180567A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
somatosensory
display terminal
application
standardized
Prior art date
Application number
PCT/CN2015/078917
Other languages
English (en)
French (fr)
Inventor
王永
许科
Original Assignee
阿里巴巴集团控股有限公司
王永
许科
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司, 王永, 许科 filed Critical 阿里巴巴集团控股有限公司
Priority to US15/313,518 priority Critical patent/US20170188082A1/en
Publication of WO2015180567A1 publication Critical patent/WO2015180567A1/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/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/41—Structure of client; Structure of client peripherals
    • H04N21/422—Input-only peripherals, i.e. input devices connected to specially adapted client devices, e.g. global positioning system [GPS]
    • H04N21/42204—User interfaces specially adapted for controlling a client device through a remote control device; Remote control devices therefor
    • H04N21/42206—User interfaces specially adapted for controlling a client device through a remote control device; Remote control devices therefor characterized by hardware details
    • H04N21/42222—Additional components integrated in the remote control device, e.g. timer, speaker, sensors for detecting position, direction or movement of the remote control, microphone or battery charging device
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38—Information transfer, e.g. on bus
    • G06F13/382—Information transfer, e.g. on bus using universal interface adapter
    • G06F13/387—Information transfer, e.g. on bus using universal interface adapter for adaptation of different data processing systems to different peripheral devices, e.g. protocol converters for incompatible systems, open system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/017—Gesture based interaction, e.g. based on a set of recognized hand gestures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0641—Shopping interfaces
    • G06Q30/0643—Graphical representation of items or shoppers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V10/00—Arrangements for image or video recognition or understanding
    • G06V10/96—Management of image or video recognition tasks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V40/00—Recognition of biometric, human-related or animal-related patterns in image or video data
    • G06V40/20—Movements or behaviour, e.g. gesture recognition
    • 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/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/41—Structure of client; Structure of client peripherals
    • H04N21/422—Input-only peripherals, i.e. input devices connected to specially adapted client devices, e.g. global positioning system [GPS]
    • H04N21/42201—Input-only peripherals, i.e. input devices connected to specially adapted client devices, e.g. global positioning system [GPS] biosensors, e.g. heat sensor for presence detection, EEG sensors or any limb activity sensors worn by the user
    • 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/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/41—Structure of client; Structure of client peripherals
    • H04N21/422—Input-only peripherals, i.e. input devices connected to specially adapted client devices, e.g. global positioning system [GPS]
    • H04N21/42204—User interfaces specially adapted for controlling a client device through a remote control device; Remote control devices therefor
    • 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/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/41—Structure of client; Structure of client peripherals
    • H04N21/422—Input-only peripherals, i.e. input devices connected to specially adapted client devices, e.g. global positioning system [GPS]
    • H04N21/42204—User interfaces specially adapted for controlling a client device through a remote control device; Remote control devices therefor
    • H04N21/42206—User interfaces specially adapted for controlling a client device through a remote control device; Remote control devices therefor characterized by hardware details
    • H04N21/4222—Remote control device emulator integrated into a non-television apparatus, e.g. a PDA, media center or smart toy
    • 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/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
    • H04N21/43615—Interfacing a Home Network, e.g. for connecting the client to a plurality of peripherals
    • 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/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
    • H04N21/4363—Adapting the video stream to a specific local network, e.g. a Bluetooth® network
    • H04N21/43637—Adapting the video stream to a specific local network, e.g. a Bluetooth® network involving a wireless protocol, e.g. Bluetooth, RF or wireless LAN [IEEE 802.11]
    • 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/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47—End-user applications
    • H04N21/482—End-user interface for program selection
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/20—Pc systems
    • G05B2219/23—Pc programming
    • G05B2219/23021—Gesture programming, camera sees hand, displays it on screen, grasp buttons
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/35—Nc in input of data, input till input file format
    • G05B2219/35381—Convert in real time input peripheral data to processor data, ouput data format

Definitions

  • the present application relates to the technical field of intelligent display terminals, and in particular, to a method for implementing data interaction between an intelligent display terminal and a somatosensory device.
  • the present application relates to a device for realizing data interaction between an intelligent display terminal and a somatosensory device, a somatosensory device middleware for realizing data interaction between the intelligent display terminal and the somatosensory device, and a software development tool for realizing data interaction between the intelligent display terminal and the somatosensory device. package.
  • Smart TV terminal refers to a smart TV or TV box (such as: Apple TV, Xiaomi Box, LeTV TV and Facebook's Tmall Box) that can be equipped with intelligent operating systems (such as IOS system, Android system and Facebook TV OS). And other terminal equipment. While enjoying ordinary TV content, users can also install and uninstall various application software and games by themselves, and expand and upgrade the functions of the TV.
  • intelligent operating systems such as IOS system, Android system and Facebook TV OS.
  • the operating system of the smart TV terminal is derived from the smartphone operating system.
  • the operating system of the smart TV terminal only supports one set of somatosensory devices.
  • a multiplayer mode somatosensory game is first developed. Both need their specific gamepads (such as: sports plus and bully multiplayer games), the game to achieve different games by directly reading the different tag data transmitted by its gamepad to distinguish different gamepads. People mode.
  • the method for managing a somatosensory device on a smart television terminal has obvious drawbacks.
  • the software or game installed on the smart TV terminal can only perform data interaction with a specific one or several somatosensory devices, and the compatibility is poor; in addition, for software developers, it can only be developed according to a specific somatosensory device.
  • the game developed by the user can only be applied to a specific somatosensory device, and the interface is not uniform; for the user, to purchase a somatosensory device, only one or a series corresponding to the somatosensory device can be played. game, And once the game is out of date, the user wants to play other games, then the new somatosensory device must be re-purchased, and the somatosensory device is discarded, resulting in wasted resources.
  • the present invention provides a method for realizing data interaction between an intelligent display terminal and a somatosensory device, so as to solve the problem of poor compatibility and inconsistent interfaces of the existing methods.
  • the present application further provides an apparatus for realizing data interaction between an intelligent display terminal and a somatosensory device, a somatosensory device middleware for realizing data interaction between the intelligent display terminal and the somatosensory device, and a software development tool for realizing data interaction between the intelligent display terminal and the somatosensory device. package.
  • the present application provides a method for implementing data interaction between an intelligent display terminal and a somatosensory device, including:
  • the application reads the standardized somatosensory data.
  • the device data uploaded by the smart television terminal to read the somatosensory device is received by the interface driving module;
  • the interface driving module includes: a USB driver, a WIFI driver, and/or a Bluetooth driver.
  • the converting the device data into standardized somatosensory data includes:
  • the somatosensory data is converted into standardized somatosensory data based on a preset conversion algorithm.
  • the conversion algorithm is formulated for the somatosensory data format according to a relationship between a somatosensory data format and a standardized somatosensory data format.
  • the method includes:
  • the standardized somatosensory data is packaged according to a proprietary protocol to obtain a somatosensory data packet
  • the somatosensory data packet is sent to the application.
  • the application reads the standardized somatosensory data, including:
  • the application receives the somatosensory data packet
  • the application parses the somatosensory data packet according to the proprietary protocol to obtain standardized somatosensory data.
  • the application receives the somatosensory data packet, and specifically, the application receives the somatosensory data packet through an application programming interface.
  • the smart display terminal sends an instruction to the somatosensory device through the application programming interface.
  • the present application further provides an apparatus for implementing data interaction between an intelligent display terminal and a somatosensory device, including:
  • a device data reading unit configured to read device data uploaded by the somatosensory device based on the smart display terminal
  • a data conversion unit configured to convert the device data into standardized somatosensory data
  • a data invoking unit configured to implement an application to read the standardized somatosensory data.
  • the data conversion unit includes:
  • a data standard acquisition subunit configured to acquire a data format standard adopted by the somatosensory device corresponding to the device data
  • a device data parsing subunit configured to parse the device data according to the data format standard, and generate somatosensory data
  • the normalized somatosensory data generating subunit is configured to convert the somatosensory data into standardized somatosensory data based on a preset conversion algorithm.
  • the device that implements data interaction between the smart display terminal and the somatosensory device includes:
  • a data packing unit configured to package the standardized somatosensory data according to a proprietary protocol to obtain a somatosensory data packet
  • a data sending unit configured to send the somatosensory data packet to an application.
  • the data calling unit includes:
  • a data receiving subunit the application receiving the somatosensory data packet
  • a data parsing subunit the application parsing the somatosensory data packet according to the proprietary protocol to obtain standardized device data.
  • the present application further provides a somatosensory device middleware for realizing data interaction between an intelligent display terminal and a somatosensory device, comprising: a drive docking unit, a data standardization unit, a somatosensory device management unit, and a data communication unit;
  • the driving docking unit is configured to read device data uploaded by the somatosensory device based on the smart television terminal, and send a command that is downlinked by the application program;
  • the data normalization unit is configured to convert the device data into standardized somatosensory data
  • the somatosensory device management unit is configured to manage a somatosensory device that accesses the smart display terminal and device data corresponding to the somatosensory device;
  • the data communication unit performs data communication with the application based on inter-process communication.
  • the data standardization unit includes:
  • a data format standard acquisition subunit configured to acquire a data format standard adopted by the somatosensory device corresponding to the device data
  • a data parsing subunit configured to parse the device data according to the data format standard to generate somatosensory data
  • the data conversion subunit is configured to convert the somatosensory data into standardized somatosensory data based on a preset conversion algorithm.
  • the somatosensory device management unit includes:
  • a parsing subunit configured to parse the normalized somatosensory data to obtain device feature information
  • a storage subunit configured to store the normalized somatosensory data in a data storage area corresponding to the device feature information.
  • the data communication unit includes:
  • a somatosensory data packet generating subunit configured to package the standardized somatosensory data according to a proprietary protocol to obtain a somatosensory data packet;
  • a somatosensory data packet transmitting subunit configured to send the somatosensory data packet to the application
  • An instruction packet receiving subunit configured to receive an instruction data packet sent by the application
  • the instruction packet parsing subunit is configured to parse the instruction packet into standardized instruction data according to a proprietary protocol.
  • the inter-process communication includes: a message queue, a shared memory, or a Socket socket.
  • the present application further provides a software development kit for implementing data interaction between an intelligent display terminal and a somatosensory device, comprising: a data communication unit, an event management unit, a somatosensory device management unit, and an interface encapsulation unit;
  • the data communication unit performs data communication between the interprocess communication and the somatosensory device middleware
  • the event management unit implements operation control on the application program based on preset various somatosensory events
  • a somatosensory device management unit configured to manage a somatosensory device that accesses the smart display terminal and device data corresponding to the somatosensory device;
  • An interface providing unit for providing an application interface to an application.
  • the data communication unit includes:
  • a somatosensory data packet receiving subunit configured to receive a somatosensory data packet sent by the somatosensory device middleware
  • a somatosensory packet parsing subunit configured to parse the somatosensory data packet according to a proprietary protocol to obtain standardized somatosensory data
  • An instruction packet generating subunit configured to package the instruction data according to a private protocol to obtain an instruction data packet
  • An instruction packet transmission subunit configured to send the instruction data packet to the somatosensory device middleware.
  • the somatosensory device management unit includes:
  • a somatosensory event parsing subunit configured to parse the somatosensory event to obtain device feature information and standardized somatosensory data
  • a somatosensory device acquisition subunit configured to acquire, from the somatosensory device list, the somatosensory device corresponding to the device feature information according to the device feature information;
  • a data storage subunit for storing the standardized somatosensory data to the device characteristic letter The data is in the corresponding data storage area.
  • the interface providing unit includes:
  • An interface implementation subunit configured to implement the application programming interface based on the somatosensory device management unit
  • An interface encapsulation subunit configured to package the application programming interface into a library file and output the same.
  • the method for realizing data interaction between the smart display terminal and the somatosensory device provided by the present application has limited limitation and saves resources.
  • the method for implementing data interaction between the smart display terminal and the somatosensory device includes: reading device data uploaded by the somatosensory device based on the smart display terminal; converting the device data into standardized somatosensory data; and reading the standardized somatosensory by the application program data.
  • the above method provided by the present application can convert device data collected by a somatosensory device produced by different device manufacturers into standardized somatosensory data of a unified data format standard, so that an application installed on the intelligent display terminal can be compatible with different data formats produced by different device manufacturers.
  • the standard somatosensory device has good compatibility; in addition, the above method provided by the present application provides a unified interface to software developers based on the standardized somatosensory data.
  • the present application further provides a somatosensory device middleware for implementing data interaction between an intelligent display terminal and a somatosensory device, including a drive docking unit, a data standardization unit, a somatosensory device management unit, and a data communication unit;
  • the drive docking unit is configured to be based on
  • the smart television terminal reads the device data uploaded by the somatosensory device and sends a command downlinked by the application;
  • the data standardization unit is configured to convert the device data into standardized somatosensory data;
  • the somatosensory device management unit is configured to manage a somatosensory device that accesses the smart display terminal and device data corresponding to the somatosensory device;
  • the data communication unit performs data communication with the application program based on inter-process communication.
  • the somatosensory device middleware converts the device data uploaded by the somatosensory device of different data format standards produced by different device manufacturers into the standardized somatosensory data of the unified data format standard, and the application program calls to make the application compatible. Produced by different equipment manufacturers Somatosensory devices with different data format standards have good compatibility.
  • the present application further provides a software development kit for implementing data interaction between an intelligent display terminal and a somatosensory device, comprising a data communication unit, an event management unit, a somatosensory device management unit, an interface encapsulation unit, and the data communication unit, based on the process Data communication between the communication and the somatosensory device middleware; the event management unit implements operation control of the application program based on preset various somatosensory events; and the somatosensory device management unit is configured to manage access to the smart display a somatosensory device of the terminal and device data corresponding to the somatosensory device; and an interface providing unit for providing an application program interface to the application.
  • the software development toolkit provided by the present application provides a unified application program interface to software developers based on standardized somatosensory data of a unified data format standard, thereby preventing software developers from developing the same software or game for different data format standards. Corresponding software or games save resources.
  • FIG. 1 is a flowchart of a method for implementing data interaction between an intelligent display terminal and a somatosensory device according to the first embodiment of the present application.
  • FIG. 2 is a schematic diagram of an apparatus for implementing data interaction between an intelligent display terminal and a somatosensory device according to a second embodiment of the present application.
  • FIG. 3 is a schematic diagram of a somatosensory device middleware for implementing data interaction between an intelligent display terminal and a somatosensory device according to a third embodiment of the present application.
  • FIG. 4 is a schematic diagram of a software development kit for implementing data interaction between an intelligent display terminal and a somatosensory device according to a fourth embodiment of the present application.
  • the present application provides a method for realizing data interaction between an intelligent display terminal and a somatosensory device, and the present application further provides a device for realizing data interaction between an intelligent display terminal and a somatosensory device, and is used for intelligence.
  • FIG. 1 it is a flowchart of a method for implementing data interaction between a smart display terminal and a somatosensory device according to a first embodiment of the present application.
  • S101 Read device data uploaded by the somatosensory device based on the smart display terminal.
  • the smart display terminal refers to a device terminal for playing a display function, and can be installed to run a smart operating system and an application, such as a smart TV terminal and a PC;
  • the somatosensory device includes a somatosensory handle, a smart mobile terminal, and a wearable
  • the device data includes data collected by sensors built in the somatosensory device, and further includes device information data (device ID of the somatosensory device, device manufacturer ID, device name, and sensor model, type, etc.).
  • a smart TV terminal is taken as an example for description.
  • Other types of intelligent display terminals are similar to the smart TV terminal.
  • the following embodiments provide a method for realizing data interaction between the smart display terminal and the somatosensory device. Not listed one by one.
  • the process of uploading the device data by the somatosensory device includes the following two steps: 1) the somatosensory device collects device data, and the somatosensory device collects through the built-in sensor. Device data of the current somatosensory device; 2) the somatosensory device uploads the device data to the smart TV terminal.
  • the device data uploaded by the somatosensory device is read based on the smart display terminal.
  • the device data uploaded by the smart television terminal to be read by the somatosensory device is received by the interface driving module, wherein the interface driving module comprises: a USB driver, a WIFI driver, and a Bluetooth driver.
  • the converting the device data into standardized somatosensory data includes:
  • the device data includes data collected by sensors built in the somatosensory device and device information data
  • the device information data includes: a device ID of the somatosensory device, a device manufacturer ID, a device name, and a sensor model and type.
  • the data format standards of the corresponding device data may also be different.
  • the data format standard corresponding to the somatosensory device provided by the somatosensory equipment factory or the data format standard corresponding to the sensor built in the somatosensory device provided by the sensor manufacturer is obtained in advance, and the data format standard is stored.
  • the somatosensory data refers to data capable of characterizing the motion characteristics of the somatosensory device; the purpose of this step is to convert the data collected by the sensors built in the somatosensory device of the device data into analytically calculated to be able to characterize the motion characteristics of the somatosensory device or the user's somatosensory action. Somatosensory data.
  • the standardized data refers to somatosensory data that characterizes the motion characteristics of the somatosensory device or the user's somatosensory motion based on a unified standard; the purpose of this step is to convert the somatosensory data of different data format standards into the somatosensory data of the unified data format standard, that is, standardize the sense of body. Data; the conversion algorithm is formulated based on a relationship between a data format standard of the somatosensory data and a data format standard of standardized somatosensory data.
  • the standardized somatosensory data is transmitted to the application.
  • S103 The standardized somatosensory data is packaged according to a proprietary protocol to obtain a somatosensory data packet.
  • the standardized somatosensory data is packaged according to a proprietary protocol to obtain a somatosensory data packet; after the somatosensory data packet is obtained, the somatosensory data packet is transmitted to the application.
  • the standardized somatosensory data according to the steps described in this step is The packaging of the private protocol is not the focus of this embodiment, and will not be described here.
  • S104 Send the somatosensory data packet to an application.
  • Sending the somatosensory data packet to the application is implemented based on an inter-process communication manner, and the inter-process communication manner includes: a message queue, a shared memory, and a Socket socket.
  • the method for transmitting the somatosensory data packet to the application may be implemented in a manner other than the embodiment, which is not limited herein.
  • the application receives the somatosensory data packet.
  • the application receives the somatosensory data packet transmitted by the inter-process communication method, and after receiving the somatosensory data packet, parses the somatosensory data packet into standardized device data.
  • S106 The application parses the somatosensory data packet according to a proprietary protocol to obtain standardized somatosensory data.
  • the middle between the somatosensory device middleware and the application is achieved.
  • a unified standard for data namely: a proprietary protocol.
  • a private protocol is established between the somatosensory device middleware and the application program to ensure that the application can acquire the complete information contained in the data information based on the private protocol, and the somatosensory device middleware can be obtained based on the private protocol.
  • the complete information contained in the instruction information avoids data loss.
  • the application After receiving the somatosensory data packet according to the application described in the above step S105, the application parses the somatosensory data packet according to the private protocol to obtain standardized device data.
  • a method for realizing data interaction between the smart display terminal and the somatosensory device is provided.
  • the present application further provides an apparatus for realizing data interaction between the smart display terminal and the somatosensory device.
  • FIG. 2 a schematic diagram of an apparatus for implementing data interaction between a smart display terminal and a somatosensory device according to a second embodiment of the present application is shown.
  • the device for implementing data interaction between the smart display terminal and the somatosensory device described in the present application includes:
  • the device data reading unit 201 is configured to read device data uploaded by the somatosensory device based on the smart display terminal;
  • a data conversion unit 202 configured to convert the device data into standardized somatosensory data
  • the data invoking unit 205 is configured to implement an application to read the standardized somatosensory data.
  • the data conversion unit 202 includes:
  • a data standard obtaining sub-unit 202-1 configured to acquire a data format standard adopted by the somatosensory device corresponding to the device data;
  • the device data parsing sub-unit 202-1 is configured to parse the device data according to the data format standard to generate somatosensory data
  • the standardized somatosensory data generating sub-unit 202-3 is configured to convert the somatosensory data into standardized somatosensory data based on a preset conversion algorithm.
  • the device that implements data interaction between the smart display terminal and the somatosensory device includes:
  • a data packing unit 203 configured to package the standardized somatosensory data according to a proprietary protocol, to obtain a somatosensory data packet;
  • the data sending unit 204 is configured to send the somatosensory data packet to an application.
  • the data invoking unit 205 includes:
  • the data receiving subunit 205-1 the application receives the somatosensory data packet
  • the data parsing subunit 205-2 the application parses the somatosensory data packet according to the private protocol to obtain standardized device data.
  • an intelligent display terminal and a somatosensory device are provided for data communication.
  • the present application further provides a somatosensory device middleware for realizing data interaction between the smart display terminal and the somatosensory device, which is used in the method for realizing data interaction between the smart display terminal and the somatosensory device.
  • a step of converting the device data into standardized somatosensory data and a step of implementing an intelligent display terminal to send an instruction to the somatosensory device through the application programming interface.
  • FIG. 3 a schematic diagram of a somatosensory device middleware for implementing data interaction between an intelligent display terminal and a somatosensory device according to a third embodiment of the present application is shown.
  • the function of the somatosensory device middleware is to convert the device data uploaded by the somatosensory device into standardized somatosensory data having a unified data format; if the somatosensory device middleware is not available, even if the application can directly read based on the smart display device
  • the device data uploaded by the somatosensory device is obtained, and the device data of different data format standards cannot be recognized, and the data cannot be called; the application cannot perform data interaction with the somatosensory device, and the smart display terminal and the somatosensory device implement data interaction method. can not achieve.
  • the somatosensory device middleware has an indispensable effect on the implementation of the method for realizing data interaction between the smart display terminal and the somatosensory device.
  • the somatosensory device middleware for implementing data interaction between the smart display terminal and the somatosensory device comprises: a drive docking unit 301, a data normalization unit 302, a somatosensory device management unit 303, and a data communication unit 304.
  • Driving the docking unit 301 configured to read device data uploaded by the somatosensory device based on the smart television terminal, and send a command that is downlinked by the application;
  • the device data includes data collected by sensors built in the somatosensory device and device information data
  • the device information data includes: a device ID of the somatosensory device, a device manufacturer ID, a device name, and a sensor model and type.
  • the data format standards of the corresponding device data may also be different.
  • the drive docking unit 301 serves as an interface between the somatosensory device and the smart display terminal, and the interface is implemented by an interface driver, which includes: a USB driver, a WIFI driver, and a Bluetooth driver; and, in addition, other drivers may be included.
  • an interface driver which includes: a USB driver, a WIFI driver, and a Bluetooth driver; and, in addition, other drivers may be included.
  • infrared driving, etc. is not limited herein.
  • the driving device provides data communication between the somatosensory device and the smart display terminal.
  • the somatosensory device uploads device data collected by itself to the smart display terminal through a USB interface.
  • the process of uploading device data to the smart display terminal and the somatosensory device to upload the device data to the smart display terminal through the USB interface is similar to the process of uploading the device data by using the WIFI driver and the Bluetooth driver, and details are not described herein.
  • the data normalization unit 302 is configured to convert the device data into standardized somatosensory data
  • the somatosensory device middleware After the somatosensory device middleware receives the device data uploaded by the somatosensory device based on the drive docking unit 301, the somatosensory device middleware reads the device data based on the data normalization unit 302, and converts the device data into standardized somatosensory data.
  • the standardized somatosensory data refers to data generated after converting device data of different data format standards corresponding to different somatosensory devices based on a unified data format standard.
  • the data normalization unit 302 includes: a data format standard acquisition subunit 302-1, a data parsing subunit 302-2, and a data conversion subunit 302-3;
  • a data format standard obtaining sub-unit 302-1 configured to acquire a data format standard adopted by the somatosensory device corresponding to the device data;
  • the data normalization unit 302 needs to convert the device data uploaded by the somatosensory device into standardized somatosensory data.
  • An important premise is that the data standardization unit 302 can first identify device data of different data format standards uploaded by different somatosensory devices.
  • the data format standard acquisition subunit 302-1 of the data standardization unit 302 acquires and stores the data format standard corresponding to the somatosensory device provided by the different somatosensory equipment factory; and acquires the physical sense provided by the different somatosensory equipment factory. After the data format standard corresponding to the device, the data normalization unit 302 can identify the device data uploaded by the somatosensory device, and complete the data preparation premise of converting the device data into standardized somatosensory data.
  • the data parsing sub-unit 302-2 is configured to parse the device data according to the data format standard to generate somatosensory data
  • the somatosensory data refers to data capable of characterizing the motion (ie, user's somatosensory motion) characteristics of the somatosensory device.
  • the data parsing sub-unit 302-2 acquires a data format standard corresponding to the somatosensory device provided by the somatosensory equipment factory acquired by the sub-unit 302-1 based on the data format standard to the device. The data is parsed, and the parsed device data is converted into somatosensory data through analysis and calculation.
  • the somatosensory data corresponds to the data format standard, that is, one somatosensory device corresponds to one type of data format standard somatosensory data, and the data format standards of the somatosensory data corresponding to different somatosensory devices are different from each other. .
  • the data conversion subunit 302-3 is configured to convert the somatosensory data into standardized somatosensory data based on a preset conversion algorithm.
  • the standardized somatosensory data refers to the somatosensory data of the somatosensory device motion feature or the user's somatosensory motion based on the unified standard, that is, the somatosensory data obtained by the data parsing subunit 302-2 to different data format standards is converted into a unified standard based Somatosensory data.
  • the data conversion sub-unit 302-3 converts the somatosensory data into a unified standard amount of somatosensory data based on a preset conversion algorithm, that is, normalized somatosensory data.
  • the conversion algorithm is formulated based on a relationship between a data format standard of the somatosensory data and a data format standard of standardized somatosensory data.
  • the somatosensory device management unit 303 is configured to manage a somatosensory device that accesses the smart display terminal or device data corresponding to the somatosensory device;
  • the somatosensory device management unit 303 includes a parsing subunit 303-1 and a storage subunit 303-2.
  • the parsing subunit 303-1 performs parsing based on the normalized somatosensory data to obtain device feature information
  • the device data includes data collected by sensors built in the somatosensory device and device information data. Further, the standardized somatosensory data also includes data collected by the sensor and device information data; the device information data includes: a device ID of the somatosensory device, Device manufacturer ID, device name, and sensor model and type.
  • the device feature information refers to device data information capable of determining a somatosensory device, such as a device ID of a somatosensory device.
  • the storage subunit 303-2 is configured to store the normalized somatosensory data into a data storage area corresponding to the device feature information.
  • the function of the storage sub-unit 303-2 is to store different standardized somatosensory data into different data storage areas; and, for the data storage area corresponding to the same device feature information, The standardized somatosensory data stored in it remains updated.
  • the standardized somatosensory data stored in the data storage area is updated with the new standardized somatosensory data to update the data.
  • the data storage area corresponds to the device ID of the somatosensory device, and one device ID corresponds to one data storage area.
  • the data storage area may be a storage area in the database; other data storage units may be used, which are not limited herein.
  • the data communication unit 304 performs data communication with the application based on inter-process communication.
  • the somatosensory device middleware runs in a separate process; likewise, the application runs in a separate process, and in order to implement data communication between the somatosensory device middleware and the application, inter-process communication is adopted.
  • inter-process communication mode includes: a message queue, a shared memory, and a Socket socket.
  • the method may be implemented in other manners, which is not limited herein.
  • the data communication unit 304 includes: a somatosensory data packet generation subunit 304-1, a somatosensory data packet transmission subunit 304-2, an instruction data packet reception subunit 304-3, and an instruction packet analysis subunit 304-4;
  • the somatosensory data packet generation subunit 304-1 is configured to package the standardized somatosensory data according to a proprietary protocol to obtain a somatosensory data packet;
  • the somatosensory device middleware and the application program A unified standard for achieving data, namely: a proprietary agreement.
  • a private protocol is established between the somatosensory device middleware and the application program to ensure that the application can acquire the complete information contained in the data information based on the private protocol. And the somatosensory device middleware can acquire the complete information contained in the instruction information based on the private protocol, thereby avoiding data loss.
  • the somatosensory device middleware After the somatosensory device middleware and the application program reach a private agreement, the somatosensory device middleware packages the standardized data according to the proprietary protocol, and generates a somatosensory data packet;
  • the somatosensory device middleware After acquiring the somatosensory data packet, the somatosensory device middleware sends the somatosensory data packet to the application;
  • the application After receiving the somatosensory data packet, the application parses the somatosensory data packet according to the private protocol, obtains standardized somatosensory data, and performs related operations;
  • the application package the instruction data according to the private protocol, and generate an instruction data packet;
  • the application data packet is sent to the somatosensory device middleware;
  • the somatosensory device middleware After receiving the instruction data packet, the somatosensory device middleware parses the instruction data packet according to the proprietary protocol to obtain standardized instruction data.
  • a somatosensory data packet sending subunit 304-2 configured to send the somatosensory data packet to the application
  • An instruction packet receiving subunit 304-3 configured to receive an instruction data packet sent by the application
  • the instruction packet parsing subunit 304-4 is configured to parse the instruction packet into standardized instruction data according to a proprietary protocol.
  • the somatosensory packet transmission subunit 304-2, the instruction packet receiving subunit 304-3, and the instruction packet parsing subunit 304-4 may be referred to the description of the somatosensory packet generation subunit 304-1 described above, and Let me repeat.
  • the application cannot be compatible with the somatosensory device, and is provided by a certain device manufacturer.
  • a certain type of somatosensory device only the corresponding one or a series of games can be compatible with the somatosensory device, and other applications or third-party applications cannot be compatible with the somatosensory device; for example, Nintendo and
  • the game controller can only install the game program specially developed for the game machine. Most of the game programs on the market cannot be installed or cannot be implemented.
  • the somatosensory device middleware provided in this embodiment acquires the somatosensory device of different device manufacturers.
  • the data format standard adopted by the device data is then converted into the somatosensory data representing the motion characteristics of the somatosensory device according to the data format standard, and the somatosensory data is converted into the standardized somatosensory data having the unified data format according to a preset conversion algorithm.
  • the data transmission format of the somatosensory device is unified, and finally, the standardized somatosensory data is provided to the application, so that the application can be compatible with the somatosensory devices produced by different manufacturers.
  • a method for implementing data interaction between an intelligent display terminal and a somatosensory device, and a somatosensory device middleware for realizing data interaction between the smart display terminal and the somatosensory device are provided for the above intelligent display terminal.
  • the present application further provides a software development toolkit for implementing data interaction between the smart display terminal and the somatosensory device, which is used to match the somatosensory device middleware for realizing data interaction between the smart display terminal and the somatosensory device.
  • the function of the somatosensory device middleware is to convert the device data uploaded by the somatosensory device into standardized somatosensory data having a unified data format;
  • the function of the software development kit is to provide the software developer with the somatosensory device. Development criteria and basis for software (applications and games), and an interface tool for the software to invoke the standardized somatosensory data.
  • FIG. 4 a schematic diagram of a software development kit for implementing data interaction between an intelligent display terminal and a somatosensory device according to a fourth embodiment of the present application is shown.
  • the software development kit includes a data communication unit 401, an event management unit 402, a somatosensory device management unit 403, and an interface encapsulation unit 404;
  • the software development kit refers to monitoring, reading, operating, and managing intelligence.
  • a set of application development interfaces (APIs) that display the somatosensory devices on the terminal and the corresponding data of the somatosensory devices.
  • APIs application development interfaces
  • the actual form that is ultimately provided is a number of application library files, and the application (including the game) can invoke the application provided by the software development kit.
  • Program development interface is a set of application development interfaces (APIs) that display the somatosensory devices on the terminal and the corresponding data of the somatosensory devices.
  • Program development interface Program development interface.
  • the software development kit itself does not run as a separate process, but only runs in the application process that invokes it, and the somatosensory device middleware runs in an independent process.
  • the somatosensory device middleware and the software development kit implement data communication through an inter-process communication manner, and the inter-process communication manner includes: a message queue, a shared memory, and a Socket socket.
  • the inter-process communication manner includes: a message queue, a shared memory, and a Socket socket.
  • it can also be implemented in other manners, which is not limited herein.
  • the data communication unit 401 performs data communication between the inter-process communication and the somatosensory device middleware;
  • the somatosensory device middleware runs in a separate process; likewise, the application runs in a separate process, and in order to implement data communication between the somatosensory device middleware and the application, inter-process communication is adopted.
  • inter-process communication mode includes: a message queue, a shared memory, and a Socket socket.
  • the method may be implemented in other manners, which is not limited herein.
  • the data communication unit 401 includes: a somatosensory packet receiving subunit 401-1, a somatosensory packet parsing subunit 401-2, an instruction packet generating subunit 401-3, and an instruction packet transmitting subunit 401-4;
  • the somatosensory data packet receiving subunit 401-1 is configured to receive the somatosensory data packet sent by the somatosensory device middleware;
  • the somatosensory device middleware and the application program A unified standard for achieving data, namely: a proprietary agreement.
  • a private agreement is established between the somatosensory device middleware and the application to ensure that The program can acquire the complete information contained in the data information based on the private protocol, and the somatosensory device middleware can acquire the complete information contained in the instruction information based on the private protocol, thereby avoiding data loss.
  • the somatosensory device middleware After the somatosensory device middleware and the application program reach a private agreement, the somatosensory device middleware packages the standardized data according to the proprietary protocol, and generates a somatosensory data packet;
  • the somatosensory device middleware After acquiring the somatosensory data packet, the somatosensory device middleware sends the somatosensory data packet to the application;
  • the application After receiving the somatosensory data packet, the application parses the somatosensory data packet according to the private protocol, obtains standardized somatosensory data, and performs related operations;
  • the application package the instruction data according to the private protocol, and generate an instruction data packet;
  • the application data packet is sent to the somatosensory device middleware;
  • the somatosensory device middleware After receiving the instruction data packet, the somatosensory device middleware parses the instruction data packet according to the private protocol, obtains the instruction data, and performs related operations.
  • the somatosensory packet parsing subunit 401-2 is configured to parse the somatosensory data packet according to a proprietary protocol to obtain standardized somatosensory data;
  • the instruction packet generating subunit 401-3 is configured to package the instruction data according to a private protocol to obtain an instruction data packet;
  • the instruction packet transmitting subunit 401-4 is configured to send the instruction data packet to the somatosensory device middleware.
  • the somatosensory packet analysis subunit 401-2, the instruction packet generation subunit 401-3, and the instruction packet transmission subunit 401-4 can be referred to the description of the somatosensory packet receiving subunit 401-1, and Let me repeat.
  • the event management unit 402 implements operation control of the application based on preset various types of somatosensory events; the event is a mechanism for communication between objects. There are many kinds of events, such as mouse click events, mouse movement events, and button click events. The purpose of the event is to help the user complete what the user wants to accomplish; for example:
  • mouse click event For a mouse click event, after a mouse click, certain actions will occur, such as windowing, refreshing the page, or submitting data. At this point, clicking the mouse triggers a mouse click event. The events are all corresponding. For a mouse click event, the mouse click event is triggered only after the mouse click is executed, and the method or attribute in the mouse click event is executed.
  • the step of the event management unit 402 implementing the operation control of the application based on the preset various types of somatosensory events is as follows:
  • the somatosensory events include: a button event, a sensor event, and/or an air mouse event.
  • event management unit 402 may also be implemented by using an event implementation method other than the embodiment, such as an implementation of a C# event, which is not limited herein.
  • the somatosensory device management unit 403 is configured to manage a somatosensory device that accesses the smart display terminal or device data corresponding to the somatosensory device;
  • the somatosensory device management unit 403 includes a somatosensory event parsing subunit 403-1, a somatosensory device acquisition subunit 403-2, and a data storage subunit 4033.
  • the somatosensory event parsing sub-unit 403-1 is configured to parse the somatosensory event to obtain device feature information and standardized somatosensory data;
  • the somatosensory event parsing sub-unit 403-1 parses the somatosensory event, and simultaneously obtains the device corresponding to the somatosensory event. Feature information and standardized somatosensory data.
  • the somatosensory device acquisition sub-unit 403-2 is configured to acquire, from the somatosensory device list, the somatosensory device corresponding to the device feature information according to the device feature information;
  • the list of somatosensory devices refers to a list of somatosensory devices composed of all the somatosensory devices that access the smart display terminal.
  • the somatosensory event parsing sub-unit 403-1 obtains device feature information and normalized somatosensory data by parsing the somatosensory event, and the somatosensory device acquiring sub-unit 403-2 queries and acquires the device feature information from the somatosensory device list based on the device feature information.
  • the somatosensory device acquisition subunit 403-2 queries the somatosensory device corresponding to the ID from the somatosensory device list based on the somatosensory device ID.
  • the data storage sub-unit 4033 is configured to store the normalized somatosensory data into a data storage area corresponding to the device feature information.
  • the function of the data storage sub-unit 4033 is to store different standardized somatosensory data into different data storage areas; and the normalized somatosensory data stored in the data storage area corresponding to the same device feature information is kept updated.
  • the standardized somatosensory data stored in the data storage area is updated with the new standardized somatosensory data to realize Update of the data.
  • the data storage area corresponds to the device ID of the somatosensory device, and one device ID corresponds to one data storage area.
  • the data storage area may be a storage area in the database; other data storage units may be used, which are not limited herein.
  • the data storage subunit 4033, the somatosensory device acquisition subunit 403-2, and the somatosensory event parsing subunit 403-1 jointly maintain the somatosensory device list;
  • the somatosensory event parsing sub-unit 403-1 first parses the triggered somatosensory event in the event management unit 402, and obtains device feature information and normalized somatosensory data corresponding to the somatosensory event;
  • the somatosensory device acquisition sub-unit 403-2 queries and acquires the somatosensory device corresponding to the device feature information from the somatosensory device list based on the device feature information;
  • the data storage sub-unit 4033 stores the normalized somatosensory data in a data storage area corresponding to the device feature information, where the data storage area may be a storage area in a database; or may be other data storage Units are not limited here.
  • the interface providing unit 404 is configured to provide an application program interface to the application.
  • the interface providing unit 404 includes an interface implementation subunit 404-1 and an interface encapsulation subunit 404-2;
  • the interface implementation subunit 404-1 implementing the application programming interface based on the somatosensory device management unit 403;
  • the application programming interface can be implemented based on different programming languages, such as: Java, C, C++, and the like.
  • the interface encapsulation subunit 404-2 is configured to package and compile the application programming interface into a library file and output the same.
  • the software development kit is interface-encapsulated according to different application language environments, such as Java, C, and C++, and The software development kit is ultimately provided externally as an application library file.
  • API application development interface
  • the somatosensory device management unit 403 is written in the C/C++ language. Therefore, encapsulation into the Java language requires Java JNI calls.
  • API application development interface
  • the function of the application module for the application software to be packaged into a plurality of languages is implemented by the interface encapsulation unit 404, which is not limited herein.
  • a software development kit provides a unified application development interface for developers to use, and developers use the software development toolkit to develop a solution. Some applications are compatible with somatosensory devices.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media including both permanent and non-persistent, removable and non-removable media may be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include non-transitory computer readable media, such as modulated data signals and carrier waves.
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Human Computer Interaction (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Business, Economics & Management (AREA)
  • General Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Chemical & Material Sciences (AREA)
  • Analytical Chemistry (AREA)
  • Biomedical Technology (AREA)
  • Biophysics (AREA)
  • Neurosurgery (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Psychiatry (AREA)
  • Social Psychology (AREA)
  • User Interface Of Digital Computer (AREA)
  • Information Transfer Between Computers (AREA)
  • Telephonic Communication Services (AREA)

Abstract

本申请公开了一种智能显示终端与体感设备实现数据交互的方法，包括：基于智能显示终端读取体感设备上传的设备数据；将所述设备数据转化为标准化体感数据；应用程序读取所述标准化体感数据。本申请提供的上述智能显示终端与体感设备实现数据交互的方法，智能显示终端上安装的应用程序能够兼容不同设备厂商生产的不同数据格式标准的体感设备；并且向软件开发者提供了统一的接口，使体感设备与应用程序之间能够相互兼容，兼容性好。

Description

一种智能显示终端与体感设备实现数据交互的方法及装置 技术领域
本申请涉及智能显示终端技术领域，具体涉及一种智能显示终端与体感设备实现数据交互的方法。本申请同时涉及一种智能显示终端与体感设备实现数据交互的装置、用于智能显示终端与体感设备实现数据交互的体感设备中间件和用于智能显示终端与体感设备实现数据交互的软件开发工具包。
背景技术
智能电视终端，是指能够搭载智能操作系统(比如：IOS系统、Android系统和阿里巴巴TV OS)的智能电视或者电视盒子(比如：Apple TV、小米盒子、乐视TV和阿里巴巴的天猫魔盒)等终端设备。用户在欣赏普通电视内容的同时，还可以自行安装和卸载各类应用软件和游戏，对电视的功能进行扩充和升级。今年来，随着智能电视的迅速发展，各种应用于智能电视的各种应用程序也得到了快速的发展，尤其表现为游戏的多样化和丰富化；此外，为了满足用户在智能电视上的游戏需求，出现了各种各样专门适配于智能电视应用程序的外设产品，比如：手柄、遥控器、鼠标和体感设备(通过内置传感器检测用户动作或者状态的设备)。
现有技术下，智能电视终端的操作系统源于智能手机操作系统，一般来说，智能电视终端的操作系统只支持一套体感设备，为了实现多人游戏，首先开发出多人模式的体感游戏，都需要其特定的游戏手柄(比如：运动加加和小霸王的多人游戏)，游戏通过直接读取其游戏手柄传输的不同标记的数据来区分不同游戏手柄，以此实现支持游戏的多人模式。
上述现有技术提供的智能电视终端上管理体感设备的方法具有明显的缺陷。现有技术下，智能电视终端上安装的软件或者游戏只能与特定的一款或者几款体感设备实现数据交互，兼容性差；此外，对于软件开发人员来说，只能根据特定的体感设备开发出一个或者一个系列的游戏，用户开发出来的游戏只能适用于特定的体感设备，接口不统一；对于用户来说，购买一款体感设备，只能玩该体感设备对应的一款或者一个系列的游戏， 并且一旦该游戏过时，用户想要进行其它的游戏，则必须重新购买新的体感设备，该体感设备被丢弃，造成资源浪费。
发明内容
本申请提供一种智能显示终端与体感设备实现数据交互的方法，以解决现有的方法存在的兼容性差和接口不统一的问题。本申请另外提供一种智能显示终端与体感设备实现数据交互的装置、用于智能显示终端与体感设备实现数据交互的体感设备中间件和用于智能显示终端与体感设备实现数据交互的软件开发工具包。
本申请提供一种智能显示终端与体感设备实现数据交互的方法，包括：
基于智能显示终端读取体感设备上传的设备数据；
将所述设备数据转化为标准化体感数据；
应用程序读取所述标准化体感数据。
可选的，所述基于智能电视终端读取体感设备上传的设备数据，是通过接口驱动模块接收；
其中，所述接口驱动模块包括：USB驱动、WIFI驱动和/或蓝牙驱动。
可选的，所述将所述设备数据转化为标准化体感数据，包括：
获取所述设备数据对应的体感设备采用的数据格式标准；
根据所述数据格式标准解析所述设备数据，生成体感数据；
基于预设的转换算法将所述体感数据转换为标准化体感数据。
可选的，所述转换算法是根据体感数据格式与标准化体感数据格式之间的关系，为所述体感数据格式制定的。
可选的，所述应用程序读取所述标准化体感数据之前，包括：
将所述标准化体感数据按照私有协议打包，获得体感数据包；
将所述体感数据包发送至应用程序。
可选的，所述应用程序读取所述标准化体感数据，包括：
应用程序接收所述体感数据包；
所述应用程序按照所述私有协议对所述体感数据包进行解析，获得标准化体感数据。
可选的，所述应用程序接收所述体感数据包，具体是，所述应用程序通过应用程序编程接口接收所述体感数据包。
可选的，所述智能显示终端通过所述应用程序编程接口，向所述体感设备发送指令。
本申请另外提供一种智能显示终端与体感设备实现数据交互的装置，包括：
设备数据读取单元，用于基于智能显示终端读取体感设备上传的设备数据；
数据转化单元，用于将所述设备数据转化为标准化体感数据；
数据调用单元，用于实现应用程序读取所述标准化体感数据。
可选的，所述数据转化单元包括：
数据标准获取子单元，用于获取所述设备数据对应的体感设备采用的数据格式标准；
设备数据解析子单元，用于根据所述数据格式标准解析所述设备数据，生成体感数据；
标准化体感数据生成子单元，用于基于预设的转换算法将所述体感数据转换为标准化体感数据。
可选的，所述智能显示终端与体感设备实现数据交互的装置，包括：
数据打包单元，用于将所述标准化体感数据按照私有协议打包，获得体感数据包；
数据发送单元，用于将所述体感数据包发送至应用程序。
可选的，所述数据调用单元，包括：
数据接收子单元，应用程序接收所述体感数据包；
数据解析子单元，所述应用程序按照所述私有协议对所述体感数据包进行解析，获得标准化设备数据。
本申请还提供一种用于智能显示终端与体感设备实现数据交互的体感设备中间件，包括：驱动对接单元，数据标准化单元，体感设备管理单元，数据通信单元；
所述驱动对接单元，用于基于智能电视终端读取体感设备上传的设备数据，以及发送由应用程序下行的命令；
所述数据标准化单元，用于将所述设备数据转化为标准化体感数据；
所述体感设备管理单元，用于管理接入所述智能显示终端的体感设备以及该体感设备对应的设备数据；
所述数据通信单元，基于进程间通信与所述应用程序之间进行数据通信。
可选的，所述数据标准化单元包括：
数据格式标准获取子单元，用于获取所述设备数据对应的体感设备采用的数据格式标准；
数据解析子单元，用于根据所述数据格式标准解析所述设备数据，生成体感数据；
数据转换子单元，用于基于预设的转换算法将所述体感数据转换为标准化体感数据。
可选的，所述体感设备管理单元包括：
解析子单元，用于对所述标准化体感数据进行解析，获得设备特征信息；
存储子单元，用于将所述标准化体感数据存储到所述设备特征信息对应的数据存储区域中。
可选的，所述数据通信单元包括：
体感数据包生成子单元，用于将所述标准化体感数据按照私有协议打包，获得体感数据包；
体感数据包发送子单元，用于将所述体感数据包发送至所述应用程序；以及
指令数据包接收子单元，用于接收所述应用程序发送的指令数据包；
指令数据包解析子单元，用于将所述指令数据包按照私有协议解析为标准化的指令数据。
可选的，所述进程间通信包括：消息队列、共享内存或Socket套接字。
本申请还提供一种用于智能显示终端与体感设备实现数据交互的软件开发工具包，包括：数据通信单元，事件管理单元，体感设备管理单元，接口封装单元；
所述数据通信单元，基于进程间通信与体感设备中间件之间进行数据通信；
所述事件管理单元，基于预设的各类体感事件实现对所述应用程序的操作控制；
体感设备管理单元，用于管理接入所述智能显示终端的体感设备以及该体感设备对应的设备数据；
接口提供单元，用于向应用程序提供应用程序接口。
可选的，所述数据通信单元包括：
体感数据包接收子单元，用于接收所述体感设备中间件发送的体感数据包；
体感数据包解析子单元，用于将所述体感数据包按照私有协议进行解析，获得标准化体感数据；
指令数据包生成子单元，用于将所述指令数据按照私有协议打包，获得指令数据包；
指令数据包发送子单元，用于将所述指令数据包发送至所述体感设备中间件。
可选的，所述体感设备管理单元包括：
体感事件解析子单元，用于对所述体感事件进行解析，获得设备特征信息和标准化体感数据；
体感设备获取子单元，用于根据所述设备特征信息从体感设备列表中获取该设备特征信息对应的体感设备；
数据存储子单元，用于将所述标准化体感数据存储到所述设备特征信 息对应的数据存储区域中。
可选的，所述接口提供单元包括：
接口实现子单元，基于所述体感设备管理单元实现所述应用程序编程接口；
接口封装子单元，用于将所述应用程序编程接口打包编译成库文件并输出。
与现有技术相比，本申请具有以下优点:
本申请提供的智能显示终端与体感设备实现数据交互的方法，局限性小，节省资源。
本申请提供的智能显示终端与体感设备实现数据交互的方法，包括：基于智能显示终端读取体感设备上传的设备数据；将所述设备数据转化为标准化体感数据；应用程序读取所述标准化体感数据。
本申请提供的上述方法，能够将不同设备厂商生产的体感设备采集的设备数据转换为统一数据格式标准的标准化体感数据，使智能显示终端上安装的应用程序能够兼容不同设备厂商生产的不同数据格式标准的体感设备，兼容性好；此外，本申请提供的上述方法基于所述标准化体感数据向软件开发者提供统一的接口。
本申请另外提供一种用于智能显示终端与体感设备实现数据交互的体感设备中间件，包括驱动对接单元，数据标准化单元，体感设备管理单元，数据通信单元；所述驱动对接单元，用于基于智能电视终端读取体感设备上传的设备数据，以及发送由应用程序下行的命令；所述数据标准化单元，用于将所述设备数据转化为标准化体感数据；所述体感设备管理单元，用于管理接入所述智能显示终端的体感设备以及该体感设备对应的设备数据；所述数据通信单元，基于进程间通信与所述应用程序之间进行数据通信。
本申请提供的所述体感设备中间件，将不同设备厂商生产的不同数据格式标准的体感设备上传的设备数据转化为统一的数据格式标准的标准化体感数据，供应用程序调用，使应用程序能够兼容不同设备厂商生产的 不同数据格式标准的体感设备，兼容性好。
本申请还提供一种用于智能显示终端与体感设备实现数据交互的软件开发工具包，包括数据通信单元，事件管理单元，体感设备管理单元，接口封装单元；所述数据通信单元，基于进程间通信与体感设备中间件之间进行数据通信；所述事件管理单元，基于预设的各类体感事件实现对所述应用程序的操作控制；体感设备管理单元，用于管理接入所述智能显示终端的体感设备以及该体感设备对应的设备数据；接口提供单元，用于向应用程序提供应用程序接口。
本申请提供的所述软件开发工具包，基于统一数据格式标准的标准化体感数据向软件开发人员提供统一的应用程序接口，避免了软件开发人员就同一款软件或者游戏针对不同的数据格式标准开发出对应的软件或者游戏，节省了资源。
附图说明
图1是本申请第一实施例提供的一种智能显示终端与体感设备实现数据交互的方法处理流程图。
图2是本申请第二实施例提供的一种智能显示终端与体感设备实现数据交互的装置示意图。
图3是本申请第三实施例提供的一种用于智能显示终端与体感设备实现数据交互的体感设备中间件示意图。
图4是本申请第四实施例提供的一种用于智能显示终端与体感设备实现数据交互的软件开发工具包示意图。
具体实施方式
在下面的描述中阐述了很多具体细节以便于充分理解本申请。但是本申请能够以很多不同于在此描述的其它方式来实施，本领域技术人员可以在不违背本申请内涵的情况下做类似推广，因此本申请不受下面公开的具体实施的限制。
本申请提供一种智能显示终端与体感设备实现数据交互的方法，本申请另外提供一种智能显示终端与体感设备实现数据交互的装置、用于智能 显示终端与体感设备实现数据交互的体感设备中间件以及用于智能显示终端与体感设备实现数据交互的软件开发工具包。
下面结合附图和实施例对本申请的智能显示终端与体感设备实现数据交互的方法进行详细说明。
实施例一
参照图1，其示出了本申请第一实施例提供的一种智能显示终端与体感设备实现数据交互的方法处理流程图。
本实施例所述一种智能显示终端与体感设备实现数据交互的方法包括如下步骤：
S101；基于智能显示终端读取体感设备上传的设备数据。
所述智能显示终端是指用于播放显示功能的设备终端，并且能够安装运行智能操作系统和应用程序，比如：智能电视终端和PC；所述体感设备包括体感手柄、智能移动终端以及可穿戴式设备；所述设备数据包括体感设备内置的传感器采集的数据，此外，所述设备数据还包括设备信息数据(体感设备的设备ID、设备厂商ID、设备名称以及传感器型号、类型等)。
本实施例中，以智能电视终端为例进行说明，其它类型的智能显示终端与智能电视终端相类似，参照本实施例提供如下智能显示终端与体感设备实现数据交互的方法即可，本实施例不在一一列出。
本步骤所述的基于智能显示终端读取体感设备上传的设备数据之前，所述体感设备上传所述设备数据的过程包括如下两步：1)体感设备采集设备数据，体感设备通过内置的传感器采集当前体感设备的设备数据；2)所述体感设备将所述设备数据上传至所述智能电视终端。
完成所述体感设备上传所述设备数据的步骤之后，基于智能显示终端读取体感设备上传的设备数据。所述基于智能电视终端读取体感设备上传的设备数据，是通过接口驱动模块接收；其中，所述接口驱动模块包括：USB驱动、WIFI驱动和蓝牙驱动。
完成本步骤所述的基于智能显示终端读取体感设备上传的设备数据 之后，则进行将所述设备数据转化为标准化体感数据的步骤。
S102；将所述设备数据转化为标准化体感数据。
所述将设备数据转化为标准化体感数据包括：
1)获取所述设备数据对应的体感设备采用的数据格式标准；
所述设备数据包括体感设备内置的传感器采集的数据以及设备信息数据，所述设备信息数据包括：体感设备的设备ID、设备厂商ID、设备名称以及传感器型号、类型等。对于体感设备的设备ID、设备厂商ID、设备名称以及传感器型号、类型不同的体感设备，所对应的设备数据的数据格式标准也有可能不同。
本步骤中，提前获取体感设备厂提供的体感设备对应的数据格式标准或者传感器厂商提供的所述体感设备内置的传感器对应的数据格式标准，并将所述数据格式标准存储。
2)根据所述数据格式标准解析所述设备数据，生成体感数据；
所述体感数据是指能够表征体感设备运动特征的数据；本步骤的目的在于将所述设备数据中体感设备内置的传感器采集的数据通过解析计算转化为能够表征体感设备运动特征或者用户体感动作的体感数据。
3)基于预设的转换算法将所述体感数据转换为标准化体感数据。
所述标准化数据是指基于统一标准的表征体感设备运动特征或者用户体感动作的体感数据；本步骤的目的在于将不同数据格式标准的体感数据转化为统一数据格式标准的体感数据，即：标准化体感数据；所述转化算法是根据所述体感数据的数据格式标准与标准化体感数据的数据格式标准之间的关系制定的。
根据上述三个步骤将所述设备数据转化为标准化体感数据之后，将所述标准化体感数据发送至应用程序。
S103；将所述标准化体感数据按照私有协议打包，获得体感数据包。
将所述标准化体感数据发送至应用程序之前，将所述标准化体感数据按照私有协议打包，获得体感数据包；获得所述体感数据包之后，将所述体感数据包发送至应用程序。本步骤中所述的将所述标准化体感数据按照 私有协议打包，不属于本实施例的重点，在此不赘述。
S104；将所述体感数据包发送至应用程序。
将所述体感数据包发送至应用程序基于进程间通信方式实现，所述进程间通信方式包括：消息队列、共享内存和Socket套接字。此外，还可以采用本实施例之外的方式实现将所述体感数据包发送至应用程序，在此不作限定。
S105；应用程序接收所述体感数据包。
应用程序接收所述通过进程间通信方式发送的体感数据包，接收到所述体感数据包之后，将所述体感数据包解析为标准化设备数据。
S106；所述应用程序按照私有协议对所述体感数据包进行解析，获得标准化体感数据。
对于体感设备中间件与所述应用程序之间的基于进程间通信的数据通信，为保证体感设备中间件和应用程序双方数据的一致性和有效性，在体感设备中间件和应用程序之间达成数据的统一标准，即：私有协议。
在所述体感设备中间件和应用程序双方建立私有协议，确保应用程序能够识别体感设备中间件向所述应用程序发送的数据信息，以及体感设备中间件能够识别应用程序向所述体感设备中间件发送的指令信息；
此外，在所述体感设备中间件和应用程序双方建立私有协议，确保应用程序能够基于所述私有协议获取所述数据信息当中包含的完整的信息，以及体感设备中间件能够基于所述私有协议获取所述指令信息当中包含的完整的信息，避免了数据丢失。
根据上述步骤S105所述的应用程序接收所述体感数据包之后，所述应用程序按照所述私有协议对所述体感数据包进行解析，获得标准化设备数据。
实施例二
在上述的实施例中，提供了一种智能显示终端与体感设备实现数据交互的方法，与之相对应的，本申请还提供了一种智能显示终端与体感设备实现数据交互的装置。
参照图2，其示出了根据本申请第二实施例提供的一种智能显示终端与体感设备实现数据交互的装置示意图。
由于装置实施例基本相似于方法实施例，所以描述得比较简单，相关的部分请参见方法实施例的对应说明即可。下述描述的装置实施例仅仅是示意性的。
本申请所述智能显示终端与体感设备实现数据交互的装置，包括：
设备数据读取单元201，用于基于智能显示终端读取体感设备上传的设备数据；
数据转化单元202，用于将所述设备数据转化为标准化体感数据；
数据调用单元205，用于实现应用程序读取所述标准化体感数据。
可选的，所述数据转化单元202包括：
数据标准获取子单元202-1，用于获取所述设备数据对应的体感设备采用的数据格式标准；
设备数据解析子单元202-1，用于根据所述数据格式标准解析所述设备数据，生成体感数据；
标准化体感数据生成子单元202-3，用于基于预设的转换算法将所述体感数据转换为标准化体感数据。
可选的，所述智能显示终端与体感设备实现数据交互的装置，包括：
数据打包单元203，用于将所述标准化体感数据按照私有协议打包，获得体感数据包；
数据发送单元204，用于将所述体感数据包发送至应用程序。
可选的，所述数据调用单元205，包括：
数据接收子单元205-1，应用程序接收所述体感数据包；
数据解析子单元205-2，所述应用程序按照所述私有协议对所述体感数据包进行解析，获得标准化设备数据。
实施例三
在上述的实施例中，提供了一种智能显示终端与体感设备实现数据交 互的方法，此外，本申请还提供了一种用于智能显示终端与体感设备实现数据交互的体感设备中间件，用于上述的智能显示终端与体感设备实现数据交互的方法中，用于实现将所述设备数据转化为标准化体感数据的步骤；以及用于实现智能显示终端通过所述应用程序编程接口，向所述体感设备发送指令的步骤。
参照图3，其示出了本申请第三实施例提供的一种用于智能显示终端与体感设备实现数据交互的体感设备中间件示意图。
本申请中，所述体感设备中间件的作用是将体感设备上传的设备数据转化为具有统一数据格式的标准化体感数据；如果没有所述体感设备中间件，即使应用程序能够直接基于智能显示设备读取到体感设备上传的设备数据，对于不同数据格式标准的设备数据也无法识别，更无法调用；应用程序无法与体感设备之间进行数据交互，所述智能显示终端与体感设备实现数据交互的方法无法实现。综上所述，体感设备中间件对于所述智能显示终端与体感设备实现数据交互的方法的实现具有不可或缺的作用。
所述用于智能显示终端与体感设备实现数据交互的体感设备中间件包括：驱动对接单元301、数据标准化单元302、体感设备管理单元303和数据通信单元304。
驱动对接单元301，用于基于智能电视终端读取体感设备上传的设备数据，以及发送由应用程序下行的命令；
所述设备数据包括体感设备内置的传感器采集的数据以及设备信息数据，所述设备信息数据包括：体感设备的设备ID、设备厂商ID、设备名称以及传感器型号、类型等。对于体感设备的设备ID、设备厂商ID、设备名称以及传感器型号、类型不同的体感设备，所对应的设备数据的数据格式标准也有可能不同。
所述驱动对接单元301充当所述体感设备与智能显示终端之间的接口，该接口通过接口驱动实现，所述接口驱动包括：USB驱动、WIFI驱动和蓝牙驱动；此外，还可包括其它驱动，比如红外驱动等，在此不作限定。
若所述体感设备通过USB接口与所述智能显示终端连接时，通过USB 驱动提供所述体感设备与所述智能显示终端之间的数据通信；本实施例中，所述体感设备通过USB接口将自身采集的设备数据上传至智能显示终端。此外，所述体感设备通过WIFI驱动和蓝牙驱动上传设备数据至智能显示终端与体感设备通过USB接口将设备数据上传至智能显示终端过程相类似，在此不赘述。
所述数据标准化单元302，用于将所述设备数据转化为标准化体感数据；
体感设备中间件基于驱动对接单元301接收体感设备上传的设备数据之后，所述体感设备中间件基于数据标准化单元302读取该设备数据，并且将该设备数据转化为标准化体感数据。所述标准化体感数据是指将不同体感设备对应的不同数据格式标准的设备数据基于统一的数据格式标准转化之后生成的数据。
所述数据标准化单元302包括：数据格式标准获取子单元302-1、数据解析子单元302-2以及数据转换子单元302-3；
数据格式标准获取子单元302-1，用于获取所述设备数据对应的体感设备采用的数据格式标准；
所述数据标准化单元302要想将所述体感设备上传的设备数据转化为标准化体感数据，一个重要的前提是数据标准化单元302首先能够识别不同体感设备上传的不同数据格式标准的设备数据。本实施例中，所述数据标准化单元302当中的数据格式标准获取子单元302-1获取不同体感设备厂提供的体感设备对应的数据格式标准并存储；获取到所述不同体感设备厂提供的体感设备对应的数据格式标准之后，所述数据标准化单元302才能够识别所述体感设备上传的设备数据，完成将所述设备数据转化为标准化体感数据的数据准备前提。
数据解析子单元302-2，用于根据所述数据格式标准解析所述设备数据，生成体感数据；
所述体感数据是指能够表征体感设备的运动(即：用户体感动作)特征的数据。所述数据解析子单元302-2基于上述数据格式标准获取子单元302-1获取的体感设备厂提供的体感设备对应的数据格式标准对所述设备 数据进行解析，并将该解析之后的设备数据进过分析计算转化为体感数据。需要说明的是，此处，所述体感数据与数据格式标准一一对应，即：一种体感设备对应一种数据格式标准的体感数据，不同体感设备对应的体感数据的数据格式标准互不相同。
数据转换子单元302-3，用于基于预设的转换算法将所述体感数据转换为标准化体感数据。所述标准化体感数据是指基于统一标准的表征体感设备运动特征或者用户体感动作的体感数据，即：将上述数据解析子单元302-2获取到不同数据格式标准的体感数据转换为基于统一标准的体感数据。
本实施例中，所述数据转换子单元302-3基于预设的转换算法将所述体感数据转换为统一标准额的体感数据，即：标准化体感数据。
所述转换算法是根据所述体感数据的数据格式标准与标准化体感数据的数据格式标准之间的关系制定的。
所述体感设备管理单元303，用于管理接入所述智能显示终端的体感设备或者该体感设备对应的设备数据；
所述体感设备管理单元303包括：解析子单元303-1和存储子单元303-2。
解析子单元303-1，基于所述标准化体感数据进行解析，获得设备特征信息；
所述设备数据包括体感设备内置的传感器采集的数据以及设备信息数据，更进一步，所述标准化体感数据也包括传感器采集的数据和设备信息数据；所述设备信息数据包括：体感设备的设备ID、设备厂商ID、设备名称以及传感器型号、类型等。所述设备特征信息是指能够确定体感设备的设备数据信息，比如：体感设备的设备ID。
存储子单元303-2，用于将所述标准化体感数据存储到所述设备特征信息对应的数据存储区域中。
所述存储子单元303-2的作用是将不同的标准化体感数据存储到不同的数据存储区域当中；并且，对同一设备特征信息对应的数据存储区域当 中存储的标准化体感数据保持更新。
对于同一体感设备，当有新的标准化体感数据生成时，以所述新的标准化体感数据更新所述数据存储区域中存储的标准化体感数据，实现数据的更新。
本实施例中，所述数据存储区域与体感设备的设备ID相对应，一个设备ID对应一个数据存储区域。所述数据存储区域可以是数据库当中的一个储存区域；也可以是其它的数据存储单元，在此不作限定。
所述数据通信单元304，基于进程间通信与所述应用程序之间进行数据通信。
所述体感设备中间件运行于独立的进程中；同样，所述应用程序运行于独立的进程中，为了实现所述体感设备中间件与所述应用程序之间的数据通信，采用进程间通信的方式，从而实现所述体感设备中间件与所述应用程序之间的数据交互。所述进程间通信方式包括：消息队列、共享内存和Socket套接字，除此之外，还可以采用其它的方式实现，在此不作限定。
所述数据通信单元304包括：体感数据包生成子单元304-1、体感数据包发送子单元304-2、指令数据包接收子单元304-3以及指令数据包解析子单元304-4；
体感数据包生成子单元304-1，用于将所述标准化体感数据按照私有协议打包，获得体感数据包；
对于所述体感设备中间件与所述应用程序之间的基于进程间通信的数据通信，为保证体感设备中间件和应用程序双方数据的一致性和有效性，在体感设备中间件和应用程序之间达成数据的统一标准，即：私有协议。
在所述体感设备中间件和应用程序双方建立私有协议，确保应用程序能够识别体感设备中间件向所述应用程序发送的数据信息，以及体感设备中间件能够识别应用程序向所述体感设备中间件发送的指令信息；
此外，在所述体感设备中间件和应用程序双方建立私有协议，确保应用程序能够基于所述私有协议获取所述数据信息当中包含的完整的信息， 以及体感设备中间件能够基于所述私有协议获取所述指令信息当中包含的完整的信息，避免了数据丢失。
在所述体感设备中间件和应用程序双方达成私有协议之后，体感设备中间件按照所述私有协议将所述标准化数据进行打包，并生成体感数据包；
体感设备中间件获取到所述体感数据包之后，将该体感数据包发送至应用程序；
应用程序接收到所述体感数据包之后，按照所述私有协议对该体感数据包进行解析，获得标准化体感数据并进行相关操作；
类似的，在所述体感设备中间件和应用程序双方达成私有协议之后，应用程序按照所述私有协议将所述指令数据进行打包，并生成指令数据包；
应用程序获取到所述指令数据包之后，将该指令数据包发送至体感设备中间件；
体感设备中间件接收到所述指令数据包之后，按照所述私有协议对该指令数据包进行解析，获得标准化的指令数据。
体感数据包发送子单元304-2，用于将所述体感数据包发送至所述应用程序；
参见上述体感数据包生成子单元304-1的说明即可，此处不再赘述。
指令数据包接收子单元304-3，用于接收所述应用程序发送的指令数据包；
参见上述体感数据包生成子单元304-1的说明即可，此处不再赘述。
指令数据包解析子单元304-4，用于将所述指令数据包按照私有协议解析为标准化的指令数据。
所述体感数据包发送子单元304-2、指令数据包接收子单元304-3以及指令数据包解析子单元304-4参见上述体感数据包生成子单元304-1的说明即可，此处不再赘述。
现有技术下，应用程序无法兼容体感设备，对于某一设备厂家提供的 某一型号的体感设备，只有对应的一款或者一个系列的游戏能够与所述体感设备兼容，除此之外，其它应用程序或者第三方应用程序都无法与所述体感设备兼容；比如任天堂和小霸王游戏机，只能安装对应该游戏机专门开发的游戏程序，市面上的大部分游戏程序无法安装或者无法实现；本实施例提供的所述体感设备中间件，获取不同设备厂商体感设备对应的设备数据采用的数据格式标准，然后根据数据格式标准对应的将设备数据转化为表征体感设备运动特征的体感数据，并且将体感数据按照预设的转换算法转换为具有统一数据格式的标准化体感数据，统一了体感设备的数据传输格式，最后，将所述标准化体感数据向应用程序提供，使应用程序能够兼容不同厂商生产的体感设备。
实施例四
在上述的实施例中，提供了一种智能显示终端与体感设备实现数据交互的方法，以及一种用于智能显示终端与体感设备实现数据交互的体感设备中间件，用于上述的智能显示终端与体感设备实现数据交互的方法中，用于实现将所述设备数据转化为标准化体感数据的步骤；以及用于实现智能显示终端通过所述应用程序编程接口，向所述体感设备发送指令的步骤；此外，本申请还提供了一种用于智能显示终端与体感设备实现数据交互的软件开发工具包，用于与上述的用于智能显示终端与体感设备实现数据交互的体感设备中间件相互匹配。
本申请中，所述体感设备中间件的作用是将体感设备上传的设备数据转化为具有统一数据格式的标准化体感数据；所述软件开发工具包的作用是为软件开发人员提供与体感设备相匹配的软件(应用程序和游戏)的开发标准和依据，并且为所述软件调用所述标准化体感数据提供了接口工具。
参照图4，其示出了根据本申请第四实施例提供的一种用于智能显示终端与体感设备实现数据交互的软件开发工具包示意图。
所述软件开发工具包包括数据通信单元401、事件管理单元402、体感设备管理单元403和接口封装单元404；
本实施例中，所述软件开发工具包是指监听、读取、操作、管理智能 显示终端上体感设备以及体感设备对应数据的一套应用程序开发接口(API)，其最终提供的实际形式是若干个应用程序库文件，应用程序(包括游戏)可调用软件开发工具包提供的应用程序开发接口。
需要说明的是，本实施例中，所述软件开发工具包本身不作为一个独立的进程运行，仅运行在调用它的应用程序进程当中，所述体感设备中间件运行于独立的进程中，所述体感设备中间件与所述软件开发工具包之间通过进程间通信方式实现数据通信，所述进程间通信方式包括：消息队列、共享内存和Socket套接字。此外，还可以采用其它的方式实现，在此不作限定。
所述数据通信单元401，基于进程间通信与体感设备中间件之间进行数据通信；
所述体感设备中间件运行于独立的进程中；同样，所述应用程序运行于独立的进程中，为了实现所述体感设备中间件与所述应用程序之间的数据通信，采用进程间通信的方式，从而实现所述体感设备中间件与所述应用程序之间的数据交互。所述进程间通信方式包括：消息队列、共享内存和Socket套接字，除此之外，还可以采用其它的方式实现，在此不作限定。
所述数据通信单元401包括：体感数据包接收子单元401-1、体感数据包解析子单元401-2、指令数据包生成子单元401-3和指令数据包发送子单元401-4；
体感数据包接收子单元401-1，用于接收所述体感设备中间件发送的体感数据包；
对于所述体感设备中间件与所述应用程序之间的基于进程间通信的数据通信，为保证体感设备中间件和应用程序双方数据的一致性和有效性，在体感设备中间件和应用程序之间达成数据的统一标准，即：私有协议。
在所述体感设备中间件和应用程序双方建立私有协议，确保应用程序能够识别体感设备中间件向所述应用程序发送的数据信息，以及体感设备中间件能够识别应用程序向所述体感设备中间件发送的指令信息；
此外，在所述体感设备中间件和应用程序双方建立私有协议，确保应 用程序能够基于所述私有协议获取所述数据信息当中包含的完整的信息，以及体感设备中间件能够基于所述私有协议获取所述指令信息当中包含的完整的信息，避免了数据丢失。
在所述体感设备中间件和应用程序双方达成私有协议之后，体感设备中间件按照所述私有协议将所述标准化数据进行打包，并生成体感数据包；
体感设备中间件获取到所述体感数据包之后，将该体感数据包发送至应用程序；
应用程序接收到所述体感数据包之后，按照所述私有协议对该体感数据包进行解析，获得标准化体感数据并进行相关操作；
类似的，在所述体感设备中间件和应用程序双方达成私有协议之后，应用程序按照所述私有协议将所述指令数据进行打包，并生成指令数据包；
应用程序获取到所述指令数据包之后，将该指令数据包发送至体感设备中间件；
体感设备中间件接收到所述指令数据包之后，按照所述私有协议对该指令数据包进行解析，获得指令数据并进行相关操作。
体感数据包解析子单元401-2，用于将所述体感数据包按照私有协议进行解析，获得标准化体感数据；
参见上述体感数据包接收子单元401-1的说明即可，此处不再赘述。
指令数据包生成子单元401-3，用于将所述指令数据按照私有协议打包，获得指令数据包；
参见上述体感数据包接收子单元401-1的说明即可，此处不再赘述。
指令数据包发送子单元401-4，用于将所述指令数据包发送至所述体感设备中间件。
所述体感数据包解析子单元401-2、指令数据包生成子单元401-3以及指令数据包发送子单元401-4参见上述体感数据包接收子单元401-1的说明即可，此处不再赘述。
所述事件管理单元402，基于预设的各类体感事件实现对所述应用程序的操作控制；事件是对象之间通信的一种机制。事件有很多种，常用的事件有鼠标单击事件、鼠标移动事件和按钮单击事件等。事件的作用是帮助用户完成用户想完成的是事；例如：
对于鼠标单击事件，单击鼠标之后，肯定会发生某种动作，比如出窗口、刷新页面或者提交数据等，此时单击鼠标这一操作就触发了鼠标单击事件。事件都是相对应的，对于鼠标单击事件而言，只有单击鼠标这一操作被执行之后，才会触发鼠标单击事件，并且执行该鼠标单击事件当中的方法或者属性。
本实施例中，所述事件管理单元402基于预设的各类体感事件实现对所述应用程序的操作控制的步骤如下：
1)根据所述标准化体感数据的数据类型定义不同类型的体感事件；所述体感事件包括：按键事件、传感器事件和/或空鼠事件。
2)通过事件监听器来监听所述体感事件；若所述体感事件被触发，则执行该体感事件对应的操作响应，实现对所述应用程序的操作控制。
此外，需要说明的是，所述事件管理单元402还可以采用本实施例之外的事件实现方法来实现，比如C#事件的实现，在此不作限定。
体感设备管理单元403，用于管理接入所述智能显示终端的体感设备或者该体感设备对应的设备数据；
所述体感设备管理单元403包括：体感事件解析子单元403-1、体感设备获取子单元403-2和数据存储子单元403-3。
所述体感事件解析子单元403-1，用于对所述体感事件进行解析，获得设备特征信息和标准化体感数据；
对于上述事件管理单元402中实现的各类体感事件，若所述体感事件中一体感事件被触发，则体感事件解析子单元403-1该体感事件进行解析，并同时获得该体感事件对应的设备特征信息和标准化体感数据。
所述体感设备获取子单元403-2，用于根据所述设备特征信息从体感设备列表中获取该设备特征信息对应的体感设备；
所述体感设备列表是指所有接入所述智能显示终端的体感设备组成的体感设备列表。
上述体感事件解析子单元403-1通过解析体感事件获得设备特征信息和标准化体感数据，所述体感设备获取子单元403-2基于该设备特征信息从体感设备列表中查询并获取到该设备特征信息对应的体感设备；本实施例中，体感设备获取子单元403-2基于体感设备ID从体感设备列表中查询该ID对应的体感设备。
所述数据存储子单元403-3，用于将所述标准化体感数据存储到所述设备特征信息对应的数据存储区域中。
所述数据存储子单元403-3的作用是将不同的标准化体感数据存储到不同的数据存储区域当中；并且，对同一设备特征信息对应的数据存储区域当中存储的标准化体感数据保持更新。
对于同一体感设备，当有新的体感事件被触发，对该体感事件进行解析获得新的标准化体感数据后，以所述新的标准化体感数据更新所述数据存储区域中存储的标准化体感数据，实现数据的更新。
本实施例中，所述数据存储区域与体感设备的设备ID相对应，一个设备ID对应一个数据存储区域。所述数据存储区域可以是数据库当中的一个储存区域；也可以是其它的数据存储单元，在此不作限定。
所述数据存储子单元403-3、体感设备获取子单元403-2以及体感事件解析子单元403-1共同维护所述体感设备列表；
所述体感事件解析子单元403-1首先对事件管理单元402中被触发的体感事件进行解析，获得该体感事件对应的设备特征信息和标准化体感数据；
所述体感设备获取子单元403-2基于该设备特征信息从体感设备列表中查询并获取到该设备特征信息对应的体感设备；
所述数据存储子单元403-3将所述标准化体感数据存储到所述设备特征信息对应的数据存储区域当中，所述数据存储区域可以是数据库当中的一个储存区域；也可以是其它的数据存储单元，在此不作限定。
接口提供单元404，用于向应用程序提供应用程序接口。
所述接口提供单元404包括接口实现子单元404-1和接口封装子单元404-2；
接口实现子单元404-1，基于所述体感设备管理单元403实现所述应用程序编程接口；
需要说明的是，所述应用程序编程接口可基于不同的编程语言实现，如：Java、C和C++等。接口封装子单元404-2，用于将所述应用程序编程接口打包编译成库文件并输出。
对体感设备管理单元403提供的标准化体感数据和设备特征信息等，所述软件开发工具包根据不同的应用程序语言环境进行接口封装，典型的语言环境如：Java、C和C++，并且，所述软件开发工具包最终以应用程序库文件的方式对外提供。
例如：
基于Java语言进行接口封装的过程如下：
1)、以Java语言定义体感设备类、体感设备管理类以及体感事件类等；
2)、定义所述体感设备类、体感设备管理类以及体感事件类所需要对外公开的应用程序开发接口(API)，并根据体感设备管理单元403实现所述应用程序开发接口(API)；此外，体感设备管理单元403采用C/C++语言编写，因此，封装成Java语言，需要用到Java的JNI调用；
3)将所述应用程序开发接口(API)打包编译成库文件对外输出，并同时输出软件开发工具包手册文档，供应用程序开发者使用。
除此之外，还可以采用其它的编程语言实现所述接口封装单元404完成的用于面向应用软件提供封装为多种语言的应用程序接口的功能，本实施例在此不作限定。
现有技术下，对于某一厂商或者开发者开发的应用程序，只能与开发该应用程序时所面向的特定的一款或者多款体感设备之间相互兼容，无法兼容其它的体感设备。本实施例中，通过软件开发工具包提供统一的应用程序开发接口供开发人员使用，开发人员利用该软件开发工具包开发的所 有应用程序都能够与体感设备兼容。
本申请虽然以较佳实施例公开如上，但其并不是用来限定本申请，任何本领域技术人员在不脱离本申请的精神和范围内，都可以做出可能的变动和修改，因此本申请的保护范围应当以本申请权利要求所界定的范围为准。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
1、计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括非暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
2、本领域技术人员应明白，本申请的实施例可提供为方法、系统或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。

Claims (21)

  1. 一种智能显示终端与体感设备实现数据交互的方法，其特征在于，包括：
    基于智能显示终端读取体感设备上传的设备数据；
    将所述设备数据转化为标准化体感数据；
    应用程序读取所述标准化体感数据。
  2. 根据权利要求1所述的智能显示终端与体感设备实现数据交互的方法，其特征在于，所述基于智能电视终端读取体感设备上传的设备数据，是通过接口驱动模块接收；
    其中，所述接口驱动模块包括：USB驱动、WIFI驱动和/或蓝牙驱动。
  3. 根据权利要求1所述的智能显示终端与体感设备实现数据交互的方法，其特征在于，所述将所述设备数据转化为标准化体感数据，包括：
    获取所述设备数据对应的体感设备采用的数据格式标准；
    根据所述数据格式标准解析所述设备数据，生成体感数据；
    基于预设的转换算法将所述体感数据转换为标准化体感数据。
  4. 根据权利要求3所述的智能显示终端与体感设备实现数据交互的方法，其特征在于，所述转换算法是根据体感数据格式与标准化体感数据格式之间的关系，为所述体感数据格式制定的。
  5. 根据权利要求1所述的智能显示终端与体感设备实现数据交互的方法，其特征在于，所述应用程序读取所述标准化体感数据之前，包括：
    将所述标准化体感数据按照私有协议打包，获得体感数据包；
    将所述体感数据包发送至应用程序。
  6. 根据权利要求5所述的智能显示终端与体感设备实现数据交互的方法，其特征在于，所述应用程序读取所述标准化体感数据，包括：
    应用程序接收所述体感数据包；
    所述应用程序按照所述私有协议对所述体感数据包进行解析，获得标准化体感数据。
  7. 根据权利要求6所述的智能显示终端与体感设备实现数据交互的方法，其特征在于，所述应用程序接收所述体感数据包，具体是，所述应用程序通过应用程序编程接口接收所述体感数据包。
  8. 根据权利要求7所述的智能显示终端与体感设备实现数据交互的方法，其特征在于，所述智能显示终端通过所述应用程序编程接口，向所述体感设备发送指令。
  9. 一种智能显示终端与体感设备实现数据交互的装置，其特征在于，包括：
    设备数据读取单元，用于基于智能显示终端读取体感设备上传的设备数据；
    数据转化单元，用于将所述设备数据转化为标准化体感数据；
    数据调用单元，用于实现应用程序读取所述标准化体感数据。
  10. 根据权利要求9所述的智能显示终端与体感设备实现数据交互的装置，其特征在于，所述数据转化单元包括：
    数据标准获取子单元，用于获取所述设备数据对应的体感设备采用的数据格式标准；
    设备数据解析子单元，用于根据所述数据格式标准解析所述设备数据，生成体感数据；
    标准化体感数据生成子单元，用于基于预设的转换算法将所述体感数据转换为标准化体感数据。
  11. 根据权利要求9所述的智能显示终端与体感设备实现数据交互的装置，其特征在于，包括：
    数据打包单元，用于将所述标准化体感数据按照私有协议打包，获得体感数据包；
    数据发送单元，用于将所述体感数据包发送至应用程序。
  12. 根据权利要求11所述的智能显示终端与体感设备实现数据交互的装置，其特征在于，所述数据调用单元，包括：
    数据接收子单元，应用程序接收所述体感数据包；
    数据解析子单元，所述应用程序按照所述私有协议对所述体感数据包进行解析，获得标准化设备数据。
  13. 一种用于智能显示终端与体感设备实现数据交互的体感设备中间件，其特征在于，包括：驱动对接单元，数据标准化单元，体感设备管理单元，数据通信单元；
    所述驱动对接单元，用于基于智能电视终端读取体感设备上传的设备数据，以及发送由应用程序下行的命令；
    所述数据标准化单元，用于将所述设备数据转化为标准化体感数据；
    所述体感设备管理单元，用于管理接入所述智能显示终端的体感设备以及该体感设备对应的设备数据；
    所述数据通信单元，基于进程间通信与所述应用程序之间进行数据通信。
  14. 根据权利要求13所述的用于智能显示终端与体感设备实现数据交互的体感设备中间件，其特征在于，所述数据标准化单元包括：
    数据格式标准获取子单元，用于获取所述设备数据对应的体感设备采用的数据格式标准；
    数据解析子单元，用于根据所述数据格式标准解析所述设备数据，生成体感数据；
    数据转换子单元，用于基于预设的转换算法将所述体感数据转换为标准化体感数据。
  15. 根据权利要求13所述的用于智能显示终端与体感设备实现数据交互的体感设备中间件，其特征在于，所述体感设备管理单元包括：
    解析子单元，用于对所述标准化体感数据进行解析，获得设备特征信息；
    存储子单元，用于将所述标准化体感数据存储到所述设备特征信息对应的数据存储区域中。
  16. 根据权利要求13所述的用于智能显示终端与体感设备实现数据交互的体感设备中间件，其特征在于，所述数据通信单元包括：
    体感数据包生成子单元，用于将所述标准化体感数据按照私有协议打包，获得体感数据包；
    体感数据包发送子单元，用于将所述体感数据包发送至所述应用程序；以及
    指令数据包接收子单元，用于接收所述应用程序发送的指令数据包；
    指令数据包解析子单元，用于将所述指令数据包按照私有协议解析为标准化的指令数据。
  17. 根据权利要求13所述的用于智能显示终端与体感设备实现数据交互的体感设备中间件，其特征在于，所述进程间通信包括：消息队列、共享内存或Socket套接字。
  18. 一种用于智能显示终端与体感设备实现数据交互的软件开发工具包，其特征在于，包括：数据通信单元，事件管理单元，体感设备管理单元，接口封装单元；
    所述数据通信单元，基于进程间通信与体感设备中间件之间进行数据通信；
    所述事件管理单元，基于预设的各类体感事件实现对所述应用程序的操作控制；
    体感设备管理单元，用于管理接入所述智能显示终端的体感设备以及该体感设备对应的设备数据；
    接口提供单元，用于向应用程序提供应用程序接口。
  19. 根据权利要求18所述的用于智能显示终端与体感设备实现数据交互的软件开发工具包，其特征在于，所述数据通信单元包括：
    体感数据包接收子单元，用于接收所述体感设备中间件发送的体感数据包；
    体感数据包解析子单元，用于将所述体感数据包按照私有协议进行解析，获得标准化体感数据；
    指令数据包生成子单元，用于将所述指令数据按照私有协议打包，获得指令数据包；
    指令数据包发送子单元，用于将所述指令数据包发送至所述体感设备中间件。
  20. 根据权利要求18所述的用于智能显示终端与体感设备实现数据交互的软件开发工具包，其特征在于，所述体感设备管理单元包括：
    体感事件解析子单元，用于对所述体感事件进行解析，获得设备特征信息和标准化体感数据；
    体感设备获取子单元，用于根据所述设备特征信息从体感设备列表中获取该设备特征信息对应的体感设备；
    数据存储子单元，用于将所述标准化体感数据存储到所述设备特征信息对应的数据存储区域中。
  21. 根据权利要求18所述的用于智能显示终端与体感设备实现数据交互的软件开发工具包，其特征在于，所述接口提供单元包括：
    接口实现子单元，基于所述体感设备管理单元实现所述应用程序编程接口；
    接口封装子单元，用于将所述应用程序编程接口打包编译成库文件并输出。
PCT/CN2015/078917 2014-05-30 2015-05-14 一种智能显示终端与体感设备实现数据交互的方法及装置 WO2015180567A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/313,518 US20170188082A1 (en) 2014-05-30 2015-05-14 A method and a device for exchanging data between a smart display terminal and motion-sensing equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410238796.4 2014-05-30
CN201410238796.4A CN105404385B (zh) 2014-05-30 2014-05-30 一种智能显示终端与体感设备实现数据交互的方法及装置

Publications (1)

Publication Number Publication Date
WO2015180567A1 true WO2015180567A1 (zh) 2015-12-03

Family

ID=54698068

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/078917 WO2015180567A1 (zh) 2014-05-30 2015-05-14 一种智能显示终端与体感设备实现数据交互的方法及装置

Country Status (4)

Country Link
US (1) US20170188082A1 (zh)
CN (1) CN105404385B (zh)
HK (1) HK1221045A1 (zh)
WO (1) WO2015180567A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107529132A (zh) * 2017-09-05 2017-12-29 北京京东尚科信息技术有限公司 蓝牙设备与应用程序之间传输数据的方法和装置
CN109951860A (zh) * 2017-12-21 2019-06-28 深圳Tcl新技术有限公司 一种获取wifi信息的方法、智能电视及存储介质

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106209968A (zh) * 2016-06-16 2016-12-07 西安佳信系统集成有限责任公司 一种物联数据智能集成中间件
CN106534917A (zh) * 2016-11-03 2017-03-22 深圳市天易联科技有限公司 信息处理的方法及装置
CN106648085A (zh) * 2016-12-12 2017-05-10 上海拆名晃信息科技有限公司 一种虚拟现实设备姿态信息的捕捉方法
CN109298852B (zh) * 2018-08-23 2022-03-04 北京凌宇智控科技有限公司 简化虚拟现实应用程序开发的方法及可读存储介质
CN109085927A (zh) * 2018-09-10 2018-12-25 南昌黑鲨科技有限公司 基于体感的操作控制组件、方法、智能终端及计算机可读存储介质
CN109462613A (zh) * 2018-12-27 2019-03-12 郑州春泉节能股份有限公司 一种通讯协议兼容方法
CN109814848A (zh) * 2019-02-21 2019-05-28 广州卓远虚拟现实科技有限公司 一种虚拟现实通用动感引擎
CN110471707B (zh) * 2019-08-29 2022-09-13 广州创幻数码科技有限公司 一种兼容各种硬件的虚拟主播系统及实现方法
CN112433789B (zh) * 2020-11-24 2024-05-24 深圳供电局有限公司 一种智能设备接入的管理方法及系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103049852A (zh) * 2012-12-19 2013-04-17 武汉世纪炎龙网络科技有限公司 虚拟试衣系统
CN103258078A (zh) * 2013-04-02 2013-08-21 上海交通大学 融合Kinect设备和Delmia环境的人机交互虚拟装配系统

Family Cites Families (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5805682A (en) * 1995-11-30 1998-09-08 Bell Atlantic Network Services, Inc. Method for delivering call related information to a video display
US20050134578A1 (en) * 2001-07-13 2005-06-23 Universal Electronics Inc. System and methods for interacting with a control environment
US20050021371A1 (en) * 2003-01-31 2005-01-27 Basone Michael A. System for facilitating weight control incorporating hand-held computing device
US8137195B2 (en) * 2004-11-23 2012-03-20 Hillcrest Laboratories, Inc. Semantic gaming and application transformation
WO2006073936A2 (en) * 2005-01-04 2006-07-13 Qmotions, Inc. Baseball simulation device
US7464298B2 (en) * 2005-07-01 2008-12-09 International Business Machines Corporation Method, system, and computer program product for multi-domain component management
US7783613B2 (en) * 2006-02-03 2010-08-24 Infosys Technologies Ltd. Context-aware middleware platform for client devices
US7895257B2 (en) * 2006-02-21 2011-02-22 University Of Florida Research Foundation, Inc. Modular platform enabling heterogeneous devices, sensors and actuators to integrate automatically into heterogeneous networks
US8812629B2 (en) * 2008-04-18 2014-08-19 Universal Electronics Inc. System and method for configuring the remote control functionality of a portable device
US20080120414A1 (en) * 2006-11-17 2008-05-22 Nandakishore Kushalnagar Representing resource constrained devices in a network
CA2615033A1 (en) * 2007-01-12 2008-07-12 Splitfish Gameware Inc. Game controller device
US9503562B2 (en) * 2008-03-19 2016-11-22 Universal Electronics Inc. System and method for appliance control via a personal communication or entertainment device
US8200795B2 (en) * 2008-06-05 2012-06-12 Sony Computer Entertainment Inc. Mobile phone game interface
US20100069154A1 (en) * 2008-09-15 2010-03-18 Claussen Seth A Retroactive Compatibility Interactive System and Method Thereof
US20100075756A1 (en) * 2008-09-19 2010-03-25 Adam Roberts Secondary controller for emulating a console controller
US8223121B2 (en) * 2008-10-20 2012-07-17 Sensor Platforms, Inc. Host system and method for determining an attitude of a device undergoing dynamic acceleration
US8362349B2 (en) * 2009-09-11 2013-01-29 Gibson Guitar Corp. Touch pad disc jockey controller
US20110117850A1 (en) * 2009-11-18 2011-05-19 Hei Tao Fung Apparatus and Methods for Enabling Smart Portable Device to be Universal Remote Control
KR101074058B1 (ko) * 2009-12-21 2011-10-17 주식회사 케이티 이기종 현장 장치를 위한 하드웨어 어댑터
US20150199320A1 (en) * 2010-12-29 2015-07-16 Google Inc. Creating, displaying and interacting with comments on computing devices
US8918719B2 (en) * 2011-02-14 2014-12-23 Universal Electronics Inc. Graphical user interface and data transfer methods in a controlling device
US8799974B2 (en) * 2011-12-12 2014-08-05 Infosys Limited System and method for multi-standard browser for digital devices
US20130252732A1 (en) * 2012-03-23 2013-09-26 Virginia Venture Industries, Llc Interactive high definition tv with user specific remote controllers and methods thereof
US20130324236A1 (en) * 2012-06-04 2013-12-05 Techart Llc Protocol converter
CN102830799B (zh) * 2012-08-02 2015-06-10 晨星软件研发(深圳)有限公司 基于智能终端对感应装置进行感应的方法和智能终端
ES2705526T3 (es) * 2012-09-11 2019-03-25 Life Corp Sa Plataforma de comunicación ponible
US20140121010A1 (en) * 2012-10-29 2014-05-01 Nishith Shah Method and system for video gaming using game-specific input adaptation
US9514641B2 (en) * 2012-11-02 2016-12-06 Huawei Technologies Co., Ltd. Smart remote control
CN103024059B (zh) * 2012-12-19 2015-08-26 北京时代凌宇科技有限公司 一种物联网中间件系统
US9686496B2 (en) * 2012-12-20 2017-06-20 Echostar Technologies L.L.C. Apparatus, systems, and methods for notification of remote control device modes
FR3000683B1 (fr) * 2013-01-04 2016-05-06 Movea Element mobile de commande prehensible simulant un joystick ou manette de jeu equivalente a au moins un element de commande a butee physique, et procede de simulation associe
US9223459B2 (en) * 2013-01-25 2015-12-29 University Of Washington Through Its Center For Commercialization Using neural signals to drive touch screen devices
US20150102994A1 (en) * 2013-10-10 2015-04-16 Qualcomm Incorporated System and method for multi-touch gesture detection using ultrasound beamforming
US20150312622A1 (en) * 2014-04-25 2015-10-29 Sony Corporation Proximity detection of candidate companion display device in same room as primary display using upnp
US10318013B1 (en) * 2015-04-01 2019-06-11 Bansen Labs LLC System and method for converting input from alternate input devices
WO2016170512A1 (en) * 2015-04-24 2016-10-27 Tager Sean Universal game controller

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103049852A (zh) * 2012-12-19 2013-04-17 武汉世纪炎龙网络科技有限公司 虚拟试衣系统
CN103258078A (zh) * 2013-04-02 2013-08-21 上海交通大学 融合Kinect设备和Delmia环境的人机交互虚拟装配系统

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107529132A (zh) * 2017-09-05 2017-12-29 北京京东尚科信息技术有限公司 蓝牙设备与应用程序之间传输数据的方法和装置
CN107529132B (zh) * 2017-09-05 2021-04-30 北京京东尚科信息技术有限公司 蓝牙设备与应用程序之间传输数据的方法和装置
CN109951860A (zh) * 2017-12-21 2019-06-28 深圳Tcl新技术有限公司 一种获取wifi信息的方法、智能电视及存储介质
CN109951860B (zh) * 2017-12-21 2022-07-08 深圳Tcl新技术有限公司 一种获取wifi信息的方法、智能电视及存储介质

Also Published As

Publication number Publication date
US20170188082A1 (en) 2017-06-29
HK1221045A1 (zh) 2017-05-19
CN105404385A (zh) 2016-03-16
CN105404385B (zh) 2018-11-27

Similar Documents

Publication Publication Date Title
WO2015180567A1 (zh) 一种智能显示终端与体感设备实现数据交互的方法及装置
US11595477B2 (en) Cloud storage methods and systems
WO2016029792A1 (zh) 硬件设备的调试方法、装置和系统
CN108476236B (zh) 物联网数据的基于语义的内容规范
TW201826869A (zh) 設備關聯方法、裝置、終端設備和作業系統
TW201235072A (en) Method and apparatus for gaming based on mobile terminal
US10560407B2 (en) Payload description for computer messaging
US20160021327A1 (en) Controlling one or more source terminals based on remote control information
TW201533570A (zh) 快速測試及偵測行動裝置的方法及其系統
US10073688B2 (en) Method and apparatus for executing application
CN114244821B (zh) 数据处理方法、装置、设备、电子设备和存储介质
WO2012048491A1 (zh) 面向ic装备控制软件的gui平台化实现方法
US11169861B2 (en) Application server programming language cloud functions
WO2017004844A1 (zh) 一种用于智能显示设备的交互式操控系统
WO2021093674A1 (zh) 工作流系统中的bi节点执行方法、装置、设备及计算机可读存储介质
WO2023040671A1 (zh) 组合数据接口的方法、电子设备和可读存储介质
KR102065421B1 (ko) 모바일 기기 및 모바일 기기를 활용한 가상현실 기기 컨트롤러 구동 방법.
US8347314B2 (en) Method for managing java applications
US9146889B2 (en) Method and device for sending and receiving data
US20200293333A1 (en) Electronic device, application execution system, and control method therefor
US20230388575A1 (en) Establishing network connections between devices connected by a media connection
WO2022083477A1 (zh) 一种mvvm架构的应用的开发方法及终端
WO2018144517A1 (en) Semantic query processing with information asymmetry
US10761900B1 (en) System and method for secure distributed processing across networks of heterogeneous processing nodes
CN112422692A (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: 15800249

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15313518

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15800249

Country of ref document: EP

Kind code of ref document: A1