KR101997603B1 - Method And Apparatus for Interworking with non-M2M compliant device - Google Patents

Abstract

An interworking method with an M2M non-standard device according to an embodiment of the present invention may include receiving an activation request message of a function module corresponding to a service link activated in an M2M non-standard device from the M2M non-standard device; And activating the function module according to the transmission of the function module activation request message.

Description

Method and Apparatus for Interworking with M2M Non-Standard Device {Method And Apparatus for Interworking with non-M2M compliant device}

Thing communication or communication between things means communication made between devices. The communication between the objects is implemented differently from the communication of the conventional mobile phone in that it has a feature of transmitting and receiving various information in accordance with a specific pattern. In this specification, in order to implement such a thing communication, an object of the present invention is to provide a method for interworking with an M2M nonstandard device and an apparatus for implementing the same.

Machine-to-Machine (M2M) refers to communication for providing things information to a person or an intelligent device using a broadcasting communication network, or for controlling a state of things by a person or an intelligent device. M2M is also called the Internet of Things (IOT), Object to Object Intelligent Network (O2N).

While M2M communication in the early and late 1990s meant one-to-one or one-to-many communication for simple point-to-point (P2P) connection, the ultimate goal of M2M communication is to introduce location awareness, situational awareness and augmented reality. It aims to improve the quality and stability of M2M communication service by automatically operating without human control or minimizing human intervention to suit individual or situation.

M2M network communication can be utilized as an essential infrastructure that can contribute to solving social issues, preventing disasters and disasters, and saving energy through conventional u-City, u-Health, u-transportation, and u-environmental projects. Currently, M2M services include a wide range of services such as remote meter reading, building and facility management, vending machine management, indoor lighting control service, traffic information and vehicle control, emergency dispatch, fire alarm, security alarm device, vending machine, telematics, and wireless payment service. It is provided as. In addition, recently applied to medical devices such as pulse meter, electrocardiogram and the like has been actively applied in the e-Health field including telemedicine services.

M2M communication is an object-to-device communication that differs from other human-centered human-to-human communication. From these differences, technically necessary technologies may vary, and the required characteristics may vary slightly depending on the field of application using M2M communication. Currently, standardization groups around the world, such as the European Telecommunication Standard Institute (ETSI), are continuing research and development to standardize successful M2M communications. FIG. 1 shows Machine-to-Machine Communications (M2M) of ETSI Technical Specification (TS) 102 690 of ESTI standard documents; Functional architecture] shows the architecture for M2M services including device and gateway domains and network domains. Hereinafter, the contents of the standardization work performed in ETSI, including the ETSI Technical Specification (TS) 102 690, are referred to as "ETSI standard" or "M2M standard".

Referring to FIG. 1, the M2M devices 10 and 10 ′ are terminal devices that communicate with minimal or no human input and intervention, and transmit or transmit their own data on request or automatically. It is a kind of device.

In addition, according to the ETSI standard, when the M2M device 10 directly connects to the access network 40, the M2M device (M2M Service Capability) 11 of the M2M device 10 ' It is prescribed to execute the device application (DA) 12 which is an M2M application (M2M Application) of 10), and when the M2M device 10 'is connected to the access network 40 through the M2M gateway 30, M2M It is prescribed to use the M2M service capability 31 of the gateway 30.

The M2M Area Network 20 also provides a connection between the M2M device 10 'and the M2M Gateway 30. Examples of the M2M local area network 20 include a personal area network (hereinafter referred to as “PAN”) such as IEEE 802.15.x, Zigbee, Bluetooth, IETF ROLL, ISA100.11a, or a wireless local area network (Wireless Local). Area Network (hereinafter referred to as “WLAN”), PLC, M-BUS, Wireless M-BSU, and KNX.

The M2M gateway 30 is a gateway that executes the gateway application (GA) 32 which is an M2M application of the M2M gateway 30 using the M2M service capability 31, and the M2M device 10 ′ and the access network 40. It acts as a proxy between

The access network 40 is a network that allows the M2M device 10 'to M2M gateway 30 to communicate with the core network 50. Examples of the access network 40 include xDSL, HFC, FTTH, PLC, Satellite network, GERAN, UTRAN, eUTRAN, Wireless LAN, WiMAX (WiBro), and the like.

