Compact composite resource

Abstract

A network node configured to communicate with a wireless device (WD) using at least one of a wired connection and a wireless connection is described. The network node includes processing circuitry configured to determine a compact composite (CC) object associated with a resource model, where the determined CC object is to be implemented by a WD and includes at least one of a structure description resource and a compact data resource. The structure description resource includes one or more links directed to one or more resources accessible by the network node, and the compact data resource includes one or more data values associated with the one or more resources. The processing circuitry is further configured to perform at least one action to collect information associated with at least one of the CC object, the structure description resource, and the compact data resource.

Description

Technical Field

[0001] The present disclosure relates to wireless communications, and in particular to machine-to-machine communications such as lightweight machine-to-machine communications and associated object and resource models. Background Art

[0002] The 3rd Generation Partnership Project (3GPP) has developed and is developing standards for 4th (4G) (also known as Long Term Evolution (LTE)), 5th (5G) (also known as New Radio (NR)), and 6th (6G) generation wireless communication systems. Such systems provide, among other features, broadband communications between network nodes (NN) (e.g., base stations) and mobile wireless devices (WD) (e.g., user equipment (UE)), as well as communications between network nodes and between WDs (e.g., machine-to-machine (M2M) communications).

[0003] In addition, the Open Mobile Alliance (OMA) has developed and is developing specifications and / or other technical documents for the wireless communications industry, such as the OMA Lightweight M2M (LwM2M) object and resource model. The OMA LwM2M object and resource model represents information about a device using a set of resources grouped together in the form of objects. Each resource is an atomic value of interest, such as the "current temperature" or "minimum observed temperature" for an object representing information from a temperature sensor. Resources have basic data types (e.g., integer, Boolean, string) without complex substructures.

[0004] Objects are standardized in OMA, where each object is given a unique ID number that can be used in implementations that use the standard (e.g., "3303" for an IPSO temperature object). In addition, each resource has an ID that is either unique in the context of that object, or, in the case of a reusable resource, globally unique and registered in the same registry as the object ID (e.g., "sensor value" for a sensor object is "5700"). Multiple instances of objects and resources can also exist within an object, and instance IDs (usually a running index starting from zero) can be assigned to the multiple instances when the object is created.

[0005] The LwM2M protocol can be used to create, read, update, and delete such objects on an LwM2M client. The object model can also be used by other protocols and systems. Object, resource, and instance IDs are used to refer to specific parts of an object to read and write values. A protocol (e.g., LwM2M) can use a read operation with a resource ID to retrieve a single resource value, or a read operation with an object ID to retrieve all resources of an object at once. The LwM2M protocol also supports a "read composite" method for reading a selected set of resources in one or many objects. When multiple resources are read simultaneously, they are represented using one of the structured standardized data formats used by LwM2M (Sensor Measurement List (SenML) JavaScript Object Notation (JSON), Type Length Value (TLV), Concise Binary Object Representation (CBOR), SenML CBOR). These formats present data using a combination of object, resource, and instance IDs (e.g., " / 3303 / 0 / 5700" for the current value of the temperature object instance 0) and the resource value itself (e.g., "42"). For example, in SenML JSON notation, the current value of a temperature object could be [{"n":" / 3303 / 0 / 5700","v":42}].

[0006] In addition, the LwM2M protocol uses two mechanisms to link information elements: object links and the Constrained RESTful Environment (CoRE) link format. An object link is a link used to refer to a given object instance on the same client in the form of "ObjectID:InstanceID". CoRE links describe relationships between Constrained Application Protocol (CoAP) resources, which can be in the form of relative or absolute Uniform Resource Locators (URLs). Relative URLs in LwM2M usage can refer to LwM2M objects and resources on the same device. For example, in the case of LwM2M, the link "<!--3303 / 0 / 5700--> " will point to the Current Value resource of the Temperature Sensor object as discussed above.

[0007] Object Linking can be used to create LwM2M Composite Objects, which are objects created from existing objects by using Object Link resources pointing to different object instances. For example, a Thermostat object can be linked to Temperature, Setpoint, and Actuation objects. In this case, the new composite object structure is fixed at design time, and only all objects are used at composite time.

[0008] Structured formats used by LwM2M for object serialization (SenML, etc.) allow implementations to handle data with multiple resource values, but they can also introduce significant overhead for the transmission of data because the format includes identifiers (IDs) for objects and resources.

[0009] In some use cases, multiple different values ​​are sent together. Examples include smart metering (e.g., current value and average) and geolocation (latitude, longitude, and altitude values).

[0010] One way to solve the problem of efficiently combining multiple data elements into a single resource would be to define and standardize a new resource, such as an array structure, that contains all the required values ​​in a single resource. However, the approach of simply packaging multiple data values ​​into a single resource has several disadvantages, such as:

[0011] -The resource format becomes specific to that use. A specific parser for the resource is needed (e.g. a program reading an array of data will need specific knowledge to tell which array item has what meaning).

[0012] - Unable to describe the details of the embedded data items, such as their type, units, min / max values, etc., which have standard attributes in the resource description format of LwM2M objects.

[0013] - Values ​​in the packed format cannot be manipulated independently: it is not possible to read and / or change individual values ​​embedded in a resource. It is not possible to observe (e.g., determine) changes to individual values ​​(a common usage pattern for LwM2M). Summary of the invention

[0014] Some embodiments advantageously provide methods, systems, and apparatus for determining compact composite resources. Some other embodiments provide methods, systems, and apparatus for machine-to-machine communications such as lightweight machine-to-machine communications and associated object and resource models. In some embodiments, the LwM2M object model and protocol are extended to allow complex composite data types to support use cases where multiple different values ​​are sent together.

[0015] In one or more embodiments, a method is described to describe the structure and semantics of a resource (eg, a structured LwM2M resource) in terms of other resources. Links to the resource may be used along with additional information on how to map values ​​in the resource to the new structured resource.

[0016] In some embodiments, an object (such as a "compact composite" LwM2M object) is introduced that has the following two key resources:

[0017] 1) A "structural description" resource (i.e., a set of links to resources in an object hosted by the device)

[0018] 2) A resource that contains the result of combining the values ​​of these resources into a single compact structure, as described in that description

[0019] In some other embodiments, a compact composite (CC) object links to resources defined by an existing object, which can help preserve the ability for finer-grained access and semantics of individual resources (since the original resource can be discovered from the CC object link when needed).

[0020] In an embodiment, a LwM2M management server (MS) may use a compact structure format to create a compact composite object for a set of resources it needs to access. The MS may also discover existing compact composite objects. By inspecting linked resources, the structure of the combined resources may be determined (e.g., fully determined), e.g., without requiring additional specific knowledge of the object. In another embodiment, (e.g., instead of an object dedicated to the information), the structure description format may be used as a resource or metadata in an existing object to describe one or more resources of the object, i.e., an "inline description".

[0021] In another embodiment, a method for a LwM2M object model is described. The method and / or the LwM2M object model may be used to collect a set of resources into a structured resource, for example, while preserving the capabilities and original semantics of the individual resources.

[0022] In some embodiments, a combination of CoRE link format pointers may be used, such as: 1) JSON pointer / path statement or XPath statement; or 2) JSON / XML template. A combination of CoRE link format pointers may be used to describe how data elements are constructed in a resource.

[0023] One or more embodiments can combine the well-structured and fine-grained semantics of the LwM2M object model with alternative representations of resource combinations into a compact structured set. In addition, one or more embodiments can maintain the existing functionality of the LwM2M object model and protocol to interact with atomic portions of data and describe their semantics in detail, for example, while providing additional, configurable representations of these resources when software applications request (e.g., require) these resources.

[0024] Some embodiments reduce the overhead associated with transmitting multiple resource values ​​at once and provide a method for combining multiple separate but related resources into one resource. A more compact representation can reduce transmission time and, particularly for wireless sensors, can reduce energy consumption. A compact data representation is particularly beneficial for sensors that are difficult to physically access (e.g., sensors built into concrete) and replace batteries.

[0025] According to one aspect, a network node is described that is configured to communicate with a wireless device (WD) using at least one of a wired connection and a wireless connection. The network node includes a processing circuit that is configured to determine a compact composite (CC) object associated with a resource model, wherein the determined CC object is to be implemented by the WD and includes at least one of a structure description resource and a compact data resource. The structure description resource includes one or more links to one or more resources accessible by the network node, and the compact data resource includes one or more data values ​​associated with the one or more resources. The processing circuit is also configured to perform at least one action to collect information associated with at least one of the CC object, the structure description resource, and the compact data resource.

[0026] In some embodiments, determining the CC object includes creating the CC object, wherein creating the CC object includes sending a first request for creating the CC object, the first request triggering the WD to implement the CC object.

[0027] In some other embodiments, determining the CC object includes discovering the CC object at least by sending a second request for reading the one or more links.

[0028] In an embodiment, determining the CC object comprises examining one or more links to determine a structure of the compact data resource and performing the at least one action to collect the information based on the determined structure.

[0029] In another embodiment, performing the at least one action includes causing sending a third request for creating or discovering another CC object based on examining the one or more links.

[0030] In some embodiments, CC objects are pre-instantiated in the WD.

[0031] In some other embodiments, the processing circuit is further configured to: perform at least one of the following reception: receiving a data request for providing data associated with a CC object from a software application, and receiving a CC object identifier from a WD; and determine the CC object based on at least one of the received data request and the received CC object identifier.

[0032] In an embodiment, the processing circuit is further configured to cause sending a fourth request for creating a compact data resource using a compound read operation or updating a compact data resource using a compound read operation. The fourth request includes an indication indicating whether the compact data resource is to be created or updated.

[0033] In another embodiment, the one or more links point to at least one of an array of data values ​​and a mapping of data values.

[0034] In some embodiments, at least one of the following is true: the information includes one or more data values ​​associated with one or more resources; the resource model is a lightweight machine-to-machine (LwM2M) object resource model; the CC object is a CC LwM2M object; the network node is a LwM2M management server; and the WD is a LwM2M client.

