FI123400B - Method and device for controlling the scheme of a web service - Google Patents

Description

Method and device for controlling the scheme of a web service

Area

The invention relates to a method and apparatus for controlling a scheme of a web service. In particular, the invention relates to the management of circuits used in binary network services between computer servers or nodes in computer networks.

Background

The following description of the prior art may include insights, discoveries, conceptions, or descriptions, or associations, with descriptions not known in the art prior to the present invention, but resulting from the invention. Some such aspects of the invention may be specifically mentioned below, while other such aspects of the invention will be apparent from their context.

In modern communication and computer networks, the exchange of information between software and computers is an important factor. Different programs, computers and processors exchange information without human intervention. Different environments use different networks and protocols. On the Internet, the Transmission Control Protocol / Internet Protocol (TCP / IP) is the basic communication protocol. TCP / IP takes care of the compilation and decompression of the data transmitted in packets. The IP takes care of the detection so that packets are delivered to the correct destination. TCP / IP uses Hypertext Transfer Protocol HTTP as a client / server protocol. The program can send an HTTP request to a server that responds with another HTTP message.

$ 2 25 The exchange of interoperable messages using the Application Program Interfaces (APIs) provided by the servers on the Internet is accomplished through 0 web services. The web service can be implemented in many ways, typically $ 2 using the REST (Representational State Transfer) model, which includes, for example, the internal features of a network protocol such as HTTP, as well as coding the payload in Extensible Markup Language (XML), or remote ^ called via Simple Object Access Protocol (SOAP), o SOAP is an Internet service message protocol that is widely used on the Internet to send automatic messages between computer servers. SOAP provides an open-format format for exchanging computer-to-computer messages 35 for any purpose. Currently, the content of the SOAP-2 message is encoded using XML. XML can be used to represent any information. The messages consist of structured XML tags. When SOAP messages are sent over the Internet, the messages use an application protocol such as HTTP over TCP / IP or SIP (Session Initiation Protocol) over 5 TCP / IP.

Low-power wireless networks, such as IEEE 802.15.4-based embedded and sensor networks, have very limited packet transmission resources. These networks are very energy efficient and the circuit technology is cheap. As a result, technology is moving into embedded devices very rapidly, for example in automation, measurement, tracking and control.

Current web service technologies are far too complex (titles, content parsing) and heavy (heavy header and content load) on low-performing wireless networks. Recently, binary 15 network service protocols have been developed for low-power wireless networks. The binary web service solution includes the use of a suitable web service protocol (e.g., simplified HTTP or a binary web service protocol, such as Constrained Application Protocol CoAP), and efficient content coding (e.g., Efficient XML Interchange EXI, binary XML or Fast 20 Infoset Fl).

Typical web services use XML to encode content utilizing XML schemas whose namespace information is well known or readily available. Furthermore, even in the absence of accurate schema information, an XML document can be parsed with an endpoint. However, this does not apply to binary web services. To meet the requirements of a very low overhead, XML encoding technologies such as EXI utilize out-of-band 5 schema information (so-called schema-informed space in EXI). bi-

C \ J

^ Many components are needed for the development of virtual network services, such as embedded client devices, proxy servers, and servers. For this system to work most efficiently, all components must have the correct | schema information and must be able to identify which schema is being used for which binary payload of the web service.

CD

J Usually, if the schema has been used to encode the message, the schema ID may have been included in the message header. However, the present state of the art only illustrates how schema information is used to encode or decode payload, but not how schema is identified, managed, and optimized over the entire binary network service system (called domain).

Quick description

An object of the invention is to provide an improved solution for controlling the scheme of a network 5 service between computer servers or nodes in computer networks.

An aspect of the present invention is provided by a device comprising a processor; a memory containing computer program code configured by the processor to cause the device to at least: control the storage of schema information of the 10 binary web service systems, the schematics depicting encoding / decoding of binary XML messages; providing an interface for keeping schema information current on each component of the binary web service system.