The core network 50 is a network that provides IP connectivity, access network control and network service control functions, interconnection with other networks, roaming functions, and the like. Examples of the core network 50 are 3GPP CN, ETSI TISPAN CN, 3GPP2 CN, IMS, and the like.

The M2M service capability 60 of the network domain provides a function that can be shared by different applications, and provides an environment for accessing other service capabilities through an open interface. Using these M2M service capabilities, it is possible to develop and deploy optimal applications without considering the characteristics of lower network layers.

Network applications (NA) 70, which are M2M applications in the network domain, execute M2M service logic and provide them in the M2M system using the M2M service capability 60 through an open interface.

Meanwhile, according to FIG. 1, the network domain is defined to include M2M Management Functions and Network Management Functions. Here, M2M Management Functions (80) is composed of all the functions required to manage M2M service capabilities in the network domain, the management of the M2M device to M2M gateway specific M2M service capabilities Will be used. In addition, the network management functions 90 are composed of all functions required to manage the access network 40 and the core network 50, and provide provisioning, supervision, and fault management. And other features.

In addition, according to the ETSI standard, a layer representing M2M service capacities in a network domain is referred to as a network service capability layer (hereinafter referred to as “NSCL”), and a layer representing M2M service capabilities of a gateway. The Gateway Service Capability Layer (hereinafter referred to as "GSCL") and the layer representing the M2M Service Capabilities of the M2M device are referred to as the Device Service Capability Layer (hereinafter referred to as "DSCL"). Is defined as The NSCL, GSCL, and DSCL are collectively referred to as a Service Capability Layer (hereinafter, referred to as “SCL”). Here, NSCL refers to a platform that is individually set up for each service by a service provider that provides each M2M service. Hereinafter, the NSCL is also referred to as an “M2M service platform”.

Meanwhile, the ETSI standard includes the DA 12 and the DSCL 11 of the M2M device 10, the M2M device 10 ′ and the gateway 30, the GSCL 31, and the GA 32 and the gateway 30. Reference points between GSCL (31) are dIa, DSCL (11) and reference points between GSCL (31) and NSCL (60) mId, and reference points between NA (70) and NSCL (60). Is defined as mIa.

In order to facilitate the supply and demand of content in the M2M service environment as described above, the existing hit service and killer application should be able to be easily transferred in a short time. That is, for example, in the case of a killer application in a conventional smartphone environment, in order to transfer it to an M2M service environment, the killer application should be released after redesigning, redeveloping, and testing the M2M platform. Therefore, even though the same service is provided, there is a problem that the development cost must be paid again because the terminal platform is changed.

In the case of M2M service, the best performance should be expressed regardless of the operating environment of the device. In other words, in the M2M environment, the device varies in performance from sensors to smartphones, so it is necessary to ensure the quality of applications that are applications in various device system environments. Since the performance of an application depends on the hardware environment in which the application is executed, the performance of the same application depends on the performance of the device, and also poses a risk in stability.

In addition, the conventional M2M service based on the ETSI standard is an in-house building, for example, a communication service provider generally constructs and provides management functions of the M2M service in the form of system integration (SI). . However, this case requires excessive initial investment in the long tail M2M market, making it difficult to guarantee profitability. Therefore, there is a need to reduce the cost of platform construction by dynamically constructing the service execution environment according to the device system specification when connecting to the M2M service provider without establishing the service environment statically.

In addition, in the case of the conventional M2M service, even in competition or heterogeneous M2M ecosystem does not consider providing an environment in which the service can run. Even if the market standardization is made through the M2M standard as described above, it is hoped that, over time, the M2M platform based on the M2M standard will be built to protect the ecosystem of each carrier and manufacturer, thereby technically preventing competitors from entering the market. Because you may want to. Therefore, if there is such a technical protection barrier, there is a need for a method in which the service can be executed in the ecosystem of the other party.

The present invention has been made to solve the problems of the prior art as described above, it is an object of the present invention to implement an efficient method and apparatus for interworking with M2M non-standard devices that can provide an execution environment independent of the M2M terminal platform. .