[0035] According to another aspect, a method in a network node is described, the network node being configured to communicate with a wireless device (WD) using at least one of a wired connection and a wireless connection. The method includes determining a compact composite (CC) object associated with a resource model, wherein the determined CC object is to be implemented by the WD and includes at least one of a structure description resource and a compact data resource. The structure description resource includes one or more links to one or more resources accessible by the network node, and the compact data resource includes one or more data values ​​associated with the one or more resources. The method also includes performing at least one action to collect information associated with at least one of the CC object, the structure description resource, and the compact data resource.

[0036] In some embodiments, determining the CC object includes creating the CC object.Creating the CC object includes sending a first request for creating the CC object, the first request triggering the WD to implement the CC object.

[0037] In some other embodiments, determining the CC object includes discovering the CC object at least by sending a second request for reading the one or more links.

[0038] In an embodiment, determining the CC object comprises examining one or more links to determine a structure of the compact data resource and performing the at least one action to collect the information based on the determined structure.

[0039] In another embodiment, performing the at least one action includes causing sending a third request for creating or discovering another CC object based on examining the one or more links.

[0040] In some embodiments, CC objects are pre-instantiated in the WD.

[0041] In some other embodiments, the method further includes receiving at least one of: receiving a data request from a software application for providing data associated with a CC object, and receiving a CC object identifier from a WD; and determining the CC object based on at least one of the received data request and the received CC object identifier.

[0042] In an embodiment, the method further comprises sending a fourth request for creating the compact data resource using the compound read operation or updating the compact data resource using the compound read operation, wherein the fourth request comprises an indication indicating whether the compact data resource is to be created or updated.

[0043] In another embodiment, the one or more links point to at least one of an array of data values ​​and a mapping of data values.

[0044] In some embodiments, at least one of the following is true: the information includes one or more data values ​​associated with one or more resources; the resource model is a lightweight machine-to-machine (LwM2M) object resource model; the CC object is a CC LwM2M object; the network node is a LwM2M management server; and the WD is a LwM2M client.

[0045] According to one aspect, a wireless device (WD) is described that is configured to communicate with a network node using at least one of a wired connection and a wireless connection. The WD includes a processing circuit that is configured to determine a compact composite (CC) object associated with a resource model. The determined CC object is implemented by the WD and includes at least one of a structure description resource and a compact data resource. The structure description resource includes one or more links to one or more resources accessible by the network node, and the compact data resource includes one or more data values ​​associated with the one or more resources. The processing circuit is also configured to perform at least one action to provide information associated with at least one of the CC object, the structure description resource, and the compact structure resource.

[0046] In some embodiments, determining the CC object includes creating the CC object based on a first request received from the network node.

[0047] In some other embodiments, determining the CC object includes making the CC object discoverable by the network node based on a second request received from the network node to read the one or more links.

[0048] In an embodiment, the provided information triggers the network node to examine one or more links to determine the structure of the compact data resource.

[0049] In another embodiment, the processing circuit is further configured to: receive a third request for creating or discovering another CC object based on checking the one or more links.

[0050] In some embodiments, CC objects are pre-instantiated in the WD.

[0051] In some other embodiments, the processing circuit is further configured to cause sending of a CC object identifier that can be used by the network node to determine the CC object.

[0052] In an embodiment, the processing circuit is further configured to receive a fourth request for creating a compact data resource using a compound read operation or updating a compact data resource using a compound read operation. The fourth request includes an indication indicating whether the compact data resource is to be created or updated.

[0053] In another embodiment, the one or more links point to at least one of an array of data values ​​and a mapping of data values.

[0054] In some embodiments, at least one of the following is true: the information includes one or more data values ​​associated with one or more resources; the resource model is a lightweight machine-to-machine (LwM2M) object resource model; the CC object is a CC LwM2M object; the network node is a LwM2M management server; and the WD is a LwM2M client.

[0055] According to another aspect, a method in a wireless device (WD) is described, the WD being configured to communicate with a network node using at least one of a wired connection and a wireless connection. The method includes determining a compact composite (CC) object associated with a resource model, wherein the determined CC object is to be implemented by the WD and includes at least one of a structure description resource and a compact data resource. The structure description resource includes one or more links to one or more resources accessible by the network node, and the compact data resource includes one or more data values ​​associated with the one or more resources. At least one action is performed to provide information associated with at least one of the CC object, the structure description resource, and the compact structure resource.

[0056] In some embodiments, determining the CC object includes creating the CC object based on a first request received from the network node.

[0057] In some other embodiments, determining the CC object includes making the CC object discoverable by the network node based on a second request received from the network node to read the one or more links.

[0058] In an embodiment, the provided information triggers the network node to examine one or more links to determine the structure of the compact data resource.

[0059] In another embodiment, the method further comprises receiving a third request for creating or discovering another CC object based on checking the one or more links.

[0060] In some embodiments, CC objects are pre-instantiated in the WD.

[0061] In some other embodiments, the method further includes sending a CC object identifier that can be used by the network node to determine the CC object.

[0062] In an embodiment, the method further comprises receiving a fourth request for creating a compact data resource using a compound read operation or updating a compact data resource using a compound read operation, the fourth request comprising an indication indicating whether the compact data resource is to be created or updated.

[0063] In another embodiment, the one or more links point to at least one of an array of data values ​​and a mapping of data values.

[0064] In some embodiments, at least one of the following is true: the information includes one or more data values ​​associated with one or more resources; the resource model is a lightweight machine-to-machine (LwM2M) object resource model; the CC object is a CC LwM2M object; the network node is a LwM2M management server; and the WD is a LwM2M client. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] A more complete understanding of the present embodiments and the attendant advantages and features thereof will be more readily appreciated by reference to the following detailed description when considered in conjunction with the accompanying drawings, in which:

[0066] Figure 1 is a schematic diagram illustrating an example network architecture of a communication system connected to a host computer via an intermediate network according to the principles of the present disclosure;

[0067] Figure 2 is a block diagram of a host computer communicating with a wireless device via a network node over an at least partially wireless connection according to some embodiments of the present disclosure;

[0068] Figure 3 is a flow chart illustrating an example method for executing a client application at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0069] Figure 4 is a flow chart illustrating an example method for receiving user data at a wireless device implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0070] Figure 5 is a flow chart illustrating an example method implemented in a communication system including a host computer, a network node, and a wireless device for receiving user data from a wireless device at a host computer according to some embodiments of the present disclosure;

[0071] Figure 6is a flow chart illustrating an example method for receiving user data at a host computer implemented in a communication system including a host computer, a network node, and a wireless device according to some embodiments of the present disclosure;

[0072] Figure 7 is a flow chart of an example process in a network node according to some embodiments of the present disclosure;

[0073] Figure 8 is a flow chart of an example process in a wireless device according to some embodiments of the present disclosure;

[0074] Fig. 9 is a flow chart of another example process in a network node according to some embodiments of the present disclosure;

[0075] Fig.10 is a flow chart of another example process in a wireless device according to some embodiments of the present disclosure;

[0076] Fig.11 shows an example high level system overview according to some embodiments of the present disclosure;

[0077] Fig.12 shows an example sequence diagram according to some embodiments of the present disclosure;

[0078] Fig.13 illustrates example discovery of target link content according to some embodiments of the present disclosure; and

[0079] Fig.14 An example sequence diagram of inline description according to some embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0080] Before describing the example embodiments in detail, it is noted that the embodiments reside primarily in combinations of device components and processing steps related to determining compact composite resources. Therefore, components are appropriately represented in the drawings by conventional symbols, and only those specific details relevant to understanding the embodiments are shown so as not to obscure the present disclosure with details that are obvious to those of ordinary skill in the art having the benefit of the description herein. Like numerals refer to like elements throughout the specification.

[0081] As used herein, relational terms (e.g., "first" and "second", "top" and "bottom", etc.) may be used only to distinguish one entity or element from another entity or element, without necessarily requiring or implying any physical or logical relationship or order between these entities or elements. The terms used herein are only used for the purpose of describing specific embodiments, not for limiting the concepts described herein. Unless the context clearly indicates otherwise, the singular forms "one", "an", and "the" as used herein are intended to also include plural forms. It will also be understood that the terms "including", "having", and / or "comprising" when used herein indicate the presence of stated features, elements, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, steps, operations, elements, components, and / or combinations thereof.

[0082] In the embodiments described herein, the connection terms "in communication with..." and the like may be used to indicate electrical communication or data communication, which may be achieved, for example, by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling, or optical signaling. Those skilled in the art will appreciate that multiple components may interoperate and that modifications and variations may be implemented for electrical and data communications.

[0083] In some embodiments described herein, the terms "coupled," "connected," and the like may be used herein to indicate connections, although not necessarily directly indicated, and may include wired and / or wireless connections.

[0084] The term "network node" as used herein may be any kind of network node included in a radio network, and the network node may also include any of the following: a base station (BS), a radio base station, a base transceiver station (BTS), a base station controller (BSC), a radio network controller (RNC), a gNodeB (gNB), an evolved NodeB (eNB or eNodeB), a NodeB, a multi-standard radio (MSR) radio node (such as an MSR) BS), multi-cell / multicast coordination entity (MCE), integrated access and backhaul (IAB) node, relay node, donor node control relay, radio access point (AP), transmission point, transmission node, remote radio unit (RRU) remote radio head (RRH), core network node (e.g., mobility management entity (MME), self-organizing network (SON) node, coordination node, positioning node, MDT node, etc.), external node (e.g., third-party node, node outside the current network), node in distributed antenna system (DAS), spectrum access system (SAS) node, element management system (EMS), server (e.g., LwM2M server, LwM2M management server, LwM2M boot server), client (e.g., LwM2M client, IoT device / gateway), etc. The network node may also include test equipment. The term "radio node" used in this article may also be used to represent a wireless device (WD), such as a wireless device (WD) or a radio network node.

[0085] In some embodiments, the non-limiting terms wireless device (WD) or user equipment (UE) are used interchangeably. The WD in this article can be any type of wireless device capable of communicating with a network node or another WD via a radio signal, such as a wireless device (WD). The WD can also be a radio communication device, a target device, a device-to-device (D2D) WD, a machine type WD, or a WD capable of machine-to-machine communication (M2M), a low-cost and / or low-complexity WD, a sensor equipped with a WD, a tablet computer, a mobile terminal, a smart phone, a laptop embedded device (LEE), a laptop mounted device (LME), a USB adapter or a client terminal equipment (CPE), an Internet of Things (IoT) device or a narrowband IoT (NB-IOT) device, a server (e.g., a LwM2M server, a LwM2M management server, a LwM2M boot server), a client (e.g., a LwM2M client, an IoT device / gateway), etc.