In another aspect of the present invention, there is provided a method if-15a: controlling the storage of schema information for a binary web service system, said schematics illustrating encoding / decoding of binary XML messages; and providing an interface for keeping schema information current on each component of the binary network service system.

An aspect of the present invention is provided with a device comprising means for controlling the storage of schema information of a binary web service system, said schematics illustrating encoding / decoding of binary XML messages; means for providing an interface for keeping chart information current in each of the 25 components of the binary network service system.

C/O

An aspect of the present invention is provided by a device comprising a processor; a memory that contains computer program code that is confi

CVJ

9 gourced by a processor to cause the device to at least: load a ™ schema depicting encoding / decoding of binary XML messages; ir 30 analyzing the schema with one or more test payloads; to optimize

CL

schema based on analysis; creating a Code Library based on schema ^.

o ° Pattern list

Embodiments of the present invention will now be described, by way of example only, with reference to the accompanying drawings, in which Figure 4 illustrates an example of a system in which embodiments of the invention may be applied; Figures 2A, 2B and 2C are flow charts illustrating embodiments of the invention; Figures 3A, 3B, 4A, 4B and 4C are flow charts illustrating embodiments of the invention; and Figure 5 illustrates an example of a control device.

Description of Embodiments

The following embodiments are exemplary. Although the description may refer to "" one "embodiment or" "some" embodiments at several points, this does not necessarily mean that each such reference is to the same embodiment or embodiments, or that the feature is applicable to only one embodiment. The individual features of the various embodiments may also be combined to provide other embodiments.

15 As already stated, modern applications run on data processing equipment connected to communication and computer networks communicate with one another. Web service methods, such as SOAP or REST, were designed to provide an appropriate platform for communication between applications running in different environments, operating systems, and different computers.

Generally, web services use XML to encode content. Sent messages are XML documents that contain given elements, some of which are necessary and some are optional. Web services may utilize XML schemas that describe how information is encoded into messages and which elements are necessary and optional. In practice

C/O

In principle, the schema describes the language Dice used to encode the payload of messages and generally includes links to other references such as namespaces.

CVJ

9 Schema is a description of the structure of an XML document. Other form description ™ languages, such as Abstract Syntax Notation One (ASN.1), utilize schematic description of I 30 information grammar and structure.

Figure 1 illustrates an example of a network in which embodiments of the invention may be applied. The exemplary network of Figure 1 comprises a low-power wireless network 110, an Internet / Intranet 122, and an IP-based network having a server 104. The low-power wireless network may be connected to an Internet / Internet and IP-based network by proxy 106. , which is physically 5 either a wireless router between an Internet / Internet intranet and a low-power wireless network or an edge server on an IP network. The proxy node's logical functionality can even be implemented on a server.

In the Internet / Intranet 122 and the IP-based network with the service 104, the communication is implemented using XML coding and transmitted over TCP / IP via HTTP.

The low-power wireless network 110 may be a multi-hop network comprising a plurality of wireless low-power nodes. In this simplified example, one node 108 is described.

In one embodiment, wireless links of wireless network 110 may be implemented using IEEE 802.15.4 with Internet Protocol v6 (6lowpan), IEEE 802.15.4 with ZigBee, Bluetooth, or Bluetooth Ultra Low Power (ULP), low-power wireless LAN (Low Power Wireless Local Area Network), private low power radio, cellular radio system, or any other system suitable for low power transmission. IEEE stands for Institute of Electrical and Electronics Engineers.

The binary web service system utilizes the web service protocol (either binary protocol or full HTTP) and binary coded payload content. These binary techniques are typically applied on a limited network or on limited devices that do not have the resources or capacity to provide complete network services. In Figure 1, a low-power wireless network 110 is such a limited domain consisting of a limited node 108 utilizing a binary network service protocol and payload payload 114. The proxy node or proxy 106 may be used to convert binary network service protocols to payload services 11. can be

C \ J

^ can also be used as a cache or to provide additional security for a limited domain ° so that protocols are not modified or payload encoded. If the payload 30 remains encoded 112, the server 104 must also be aware of the payload | man encoding schema information.