In order to achieve the above object, a method of interworking with an M2M nonstandard device according to an embodiment of the present invention includes receiving an activation request message of a function module corresponding to a service link activated in an M2M nonstandard device from the M2M nonstandard device; ; And activating the function module according to the transmission of the function module activation request message.

Here, the functional module may process data according to a protocol conforming to the M2M standard.

In addition, the activation request message of the function module may include bulk data generated by the M2M non-standard device, the activation step of the function module, according to the activation of the function module for the bulk data according to the M2M standard Generating a related resource.

The method may further include transmitting a resource generation complete message according to the generation of the resource to the M2M non-standard device; And forwarding the generated resource to a destination according to a data transmission request message from the M2M non-standard device.

In accordance with another aspect of the present invention, there is provided an apparatus for implementing an M2M entity, including: a communication unit configured to receive an activation message of a function module corresponding to a service link activated in an M2M nonstandard device from the M2M nonstandard device; And a link capability unit including a plurality of function modules including the function module activated according to the transmission of the function module activation message.

Here, the activation message of the function module may include bulk data generated in the M2M non-standard device, and the link capability may process the bulk data according to a protocol conforming to the M2M standard.

In order to achieve the above object, a method of interworking with an M2M entity according to another embodiment of the present invention includes the activation request message of a function module of an M2M entity corresponding to the service link according to activation of a service link. Transmitting to; And receiving a response message from the M2M entity as a result of the activation of the functional module of the M2M entity.

The activation request message of the function module may include bulk data to be processed by the function module of the M2M entity.

In order to achieve the above object, an apparatus for interworking with an M2M entity according to another embodiment of the present invention includes a virtual player unit including a plurality of service links respectively corresponding to a plurality of functional modules implemented in the M2M entity. ; And a communication unit configured to transmit an activation request message of a function module corresponding to the service link to the M2M entity by activation of the service link.

The activation request message of the function module may include bulk data to be processed by the function module of the M2M entity.

According to the present invention, by using a virtual SCL player that can be independently executed in the M2M terminal platform, the service can be optimally executed even in a heterogeneous M2M environment that does not conform to the M2M standard. This makes it easy to build and spread the M2M service ecosystem.

In addition, existing killer applications can be applied to the M2M market in a short time to maximize the effectiveness of the customer's use of M2M in a short time, and to maintain its ecosystem despite changes in the base environment, so that the M2M environment can be efficiently and economically There is an effect that can spread.

1 illustrates an architecture for an M2M service comprising a device and gateway domain and a network domain according to the prior art.
Figure 2 schematically shows the overall configuration of the M2M system to which the present invention can be applied.
3 is a diagram illustrating a detailed functional module for implementing an xIP function according to an embodiment of the present invention.
4 is a diagram conceptually illustrating an interworking relationship with a M2M non-standard device in which a virtual SCL player is implemented using a DIP function of an M2M device according to an embodiment of the present invention.
5 is a diagram schematically showing the configuration of an M2M non-standard device and an M2M entity according to an embodiment of the present invention.
6 is a diagram illustrating a procedure for processing data generated in an M2M non-standard device according to an embodiment of the present invention.
7 is a diagram illustrating a procedure of processing data generated in an M2M non-standard device according to another embodiment of the present invention.
8 is a diagram illustrating a procedure for downloading and executing a virtual SCL player to an M2M non-standard device according to an embodiment of the present invention.

Hereinafter, with reference to the accompanying drawings, it will be described in detail the present invention. As the inventive concept allows for various changes and numerous modifications, particular embodiments will be illustrated in the drawings and described in detail in the text. However, this is not intended to limit the present invention to the specific disclosed form, it should be understood to include all modifications, equivalents and substitutes included in the spirit and scope of the present invention.

In describing the drawings, similar reference numerals are used for similar elements. Here, terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component. Singular expressions include plural expressions unless the context clearly indicates otherwise.

In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, action, component, part, or combination thereof described on the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, parts, or combinations thereof.

Also, unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

Figure 2 schematically shows the overall configuration of the M2M system to which the present invention can be applied.

Referring to FIG. 2, the entire M2M system 100 includes a network application (NA) 70, an M2M service platform (NSCL) 60, an M2M device 10a, 10b, 10 ′, and an M2M gateway ( M2M Gateway) may be included. Hereinafter, the description will be given based on portions which do not overlap with the above description with reference to FIG. 1.