[0086] In some embodiments, the LwM2M client may be a component running on a device (such as a WD) implementing the LwM2M protocol, for example, for interacting with a LwM2M server and / or a LwM2M boot server. The LwM2M client may be implemented in IoT devices and gateways. The LwM2M server may be a component (e.g., a NN) that implements the server-side functionality of the LwM2M protocol, for example, for interacting with a LwM2M client. The LwM2M server software (i.e., a software application on the NN) may run on a non-IoT device (e.g., a NN) (e.g., a local server or a cloud-based infrastructure).

[0087] In addition, in some embodiments, the general term "radio network node" is used. It can be any type of radio network node, including any of the following: base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), NodeB, gNB, multi-cell / multicast coordination entity (MCE), IAB node, relay node, access point, radio access point, remote radio unit (RRU) remote radio head (RRH).

[0088] Note that although terminology from one particular wireless system (e.g., 3GPP LTE and / or New Radio (NR)) may be used in the present disclosure, this should not be considered to limit the scope of the present disclosure to only the aforementioned systems. Other wireless systems (including but not limited to Wideband Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB), Global System for Mobile Communications (GSM), and LwM2M) may also benefit from utilizing the concepts covered within the present disclosure.

[0089] Also note that the functions performed by a wireless device or network node described herein may be distributed across multiple wireless devices and / or network nodes. In other words, it is contemplated that the functions of the network nodes and wireless devices described herein are not limited to being performed by a single physical device, but may in fact be distributed across several physical devices.

[0090] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present disclosure belongs. It will be further understood that the terms used herein should be interpreted as being consistent with their meanings in the context of this specification and the relevant technology, and not interpreted as ideal or overly formal meanings, unless so explicitly defined herein.

[0091] Referring now to the drawings, in which like elements are referred to by like reference numerals, Figure 1, a schematic diagram of a communication system 10 according to an embodiment is shown, for example, a 3GPP-type cellular network that can support standards such as LTE and / or NR (5G), which includes an access network (e.g., a radio access network) 12 and a core network 14. The access network 12 includes a plurality of network nodes 16a, 16b, 16c (collectively referred to as network nodes 16), such as NBs, eNBs, gNBs or other types of radio access points, each of which defines a corresponding coverage area 18a, 18b, 18c (collectively referred to as coverage area 18). Each network node 16a, 16b, 16c can be connected to the core network 14 via a wired or wireless connection 20. A first wireless device (WD) 22a located in the coverage area 18a is configured to be wirelessly connected to the corresponding network node 16a or to be paged by the corresponding network node 16a. A second WD 22b in the coverage area 18b can be wirelessly connected to the corresponding network node 16b. Although multiple WDs 22a, WD22b (collectively referred to as wireless devices 22) are shown in this example, the disclosed embodiments are equally applicable to situations where only a single WD is located in the coverage area or a single WD is connected to a corresponding network node 16. Note that although only two WDs 22 and three network nodes 16 are shown for convenience, the communication system may include more WDs 22 and network nodes 16.

[0092] Additionally, it is contemplated that the WD 22 may communicate simultaneously with more than one network node 16 and more than one type of network node 16 and / or may be configured to communicate individually with more than one network node 16 and more than one type of network node 16. For example, the WD 22 may have dual connectivity with a network node 16 that supports LTE and the same or different network nodes 16 that support NR. For example, the WD 22 may communicate with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0093] The communication system 10 itself may be connected to a host computer 24, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 24 may be owned or under the control of a service provider, or may be operated by or on behalf of a service provider. The connections 26, 28 between the telecommunications network 10 and the host computer 24 may extend directly from the core network 14 to the host computer 24, or may extend through an optional intermediate network 30. The intermediate network 30 may be one or a combination of more than one of a public network, a private network, or a servo network; the intermediate network 30 (if any) may be a backbone network or the Internet; in some embodiments, the intermediate network 30 may include two or more sub-networks (not shown).

[0094] Figure 1 The communication system as a whole implements a connection between one of the connected WD 22a, WD 22b and the host computer 24. The connection can be described as an over-the-top (OTT) connection. The host computer 24 and the connected WD 22a, WD 22b are configured to send data and / or signaling via the OTT connection using the access network 12, the core network 14, any intermediate network 30, and possible other intermediate infrastructures (not shown). At least some of the participating communication devices through which the OTT connection passes do not know the routing of the uplink and downlink communications, and in this sense, the OTT connection can be transparent. For example, the network node 16 may not be informed or need not be informed of the past routing of the incoming downlink communication, which has data originating from the host computer 24 and to be forwarded (e.g., handed over) to the connected WD 22a. Similarly, the network node 16 does not need to know the future routing of the uplink communication originating from the WD 22a and toward the output of the host computer 24.

[0095] The network node 16 is configured to include a NN management unit 32, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, for example, determining a compact composite (CC) object associated with a resource model, the determined CC object to be implemented by the WD and including at least one of a structure description resource and a compact structure resource. The wireless device 22 is configured to include a WD management unit 34, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, for example, determining a compact composite (CC) object associated with a resource model, the determined CC object to be implemented by the WD and including at least one of a structure description resource and a compact structure resource.

[0096] Now refer to Figure 2An example implementation according to an embodiment of the WD 22, network node 16, and host computer 24 discussed in the previous paragraphs is described. In the communication system 10, the host computer 24 includes hardware (HW) 38, which includes a communication interface 40, which is configured to establish and maintain a wired or wireless connection with the interface of different communication devices of the communication system 10. The host computer 24 also includes a processing circuit 42, which may have storage and / or processing capabilities. The processing circuit 42 may include a processor 44 and a memory 46. Specifically, as a supplement or alternative to a processor (e.g., a central processing unit) and a memory, the processing circuit 42 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or FPGAs (field programmable gate arrays) and / or ASICs (application-specific integrated circuits) suitable for executing instructions. The processor 44 may be configured to access (e.g., write to or read from) a memory 46, which may include any type of volatile and / or non-volatile memory, such as cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read Only Memory).

[0097] Processing circuitry 42 may be configured to control any of the methods and / or processes described herein, and / or cause these methods and / or processes to be performed, for example, by host computer 24. Processor 44 corresponds to one or more processors 44 for performing the functions of host computer 24 described herein. Host computer 24 includes memory 46, which is configured to store data, program software code, and / or other information described herein. In some embodiments, software 48 and / or host application 50 may include instructions that, when executed by processor 44 and / or processing circuitry 42, cause processor 44 and / or processing circuitry 42 to perform the processes described herein with respect to host computer 24. These instructions may be software associated with host computer 24.

[0098] The software 48 can be executed by the processing circuit 42. The software 48 includes a host application 50. The host application 50 can be operated to provide services to a remote user, such as a WD 22 connected via an OTT connection 52, which is terminated at the WD 22 and the host computer 24. When providing services to the remote user, the host application 50 can provide user data sent using the OTT connection 52. "User data" can be data and information described herein as implementing the described functions. In an embodiment, the host computer 24 can be configured to provide control and functions to a service provider and can be operated by or on behalf of the service provider. The processing circuit 42 of the host computer 24 can enable the host computer 24 to observe, monitor, control the network node 16 and / or the wireless device 22, send to the network node 16 and / or the wireless device 22, and / or receive from the network node 16 and / or the wireless device 22. The processing circuitry 42 of the host computer 24 may include a host management unit 54 configured to enable a service provider to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, such as observing / monitoring / controlling the network nodes 16 and / or user devices 22, sending to / receiving from the network nodes 16 and / or wireless devices 22.

[0099] The communication system 10 also includes a network node 16 disposed in the communication system 10, the network node 16 including hardware 58 that enables it to communicate with the host computer 24 and the WD 22. The hardware 58 may include: a communication interface 60 for establishing and maintaining a wired or wireless connection with the interface of different communication devices of the communication system 10; and a radio interface 62 for establishing and maintaining at least a wireless connection 64 with the WD 22 located in the coverage area 18 served by the network node 16. The radio interface 62 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The communication interface 60 may be configured to facilitate a connection 66 with the host computer 24. The connection 66 may be direct, or it may be through the core network 14 of the communication system 10 and / or through one or more intermediate networks 30 external to the communication system 10.

[0100] In the illustrated embodiment, the hardware 58 of the network node 16 also includes a processing circuit 68. The processing circuit 68 may include a processor 70 and a memory 72. Specifically, as a supplement or alternative to a processor (e.g., a central processing unit) and a memory, the processing circuit 68 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) adapted to execute instructions. The processor 70 may be configured to access (e.g., write to or read from) the memory 72, which may include any type of volatile and / or non-volatile memory, such as a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0101] Therefore, the network node 16 also has software 74 stored internally, for example, in the memory 72 or stored in an external memory (e.g., a database, a storage array, a network storage device, etc.) that can be accessed by the network node 16 via an external connection. The software 74 may include at least one NN application 76 (e.g., an application, a software application, a program, a user interface, for example, for providing one or more functions related to LwM2M, requesting / receiving / displaying data such as temperature measured by a sensor (i.e., a wireless device)). The software 74 may be executed by the processing circuit 68. The processing circuit 68 may be configured to control any method and / or process described herein, and / or cause these methods and / or processes to be performed, for example, by the network node 16. The processor 70 corresponds to one or more processors 70 for performing the network node 16 functions described herein. The memory 72 is configured to store data, program software code, and / or other information described herein. In some embodiments, the software 74 may include instructions that, when executed by the processor 70 and / or the processing circuit 68, cause the processor 70 and / or the processing circuit 68 to perform the process described herein with respect to the network node 16. For example, the processing circuit 68 of the network node 16 may include a NN management unit 32, which is configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, for example, determining a compact composite (CC) object associated with a resource model, the determined CC object to be implemented by the WD and including at least one of a structure description resource and a compact structure resource.

[0102] The communication system 10 also includes the already mentioned WD 22. The WD 22 may have hardware 80, which may include a radio interface 82 configured to establish and maintain a wireless connection 64 with a network node 16 serving the coverage area 18 in which the WD 22 is currently located. The radio interface 82 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers.