In order for the system architecture of Figure 1 to work effectively,

C/O

J out-of-band schema information is used to encode the content of the load. This is typically XML schema information used, for example, for encoding / decoding between XML content and EXI or Fast Infoset formats. The unit with which the payload is to be parsed, coded or decoded must know the correct schema information.

In one embodiment, the network of Figure 1 comprises a control unit 102 and a circuit configuration memory 120 operatively connected to a control unit 5. One or more components 104, 106, 108 of the network belonging to the binary network service system utilize schema information managed by the control device.

The control device 102 is configured to provide a schema control interface 116a to 116c used with all system components. The Hall-10 device 102 also has an interface 118 with a schema memory 120. The control device can be implemented and positioned in many ways. Typically, device 102 is a separate application on a separate server. It can be integrated with one of the other system components, such as server 104 or proxy or proxy 106.

15 For a binary web service system to work effectively, the same schema configuration must be available for all components. In one embodiment, the management device 102 is configured to maintain schema-related information and provide information to the network service system through the schema management interface 116a-116c. The schema information of one domain 20 should be consistent. A domain can be defined as a set of network service components (nodes, proxies, and servers) that are managed by a management unit that shares the same schema configuration. A management unit can maintain multiple domains, and components can participate in multiple domains (in this case, the inter-domain schema-space may not overlap).

Single domain schemas are assigned a unique identifier, 5 SchemalD. The tag can be an integer, but it can also be an alphabet-

C \ J

^ a meridian name or any other appropriate identifier. In one embodiment, the management device 102 is configured to assign a unique identifier to each domain schema 30 and to maintain information about the identities and the domain | defined schemes. Management device 102 may store information related to IDs and schemas in memory 120.

CD

J In the case of an XML schema, the schema-related information may be a URI pointing to the actual schema on the Internet. The URI comes from the Uniform Resource Identifier. An example URI is a Uniform Resource Locator (URL). An example of a URI pointing to a schema on the Internet is: http://www.example.com/SensorData.xsd

In one embodiment, the control device is configured to track a set of schema information for each domain within the device. The information may be stored in memory 120. Schema information may include a domain, SchemalD, which is always unique within a given domain, and schema-related URI, which may be stored locally or remotely. Schema information may also comprise other configuration information. The following is a pre-10 example of schema information for a domain named www.example.com:

Domain SchemalD Schema www.example.com O http://www.example.com/Default.xsd www.example.com 1 http://www.example.com/SensorData.xsd www.example.com 2 http: / /www.exampie.com/EneravMessaQe.xsd 15 www.example.com 3 http://www.exampie.com/Actuator.xsd

In the example above, the scheme information comprises information from four different schemes having SchemalD's of O, 1,2, and 3.

When a system component (node, proxy, or server) receives an encrypted network service payload, it must know the schema 20 to decode it. In one embodiment, SchemalD is included either in the header of the web service protocol, for example in the HTTP content type header or in the corresponding payload type of other protocols, or in the payload encoding header itself. In the EXI standard, such a SchemalD field is in its own payload header, which can be decoded even though the payload scheme is not yet known. Alternatively, SchemalD may be located immediately after the protocol header, but just before the encoded payload, as a "magic byte". When the encoded payload SchemalD is

C \ J

The interleaved, schema information is retrieved, checked, and then used in decoding.

CVJ

In one embodiment, the circuit configuration information and the silicon related schemas are stored locally on each component. The schema configuration interface 116a - 116c of the control device 102 is used for the same

CD

J to maintain the schema configuration for all components in the same domain.

00 00 The information stored by the control unit 102 can be updated in many different ways. In one embodiment, the circuits are installed on all components by means of a management tool. Adding a new schema to the system is triggered manually via the user or a computer interface. This method can be called a static method.

In one embodiment, the system components automatically search for and configure new schema information. Adding a new schema to the system is done automatically through schema search when new schema is detected. This method can be called a dynamic method.