The M2M system according to the embodiment of the present invention may further include a device (d) (hereinafter referred to as "non-ETSI M2M compliant device") that does not comply with the predetermined ETSI M2M standard as described above. The M2M non-standard device (d) corresponds to a device in which the service capability defined in the M2M standard is not implemented or cannot be used in the device itself, and is installed by an individual M2M service provider regardless of the M2M standard. A device may be included The present invention relates to the implementation of functionality to support interworking of such M2M non-standard devices (d) with devices, gateways, and M2M service platforms that conform to the M2M standard.

To this end, according to the present invention, the network interworking proxy (NIP) 63 function, the gateway interworking proxy (GIP) function, and the device interworking proxy (DIP) 13 function, which are used for communication with the M2M non-standard device (d), respectively, are provided. It may be included in NSCL 60, GSCL 31 and DSCL 11b. Here, the M2M device 10b, M2M gateway 30 and M2M service platform (or NSCL 60) having xIP (NIP, GIP or DIP) function for interworking with the M2M non-standard device (d) is referred to as “ M2M entity ”.

3 is a diagram illustrating a detailed functional module for implementing an xIP function according to an embodiment of the present invention. Since the present invention relates to interworking with an M2M non-standard device, the xIP function is related to an M2M terminal platform according to the M2M standard, and the functional module illustrated in FIG. 3 includes a functional architecture provided by the ETSI standard as described above. Functional architecture, but this is only an example and it will be apparent that other functional modules may be included in other architectures.

As shown in FIG. 3, the xIP function can be roughly divided into service capability and network capability.

The network capability is for performing a network capability function at a network layer, comprising: a data collection function module for collecting data from a device; A connection / session management function module for the collected data; QoS management function module for quality management; It may be configured to include an ID / Address management function module and the like.

The service capability is to perform a service capability function in the service layer, and includes a control management function module for individual and group control; Authentication / opening management function modules of gateways, devices and applications; A security management function module; It may be configured to include a gateway / device profile management module and the like.

4 is a diagram conceptually showing an interworking relationship with a M2M non-standard device d in which a virtual SCL player is implemented using the DIP 13 of the M2M device 10b as an example of an M2M entity according to an embodiment of the present invention. .

As shown in FIG. 4, in order to interwork with the M2M non-standard device d according to the present invention, the virtual SCL player 400 and the M2M entity implemented in the M2M non-standard device d (the M2M device 10b in the example of FIG. 4). SCL Link Capability 401 implemented in the DIP.

The SCL link capability 401 implemented in the M2M entity 10b is composed of a plurality of functional modules required to process data according to a protocol conforming to the M2M standard to provide an M2M service as shown in FIG. 3. It is.

The virtual SCL player 400 implemented in the M2M non-standard device d is provided with only a service link, which is a link to each functional module of the SCL link capability 401 implemented in the M2M entity 10b. do. That is, the virtual SCL player 400 has the same configuration as the actual SCL as shown in FIG. 3, but the implementation part for each functional module is excluded and the actual SCL (i.e., the SCL link capability implemented in the M2M entity 10b). (401)] is configured to have only a service link that can be connected to each functional module.

Thus, if the service link corresponding to the functional module to be performed by the execution of the application in the M2M non-standard device (d) is activated, the M2M non-standard device (d) is a function in the M2M entity 10b corresponding to the activated service link Sends a message to the M2M entity to activate the module. Thereafter, the M2M entity 10b may activate the corresponding function module to process data according to a protocol conforming to the M2M standard, thereby interworking by connecting the M2M non-standard device d with the SCL of the M2M entity 10b. .

5 is a diagram schematically showing the configuration of an M2M non-standard device and an M2M entity according to an embodiment of the present invention.

The M2M non-standard device 500 according to the embodiment of the present invention may include an M2M application unit 501, a virtual SCL player unit 502, and a communication unit 503.

The M2M application unit 501 corresponds to an application program installed in the M2M non-standard device 500 when using the service provided by the M2M service platform.