[0103] The hardware 80 of the WD 22 also includes a processing circuit 84. The processing circuit 84 may include a processor 86 and a memory 88. Specifically, as a supplement or alternative to a processor (e.g., a central processing unit) and a memory, the processing circuit 84 may include an integrated circuit for processing and / or control, such as one or more processors and / or processor cores and / or an FPGA (field programmable gate array) and / or an ASIC (application-specific integrated circuit) suitable for executing instructions. The processor 86 may be configured to access (e.g., write to or read from) the memory 88, which may include any type of volatile and / or non-volatile memory, such as a cache and / or buffer memory and / or a RAM (random access memory) and / or a ROM (read-only memory) and / or an optical memory and / or an EPROM (erasable programmable read-only memory).

[0104] Therefore, WD 22 may also include software 90, which is stored in a memory 88 at, for example, WD 22, or in an external memory (e.g., a database, a storage array, a network storage device, etc.) accessible by WD 22. The software 90 may be executed by the processing circuit 84. The software 90 may include a client application 92. The client application 92 may be operated to provide services to human or non-human users via WD 22 with the support of the host computer 24. In the host computer 24, the executing host application 50 may communicate with the executing client application 92 via an OTT connection 52, which is terminated at WD 22 and the host computer 24. When providing services to the user, the client application 92 may receive request data from the host application 50 and provide user data in response to the request data. The OTT connection 52 may transmit both request data and user data. The client application 92 may interact with the user to generate the user data it provides.

[0105] The processing circuit 84 may be configured to control any method and / or process described herein, and / or cause such a method and / or process to be performed, for example, by the WD 22. The processor 86 corresponds to one or more processors 86 for performing the WD 22 functions described herein. The WD 22 includes a memory 88 configured to store data, program software code, and / or other information described herein. In some embodiments, the software 90 and / or the client application 92 may include instructions that, when executed by the processor 86 and / or the processing circuit 84, cause the processor 86 and / or the processing circuit 84 to perform the process described herein with respect to the WD 22. For example, the processing circuit 84 of the wireless device 22 may include a WD management unit 34 that is configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, for example, determining a compact composite (CC) object associated with a resource model, the determined CC object to be implemented by the WD and including at least one of a structure description resource and a compact structure resource.

[0106] The hardware 80 may also include a data unit 36 ​​that communicates with any component of the WD 22. The data unit 36 ​​may include a sensor (such as an Internet of Things (IoT) sensor, a motion sensor, a proximity sensor, an M2M sensor, an industrial sensor, a pollution sensor, a carbon monoxide / smoke sensor, a pressure sensor, a temperature sensor), a camera, an activity tracker, a measurement unit, a positioning unit such as a global positioning system, etc. The data unit 36 ​​may be configured to perform any steps and / or tasks and / or processes and / or methods and / or features described in the present disclosure, such as measuring one or more parameters (such as temperature, pressure, location, pollution level, carbon / smoke parts per million (PPM), humidity, wind speed / direction, motion parameters, etc.) and / or providing imaging processing (such as capturing images, recording videos, etc.) and / or providing data related to the measured parameters and / or image processing to one or more components of the WD 22 and / or any other device of the communication system 10 (such as the NN 16), for example, via the radio interface 82.

[0107] In some embodiments, the internal workings of network node 16, WD 22, and host computer 24 may be as follows: Figure 2 shown, and independently, the surrounding network topology can be Figure 1 network topology.

[0108] exist Figure 2, an OTT connection 52 is abstractly depicted to illustrate communications between a host computer 24 and a wireless device 22 via a network node 16, without explicitly involving any intermediate devices and the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from the WD 22 or the service provider operating the host computer 24, or both. The network infrastructure can also make decisions to dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network) while the OTT connection 52 is active.

[0109] The wireless connection 64 between the WD 22 and the network node 16 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improves the performance of OTT services provided to the WD 22 using the OTT connection 52, in which the wireless connection 64 may form the final part. More specifically, the teachings of some of these embodiments may improve data rates, latency, and / or power consumption, thereby providing benefits such as reduced user waiting time, relaxed restrictions on file size, better responsiveness, extended battery life, and the like.

[0110] In some embodiments, a measurement process may be provided for monitoring data rates, latency, and other factors that are the subject of improvement of one or more embodiments. There may also be an optional network function for reconfiguring the OTT connection 52 between the host computer 24 and the WD 22 in response to changes in the measurement results. The measurement process and / or the network function for reconfiguring the OTT connection 52 may be implemented in the software 48 of the host computer 24 or in the software 90 of the WD 22 or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with the communication device through which the OTT connection 52 passes; the sensor may participate in the measurement process by providing the values ​​of the monitoring quantities exemplified above or providing the values ​​of other physical quantities from which the software 48, 90 can calculate or estimate the monitoring quantities. The reconfiguration of the OTT connection 52 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not need to affect the network node 16, and the reconfiguration may be unknown or imperceptible to the network node 16. Some such processes and functions may be known and practiced in the art. In some embodiments, the measurements may involve proprietary WD signaling that facilitates the host computer 24 to measure throughput, propagation time, latency, etc. In some embodiments, the measurements may be accomplished by the software 48, 90 using the OTT connection 52 to send messages (particularly empty messages or "dummy" messages) while monitoring propagation time, errors, etc.

[0111] Thus, in some embodiments, the host computer 24 includes processing circuitry 42 configured to provide user data, and a communication interface 40 configured to forward the user data to a cellular network for transmission to the WD 22. In some embodiments, the cellular network also includes a network node 16 having a radio interface 62. In some embodiments, the network node 16 and / or the processing circuitry 68 of the network node 16 is configured to perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending transmissions to the WD 22, and / or preparing / terminating / maintaining / supporting / ending receiving transmissions from the WD 22.

[0112] In some embodiments, host computer 24 includes processing circuitry 42 and communication interface 40 configured to receive user data originating from transmissions from WD 22 to network node 16. In some embodiments, WD 22 is configured to, and / or includes a radio interface 82 and / or processing circuitry 84 configured to, perform the functions and / or methods described herein for preparing / initiating / maintaining / supporting / ending transmissions to network node 16, and / or preparing / terminating / maintaining / supporting / ending receiving transmissions from network node 16.

[0113] although Figure 1 and Figure 2 Various "units" such as NN management unit 32 and WD management unit 34 are shown as being within respective processors, but it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuit. In other words, these units may be implemented within the processing circuit in hardware or a combination of hardware and software.