Fig. 2A is a flowchart illustrating one embodiment of the invention. Figure 2A illustrates an example of a general method for controlling schematics in a binary web service system. In one embodiment, the method is performed in the control device 102 of Figure 1.

The method begins when the management tool interface initiates a static schema deployment 200A or initiates a dynamic schema discovery process 15200B where it is discovered that a particular schema should be added to the binary web service area and supported by all components.

First, in step 202, the schema URI (can point to a local memory or a remote network resource), domain information, and possibly other configuration information is brought into the process. The information is brought into the process either by a management tool, a system component receiving a payload encoded by the unknown scheme, or a system component beginning to provide a service that utilizes a payload encoded by the unknown scheme.

In step 204, the schema is retrieved from the received URI.

In step 206, the correctness of the schema is checked using a suitable schema check tool.

5 If the check fails at step 208, the DTC can be reset.

C \ J

^ static or dynamic process.

In step 210, a free SchemalD is requested for the correct scheme. In one embodiment, free SchemalD can be determined by query | by schema configuration memory 120.

In step 212, the new SchemalD is then stored in the schema URI

C/O

J and possibly with the schema itself and other configuration information to the schema configuration memory 120.

00 35 The next updated schema configuration will be installed on all components within the domain. In this example, it is assumed that the component list is maintained in memory 120. The management device comprises a circuit configuration interface 116A-116C and each system component. In one embodiment, the interface is used by applying a push method in which the control unit updates the configuration of each component.

In one embodiment, the interface is used by applying a pull method in which each component requests new control information from the control. The query can be run at certain intervals.

Figure 2A illustrates a push method for installation. In step 214, the component list is first read from memory 120.

10 In step 216, a new schema is alternately transmitted to each component using the configuration interface 116A-116C.

The method ends in step 218.

Figure 2B illustrates a pulling method for installation. The process begins at step 220 which corresponds to step 212 of Figure 2A.

In step 222, the control receives a request from the system component for new circuit information. The request comes through the configuration boundary interface 116A-116C.

At step 224, the control unit determines whether new schemes have been received since the last update.

If so, the new schema or new schema (s) is sent to the component using the configuration interface 116A-116C in step 226. If not, the component is informed in step 228 that no update is available.

The process ends in step 230.

In one embodiment, especially with embedded nodes, new firmware may need to be created, or some executable code may have to be sent to the node in order to handle the new scheme. When it comes to nodes with processing power, just a new one is enough

CVJ

^ sending schema via interface. Figure 2C illustrates such an embodiment. In one embodiment, the method of Figure 2C may replace the pattern

CVJ

30 2A step 216 or FIG. 2B step 226.

£ The method starts at step 232. At the beginning of the method, the new schema and the node to which the schema is sent are known.

CD

J In step 234, the node type is determined. The node type indicates whether ^ the node code or firmware needs to be updated or recompiled, or ^ 35 whether sending schema information is sufficient.

10

If the code does not require an update, schema information is sent to the node in step 236.

Otherwise, the node code or firmware is generated in step 238 to support the new schema information and the generated code is sent to the 5 nodes in step 240. Instead of generating the code on the control unit, the schema-supporting code can be downloaded from the Internet or memory 120.

The method ends in step 242. The same method can be repeated for all nodes to which schema information must be sent.

In the pull method of Figure 2B, the control device may dynamically generate code or firmware 10 as each node inquires about changes in circuit information. In one embodiment, the control unit generates the codes in advance and stores the new code or firmware. When the node requests changes, the control unit can reciprocally send the generated code.

Fig. 3A is a flowchart illustrating an embodiment of the invention. Figure 3A illustrates an example of a static scheme placement scheme. In one embodiment, the method is executed on a server or computer connected to the binary network service system of Figure 1. In one embodiment, the method may be implemented by a management module software module run on a management device or other server or computer.

In the static schema deployment method, the new schema can be added to the binary web service area using a manual installation method implemented, for example, through a user interface or any suitable computer application interface.

The method begins at step 302.

In step 304, the schema is downloaded to the computer. The schema can be