As described above, the virtual SCL player unit 502 may be provided to the M2M non-standard device 500 in a form of an application program having only a service link corresponding to each function module constituting the xIP function implemented in the M2M entity 510. It is provided.

In addition, when the service link is activated in the virtual SCL player unit 502 corresponding to the execution of the application of the M2M application unit 501, a function module activation message for activating a function module corresponding to the activated service link is displayed. The communication unit 503 communicates with the M2M entity 510.

The M2M entity 510 may include an SCL link capability unit 511 and a communication unit 512. The SCL link capability unit 511 includes respective function modules capable of processing data according to a protocol conforming to the M2M standard as shown in FIG. 3, and the M2M non-standard device ( When the function module activation message is received from the 500, the function module corresponding to the function module activation message is activated.

As described above, according to the present invention, only the service link is activated in the virtual SCL player unit 502 of the M2M non-standard device 500, and by executing a function module corresponding to the activated service link, the protocol conforms to the M2M standard. The creation of related resources is actually done in the SCL link capability unit 511 of the M2M entity 511.

6 is a diagram illustrating a procedure for processing data generated in an M2M non-standard device according to an embodiment of the present invention. This example corresponds to a case where the M2M non-standard device is a device for observing the wind speed, and transmits the wind speed data to the M2M service platform according to the M2M standard.

First, in step S601, the wind speed data measured by the M2M application of the wind speed measurement device is transferred to the virtual SCL player unit.

In step S602, the virtual SCL player unit activates the service link corresponding to the data collection module of the network capability, for example, to generate a resource conforming to the M2M standard according to the measurement of the wind speed data.

In step S603, according to the activation of the service link of the virtual SCL player, a function module activation message for activating a data collection module for measured wind speed data (bulk data) is transmitted along with the wind speed data to the M2M entity.

Thereafter, in step S604, the SCL link capability unit of the M2M entity activates the data collection module in the SCL link capability unit with respect to the bulk data included in the function module activation message received from the virtual SCL player, which is a format for the M2M standard. container> Create a resource. Here, the <container> resource is defined in the M2M standard, and serves as a mediator for buffering data, and is a general purpose resource used to exchange data between an application and an SCL.

If the M2M entity sends a response message indicating that the M2M <container> resource has been generated to the virtual SCL player in step S605, the virtual SCL player requests the M2M entity to transmit the generated data to the hosting SCL as a destination (step S606). Here, the hosting SCL is an SCL where a resource (Master / original Resouce) addressed according to the M2M standard should reside.

The M2M entity then finds the hosting SCL and delivers the data according to the prescribed procedure defined in the M2M standard (steps S607 and S608), and receives a response message from the hosting SCL indicating that the data has reached its destination (step S609). This is transmitted to the virtual SCL player, and the virtual SCL player transmits a response message indicating that the destination arrival of the wind speed data is completed to the M2M application (steps S609 to S611).

7 is a diagram illustrating a procedure for processing data generated in an M2M non-standard device according to another embodiment of the present invention.

According to the procedure as shown in FIG. 6, the wind speed measuring device as the M2M non-standard device can use the SCL performance of the M2M entity without putting a load on the performance of the wind speed measuring device in the course of sending the wind speed data. However, in this case, when a plurality of M2M non-standard devices are connected to the M2M entity, there may be a problem that the load of the M2M entity becomes severe.

The M2M standard applies the general principles of store-and-forward (SAF) processing to access remote hosted resources, as well as requests issued by NA or NSCL to access D / GSCL resources. It specifies that D / GA or D / GSCL apply to requests issued to access NSCL resources. In this case, for each request to access the remote hosted resources, the Issuer will accept an acceptable Tolerable Request Processing Delay Time (“TRPDT”) and / or Request Catagory; It is regulated that the load can be managed by setting “RCAT” in SCL below.

The embodiment shown in FIG. 7 solves the problem of overload by multiple processing requests by multiple M2M non-standard devices as described above using TRPDT and RCAT defined in the M2M standard. For convenience, only parts different from the embodiment shown in FIG. 6 will be described below.

In step S602, when the virtual SCL player activates a service link corresponding to the data collection module of the network capability module to generate a resource conforming to the M2M standard, the M2M entity requests TRPDT and RCAT of the SCL of the M2M entity. The response is received (steps S620 and S621).

Thereafter, in step S622, it is determined whether the SCL of the M2M entity can process wind speed measurement data using the transmitted TRPDT and RCAT. If it is determined that there is a margin, steps S603 and subsequent steps are performed in the same manner as the procedure illustrated in FIG. If it is determined that there is no margin, the procedure of step S620 is repeated after waiting for the TRPDT.

8 is a diagram illustrating a procedure for downloading and executing a virtual SCL player to an M2M non-standard device according to an embodiment of the present invention.

In the case of M2M non-standard devices, each device is likely to operate under a different operating system, but according to the present invention, avoiding a conventional platform installation method such as a porting method and the like when the M2M application connects to the M2M service provider for the first time in FIG. 8. It can be downloaded and executed on the M2M non-standard device by the procedure shown. Therefore, the virtual SCL player of the present invention can provide an application program (M2M application) developed based on the M2M standard independently of the operating system of the device, and provide a slim and powerful execution environment.

First, when the M2M non-standard device equipped with the M2M application is powered on in step S801, the M2M application is generally supplied by the M2M service provider in the case of the M2M application, so in step S802, the M2M application is registered for its M2M service platform. You have access to an M2M service provider.

Thereafter, the M2M service provider requests the operating system and system specification information of the M2M non-standard device and receives the response (steps S803 and S804).

In the next step S805 M2M service provider configures the SCL service link according to the system information of the received M2M non-standard device. In this case, the SCL service link configuration method can be selected from the following two methods. One way is to provide an execution environment to connect virtual SCL players one-to-one with the same number of M2M applications requested. The other way is to install one virtual SCL player regardless of the number of M2M applications requested. It provides a running environment that can be applied to M2M applications.

Subsequently, in step S806, the virtual SCL player is created by combining each service link through cross compilation according to the operating system information of the M2M non-standard device, and downloading a custom virtual SCL player for each M2M application and / or non-standard device. In this case (step S807), the M2M non-standard device can execute the M2M application in the virtual SCL player environment by the downloaded virtual SCL player (step S808).

10a, 10b, 10 ': M2M Device
30: M2M Gateway
60: M2M Service Platform
70: Network Application (NA)
d, 500: M2M nonstandard device
400: virtual SCL player
401: SCL Link Capability
501: M2M application unit
502: virtual SCL player section
503, 512: communication unit
511: SCL linkability part

Claims (11)

Receiving an activation request message of a function module corresponding to a service link activated in an M2M non-standard device, from the M2M non-standard device; And
And activating the function module according to the transmission of the function module activation request message. The method of claim 1,
And the function module processes data according to a protocol conforming to the M2M standard. The method of claim 1,
The activation request message of the function module includes a bulk data generated by the M2M non-standard device. The method of claim 3, wherein
Activation of the function module,
And generating related resources with respect to the bulk data according to the activation of the function module in accordance with the M2M standard. The method of claim 4, wherein
Transmitting a resource creation complete message according to generation of the resource to the M2M non-standard device; And
And delivering the generated resource to a destination according to a data transmission request message from the M2M non-standard device. A communication unit receiving an activation message of a function module corresponding to a service link activated in an M2M nonstandard device from the M2M nonstandard device; And
And a link capability unit including a plurality of function modules including the function module activated according to the transmission of the function module activation message. The method of claim 6,
The activation message of the function module includes bulk data generated in the M2M non-standard device, and the link capability unit processes the bulk data according to a protocol conforming to the M2M standard. . Transmitting an activation request message of a function module of an M2M entity corresponding to the service link to the M2M entity according to activation of a service link; And
And receiving a response message from the M2M entity as a result of the activation of the function module of the M2M entity. The method of claim 8,
The activation request message of the function module includes the bulk data to be processed by the function module of the M2M entity. A virtual player unit including a plurality of service links respectively corresponding to a plurality of function modules implemented in the M2M entity; And
And a communication unit which transmits an activation request message of a function module corresponding to the service link to the M2M entity by activating the service link. The method of claim 10,
The activation request message of the function module includes the bulk data to be processed by the function module of the M2M entity, the apparatus for interworking with the M2M entity.

Images