Patent Publication Number: US-2013232402-A1

Title: Method for Processing Sensor Data and Computing Node

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation of International Application No. PCT/CN2012/083663, filed on Oct. 29, 2012, which claims priority to Chinese Patent Application No. 201210051773.3, filed on Mar. 1, 2012, both of which are hereby incorporated by reference in their entireties. 
    
    
     STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT 
     Not applicable. 
     REFERENCE TO A MICROFICHE APPENDIX 
     Not applicable. 
     TECHNICAL FIELD 
     The present invention relates to sensor application technologies, and in particular, to a method for processing sensor data and a computing node. 
     BACKGROUND 
     Sensor devices are applied widely in terminals. Terminals herein is a generic term for terminals such as mobile phones, e-books, tablet computers, electronic albums, and the like. The widespread use of sensor devices improves user experience with more diversified functions. 
       FIG. 1  is a schematic diagram of an interaction model of a sensor device in the prior art. As shown in  FIG. 1 , a native application interacts with a sensor device directly, without necessity of using web pages for accessing. Almost all current terminal operating systems (OS) employ such an interaction mode. The following is an interaction model: 
       101 . A sensor device responds to a user response or an external environment change, and transmits sensor data to an OS. 
       102 . The OS processes the sensor data and transmits the processed sensor data to a Framework layer. 
       103 . The Framework layer determines whether a native application is in a state of being ready for receiving data, and if yes, transmits a sensor event to the native application. A Framework layer may be added or deleted depending on different implementations of the OS. 
       104 . The native application responds to the sensor event and generates a response event for operating the sensor device. 
       105 . The response event is transmitted downstream to the sensor device. 
       106 . The sensor device makes a response. 
     In the above solution, different OSs provide different system calling interfaces and use different programming languages. For example, Java and C++ are used on an Android platform, but Objective-C is used on the iOS platform of Apple Corporation. Consequently, if the same application needs to run on different OS platforms at the same time, different code is required and needs to be compiled separately, which increases development and maintenance costs. 
     SUMMARY 
     Embodiments of the present invention provide a method for processing sensor data and a computing node to solve, to some extent, a problem that an application cannot run across platform due to a direct interaction between a native application and a sensor device in the prior art. 
     In one aspect, an embodiment of the present invention provides a method for processing sensor data, applied to a computing node, where the computing node includes a hardware layer, an OS running on the hardware layer, and a browser engine running on the OS, where the hardware layer includes a first sensor device. The method includes: sensing, by the first sensor device, a state change, generating sensor data, and transmitting the sensor data to the OS in form of an event; determining, by the OS, an event type of the event according to the sensor data, and transmitting the sensor data and the event type to the browser engine, where the sensor data is also transmitted to the browser engine in form of an event; and determining, by the browser engine according to the event type, that the event has been registered, and executing processing logic of the event. 
     In another aspect, an embodiment of the present invention provides a computing node, which includes a hardware layer, an OS running on the hardware layer, and a browser engine running on the OS, where the hardware layer includes a first sensor device. The first sensor device is configured to sense a state change, generate sensor data, and transmit the sensor data to the OS in form of an event; the OS is configured to determine an event type of the event according to the sensor data, and transmit the sensor data and the event type to the browser engine, where the sensor data is also transmitted to the browser engine in form of an event; and the browser engine is configured to determine, according to the event type, that the event has been registered, and execute processing logic of the event. 
     At least one technical solution of the foregoing technical solutions has the following advantages or beneficial effects: 
     The embodiments of the present invention adopt such a technique: a sensor device senses a state change, generates sensor data, and transmits the sensor data to an OS in form of an event; the OS determines the event type of the event, and transmits the sensor data and the event type to a browser engine; according to the event type, the browser engine determines that the event has been registered, and executes processing logic of the event. In this way, the browser engine shields differences between different OSs, and solves, to some extent, a problem that an application cannot run across platform due to a direct interaction between a native application and a sensor device in the prior art; with code written only once, the written application is capable of running on different OSs, thereby enabling an application to run across platform. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       To describe the technical solutions in the embodiments of the present invention or in the prior art more clearly, the following briefly introduces the accompanying drawings required for describing the embodiments or the prior art. Apparently, the accompanying drawings in the following description show some embodiments of the present invention, and persons of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts. 
         FIG. 1  is a schematic diagram of an interaction model of a sensor device in the prior art; 
         FIG. 2  is a schematic diagram of an interaction model according to the present invention; 
         FIG. 3  is a schematic flowchart of an application based on the interaction model shown in  FIG. 2 ; 
         FIG. 4  is a schematic flowchart of a method for processing sensor data according to an embodiment of the present invention; 
         FIG. 5  is a schematic structural diagram of a Document Object Model (DOM) tree of a web page; 
         FIG. 6  is a schematic signaling diagram of loading a browser engine with a web page according to an embodiment of the present invention; 
         FIG. 7  is a schematic signaling diagram of an embodiment of the present invention in an application scenario; 
         FIG. 8  is a schematic signaling diagram of an embodiment of the present invention in another application scenario; and 
         FIG. 9  is a schematic structural diagram of a computing node according to an embodiment of the present invention. 
     
    
    
     DETAILED DESCRIPTION 
     To make the objectives, technical solutions, and advantages of the embodiments of the present invention more comprehensible, the following clearly describes the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are merely a part rather than all of the embodiments of the present invention. All other embodiments obtained by persons of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention. 
       FIG. 2  is a schematic diagram of an interaction model according to the present invention. As shown in  FIG. 2 , the interaction model includes the following steps: 
       201 . A sensor device responds to a user response or an external environment change, and transmits sensor data to an OS in form of an event. The OS may be a common OS or an embedded OS. 
       202 . The OS performs format conversion for the sensor data, preprocesses the sensor data, and transmits the preprocessed data to a Framework layer. 
       203 . The Framework layer checks whether a browser/widget is in a state of being ready for receiving data, and if the browser/widget is in the state of being ready for receiving data, transmits the sensor data to the Browser/Widget. Specifically, the state of being ready for receiving data may be determined according to whether a Browser engine in the Browser/Widget is activated. 
     A Framework layer may be added or deleted depending on implementation of the OS. The Browser engine is a web application running middleware running on the OS. 
       204 . The Browser engine in the Browser/Widget determines whether a document object model (DOM) node in a web page has corresponding event listening code, and if yes, transmits the sensor data to the corresponding web page. 
       205 . An event processing module on the web page is triggered. If the event listening code includes calling of the sensor device, a sensor module is called, and a response event is generated. 
       206 . The response event is transmitted downstream to the sensor device. 
       207 . The sensor device makes a response. 
       FIG. 3  is a schematic flowchart of an application based on the interaction model shown in  FIG. 2 . As shown in  FIG. 3 , the application process specifically includes the following steps: 
       301 . An authorized developer adds event listening code for the web page. 
     The event listening code herein may also be called event processing logic. 
       302 . The browser engine is loaded with a web page. 
       303 . The browser engine parses the web page and creates an event listening mapping table. 
     The event listening mapping table includes mapping relationships between events and their processing logic. 
       304 . A terminal user triggers the sensor device. 
       305 . The sensor device transmits the sensor data to the OS in form of an event. 
       306 . The OS transmits the event to the browser engine. 
       307 . The browser engine detects whether the event is registered. 
       308 . If the event is registered, the browser engine calls processing logic of the event according to the event listening mapping table. 
       3091 . If the processing logic includes a modification of script contents of the web page, the web page is redrawn. 
     For example, to enhance the presentation capability of the web page, a pattern may be designed on the web page, and a color of the pattern represents the current temperature. Correspondingly, processing logic of a temperature change event of a temperature sensor includes code of modifying the color of the pattern according to a temperature parameter. In this way, after the temperature sensor senses a temperature change and reports the temperature parameter, the browser engine calls the processing logic of the temperature change event. In a process of executing the processing logic, the browser engine modifies the color parameter of the pattern in the script contents of the web page, and redraws the web page according to the modified script contents. On the redrawn web page, the color of the pattern corresponds to the temperature parameter sensed by the temperature sensor. 
       3092 . If the processing logic includes calling of the sensor device, the sensor device is called. 
     It can be known from the above interaction model that, in the present invention, a web development language may be used to handle the interaction with the sensor device. The web development language runs on a browser engine, and the browser engine shields the differences between different OSs. Therefore, with code being compiled at a single attempt, the compiled application is capable of running on different OSs, thereby enabling an application to run across platform. Besides, upon generation of a system event, the sensor device reports the event immediately so that the processing logic set by the user can respond to the event quickly. For example, the embodiment of the present invention may be implemented using a method shown in  FIG. 4 . 
       FIG. 4  is a schematic flowchart of a method for processing sensor data according to an embodiment of the present invention. The method is applied to a computing node such as a mobile phone terminal, a set top box, a personal digital assistant (PDA), and the like; the computing node includes a hardware layer, an OS running on the hardware layer, and a browser engine running on the OS, where the hardware layer includes a first sensor device. The browser engine may be included in a Browser or a Widget. As shown in  FIG. 4 , the method includes the following steps: 
       401 . The first sensor device senses a state change, generates sensor data, and transmits the sensor data to the OS in form of an event. 
     For example, the first sensor device may be an accelerometer, a direction sensor, a 3-axis gyroscope (gyro), a light sensor, a temperature sensor, a touch sensor, and the like. Correspondingly, the state sensed by the first sensor device may be acceleration, direction, motion trace, magnetic field, proximity, light, temperature, touch flick, and the like. 
       402 . The OS determines an event type of the event according to the sensor data, and transmits the sensor data and the event type to the browser engine, where the sensor data is also transmitted to the browser engine in form of an event. 
     Generally, when being installed on a computing node, an OS scans installed hardware on the computing node automatically and reads corresponding drivers; or, during installing new hardware on the computing node, the OS also scans the new hardware automatically and reads its driver. Specifically, in this embodiment, the OS reads the driver of the first sensor device beforehand to obtain the event type of at least one event corresponding to the first sensor device. In  402 , the event type of the event corresponding to the sensor data is determined according to the sensor data. 
     For example, when the first sensor device is a  3 -axis gyro, events may include a direction change event, an acceleration change event, and the like, and the corresponding event type is a direction change event type, an acceleration change event type, a magnetic field change event type, and the like. When sensing a direction change, the 3-axis gyro in  401  generates sensor data inclusive of a direction parameter, and according to the direction parameter included in the sensor data, the OS in  402  determines that the event is a direction change event and that the corresponding event type is a direction change event type. 
       403 . According to the event type, the browser engine determines that the event has been registered, and executes processing logic of the event. 
     Specifically, the processing logic of the event is added by an authorized developer for the web page beforehand for the purpose of monitoring state change of the sensor device. Generally, a web page is formed by a DOM tree. Adding processing logic for a web page is actually to add event listening code for a node in the DOM tree of the web page.  FIG. 5  is a schematic structural diagram of a DOM tree of a web page. As shown in  FIG. 5 , a simple web page is formed by four nodes: namely, a Hypertext Markup Language (HTML) node, a body node, a canvas node, and a division (div) node. For example, processing logic of a direction sensor needs to be added for a canvas node, and the processing logic is to display current direction at the div node when the state of the direction sensor changes. It is assumed that an identifier (ID) of the canvas node is canvas 1 , and an ID of the div node is div 1 . The processing logic added for the canvas node is as follows: 
                                &lt;script&gt;       document.getElementById(“canvas1”).addEventListner(“orientationchanged”, function(event){       document.getElementById(“div1”).innerHTML=“direction angle:”+event.value[0]+“&lt;br/&gt;”                         +“vertical rotation angle:”+event.value[1]+“&lt;br/&gt;”           +“horizontal rotation angle:”+event.value[2]+“&lt;br/&gt;”;           })                 &lt;/script&gt;                    