C/O

5 a pre-designed scheme or it may have been designed with a suitable tool.

C \ J

^ The tool may be a management module software module.

In step 306, the loaded scheme is checked using a suitable verification method known in the art. If the schema fails the check, it | reloading.

At step 308, the verified schema is temporarily stored in the memory

C/O

J to 310. When applied to the user interface, the user can be provided with an interactive step to propose optimizations and corrections to the schema, and potential payloads are designed to achieve the best coding performance. First, in step 312, the schema itself is analyzed using information on coding techniques and schema features.

Next, the user may load one or more test payloads in step 314.

5 At step 316, each test payload is coded using the current scheme.

In step 318, the coding results are analyzed. This analysis may include, for example, the size difference between the coded and the original payload, the identification of non-optimal fields (e.g., strings), and suggestions for better payload design. In one embodiment, this analysis of the test payload (s) includes checking the completeness of the schema for the test payload (s) to ensure that each payload element is defined in the schema. Incomplete schemas are not as effective with binary XML techniques. Next, the data in each element can be analyzed in relation to the schema data type, thus identifying unnecessary strings and complex structures. Also, namespaces that are not defined in the schema cannot be packaged in tight schema-coded encodings, so they are recognized when they cause heavy string strain.

In step 320, the result of the schema and payload analysis is provided to the user or stored.

At step 322, it is decided whether to install the new scheme 202 in the system or to return to improve the payload (s) or the scheme itself to achieve better performance. In one embodiment, the enhancement cycle described is a semi-automated process. In one embodiment, the desired number of analysis and optimization steps are performed. The desired amount may be a predetermined amount or may be received as an input

C \ J

^ from the interface. In one embodiment, analysis of the ineffective features of the schema and payload (- ° loads) allows for gradual changes to the schema and also to the payload using coding efficiency | results as a measure of success.

If the schema is installed, it will be exported to the schema installation diagram of FIG. 2A.

C/O

J method.

Figures 3A and 3B illustrate another embodiment of the invention. In this embodiment, the management tool software module can be utilized to perform the process described in connection with Figure 3A to produce a new code library 12 for embedded device developers to use this new schema for firmware development. In this embodiment, the process is performed as shown in Figure 3A up to step 324, from which the process continues as shown in Figure 3B. The management tool software module can thus be configured to analyze and optimize the schema and to test the schema with a variety of payloads.

In step 326, a firmware library is created from the optimized schema. In step 328, the firmware library is stored in memory 120. This firmware can be used later in the method of Figure 2C. The process ends in step 330. The process may be implemented as a management tool software module tool run on a management device or other server or computer. The tool does not need to be online connected to the components of the binary web service when running the process of Figures 3A and 3B.

Figures 4A-4C are flow charts illustrating embodiments of the invention. The figures illustrate examples of a dynamic schema allocation method in which domain components initiate a procedure for installing a new schema on a domain. The figures show three different examples where the schema could be dynamically searched.

Figure 4A illustrates an example 402 in which a proxy can receive a notification from a node about the resources it provides. Such notice contains information about the input / output payload schemes for its resources (for example, in WADL, Web Application Description Language, or, in WSDL, Web Services Description Language). This may be the case, for example, when installing a new node on a domain.

In step 404, the proxy parses the notification and determines the number of schemas in the notification.