[0114] Figure 3 is a diagram showing a communication system (eg, Figure 1 and Figure 2 The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 2The host computer 24, network node 16 and WD 22 described herein. In the first step of the method, the host computer 24 provides user data (box S100). In an optional sub-step of the first step, the host computer 24 provides user data by executing a host application (e.g., host application 50) (box S102). In the second step, the host computer 24 initiates a transmission to the WD 22, which carries the user data (box S104). In the optional third step, in accordance with the teachings of the embodiments described throughout the present disclosure, the network node 16 sends the user data carried in the transmission initiated by the host computer 24 to the WD 22 (box S106). In the optional fourth step, the WD 22 executes a client application (e.g., client application 92) associated with the host application 50 executed by the host computer 24 (box S108).

[0115] Figure 4 is a diagram showing a communication system (eg, Figure 1 The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 1 and Figure 2 The host computer 24, network node 16 and WD 22 described. In the first step of the method, the host computer 24 provides user data (box S110). In an optional sub-step (not shown), the host computer 24 provides user data by executing a host application (e.g., host application 50). In a second step, the host computer 24 initiates a transmission to the WD 22, which carries the user data (box S112). According to the teachings of the embodiments described throughout the present disclosure, the transmission can be transmitted via the network node 16. In an optional third step, the WD 22 receives the user data carried in the transmission (box S114).

[0116] Figure 5 is a diagram showing a communication system (eg, Figure 1 The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 1 and Figure 2The host computer 24, network node 16 and WD 22 described. In the optional first step of the method, WD 22 receives input data provided by the host computer 24 (box S116). In an optional sub-step of the first step, WD 22 executes the client application 92, which provides user data in response to the received input data provided by the host computer 24 (box S118). Additionally or alternatively, in an optional second step, WD 22 provides user data (box S120). In an optional sub-step of the second step, WD provides user data by executing a client application (e.g., client application 92) (box S122). When providing user data, the executed client application 92 may also consider user input received from the user. Regardless of the specific manner of providing user data, WD 22 may initiate transmission of user data to the host computer 24 in an optional third sub-step (box S124). In a fourth step of the method, host computer 24 receives user data sent from WD 22 (block S126 ), in accordance with the teachings of the embodiments described throughout this disclosure.

[0117] Figure 6 is a diagram showing a communication system (eg, Figure 1 The communication system may include a host computer 24, a network node 16, and a WD 22, which may be a reference Figure 1 and Figure 2 The host computer 24, network node 16 and WD 22 described herein. In an optional first step of the method, the network node 16 receives user data from the WD 22 in accordance with the teachings of the embodiments described throughout the present disclosure (block S128). In an optional second step, the network node 16 initiates a transmission of the received user data to the host computer 24 (block S130). In a third step, the host computer 24 receives the user data carried in the transmission initiated by the network node 16 (block S132).

[0118] Figure 7is a flow chart of an example process in a network node. One or more blocks described herein may be performed by one or more elements of the network node 16, such as by one or more of the processing circuit 68 (including the NN management unit 32), the processor 70, the radio interface 62, and / or the communication interface 60. The network node 16 (such as via the processing circuit 68 and / or the processor 70 and / or the radio interface 62 and / or the communication interface 60) is configured to: determine (block S134) a compact composite (CC) object associated with the resource model, wherein the determined CC object is to be implemented by the WD 22 and includes at least one of a structure description resource and a compact structure resource; and perform (block S136) at least one action to collect information associated with at least one of the CC object, the structure description resource, and the compact structure resource.

[0119] In some embodiments, the CC object includes links to one or more resources including at least one of a structure description resource and a compact structure resource.

[0120] In some other embodiments, determining the CC object includes at least one of the following items: creating a CC object, wherein creating the CC object includes sending a first request for creating the CC object, the first request triggering WD 22 to implement the CC object, and the group of resources can be accessed by the network node 16; discovering the created CC object by at least sending a second request for reading links of the CC object; and checking the links of the CC object to determine the structure of the compact structure resource, and performing at least one action to collect information based on the determined structure.

[0121] In an embodiment, at least one of the following holds true: the resource model is a lightweight machine-to-machine (LwM2M) object resource model; the CC object is a CC LwM2M object; the network node 16 is a LwM2M management server; and the WD 22 is a LwM2M client.

[0122] Figure 8is a flow chart of an example process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the wireless device 22, such as by one or more of the processing circuit 84 (including the WD management unit 34), the data unit 36, the processor 86, the radio interface 82, and / or the communication interface 60. The wireless device 22 (such as via the processing circuit 84 and / or the processor 86 and / or the radio interface 82) is configured to: determine (block S138) a compact composite (CC) object associated with a resource model, wherein the determined CC object is to be implemented by the WD 22 and includes at least one of a structure description resource and a compact structure resource; and perform (block S140) at least one action to provide information associated with at least one of the CC object, the structure description resource, and the compact structure resource.

[0123] In some embodiments, the CC object includes links to one or more resources including at least one of a structure description resource and a compact structure resource.

[0124] In some other embodiments, determining the CC object includes at least one of the following: creating a CC object for a set of resources, wherein the created CC object is implemented by the WD based on a first request of the network node 16, and the set of resources is accessible by the network node 16; and receiving a second request for reading a link of the CC object, wherein the received request allows the network node 16 to discover the created CC object. Discovering the created object can be used by the network node 16 to examine the links of the CC object to determine the structure of the compact structure resource and perform at least one action to collect the information.

[0125] In an embodiment, at least one of the following holds true: the resource model is a lightweight machine-to-machine (LwM2M) object resource model; the CC object is a CC LwM2M object; the network node 16 is a LwM2M management server; and the WD 22 is a LwM2M client.

[0126] Fig. 91 is a flow chart of an example process in a network node 16. One or more blocks described herein may be performed by one or more elements of the network node 16, such as by one or more of the processing circuit 68 (including the NN management unit 32), the processor 70, the radio interface 62, and / or the communication interface 60. The network node 16 (such as via the processing circuit 68 and / or the processor 70 and / or the radio interface 62 and / or the communication interface 60) is configured to determine (block 142) a compact composite (CC) object associated with a resource model. The determined CC object is to be implemented by the WD 22 and includes at least one of a structure description resource and a compact data resource. The structure description resource includes one or more links pointing to one or more resources accessible by the network node 16. The compact data resource includes one or more data values ​​associated with one or more resources. The network node 16 is also configured to perform (block S144) at least one action to collect information associated with at least one of the CC object, the structure description resource, and the compact data resource.

[0127] In some embodiments, determining the CC object includes creating the CC object.Creating the CC object includes sending a first request for creating the CC object, the first request triggering WD 22 to implement the CC object.

[0128] In some other embodiments, determining the CC object includes discovering the CC object at least by sending a second request for reading the one or more links.

[0129] In an embodiment, determining the CC object includes examining one or more links to determine a structure of the compact data resource and performing at least one action based on the determined structure to collect the information.

[0130] In another embodiment, performing at least one action includes causing sending a third request to create or discover another CC object based on examining the one or more links.

[0131] In some embodiments, CC objects are pre-instantiated in WD 22 .

[0132] In some other embodiments, the method further includes at least one of: receiving a data request for providing data associated with a CC object from a software application and receiving a CC object identifier from a WD; and determining the CC object based on at least one of the received data request and the received CC object identifier.

[0133] In an embodiment, the method further comprises sending a fourth request for creating the compact data resource using the compound read operation or updating the compact data resource using the compound read operation, wherein the fourth request comprises an indication indicating whether the compact data resource is to be created or updated.

[0134] In another embodiment, the one or more links point to at least one of an array of data values ​​and a mapping of data values.

[0135] In some embodiments, at least one of the following is true: the information includes one or more data values ​​associated with one or more resources; the resource model is a lightweight machine-to-machine (LwM2M) object resource model; the CC object is a CC LwM2M object; the network node is a LwM2M management server; and the WD is a LwM2M client.

[0136] Fig.10 is a flow chart of an example process in a wireless device 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of the wireless device 22, such as by one or more of the processing circuit 84 (including the WD management unit 34), the data unit 36, the processor 86, the radio interface 82, and / or the communication interface 60. The wireless device 22 (such as via the processing circuit 84 and / or the processor 86 and / or the radio interface 82) is configured to determine (block S146) a compact composite (CC) object associated with a resource model, wherein the determined CC object is to be implemented by the WD 22 and includes at least one of a structure description resource and a compact data resource. The structure description resource includes one or more links pointing to one or more resources accessible by the network node 16. The compact data resource includes one or more data values ​​associated with one or more resources. The wireless device 22 is also configured to perform (block S148) at least one action to provide information associated with at least one of the CC object, the structure description resource, and the compact structure resource.

[0137] In some embodiments, determining the CC object includes creating the CC object based on a first request received from the network node 16 .

[0138] In some other embodiments, determining the CC object includes making the CC object discoverable by the network node 16 based on a second request received from the network node 16 to read the one or more links.

[0139] In an embodiment, the provided information triggers the network node 16 to examine one or more links to determine the structure of the compact data resource.

[0140] In another embodiment, the method further comprises receiving a third request for creating or discovering another CC object based on checking the one or more links.

[0141] In some embodiments, CC objects are pre-instantiated in WD 22 .

[0142] In some other embodiments, the method further includes sending a CC object identifier that can be used by the network node 16 to determine the CC object.

[0143] In an embodiment, the method further comprises receiving a fourth request for creating a compact data resource using a compound read operation or updating a compact data resource using a compound read operation, the fourth request comprising an indication indicating whether the compact data resource is to be created or updated.

[0144] In another embodiment, the one or more links point to at least one of an array of data values ​​and a mapping of data values.

[0145] In some embodiments, at least one of the following is true: the information includes one or more data values ​​associated with one or more resources; the resource model is a lightweight machine-to-machine (LwM2M) object resource model; the CC object is a CC LwM2M object; the network node 16 is a LwM2M management server; and the WD is a LwM2M client.

[0146] Having described the general process flow of the arrangements of the present disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the present disclosure, the following sections provide details and examples for determining arrangements for compact composite resources.

[0147] Fig.11 A high-level system overview of the interaction of the NN 16 (e.g., LwM2M Management Server (MS)), the WD 22 (e.g., LwM2M Client), and the NN application 76 (e.g., application) is shown. Note that the NN application 76 may be included in the NN 16 or another NN 16 or any other device / node of the communication system 10. In addition, although the WD 22 and the NN 16 are shown as including a LwM2MMS and a LwM2M Client, respectively, the present disclosure is not limited thereto, i.e., the LwM2M MS and the LwM2M Client may be included in any component of the communication system 10.

[0148] In some embodiments, one or more key extensions related to the present disclosure reside in WD 22 (e.g., LwM2M client) and NN 16 (e.g., LwM2M server), which can satisfy application requests more efficiently than via other arrangements. WD 22 (e.g., LwM2M client) can be configured to implement a set of standardized objects (e.g., "temperature" and "location") based on the capabilities it has (e.g., temperature sensor and GPS receiver) (e.g., perform one or more steps associated with a set of standardized objects).

[0149] When using a compact composite (CC) object embodiment, the NN (e.g., LwM2M MS) can discover whether the WD 22 (e.g., LwM2M client) implements one or more embodiments of the present disclosure by discovering (e.g., using a registration or discovery method, etc.) an existing CC object instance on the WD 22 (e.g., LwM2M client). If the WD 22 (e.g., LwM2M client) does not currently implement any CC object, the NN 16 (e.g., LwM2M server) can create (e.g., attempt to create, request to create) a new instance of the CC object. A WD 22 (e.g., LwM2M client) that supports CC functionality can accept the request for creation. A WD 22 (e.g., LwM2M client) that does not support CC functionality can return an error at this step.

[0150] When using “inline descriptions” (i.e., in the same object hosting the target resource used in the resulting structured data), the client NN 16 (e.g., LwM2M MS) can detect support from a new object schema version (e.g., if the description is part of that schema, such as a new property of a resource) or the presence of TargetLinks resources (see section “CompactData reusable resources”).

[0151] The NN application 76 (e.g., application) may send one or more requests to the NN 16 (e.g., LwM2M MS) to obtain information that the WD 22 (e.g., LwM2M client) has (e.g., sensor data provided by the data unit 36). The NN 16 (e.g., LwM2M MS) may convert the request to the best available LwM2M protocol and object model method, for example, using CC object resources (if available). The CC object may include at least the following two resources:

[0152] oTargetLinks (Readable and Writable, Multi-Instance Resources, with CoRE Link data type), which can include CoRE links to resource instances to be stored in the CompactData array. Each linked resource instance can result in a new item in the CompactData array. The linked instance identifier (ID) can correspond to an array index into the resulting array.

[0153] - In one embodiment, the resource is single-instanced and the order of the links in the (CoRE link standard) comma-delimited linked list is used to determine the array index. In another embodiment, additional attributes may be used to determine the array index or other location (see section "Expressive and Efficient Data Structures"). The first embodiment with separate instance IDs allows for more fine-grained control over links using the LwM2M protocol (e.g., easy creation, update, and removal of individual links) and / or additional attributes for more control over the resulting compact data structure.

[0154] - Links can point to other resources in the same object instance. They can also link to resources in other objects.

[0155] o CompactData (e.g., readable and writable, single-instance resource, with an opaque (byte string) data type), which may include a CBOR array of resources that are compacted in the same order as the links in the target linked resource.

[0156] - In one embodiment, the data may include JSON, Extensible Markup Language (XML), Efficient XML Interchange (EXI) (compressed XML), and / or other structured formats that support representing a list of at least one item (e.g., CSV (comma separated values) or TLV (type-length-value) items).

[0157] A CC object may also include additional resources with usage information about the object, such as:

[0158] ο Description (e.g., Readable and Writable, Single-Instance Resource, with String data type): A human-readable description of the purpose and intended use of this compact composite object instance

[0159] The TargetLinks resource can be used to discover the contents of a CompactData resource and / or configure a CC object instance to include certain resource values ​​in a CompactData resource. A CompactData resource is an array of values, with one array item per link in the TargetLinks.

[0160] Note that in one or more embodiments, matching the instance ID of the TargetLinks resource with the array index in the CompactData array is described. As a result, this enables the use of sparse arrays (e.g., more values ​​can be added later without changing the array index of the value). If sparse arrays are not desired, other embodiments may include the resource values ​​in the array in the order of the instance ID, but without leaving gaps even if the instance IDs are not consecutive.

[0161] CompactData reusable resources

[0162] In one embodiment, the CompactData reusable resource can be defined as a new resource in any other object and / or embedded as a new resource in any other object (e.g., instead of providing the CompactData in a new object). In this case, TargetLinks can hold static values ​​and be defined as static reusable resources at design time, or alternatively defined as metadata in the object definition. Existing objects can be updated and / or new objects defined. In some cases, compact composite objects are not used. In addition, CompactData can be a multi-instance resource to support multiple ways of compressing data in a closed object (e.g., one instance combines the current, Min (i.e., minimum) and Max (i.e., maximum) temperatures and another minimum, maximum and average temperatures, and / or adding resources from other objects).

[0163] In another embodiment, other methods (e.g., methods other than methods using reusable resources) may be implemented to specify one or more resources of an object to hold the contents of CompactData and / or TargetLinks. These contents may include new standardized data types for this purpose, metadata in the schema, or metadata as LwM2M attributes.

[0164] Efficient Link Set Representation

[0165] In some embodiments, because the CoRE link format is a relatively verbose format, an alternative implementation (e.g., a restricted implementation) may provide a more compact implementation for the TargetLinks set. Representing link values ​​as a CBOR array where each array entry contains an object, resource, or instance ID is one option. Further compression may be obtained by delta-encoding the IDs (i.e., representing only the difference from the previous ID in the array).

[0166] Even further compression can be achieved using new formats and resources that can represent registered sets of links as shorthand. In this case, a new registry is created, and if a set of links for an application or use case is common, the set can be registered in that registry and given a single unique ID value. Such a registry can be hosted by a standardization organization (e.g., OMA), or it can be application-specific, or a combination of both (considering appropriate namespaces). A NN application 76 (e.g., an application) that is aware of the value can use it as shorthand for the complete set of links. For example, assume a set of three links (temperature object sensor value and min / max values, represented here in the CoRE link format):

[0167] <!--3303 / 0 / 5700--> ,<!--3303 / 0 / 5601-->,<!--3303 / 0 / 5602-->

[0168] The collection may be registered and given a new ID, such as "Collection 42". If the WD 22 (e.g., LwM2M Client) supports this method, a new resource "RegisteredTargetLinks" may host the value. When a known value is written to this resource, the WD 22 (e.g., LwM2M Client) writes the resulting registered collection to the TargetLinks resource (for discovery by implementations that do not support the shorthand), and updates the CompactData accordingly. The NN 16 (e.g., LwM2M MS) may read this resource instead of the TargetLinks resource to save transmitted data.

[0169] Expressive and efficient data structures

[0170] One or more features of an embodiment are designed for applications or use cases that require access to multiple resources and require efficient (compact) data transfer. One or more steps may be performed on the structure of the data sent, e.g., so that it can be parsed correctly. Two categories of solutions are proposed (e.g., on the structure of the data sent): 1) JSON (or other structured data such as XML) templates, where CoRE links are used as placeholders for data to be added; 2) CoRE links with JSON paths or pointers (or Xpath if XML is used).

[0171] An example JSON template could be as follows:

[0172] {"temp":{"val":"<!--3303 / 0 / 5700--> ", "min": "<!--3303 / 0 / 5601--> ", "max": "<!--3303 / 0 / 5602--> ”}}

[0173] This example can be represented by a JSON path as:

[0174] <!--3303 / 0 / 5700--> ;p= / temp / val,<!--3303 / 0 / 5601--> ;p= / temp / min,<!--3303 / 0 / 5602--> ;p= / temp / max

[0175] The example described in the "Efficient Link Set Representation" section can be rewritten using JSON path parameters and CoRE links as follows:

[0176] <!--3303 / 0 / 5700--> ; p = / 1,<!--3303 / 0 / 5601-->; p = / 2,<!--3303 / 0 / 5602--> ; p = / 3

[0177] In this case, the parameter p= / N indicates that such a resource is to be found at position N of the resulting array.

[0178] Another example using JSON templates to result in a compact array format could be:

[0179] [“<!--3303 / 0 / 5700--> ”, “<!--3303 / 0 / 5601--> ”, “<!--3303 / 0 / 5602--> ”]

[0180] exist Fig.12 In step S200, the NN application 76 indicates to the NN 16 (e.g., LwM2M MS) the kind of information it needs and when it needs it. Since the NN application 76 requests a group of related information elements to be transmitted at the same time, the NN 16 (e.g., LwM2M MS) uses a compact composite (CC) object to optimize the data transmission between the NN 16 (e.g., LwM2M MS) and the WD 22 (e.g., LwM2M client).

[0181] In step 202 , the NN 16 (eg, LwM2M MS) creates a new CC object on the WD 22 (eg, LwM2M client) with three links: the current value, minimum value, and maximum value of the temperature object.

[0182] Since the WD 22 (eg, LwM2M client) implements the method, in step S204 , the WD 22 confirms the creation and notifies the NN 16 (eg, LwM2M MS) that it has created a new CC object with instance ID 0 .

[0183] In step S206 , the NN 16 (eg, LwM2M MS) is set to observe the CompactData resource of the newly created object at a reporting interval of 10 minutes.

[0184] Since the NN application 76 is also interested in the same set of values ​​when the minimum value changes, in step S208, the NN 16 (e.g., LwM2M MS) sets a separate observation on the resource without any time constraints. Alternatively, this step can also use virtual observation (i.e., a function for notifying the LwM2M server of multiple resources in one notification message) to set the value to be reported as CompactData; therefore, steps S214 and S216 are removed.

[0185] In step S210, after a predetermined time (e.g., 10 minutes) has passed (without a change in the minimum value), the WD 22 (e.g., LwM2M client) sends a notification about the current set of values, as requested in the observation of step S206. The NN 16 (e.g., LwM2M MS) forwards the set of data items to the application (step S212). When the minimum value changes, the NN 16 (e.g., LwM2M MS) is notified of the change (step S214), and the NN 16 (e.g., LwM2M MS) can request the current values ​​of all three resources using a GET of the CompactData resource (steps S216 and S218), and forward the information to the NN application 76 (step S220).

[0186] Discover existing target links

[0187] If a compact composite object already exists, or the CC resource is part of another object (see the "Inline Description" section), the TargetLinks content can be discovered from that object, such as Fig.13 Step S300 can be Fig.12 The same as step S200 of , but steps S302 and S304 retrieve the existing TargetLinks of the NN 16 (e.g., LwM2M MS). The NN 16 (e.g., LwM2M MS) checks whether any content in the resulting CompactData matches the content requested by the application. If there are any matches, these contents are used; if there are no matches, a new CompactData is created or other LwM2M methods are used. In step S306, verification is performed on which links exist.

[0188] refer to Fig.14 Another embodiment is described below. Fig.14 In step S400, Fig.13 The same as S300 of: NN application 76 indicates to NN 16 (e.g., LwM2M MS) what kind of information it needs and when it needs it. Since NN application 76 requests a group of related information elements to be transmitted at the same time, NN 16 (e.g., LwM2M MS) uses the CompactData resource contained in the temperature object to optimize the data transmission between NN 16 (e.g., LwM2M MS) and WD 22 (e.g., LwM2M client).

[0189] In step S402 , the NN 16 (eg, LwM2M MS) is configured to observe the CompactData resource of the temperature object at a reporting interval of 10 minutes.

[0190] In step S404 , after 10 minutes have passed (no change in the minimum value), the WD 22 (eg, LwM2M client) sends a notification about the current value set, as requested in the observation of S402 .

[0191] The NN 16 (eg, LwM2M MS) forwards only the requested set of data items to the NN application 76 (step S406).

[0192] In one or more embodiments, a link is described such that the link links to an array (or map) of values ​​(eg, of a resource instance). In some embodiments, the array of values ​​may include an array (eg, an existing array) of temperature values:<!--3303 / 0 / 5700--> ; type = arr, where CompactData: [val1, val2, val3, ...]. In some other embodiments, the array of position values ​​can be represented as<!--6 / 0 / 0--> ;type=arr1,<!--6 / 0 / 1--> ; type = arr2, where CompactData:

[0193] [[lon1, lat1], [lon2, lat2] ...]. In some embodiments, an array of temperature values ​​(eg, an existing array) may be represented as [<!--3303 / 0 / 5700--> ], where CompactData: [val1, val2, val3, ...]. In some other embodiments, the array of position values ​​may be represented as [<!--6 / 0 / 0--> ,<!--6 / 0 / 1--> ], where CompactData: [[lon1, lat1], [lon2, lat2] ... ]. That is, in some embodiments, a different syntax (ie, a "template") may be used, where square brackets in the template indicate the presence of an array and / or a CoRE link indicates the value of each element.

[0194] In one or more embodiments,<!--3303 / 0 / 5700--> is a link, where "3303" is an identifier (e.g., a standard identifier for a temperature sensor), "0" is the first temperature object instance, "5700" is a resource (e.g., the current value of the resource), and type=arr indicates that the resulting CompactData should be an array of values ​​from all object instances of type "3303" (starting with instance "0"). When using a template, the same resulting array structure can be indicated by square brackets (e.g., instead of using "type"). In some embodiments, using<!--6 / 0 / 0-->, where "6" indicates a location object identifier, followed by "0" indicating the first location object instance, and then "0" indicating the resource "longitude" (or resource value) and "1" indicating the resource "latitude". Parameter "arr1" indicates that the value of resource "0" will be the first element of the resulting inner array, and "arr2" indicates that the value of resource "1" will be the second element. All inner arrays are stored within another array, resulting in a set of nested arrays in the CompactData resource.

[0195] In an embodiment, an XML file may be used to describe an object, a compact complex, a resource, an item, an item identifier. A non-limiting example of an XML file is as follows:

[0196] -->

[0197] <LWM2Mxmlns:xsi=“http: / / www.w3.org / 2001 / XMLSchema-instance”xsi:noNamespaceSchemaLocation=“http: / / openmobilealliance.org / tech / profiles / LWM2M.xsd”>

[0198] <object objecttype=""MODefinition”">

[0199] <name> CompactComposite< / name>

[0200] <description1> This object is able to collect a set of resource values ​​from other objects into a single resource representation with an array of values.< / description1>

[0201] <objectid> 511< / objectid>

[0202] <objecturn> urn:oma:lwm2m:ext:511< / objecturn>

[0203] <lwm2mversion> 1.1< / lwm2mversion>

[0204] <objectversion> 1.0< / objectversion>

[0205] <multipleinstances> Multiple< / multipleinstances>

[0206] <mandatory> Optional< / mandatory>

[0207] <resources>

[0208] <item id=""4020”">

[0209] <name> Target Links< / name>

[0210] <operations> R< / operations>

[0211] <multipleinstances> Single< / multipleinstances>

[0212] <mandatory> Mandatory< / mandatory>

[0213] <type> Corelnk< / type>

[0214] <rangeenumeration / >

[0215] <units / >

[0216] <description> One or more CoRE links pointing to resource instances whose values ​​will be stored in the compact data array. Each link produces a new entry in the CompactData array: the first link points to the resource instance with the value of the first array entry, the second link points to the instance with the second array entry, and so on. For single-instance resources, the resource instance ID can be omitted from this link, but for multi-instance resources it must be present.< / description>

[0217] < / item>

[0218] <item id=""4021”">

[0219] <name> CompactData< / name>

[0220] <operations> R< / operations>

[0221] <multipleinstances> Single< / multipleinstances>

[0222] <mandatory> Mandatory< / mandatory>

[0223] <type> Opaque< / type>

[0224] <rangeenumeration / >

[0225] <units / >

[0226] <description> The CBOR array of resource values ​​is in the same order as the links in the target linked resource, or an empty value if there is an error (e.g. the link points to a non-existent resource).< / description>

[0227] < / item>

[0228] <item id="”4023”">

[0229] <name> Description< / name>

[0230] <operations> R< / operations>

[0231] <multipleinstances> Single< / multipleinstances>

[0232] <mandatory> Optional< / mandatory>

[0233] <type> String< / type>

[0234] <rangeenumeration / >

[0235] <units / >

[0236] <description> A human-readable description of the compact data produced by the target link.< / description>

[0237] < / item>

[0238] < / resources>

[0239] < / object>

[0240]

[0241] In some embodiments, resource IDs may include "0", "1", and "2" (eg, instead of 4020, 4021, and 4023), which may be object-specific resources rather than reusable resources. In some other embodiments, resource IDs are reusable.

[0242] The following is a non-limiting list of example embodiments:

[0243] Embodiment A1. A network node 16 configured to communicate with a wireless device (WD) 22, the network node 16 being configured to perform the following operations: and / or comprising a wireless point interface and / or comprising a processing circuit configured to perform the following operations:

[0244] determining a compact composite (CC) object associated with the resource model, the determined CC object being implemented by the WD 22 and including at least one of a structure description resource and a compact structure resource; and

[0245] At least one action is performed to collect information associated with at least one of a CC object, a structure description resource, and a compact structure resource.

[0246] Embodiment A2. The network node of Embodiment A1, wherein the CC object comprises a link to one or more resources, the one or more resources comprising at least one of a structure description resource and a compact structure resource.

[0247] Embodiment A3. The network node of embodiment A2, wherein determining the CC object comprises at least one of:

[0248] Creating a CC object, the creating the CC object comprising sending a first request for creating the CC object, the first request triggering the WD 22 to implement the CC object, the set of resources being accessible to the network node;

[0249] discovering the created CC object by at least sending a second request for reading a link to the CC object; and

[0250] Links of the CC object are examined to determine a structure of the compact structure resource, and at least one action is performed based on the determined structure to collect the information.

[0251] Embodiment A4. The network node of Embodiments A1 to A3, wherein at least one of the following is true:

[0252] The resource model is a lightweight machine-to-machine (LwM2M) object resource model;

[0253] The CC object is a CC LwM2M object;

[0254] The network node is a LwM2M management server; and

[0255] The WD 22 is a LwM2M client.

[0256] Embodiment B1. A method implemented in a network node 16 configured to communicate with a wireless device (WD) 22, the method comprising:

[0257] determining a compact composite (CC) object associated with the resource model, the determined CC object being implemented by the WD 22 and including at least one of a structure description resource and a compact structure resource; and

[0258] At least one action is performed to collect information associated with at least one of a CC object, a structure description resource, and a compact structure resource.

[0259] Embodiment B2. The method according to embodiment B1, wherein the CC object includes a link to one or more resources, and the one or more resources include at least one of a structure description resource and a compact structure resource.

[0260] Embodiment B3. The method of embodiment B2, wherein determining the CC object comprises at least one of the following:

[0261] Creating a CC object, the creating the CC object comprising sending a first request for creating the CC object, the first request triggering the WD 22 to implement the CC object, the set of resources being accessible to the network node 16;

[0262] discovering the created CC object by at least sending a second request for reading a link to the CC object; and

[0263] Links of the CC object are examined to determine a structure of the compact structure resource, and the at least one action is performed based on the determined structure to collect the information.

[0264] Embodiment B4. The method of Embodiments B1 to B3, wherein at least one of the following is true:

[0265] The resource model is a lightweight machine-to-machine (LwM2M) object resource model;

[0266] The CC object is a CC LwM2M object;

[0267] The network node 16 is a LwM2M management server; and

[0268] The WD 22 is a LwM2M client.

[0269] Embodiment C1. A wireless device (WD) 22 configured to communicate with a network node 16, the WD 22 configured to perform the following operations: and / or including a radio interface and / or processing circuitry configured to perform the following operations:

[0270] determining a compact composite (CC) object associated with the resource model, the determined CC object being implemented by the WD 22 and including at least one of a structure description resource and a compact structure resource; and

[0271] At least one action is performed to provide information associated with at least one of a CC object, a structure description resource, and a compact structure resource.

[0272] Embodiment C2. WD 22 of Embodiment C1, wherein the CC object includes a link to one or more resources, the one or more resources including at least one of a structure description resource and a compact structure resource.

[0273] Embodiment C3. WD 22 according to Embodiment C2, wherein determining the CC object comprises at least one of the following:

[0274] Creating a CC object for a set of resources accessible by the network node 16, the created CC object being implemented by the WD 22 based on the first request of the network node 16; and

[0275] A second request is received for reading the links of the CC object, the received request allowing the network node 16 to discover the created CC object, the discovery of the created object can be used by the network node 16 to examine the links of the CC object to determine the structure of the compact structure resource and perform the at least one action to collect this information.

[0276] Embodiment C4. WD 22 according to Embodiments C1 to C3, wherein at least one of the following is true:

[0277] The resource model is a lightweight machine-to-machine (LwM2M) object resource model;

[0278] The CC object is a CC LwM2M object;

[0279] The network node 16 is a LwM2M management server; and

[0280] The WD 22 is a LwM2M client.

[0281] Embodiment D1. A method implemented in a wireless device (WD) 22 configured to communicate with a network node 16, the method comprising:

[0282] determining a compact composite (CC) object associated with the resource model, the determined CC object being implemented by the WD 22 and including at least one of a structure description resource and a compact structure resource; and

[0283] At least one action is performed to provide information associated with at least one of a CC object, a structure description resource, and a compact structure resource.

[0284] Embodiment D2. A method according to embodiment D1, wherein the CC object includes links to one or more resources, and the one or more resources include at least one of a structure description resource and a compact structure resource.

[0285] Embodiment D3. The method of embodiment D2, wherein determining the CC object comprises at least one of the following:

[0286] Creating a CC object for a set of resources accessible by the network node 16, the created CC object being implemented by the WD 22 based on the first request of the network node 16; and

[0287] A second request is received for reading the links of the CC object, the received request allowing the network node 16 to discover the created CC object, the discovery of the created object can be used by the network node 16 to examine the links of the CC object to determine the structure of the compact structure resource and perform the at least one action to collect this information.

[0288] Embodiment D4. The method of embodiments D1 to D3, wherein at least one of the following is true:

[0289] The resource model is a lightweight machine-to-machine (LwM2M) object resource model;

[0290] The CC object is a CC LwM2M object;

[0291] The network node 16 is a LwM2M management server; and

[0292] The WD 22 is a LwM2M client.

[0293] As will be appreciated by those skilled in the art, the concepts described herein may be embodied as methods, data processing systems, computer program products, and / or computer storage media storing executable computer programs. Therefore, the concepts described herein may take the form of all-hardware embodiments, all-software embodiments, or embodiments combining hardware and software aspects, which are collectively referred to herein as "circuits" or "modules". Any process, step, action, and / or function described herein may be performed by and / or associated with a corresponding module, which may be implemented in software and / or firmware and / or hardware. In addition, the present disclosure may take the form of a computer program product on a tangible computer-usable storage medium having a computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer-readable medium may be utilized, including a hard disk, a CD-ROM, an electrical storage device, an optical storage device, or a magnetic storage device.

[0294] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems, and computer program products. It will be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of multiple blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer (thereby creating a special-purpose computer), a processor of a special-purpose computer, or other programmable data processing device for producing a machine, so that the instructions (via execution by the processor of the computer or other programmable data processing device) create a computer program for implementing the flowchart and / or block diagrams. Figure 1 means for performing the functions / actions specified in one or more boxes.

[0295] These computer program instructions may also be stored in a computer-readable memory or storage medium that directs a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions / actions specified in one or more boxes of the flowchart and / or block diagram.

[0296] Computer program instructions may also be loaded into a computer or other programmable data processing apparatus so that a series of operable steps are executed on the computer or other programmable apparatus to generate a computer-implemented process, so that the instructions executed on the computer or other programmable apparatus provide steps for implementing the functions / actions specified in one or more boxes of the flowchart and / or block diagram.

[0297] It should be understood that the functions and / or actions marked in the blocks may not occur in the order marked in the operating instructions. For example, depending on the functions / actions involved, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in the opposite order. Although some figures include arrows on the communication paths to indicate the primary direction of communication, it should be understood that communication may occur in the opposite direction of the indicated arrows.

[0298] The computer program code for performing the operations of the concepts described herein can be written in an object-oriented programming language such as Python, Java® or C++. However, the computer program code for performing the operations of the present disclosure can also be written in a conventional procedural programming language such as the "C" programming language. The program code can be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer. In the latter case, the remote computer can be connected to the user's computer via a local area network (LAN) or a wide area network (WAN), or an external computer can be connected (e.g., via the Internet using an Internet service provider).

[0299] In conjunction with the above description and the accompanying drawings, many different embodiments are disclosed herein. It will be understood that it would be unduly repetitive and confusing to describe and illustrate verbatim every combination and subcombination of these embodiments. Therefore, all embodiments may be combined in any manner and / or combination, and this specification including the accompanying drawings will be construed to construct a complete written description of all combinations and subcombinations of the embodiments described herein and the manner and process of making and using them, and will support the rights and interests claiming any such combination or subcombination.

[0300] Those skilled in the art will recognize that the embodiments described herein are not limited to what has been specifically shown and described above. In addition, unless otherwise mentioned above, it should be noted that all drawings are not drawn to scale. Various modifications and changes are possible in view of the above teachings without departing from the scope of the appended claims.

Claims

1. A network node (16) configured to communicate with a wireless device WD (22) using at least one of a wired connection and a wireless connection, the network node (16) comprising a processing circuit (68), the processing circuit (68) being configured to: determining a compact composite CC object associated with a resource model, the determined CC object to be implemented by the WD (22) and comprising at least one of a structure description resource and a compact data resource, the structure description resource comprising one or more links to one or more resources accessible by the network node (16), the compact data resource comprising one or more data values ​​associated with the one or more resources; and At least one action is performed to collect information associated with at least one of the CC object, the structure description resource, and the compact data resource.

2. The network node (16) according to claim 1, wherein: Determining the CC object includes: The CC object is created, wherein the creation of the CC object includes sending a first request for creating the CC object, wherein the first request triggers the WD (22) to implement the CC object.

3. The network node (16) according to any one of claims 1 and 2, wherein: Determining the CC object includes: The CC object is discovered by at least sending a second request to read the one or more links.

4. The network node (16) according to any one of claims 1 to 3, wherein: Determining the CC object includes: The one or more links are examined to determine a structure of the compact data resource and the at least one action is performed based on the determined structure to collect the information.

5. The network node (16) according to claim 4, wherein: Performing the at least one action includes: Based on examining the one or more links, sending a third request for creating or discovering another CC object is caused.

6. The network node (16) according to any one of claims 1 to 5, wherein: The CC object is pre-instantiated in the WD (22).

7. The network node (16) according to any one of claims 1 to 6, wherein: The processing circuit (68) is further configured to: performing at least one of: receiving a data request from a software application for providing data associated with a CC object; and receiving a CC object identifier from the WD (22); as well as The CC object is determined based on at least one of the received data request and the received CC object identifier.

8. The network node (16) according to any one of claims 1 to 7, wherein: The processing circuit (68) is further configured to: Causing sending of a fourth request to create the compact data resource using a compound read operation or to update the compact data resource using a compound read operation, the fourth request including an indication indicating whether the compact data resource is to be created or updated.

9. The network node (16) according to any one of claims 1 to 8, wherein: The one or more links point to at least one of an array of the data values ​​and a mapping of the data values.

10. The network node (16) according to claim 1 to 9, wherein: At least one of the terms holds true: The information includes one or more data values ​​associated with the one or more resources; The resource model is a lightweight machine-to-machine LwM2M object resource model; The CC object is a CC LwM2M object; The network node (16) is a LwM2M management server; as well as The WD (22) is a LwM2M client.

11. A method in a network node (16), the network node being configured to communicate with a wireless device WD (22) using at least one of a wired connection and a wireless connection, the method comprising: determining (S142) a compact composite CC object associated with a resource model, the determined CC object to be implemented by the WD (22) and comprising at least one of a structure description resource and a compact data resource, the structure description resource comprising one or more links to one or more resources accessible by the network node (16), the compact data resource comprising one or more data values ​​associated with the one or more resources; as well as At least one action is performed (S144) to collect information associated with at least one of the CC object, the structure description resource, and the compact data resource.

12. The method according to claim 11, wherein: Determining the CC object includes: The CC object is created, wherein the creation of the CC object includes sending a first request for creating the CC object, wherein the first request triggers the WD (22) to implement the CC object.

13. The method according to any one of claims 11 and 12, wherein: Determining the CC object includes: The CC object is discovered by at least sending a second request to read the one or more links.

14. The method according to any one of claims 11 to 13, wherein: Determining the CC object includes: The one or more links are examined to determine a structure of the compact data resource and the at least one action is performed based on the determined structure to collect the information.

15. The method according to claim 14, wherein: Performing the at least one action includes: Based on examining the one or more links, sending a third request for creating or discovering another CC object is caused.

16. The method according to any one of claims 11 to 15, wherein: The CC object is pre-instantiated in the WD (22).

17. The method according to any one of claims 11 to 16, wherein: The method further comprises: performing at least one of: receiving a data request from a software application for providing data associated with a CC object; and receiving a CC object identifier from the WD (22); and The CC object is determined based on at least one of the received data request and the received CC object identifier.

18. The method according to any one of claims 11 to 17, wherein: The method further comprises: A fourth request is sent, the fourth request for creating the compact data resource using a compound read operation or updating the compact data resource using a compound read operation, the fourth request including an indication of whether the compact data resource is to be created or updated.

19. The method according to any one of claims 11 to 18, wherein: The one or more links point to at least one of an array of the data values ​​and a mapping of the data values.

20. The method according to any one of claims 11 to 19, wherein: At least one of the following is true: The information includes one or more data values ​​associated with the one or more resources; The resource model is a lightweight machine-to-machine LwM2M object resource model; The CC object is a CC LwM2M object; The network node (16) is a LwM2M management server; as well as The WD (22) is a LwM2M client.

21. A wireless device WD (22) configured to communicate with a network node (16) using at least one of a wired connection and a wireless connection, the WD (22) comprising a processing circuit (84), the processing circuit (84) being configured to: determining a compact composite CC object associated with a resource model, the determined CC object to be implemented by the WD (22) and comprising at least one of a structure description resource and a compact data resource, the structure description resource comprising one or more links to one or more resources accessible by the network node (16), the compact data resource comprising one or more data values ​​associated with the one or more resources; and At least one action is performed to provide information associated with at least one of the CC object, the structure description resource, and the compact structure resource.

22. The WD (22) according to claim 21, wherein: Determining the CC object includes: The CC object is created based on a first request received from the network node (16).

23. The WD (22) according to any one of claims 21 and 22, wherein Determining the CC object includes: The CC object is enabled to be discovered by the network node (16) based on a second request received from the network node (16) for reading the one or more links.

24. The WD (22) according to any one of claims 21 to 23, wherein The provided information triggers the network node (16) to examine the one or more links to determine the structure of the compact data resource.

25. The WD (22) of claim 24, wherein: The processing circuit (84) is further configured to: A third request to create or discover another CC object based on the inspection of the one or more links is received.

26. The WD (22) according to any one of claims 21 to 25, wherein The CC object is pre-instantiated in the WD (22).

27. The WD (22) according to any one of claims 21 to 26, wherein The processing circuit (84) is further configured to: Causing sending of a CC object identifier that can be used by the network node (16) to identify the CC object.

28. The WD (22) according to any one of claims 21 to 27, wherein The processing circuit (84) is further configured to: A fourth request is received, the fourth request to create the compact data resource using a compound read operation or to update the compact data resource using a compound read operation, the fourth request including an indication indicating whether the compact data resource is to be created or updated.

29. The WD (22) according to any one of claims 21 to 28, wherein The one or more links point to at least one of an array of the data values ​​and a mapping of the data values.

30. The WD (22) according to claims 21 to 29, wherein the following At least one of the terms holds true: The information includes the one or more data values ​​associated with the one or more resources; The resource model is a lightweight machine-to-machine LwM2M object resource model; The CC object is a CC LwM2M object; The network node (16) is a LwM2M management server; as well as The WD (22) is a LwM2M client.

31. A method in a wireless device WD (22), the wireless device WD (22) being configured to communicate with a network node (16) using at least one of a wired connection and a wireless connection, the method comprising: determining (S146) a compact composite CC object associated with a resource model, the determined CC object to be implemented by the WD (22) and comprising at least one of a structure description resource and a compact data resource, the structure description resource comprising one or more links to one or more resources accessible by the network node (16), the compact data resource comprising one or more data values ​​associated with the one or more resources; as well as At least one action is performed (S148) to provide information associated with at least one of the CC object, the structure description resource, and the compact structure resource.

32. The method according to claim 31, wherein: Determining the CC object includes: The CC object is created based on a first request received from the network node (16).

33. The method according to any one of claims 31 and 32, wherein: Determining the CC object includes: The CC object is enabled to be discovered by the network node (16) based on a second request received from the network node (16) for reading the one or more links.

34. A method according to any one of claims 31 to 33, wherein: The provided information triggers the network node (16) to examine the one or more links to determine the structure of the compact data resource.

35. The method of claim 34, wherein: The method further comprises: A third request to create or discover another CC object based on the inspection of the one or more links is received.

36. The method according to any one of claims 31 to 35, wherein: The CC object is pre-instantiated in the WD (22).

37. The WD (22) according to any one of claims 31 to 36, wherein The method further comprises: A CC object identifier is sent which can be used by the network node (16) to identify the CC object.

38. The method according to any one of claims 31 to 37, wherein: The method further comprises: A fourth request is received, the fourth request to create the compact data resource using a compound read operation or to update the compact data resource using a compound read operation, the fourth request including an indication indicating whether the compact data resource is to be created or updated.

39. The method according to any one of claims 31 to 38, wherein: The one or more links point to at least one of an array of the data values ​​and a mapping of the data values.

40. The method according to any one of claims 31 to 39, wherein: At least one of the following is true: The information includes the one or more data values ​​associated with the one or more resources; The resource model is a lightweight machine-to-machine LwM2M object resource model; The CC object is a CC LwM2M object; The network node (16) is a LwM2M management server; as well as The WD (22) is a LwM2M client.

Images