where “orientationchanged” represents a direction change event type. When the state of the direction sensor changes, the subsequently registered function (event) is triggered; the function processes a direction parameter transmitted by the event, and displays the current direction angle, vertical rotation angle and horizontal rotation angle at the div node. It should be noted that in practical application, a compass may be drawn on the canvas node by using the sensor data of the direction sensor directly. The description herein is intended to describe the method in the embodiment of the present invention only, and therefore, the current direction information of the terminal is displayed on the div node briefly.
 
     When a web page is loaded into a browser engine, the browser engine obtains node contents of each node in the web page by running and parsing the web page. Correspondingly, in  303 , according to previously obtained node contents, the browser engine may determine which node has registered the event. Specifically, the browser engine may be divided into  3  parts: a browser Shell, a web page parsing and rendering engine, and a script parsing engine. Equivalent to a Linux shell, the browser Shell receives an operation performed by the user for the browser interface, and calls the web page parsing and rendering engine and the script parsing engine to react accordingly. For example, when a user clicks a link on the web page, the browser Shell receives a click event of the user, calls the web page parsing and rendering engine to find the clicked website address, and opens a new web page; the web page parsing and rendering engine is responsible for operations such as parsing and rendering the web page; and the script parsing engine is responsible for parsing and executing javascript script code. In an optional embodiment of the present invention, Step  403  specifically includes the following steps: 
     The browser Shell receives the sensor data and the event type sent by the OS, determines a first web page associated with the event type, and transmits the first web page, the sensor data, and the event type to the web page parsing and rendering engine. 
     According to the event type, the web page parsing and rendering engine determines that the first node in the first web page has registered the event, and according to the identifier of the first node and the event type, searches out a portal of the processing logic of the event, and calls the script parsing engine to execute the processing logic. 
     Further, the determining a first web page associated with the event according to the event type and transmitting the first web page, the sensor data, and the event type to the web page parsing and rendering engine specifically includes: if it is determined that the event is associated with a currently active web page, the currently active web page being a first web page, transmitting the first web page, the sensor data, and the event type to the web page parsing and rendering engine; and if it is determined that the event is associated with all web pages in run time, each web page in run time being a first web page respectively, transmitting each first web page, the sensor data, and the event type to the web page parsing and rendering engine. 
     For example, events such as touch flick events and finger tap events are generally associated with the currently active web page only; a direction change event is generally associated with all web pages in run times. All web pages in run time include the currently active web page and web pages that are in run time but not active. 
     Specifically, the transmitting the first web page by the browser Shell to the web page parsing and rendering engine are specifically: transmitting a pointer of a DOM tree corresponding to the first web page to the web page parsing and rendering engine. The first web page may be any one or more web pages, and the first node may be any one or more nodes in the DOM tree of the first web page. 
     Further, to enhance the presentation and interaction capabilities of the web page and improve use experience, logic of adjusting presented web page contents according to the sensor data may be embedded into the event processing logic. Correspondingly, the process of calling the script parsing engine to execute the processing logic specifically includes the following operation: 
     The script parsing engine parses the sensor data and modifies web page contents of the first web page that are stored in the web page parsing and rendering engine. 
     With the above-mentioned example being used herein, it is assumed that direction sensor processing logic is added at the canvas node. The processing logic is to display the current direction at the div node when the state of the direction sensor changes. When the script parsing engine is triggered by the browser Shell to execute the processing logic function (event), the processing logic processes the sensor data transmitted by the browser Shell, and modifies the div node web page contents stored in the web page parsing and rendering engine according to the direction parameter included in the sensor data. The web page parsing and rendering engine updates the web page according to the modified web page contents, and displays the current direction angle, vertical rotation angle, and horizontal rotation angle at the div node. 
     Specifically, when the browser Shell transmits the sensor data to the script parsing engine, the sensor data is generally defined by an interface description language (IDL), and serves as an interface of interaction between javascript and system low-level code. The following is an exemplary interface defined by the IDL: 
     
       
         
           
               
               
             
               
                   
                   
               
             
            
               
                   
                 module events { 
               
            
           
           
               
               
            
               
                   
                 interface [ 
               
            
           
           
               
               
            
               
                   
                 Conditional=ORIENTATION_CHANGED_EVENTS 
               
            
           
           
               
               
            
               
                   
                 ] OrientationChangedEvent { 
               
            
           
           
               
               
            
               
                   
                 readonly attribute float value[3]; 
               
               
                   
                 void initOrientationChangedEvent(in float value[3]); 
               
            
           
           
               
               
            
               
                   
                 }; 
               
            
           
           
               
               
            
               
                   
                 } 
               
               
                   
                   
               
            
           
         
       
     
     In another optional embodiment of the present invention, when a web page is loaded into a browser engine, the browser engine can identify the processing logic added at each node of the web page, and register the event corresponding to the processing logic. Specifically, before step  401 , the method further includes the following steps: 
     The web page parsing and rendering engine reads script contents of the first node in the first web page, and calls the script parsing engine to execute the script contents of the first node. 
     The script parsing engine determines that there is the event type and the processing logic of the event included in the script contents of the first node, and sends the event type and the processing logic of the event to the web page parsing and rendering engine. 
     The web page parsing and rendering engine transmits the processing logic of the event to the script parsing engine to register the event. 
     The script parsing engine encapsulates the processing logic, and returns a portal of the processing logic to the web page parsing and rendering engine. 
     The web page parsing and rendering engine adds the event type of the event and the portal of the processing logic into an event monitoring list of the first node. 
       FIG. 6  is a schematic signaling diagram of loading a browser engine with a web page according to an embodiment of the present invention. As shown in  FIG. 6 , the above-mentioned example is still used herein, and the following steps are included: 
       601 . The web page parsing and rendering engine reads script contents of the canvas node in the web page. 
       602 . The web page parsing and rendering engine calls the script parsing engine to execute the script contents of the canvas node. 
       603 . The script parsing engine adds an event attribute for the canvas node. 
     Specifically, when executing the script contents of the canvas node, the script parsing engine determines that there is the event type and the processing logic of the event included in the script contents of the canvas node, and sends the event type “orientationchanged” and the processing logic function (event) of the event to the web page parsing and rendering engine. 
       604 . The web page parsing and rendering engine adds an event monitoring list for the canvas node. 
       605 . Request the script parsing engine to register the event. 
     Specifically, the web page parsing and rendering engine transmits the processing logic of the event to the script parsing engine. 
       606 . The script parsing engine encapsulates the processing logic, and returns a portal of the processing logic to the web page parsing and rendering engine. 
     Specifically, the portal of the processing logic may be an address for storing the processing logic. 
       607 . The web page parsing and rendering engine adds the event type “orientationchanged” of the event and the portal of the processing logic into an event monitoring list of the canvas node. 
     Specifically, after  607 , the script parsing engine may continue to execute the script contents of the canvas node. When it is determined that the script contents of the canvas node include other processing logic,  603 - 607  can still be performed. Because the event monitoring list of the canvas node is already created,  605  does not need to be repeated. When the script parsing engine finishes executing the script contents of the canvas node, the web page parsing and rendering engine continues to read script contents of other nodes on the web page, and calls the script parsing engine to execute the script contents. 
       FIG. 7  is a schematic signaling diagram of an embodiment of the present invention in an application scenario. In this application scenario, processing logic of the above-mentioned direction sensor is added for the canvas node, and the processing logic is to display current direction at the div node when the state of the direction sensor changes. As shown in  FIG. 7 , a signaling process specifically includes the following steps: 
       701 . The direction sensor senses direction change and transmits direction parameters to the OS in form of an event. 
       702 . According to the direction parameters, the OS determines that the event is a direction change event and transmits the event to a browser Shell. 
       703 . The browser Shell queries the web page parsing and rendering engine as to whether any DOM node has registered the direction change event. 
       704 . The web page parsing and rendering engine traverses DOM nodes, searches an event monitoring list of the DOM nodes, and determines that the canvas node has registered the direction change event. 
       705 . The web page parsing and rendering engine returns to the browser Shell a portal of the processing logic of the direction change event registered by the canvas node. 
       706 . The browser Shell transmits the portal of the processing logic and the direction parameters to the script parsing engine. 
       707 . The script parsing engine parses the direction parameters and executes the processing logic. 
       708 . The script parsing engine modifies the div node contents stored in the web page parsing and rendering engine to display the current direction at the div node. 
     In another optional embodiment of the present invention, when a web page is loaded into a browser engine, the browser engine may perform parsing to obtain an attribute defined at each node of the web page, and register the event corresponding to an event attribute if the attribute is the event attribute. Specifically, before  401 , the following steps are included: parsing, by the web page parsing and rendering engine, the first web page and determining that there is an event attribute defined for the first node in the first web page; determining the event type and processing logic of the event corresponding to the event attribute; transmitting the processing logic of the event to the script parsing engine to register the event; encapsulating, by the script parsing engine, the processing logic, and returning a portal of the processing logic to the web page parsing and rendering engine; and adding, by the web page parsing and rendering engine, the event type of the event and the portal of the processing logic into an event monitoring list of the first node. 
     Further, the determining, by the web page parsing and rendering engine according to the event type, that the first node in the first web page has registered the event specifically includes: determining, by the web page parsing and rendering engine, that the event is independent of location according to the event type, traversing an event monitoring list of each node, and determining that there is the event type of the event included in the event monitoring list of the first node. 
     Optionally, the determining, by the web page parsing and rendering engine according to the event type, that the first node in the first web page has registered the event specifically includes: determining, by the web page parsing and rendering engine, that the event is dependent on location according to the event type, and parsing location information from the sensor data; determining a first node which is matched with the location information and in the first web page according to the location information; and determining that there is the event type of the event included in the event monitoring list of the first node. 
     Specifically, whether the event is dependent on or independent of the location may be determined according to the event type. Generally, environment change sensing events are independent of location, for example, a direction change event, a temperature change event, and the like; touch sensing events are dependent on location, for example, a touch flick event, a finger tap event, and the like. For example, multiple nodes on a web page are located in different positions on the web page, and have all registered a touch flick event. The touch sensor generates sensor data when sensing a touch flick of the user. The sensor data includes location information arising from the touch flick, flick parameters, and the like. The web page parsing and rendering engine determines that the event is dependent on location according to the event type, parses the location information in the sensor data, and determines which node in the web page matches the location information, that is, on which node the touch flick occurs, and then determines whether the matched node has registered the touch flick event, and if yes, sends an identifier of the matched node to the browser Shell. 
     Because the registered event is bound to a DOM node, in responding to an event of the sensor device, it is necessary to traverse the DOM tree to find which DOM node has registered the event of the sensor device. If the DOM tree has many nodes and the depth of the tree is rather great, the traverse is performed at a high cost. Therefore, optimization may be performed by setting up a global event management Hash (Hash) table for the DOM tree to facilitate search in responding to events. In such an application scenario, after the web page parsing and rendering engine adds the portal of the processing logic returned by the script parsing engine and the event type of the event into the event monitoring list of the first node, the following step is included: the web page parsing and rendering engine adds an identifier of the first node and the event type of the event into an event management Hash table. 
     The determining, by the web page parsing and rendering engine according to the event type, that the first node in the first web page has registered the event specifically includes: the web page parsing and rendering engine queries the Hash table and determines that there is the event type of the event included in a table entry corresponding to the identifier of the first node. 
     Specifically, the format of the event management Hash table may be &lt;key, value&gt;, where key is the event type of the event, and value is a DOM node array of the event. The DOM node array may include identifiers of multiple DOM nodes that have registered the event at the same time. Further, an event registration managing module may be added, where the event registration managing module is responsible for event registration management. In specific implementation, it may be a submodule of the web page parsing and rendering engine. Correspondingly, after the signaling process  607  shown in  FIG. 6 , the following steps are included: the web page parsing and rendering engine adds the identifier of the first node and the event type of the event into an event management Hash table stored by the event registration managing module. 
     In application, it is possible that multiple nodes have registered events of the same event type. The web page parsing and rendering engine may send identifiers and event types of the multiple nodes to the browser Shell at the same time, and the browser Shell sends the identifiers, event types and sensor data of the multiple nodes to the web page parsing and rendering engine. According to the identifiers and event types of the multiple nodes, the web page parsing and rendering engine respectively finds a portal of the processing logic of the event registered by each node, and calls the script parsing engine to respectively execute the processing logic of the event registered by the multiple nodes. The events of the same event type, which are registered by different nodes, may have different processing logic. 
     Further, some types of sensor devices may feed back in response to an instruction of the user. In another optional embodiment of the present invention, the browser engine may respond to the event and operate the sensor device. Specifically, the processing logic of the reported event includes a portal of calling a sensing method of a second sensor device, and the calling the script parsing engine to execute the processing logic of the event specifically includes: the script parsing engine calls the sensing method of the second sensor device according to the portal of calling. 
     Specifically, the second sensor device is a sensor device that has a callable sensing method, and may be the same type as or a different type from the first sensor device. Generally, an authorized developer adds a portal of calling the sensing method of the second sensor device into the processing logic of an event of a specific node beforehand. A force feedback sensor in game applications is taken as an example herein. For example, in a baseball game, the force feedback sensor may transmit parameters such as direction and force of a joystick to the browser engine in form of events. In the event processing logic designed by the authorized developer, a vibration method of the force feedback sensor is called as triggered when a contact between the bat and the ball simulated by the joystick is determined according to the sensor data reported by the force feedback sensor, so as to let the user have a feeling of true batting. In this way, when the script parsing engine executes the processing logic of the event, if a contact between the bat and the ball simulated by the joystick is determined according to the sensor data reported by the force feedback sensor, the vibration method of the force feedback sensor is called according to the portal of calling the vibration method of the force feedback sensor, where the portal is included in the processing logic. Specifically, the script parsing engine may use a browser Shell and an OS to call the sensing method of the second sensor device according to the portal of calling. 
     Further, if the sensing method of the sensor device needs to be called, it is generally necessary to register the sensing method onto the script parsing engine first. Correspondingly, before  401 , the following steps are included: the browser Shell obtains, from the OS, the portal of calling the sensing method of the second sensor device; the browser Shell sends the portal of calling the sensing method of the second sensor device to the script parsing engine; and the script parsing engine stores the portal of calling the sensing method of the second sensor device. 
     Specifically, the OS may obtain, from a driver of the second sensor device, the portal of calling the sensing method of the second sensor device, and store it. The script parsing engine stores the portal of calling the sensing method of the second sensor device, that is, after the sensing method is registered, the authorized developer can quote the calling portal in code. 
       FIG. 8  is a schematic signaling diagram of an embodiment of the present invention in another application scenario. In this application scenario, the force feedback sensor may produce vibration to let the user have a feeling of true batting. As shown in  FIG. 8 , a signaling process specifically includes the following steps: 
       801 . A browser Shell obtains, from an OS, a portal of calling a vibration method of a force feedback sensor. 
       802 . The browser Shell registers the vibration method of the force feedback sensor onto a script parsing engine. 
       803 . A game developer calls the vibration method of the force feedback sensor at a specific node in a baseball game page. 
     Specifically, the node has registered a force change event of the force feedback sensor. That is, script contents of the node include processing logic of the force change event, and the processing logic of the force change event includes a portal of calling the vibration method of the force feedback sensor. 
       804 . The script parsing engine runs the script contents of the node. 
     Specifically,  804  may be: The script parsing engine executes the processing logic of the force change event based on the force change event transmitted by the force feedback sensor, where the processing logic is included in the script contents of the node. 
       805 . The script parsing engine calls the vibration method of the force feedback sensor from the browser Shell. 
       806 . The browser Shell calls the vibration method of the force feedback sensor from the OS. 
       807 . The OS calls the vibration method of the force feedback sensor. 
     The embodiment of the present invention adopts such a technique: a sensor device senses a state change, generates sensor data, and transmits the sensor data to an OS in form of an event; the OS determines the event type of the event, and transmits the sensor data and the event type to a browser engine; according to the event type, the browser engine determines that the event has been registered, and executes processing logic of the event. In this way, the browser engine shields difference between different OSs, and solves, to some extent, a problem that an application cannot run across platform due to a direct interaction between a native application and a sensor device in the prior art; with code written only once, the written application is capable of running on different OSs, thereby enabling an application to run across platform. Further, the user logic can interact with the sensor device, and the sensor device not only serves as a unidirectional input source of information, but also responds to the operation of the user. Specifically, logic of responding to/operating the sensor device is embedded into compiled web page code to simplify development. 
     Persons of ordinary skill in the art may understand that all or part of the steps in each of the foregoing method embodiments may be implemented by a program instructing relevant hardware. The program may be stored in a computer readable storage medium. When the program is run, the steps of the forgoing methods in the embodiments are performed. The storage medium includes any medium that is capable of storing program code, such as a read-only memory (ROM), a random-access memory (RAM), a magnetic disk, or an optical disk. 
       FIG. 9  is a schematic structural diagram of a computing node  900  according to an embodiment of the present invention. As shown in  FIG. 9 , the computing node  900  includes: a hardware layer  91 , an OS  92  running on the hardware layer  91 , and a browser engine  93  running on the OS  92 , where the hardware layer  91  includes a first sensor device  911 ; the first sensor device  911  is configured to sense a state change, generate sensor data, and transmit the sensor data to the OS  92  in form of an event; the OS  92  is configured to determine an event type of the event according to the sensor data, and transmit the sensor data and the event type to the browser engine  93 , where the sensor data is also transmitted to the browser engine  93  in form of an event; and the browser engine  93  is configured to determine, according to the event type, that the event has been registered, and execute processing logic of the event. 
     In an optional embodiment of the present invention, the browser engine  93  includes a browser Shell, a web page parsing and rendering engine, and a script parsing engine. 
     The browser Shell is configured to receive the sensor data and the event type sent by the OS, determine a first web page associated with the event according to the event type, and transmit the first web page, the sensor data, and the event type to the web page parsing and rendering engine. 
     The web page parsing and rendering engine is configured to determine, according to the event type, that the first node in the first web page has registered the event, search out, according to the identifier of the first node and the event type, a portal of the processing logic of the event, and call the script parsing engine. 
     The script parsing engine is configured to execute the processing logic of the event. 
     Further, the browser Shell is specifically configured to: if it is determined that the event is associated with a currently active web page, the currently active web page being a first web page, transmit the first web page, the sensor data, and the event type to the web page parsing and rendering engine; and if it is determined that the event is associated with all web pages in run time, each web page in run time being a first web page respectively, transmit each first web page, the sensor data, and the event type to the web page parsing and rendering engine. 
     In another optional embodiment of the present invention, the web page parsing and rendering engine is further configured to read script contents of the first node in the first web page and call the script parsing engine before the first sensor device senses the state change and generates the sensor data. 
     The script parsing engine is further configured to execute the script contents of the first node, determine that there is the event type and the processing logic of the event included in the script contents of the first node, and send the event type and the processing logic of the event to the web page parsing and rendering engine. 
     The web page parsing and rendering engine is further configured to transmit the processing logic of the event to the script parsing engine to register the event. 
     The script parsing engine is further configured to encapsulate the processing logic, and return a portal of the processing logic to the web page parsing and rendering engine. 
     The web page parsing and rendering engine is further configured to add the event type of the event and the portal of the processing logic into an event monitoring list of the first node. 
     In another optional embodiment of the present invention, the web page parsing and rendering engine is further configured to: parse the first web page before the first sensor device senses the state change and generates the sensor data, and determine that there is an event attribute defined for the first node in the first web page; determine the event type and processing logic of the event corresponding to the event attribute; and transmit the processing logic of the event to the script parsing engine to register the event. 
     The script parsing engine is further configured to encapsulate the processing logic, and return a portal of the processing logic to the web page parsing and rendering engine. 
     The web page parsing and rendering engine is further configured to add the event type of the event and the portal of the processing logic into an event monitoring list of the first node. 
     Further, the web page parsing and rendering engine is also configured to determine, according to the event type, that the first node in the first web page has registered the event, where the determining, according to the event type, that the first node in the first web page has registered the event specifically includes: determining that the event is independent of location according to the event type, traversing an event monitoring list of each node in the first web page, and determining that there is the event type of the event included in the event monitoring list of the first node. 
     Optionally, the web page parsing and rendering engine is configured to determine, according to the event type, that the first node in the first web page has registered the event, where the determining, according to the event type, that the first node in the first web page has registered the event specifically includes: determining that the event is dependent on location according to the event type, and parsing location information from the sensor data; determining a first node which is matched with the location information and in the first web page according to the location information; and determining that there is the event type of the event included in the event monitoring list of the first node. 
     In another optional embodiment of the present invention, the web page parsing and rendering engine is further configured to: add an identifier of the first node and the event type of the event into an event management Hash table after the event type of the event and the portal of the processing logic returned by the script parsing engine are added into the event monitoring list of the first node. 
     The web page parsing and rendering engine is configured to search out the portal of the processing logic of the event according to the identifier of the first node and the event type, where the searching out the portal of the processing logic of the event according to the identifier of the first node and the event type specifically includes: querying the Hash table and determining that there is the event type of the event included in a table entry corresponding to the identifier of the first node. 
     In another optional embodiment of the present invention, the script parsing engine is specifically configured to parse the sensor data and modify web page contents of the first web page that are stored in the web page parsing and rendering engine. 
     In another optional embodiment of the present invention, the hardware layer  91  further includes a second sensor device, where the processing logic of the event includes a portal of calling a sensing method of the second sensor device, and the script parsing engine is specifically configured to: call the sensing method of the second sensor device according to the portal of calling. 
     Further, the browser Shell is further configured to: obtain, from an OS, the portal of calling the sensing method of the second sensor device before the first sensor device senses the state change and generates the sensor data; and send the portal of calling the sensing method of the second sensor device to the script parsing engine. 
     The script parsing engine is further configured to store the portal of calling the sensing method of the second sensor device. 
     The computing node provided in the embodiment of the present invention may be a mobile phone, a personal digital assistant (PDA), a set top box, a handheld device in a specific field, and the like. 
     The embodiment of the present invention adopts such a technique: a sensor device senses a state change, generates sensor data, and transmits the sensor data to an OS in form of an event; the OS determines the event type of the event, and transmits the sensor data and the event type to a browser engine; according to the event type, the browser engine determines that the event has been registered, and executes processing logic of the event. In this way, the browser engine shields difference between different OSs, and solves, to some extent, a problem that an application cannot run across platform due to a direct interaction between a native application and a sensor device in the prior art; with code written only once, the written application is capable of running on different OSs, thereby enabling an application to run across platform. Further, the user logic can interact with the sensor device, and the sensor device not only serves as a unidirectional input source of information, but also responds to the operation of the user. Specifically, logic of responding to/operating the sensor device is embedded into compiled web page code to simplify development. 
     It should be noted that, the expression of first and second used in the descriptions of the foregoing embodiments is not intended to limit a sequence, but is only for convenience of distinguishing. 
     Finally, it should be noted that the foregoing embodiments are merely intended for describing the technical solutions of the present invention, other than limiting the present invention. Although the present invention is described in detail with reference to the foregoing embodiments, persons of ordinary skill in the art should understand that they may still make modifications to the technical solutions described in the foregoing embodiments, or make equivalent replacements to some or all the technical features thereof, as long as such modifications or replacements do not cause the essence of corresponding technical solutions to depart from the scope of the technical solutions of the embodiments of the present invention.