(M

^ In step 406, the proxy server retrieves the schema.

In step 408, the proxy checks if the schema is known

C \ J

30 area. In one embodiment, the proxy requests 118 schemas from memory | he 120.

In step 410, the LIRITs of the new circuits are transmitted to the control unit J 102 via interface 116 (116A-116C). Steps 406 through 410 are performed on all? le notification schemes. The process continues 412 as shown in Figure 2A.

C \ 1 13

Figure 4B illustrates an example 414 in which a proxy or server has received a new request with a non-coded payload (e.g., a full web service HTTP request).

In step 416, the proxy or server removes the complete schema 5 from the URI itself payload. A well-formed XML payload contains a schema URI.

In step 418, the schema URI is transmitted to the control device 102 via interface 116 (116A-116C). The process continues 420 as shown in Figure 2A.

Figure 4C illustrates an example 422 in which an application in the domain node 10 requests the use of a new schema. This may be the case, for example, when new services are updated for a domain node. Alternatively, the node may request the use of a schema that exists, but the node does not know which SchemalD should be used.

Step 424 checks whether the schema is in the domain configuration.

If not, a new schema URI is found. The URI can point to the Internet or the node can save the schema. The scheme URI is transmitted to the control device 102 via interface 116 (116A-116C) in step 432. The method continues 434 as shown in Figure 2A.

If a schema exists, step 426 checks whether the schema ID is unknown. If not, the method terminates in step 430.

If SchemalD is unknown, a new SchemalD is requested from control device 102 via interface 116 (116A to 116C) in step 428.

The method ends in step 430.

Figure 5 illustrates an example of a control unit 102. The control unit 102 may be implemented as an electronic digital computer, which may comprise: o working memory (RAM) 500, central processing unit (CPU) 502, and system clock 504.

C \ J

The CPU 502 may comprise a plurality of registers, an arithmetic logic unit, and a control unit. The control unit is controlled by a sequence of program instructions that have been transferred to ^ 30 CPUs from the working memory. The control unit may comprise a set of micro instructions in the basic | for operations. The implementation of the micro instructions may vary depending on the implementation of the CPU. Programming instructions can be coded in a programming language that can be a horn »J-level programming language such as C, Java, etc., or low-level programming? language, such as machine language or assembler. The Electronic Digital Computer ™ 35 may also comprise an operating system that can provide system services to a computer program written in program instructions. The management device 102 is configured 14 to communicate with the low-power wireless network and the Internet / Internet intranet using a suitable interface 506. The interface may comprise a wireless transceiver configured to provide the device with a wireless connection and a transceiver configured to provide the device 5 with an Internet connection. Transceivers may be implemented using solutions known in the art. In addition, the device may comprise a user interface 608, such as a display and a keyboard. The node may comprise a memory 500 for storing software and other data. The apparatus comprises a processing unit 502 configured to perform the process described in connection with Figures 2A and 2B. The processing unit 10 may be configured to control the storage of schema information for the binary web service system, which schematics describe the encoding / decoding of the binary XML messages; and controlling the device to provide an interface for keeping schema information current on each component of the binary network service system, the interface being configured to communicate with system components utilizing appropriate protocols and methods.

In one embodiment, the device may be implemented as software on a router or a computer connected to a binary network service area, or on a proxy or low-end wireless network and Internet / Internet intranet, or on a node or edge server on an IP network.

In one embodiment, a computer program is implemented on a distribution medium, the program comprising program instructions which, when downloaded to an electronic device, implements a computer process comprising: controlling the storage of schema information for a binary web service system; the schematics illustrating encoding / decoding binary XML messages; and providing an interface for keeping schema information current in each of the components of the binary network service system.

C \ J

The computer program may be in source code, object code, or some intermediate form, and may be stored in some form of intermediary, which may be any entity or device capable of relaying | this program. Such mediators include, for example, storage media, computer memory, read-only memory, and a software distribution package. Depending on the required pro-

C/O

From the processing capability, the computer program may be executed in one electronic ° digital controller or may be distributed among a set of controllers.

00 35 It will be clear to one skilled in the art that as technology advances, the inventive concept can be implemented in many ways. Embodiments of the invention are not limited to the examples described above, but may be modified within the scope of the claims.

C/O

δ

C \ J

i

CVJ

o

CVJ

X

cc

CL

δ

LO

O

δ

CVJ

Claims (22)

An apparatus comprising a processor (502); a memory (500) containing computer program code configured by the processor to cause the device to at least: control the storage of schema information of the binary network service system comprising more than one system component such as servers, proxies and low-power wireless nodes, schema information includes a schema URI (Uniform Resource Identi-10 tier) and a specified identifier and domain, which schematics encode / decode binary XML messages; providing an interface for keeping schema information current on each component of the binary web service system. The device of claim 1, wherein the processor and memory containing the computer program code are further configured to cause the device to: receive an address associated with the schema; assigns a schema identifier; Save schema and tag; 20 distributes schema information to system components. The device of claim 1 or 2, wherein the processor and the memory containing the computer program code are further configured to cause the device to: verify the schema's validity before storing and distributing the schema. C/O The device according to any one of claims 1 to 3, wherein the processor and the memory containing the computer program code are further configured to cause the device: ™ to transmit to each system component via a schema 3. message. The device according to any one of claims 1 to 4, wherein the processor and the memory containing the computer program code are still cone? gurued to cause the device: o the CVJ to receive a request for a new schema from the component via the interface and respond by sending information about the stored schema. The device according to any one of claims 1 to 5, wherein the processor and the memory containing the computer program code are further configured to cause the device to: receive from the computer functionally connected to the system information about the new scheme to be added to the system via an interface. The device according to any one of claims 1 to 6, wherein the processor and the memory containing the computer program code are further configured to cause the device to: receive a request from a system component via the interface to add a new schema to the system comprising the schema address. The device according to any one of claims 1 to 7, wherein the schema information comprises a schema identifier, a schema address, and a system identifier. The device according to any one of claims 1 to 8, wherein the processor and the memory containing the computer program code are further configured to cause the device to: 20 generate a node's firmware or code to support the new circuit information; and sends the firmware or code to the node. A method, characterized by controlling the storage of schema information 25 of a binary network service system comprising more than one system component such as servers, proxies and low-power wireless nodes 5, which schema information includes a schema URI (Uniform Resource Identifier C). And a specified identifier and domain, which schematics describe the encoding / decoding of binary XML messages; and CVJ 30 are provided as an interface for keeping chart information current each component of the binary web service system. The method of claim 10, further comprising: receiving the address associated with the schema CD J; ° assigning a scheme identifier; 00 35 storing the schema and the identifier; and distributing schema information to the system components. The method of claim 10 or 11, further comprising: transmitting a schema message to each system component via an interface. The method of any one of claims 10 to 12, further comprising: receiving a request for a new schema from the component via the interface and responding by transmitting information about the stored schema. The method of any one of claims 10 to 13, wherein the schema information comprises a schema identifier, a schema address, and a system identifier. The method of any one of claims 10 to 14, further comprising: generating a firmware or code for the node to support the new schema information; and sending the firmware or code to the node. A computer program product which encodes instructions for a computer program to perform a computer process according to the method of any one of claims 10 to 15. A computer program distribution medium that is computer readable and encodes instructions for a computer program to perform a computer process according to the method of any one of claims 10 to 15. A computer program distribution medium according to claim 17, comprising at least one of a computer readable medium, a program storage medium, a storage medium, a computer readable memory, a computer readable software distribution package and a computer readable compressed software package. A device characterized in that it has means (502) for controlling the storage of schema information of a binary network service system comprising more than one system component such as servers, proxy servers and wireless low power nodes, the schema information including schema URI a Uniform Resource Identifier and a specified identifier and domain, which schematics describe the encoding / decoding of binary XML messages; means (502) for providing an interface for keeping schema information current in each component of the binary network service system. The apparatus of claim 19, comprising means for receiving an address associated with a schema; means for assigning an identifier to the scheme; means for storing the schema and the tag; 10 means for distributing schema information to system components. A device comprising a processor (502); a memory (500) containing computer program code configured by the processor to cause the device to at least: load a schema depicting encoding / decoding of binary XML messages; analyzing the schema with one or more test payloads; optimizing the scheme based on the analysis; 20 is a schematic representation of a Code Library for encoding / decoding the associated XML according to the schema. The device of claim 21, wherein the processor and the memory containing the computer program code are further configured to cause the device to repeat the analysis and optimization steps as desired. CO δ C \ J i CVJ o CVJ X cc CL δ LO O δ CVJ