KR20140058307A - A method for registering device application for providing device mobility and an apparatus therefor - Google Patents
A method for registering device application for providing device mobility and an apparatus therefor Download PDFInfo
- Publication number
- KR20140058307A KR20140058307A KR1020130028500A KR20130028500A KR20140058307A KR 20140058307 A KR20140058307 A KR 20140058307A KR 1020130028500 A KR1020130028500 A KR 1020130028500A KR 20130028500 A KR20130028500 A KR 20130028500A KR 20140058307 A KR20140058307 A KR 20140058307A
- Authority
- KR
- South Korea
- Prior art keywords
- resource
- application
- terminal
- service
- gateway
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
The present invention relates to M2M (machine to machine) technology, and more particularly, to a method and apparatus for providing mobility of a terminal under a gateway / standard terminal.
M2M terminals are basically mobile. The standard standard terminal D and the nonstandard standard terminal or the standard standard terminal d or D 'may be moved to be connected to the plurality of gateways G or the standard terminal D.
1 shows a configuration for providing a wellness service and a self-security service.
In the configuration shown in FIG. 1, the wellness service provides data by collecting data from a scale, a footprint sensor, and a bike, and a self-security service is provided by a door open sensor, a heat sensor, To provide services.
In the self-security service, the location of the terminals will be fixed to the inside of the house due to the nature of the service. Therefore, the door open sensor and the heat sensor are always connected to the home gateway (GW).
However, in the case of the wellness service, the terminals providing data may move. For example, you could measure footprint information at home by wearing footwear with a footprint sensor, but the company could also measure footprint information. In addition, when the M2M service becomes more popular, public gateways are spread and various types of M2M terminals can be moved and data can be transmitted through a common gateway at a desired point of time.
Regardless of where the standard scales terminal (D) moves, there is no change in the address that can be connected to the scales. When you are at home, the address of the scales is http: //scale#1.and.com/DSCL_base/~~~ Wellness Services can access the address and collect data, and even if the scales move to the company, the address is the same You can access http: //scale#1.and.com/DSCL_base/~~~ . Even if the scales are in Korea or moving to other countries, the address of the scales resources that wellness services can access remains unchanged.
However, a gateway such as a footprint sensor or a bike or a terminal at the lower end of a standard terminal may be different depending on which gateway or a standard terminal is connected.
If the footprint sensor is interfaced to the home gateway, then the wellness service is http: //
The application service should ask the standard terminal / gateway that sends the data to use if it is newly added to the terminal application (DA). Therefore, the self-security service is connected to the home gateway ( http: // home_gateway # 1.public.com ) and IP camera ( http: // ip_camera # 1.btn.com ) The home gateway notifies the self-security service when the door open sensor and the heat detection sensor are interlocked with the home gateway to generate the related terminal application (DA).
However, since the wellness service not only requires the home gateway and the scales to be informed when a related terminal application (DA) is newly added, but also because the foot sensor or the bike can move and be linked to the company gateway, DA) to be added. So if you have 10 gateways in your company, you have to request all 10 gateways to provide service, even if your footprint sensors or bikes are linked to any gateways in the company. Also, if you want to get wellness services on your commute as well as on the road, you should be notified about all public gateways in your travel route.
FIG. 2 is a diagram for explaining a notification request according to movement of a non-standard standard terminal.
In order to provide mobility to the non-partial standard terminal d and D ', all the application services NA using the non-standard standard terminal d and D' are allocated to all the public gateways G You need to be notified about this. Accordingly, when an arbitrary non-part / standard standard terminal (d, D ') is connected to one public gateway, all application services that have made a notification request to the corresponding public gateway receive notifications and attempt to access the corresponding public gateways And only the application service having the access right to the non-part / standard-compliant terminal d, D 'collects data. That is, all the application services attempt to collect data but only the wellness service that has access to the footprint sensor data actually collects the data.
However, this method needs to register notifications to all public gateways every time an application service is added, and sends a notification message to all application services each time the non-standard standard terminal (d, D ') accesses the public gateway , All application services receiving the notification message are connected to the corresponding gateway. Therefore, unnecessary traffic is caused too much.
Accordingly, the present invention seeks to provide a method and apparatus for effectively accommodating movement of a non-part standard terminal (d, D ').
More specifically, when the non-partial standard terminal d or D 'is connected to the gateway G or the standard terminal D, it is applied to an application service using data generated from the non- And a method and apparatus for allowing an application service to access the gateway (G) / standard compliant terminal (D) to which the terminal is connected and collect data of the terminal.
According to an aspect of the present invention, there is provided a method for providing a service, comprising: receiving an application resource creation request from an issuer in a hosting service capability layer; creating the application resource in the hosting service capability layer; And transmitting a resource creation notification message to an application service having access right to the issue word if the issue information corresponds to a non-standard specification terminal or a partial standard specification terminal according to the information.
The terminal application registration method includes the steps of: receiving a notification request message from the application service in the host service capability layer upon generation of a resource in a lower layer of the generated resource; And transmitting a notification message for the lower layer resource creation to the application service when the resource is generated in the lower layer. In addition, upon receiving a request for the resource from the application service through a response to the notification message for the lower layer resource generation, the data stored in the resource can be transmitted.
The attribute information of the issue word may be information indicating that the issue corresponds to one of a standard specification terminal, a nonstandard specification terminal, a partial standard specification terminal and a gateway.
According to another aspect of the present invention, upon receipt of an application resource creation request from an issuer, the application resource is created, and the attribute information of the issue language is checked to determine whether the issue language is a non-standard specification terminal or a partial standard specification terminal The terminal application registering device transmits a resource creation notification message to an application service having access right to the issue word.
Every time a non-part standard compliant terminal is connected to a common gateway, a notification message is sent to all application services (NA), and all application services (NA) do not need to connect to the corresponding gateway, saving network resources.
Also, when a non-part standard terminal is connected to a gateway / standard-compliant terminal, it automatically transmits a notification message to an application service (NA) having access authority to the terminal, thereby effectively accommodating the mobility of the non-part standard terminal .
Figs. 1 and 2 are diagrams for explaining the prior art.
3 is a diagram for explaining the M2M architecture.
4 is a diagram for explaining the reference point of the ETSI TC M2M.
5 is a diagram for explaining an example of the configuration of the M2M service.
FIG. 6 is a view for explaining a collection procedure of scale data. FIG.
7 to 9 are diagrams for explaining a resource structure of scale data.
FIG. 10 is a diagram for explaining a procedure of collecting footprint sensor data.
11 to 13 are diagrams for explaining the resource structure of place-based center data.
14 is a diagram for explaining an application resource creation procedure.
15 is a diagram for explaining an application resource creation procedure according to the present invention.
FIG. 16 is a diagram for explaining a footprint sensor data collection procedure according to an application registration method according to the present invention.
Hereinafter, some embodiments of the present invention will be described in detail with reference to exemplary drawings. It should be noted that, in adding reference numerals to the constituent elements of the drawings, the same constituent elements are denoted by the same reference symbols as possible even if they are shown in different drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.
In describing the components of the present invention, terms such as first, second, A, B, (a), and (b) may be used. These terms are intended to distinguish the constituent elements from other constituent elements, and the terms do not limit the nature, order or order of the constituent elements. When a component is described as being "connected", "coupled", or "connected" to another component, the component may be directly connected or connected to the other component, Quot; may be "connected," "coupled," or "connected. &Quot;
Embodiments of the present invention will be described with reference to object communication. Object communication is variously called M2M (Machine to Machine communication), MTC (Machine Type Communication), IoT (Internet of Things), Smart Device Communication (SDC), or Machine Oriented Communication . Object communication refers to various communication in which communication is performed without a person intervening in the communication process. Object communication can be used in various fields including Smart Meter, e-Health, Connected Consumer, City Automation, and Automotive Application.
3 is a diagram showing an M2M structure as an environment to which an embodiment of the present invention is applied. The network environment to which the present invention is applied is based on the M2M architecture described in the technical committee M2M of the European Telecommunication Standards Institute (ETSI), an international standard. In the device / gateway and the M2M core platform, It is applied in an environment that provides a function to accommodate a network.
Referring to the drawings, the M2M structure includes a network and application domain or M2M platform shown on the upper side of the drawing, and an M2M device / gateway domain M2M for providing the object intelligent communication service shown on the lower side of the drawing Device domain).
The network / application domain includes an M2M application (111), a core network (113) such as 3GPP, an M2M application (111) for accessing or providing service logic to M2M Service Capabilities And an
The service capabilities (SCs) 112 of the network domain may interface with one or
The network / application domain may also include an
On the other hand, the M2M device / gateway domain includes the
The
In addition, the
For example, the
That is, the
The
M2M Service Capabilities (NSCL) in the network domain is implemented as a server platform and M2M service capability of the device / gateway domain (M2M service capability) Service Capabilities (DSCL / GSCL) 132 and 122 reside in the terminal and operate.
The service capability SC may include one or more of xAE, xGC, xRAR, xCS, xREM, xSEC, xHDR, xTM, xTM, xIP, xCB or xTOE, G for a device, or D for a device. That is, xIP can be NIP, GIP, or DIP. The xSEC described below is a security capability, which may be NSEC, GSEC or DSEC.
In the present invention, the non-standard specification terminal d refers to a terminal that does not include a terminal service capability layer DSCL and a terminal application DA, and the partial standard compliant terminal D 'includes a terminal service capability layer DSCL. However, the terminal application DA means the terminal including the terminal application DA. The terminal service capability layer is also referred to as a terminal platform, and the terminal application is also referred to as a terminal app.
The Service Capability Layer (SCL) 122 and 132 of the
To this end, reference points of mIa, mId, and dIa are defined as the interface between the network domain and the device and gateway domains according to the M2M standard structure.
4 is a diagram of an ETSI TC M2M reference point as an environment to which the embodiment of the present invention is applied.
mIa is a reference point used in the network domain and is an interface specification between NSCL (M2M Service Capability Layer in the network) and NA (Network Application) provided by the M2M platform.
mId is the interface specification between the NSCL of the network domain and the D / G SCL (DSCL or GSCL) of the device / gateway domain. In other words, mId is an interface standard applied between the NSCL of the network domain provided by the M2M platform and the DSCL (M2M Service Capabilities in the M2M Device), which is the service capability layer of the device, and the NSCL of the network and the GSCL M2M Gateway).
dIa is a reference point used in the M2M device / gateway domain. It is an interface between a device service capability layer (DSCL) and a device application (DA) provided by the M2M device, a gateway service capability layer (GSCL ), A gateway application (GA) interface, and an interface specification of GSCL and DA provided by the M2M gateway.
The M2M service structure of the M2M standard structure includes, for example, a
According to
Where x may be N for a network, G for a gateway, or D for a device. That is, xIP can be NIP, GIP, DIP.
The xIP can discover the structure of the M2M area network and create an M2M resource structure representing the M2M area network structure in the service capability layer SCL. When the M2M area network structure changes, the M2M resource structure can be managed to reflect this.
In addition,
In addition, according to
The present invention relates to a mobility provision method for a terminal that is not directly connected to the server platform 290 (NSCL), that is, the terminal located at the lower side of the
When the non-standard compliant terminal d is connected to the gateway G / standard compliant terminal D, the non-standard compliant terminal d and the gateway G / standard When a network connection is created between the nonstandard standard terminal d and the gateway G / standard terminal D using an area network such as Bluetooth or zigbee among the standard terminals D, , And also when the non-standard compliant terminal d creates an application resource in the gateway G / standard compliant terminal D. [
When the partial standard terminal D 'connects to the gateway G, the terminal / gateway application (ETSI TC M2M) of the ETSI TC M2M between the partial standard terminal D' and the gateway G DA, GA) and the terminal / gateway SCL (DSCL, GSCL) interface specification dIa is set.
In the present invention, for the sake of convenience of explanation, the application resource requesting time point commonly corresponding to the non-standard standard terminal d and D 'is connected to the non-standard standard terminal d and the gateway G / standard standard terminal D Sometimes we will limit this.
5 is an example of a configuration of an M2M service. The
6 is a diagram showing an example of a procedure for the wellness service to collect data from the scales in the configuration as shown in FIG.
First, a process in which the server platform and the terminals recognize each other through mutual registration will be described (S710).
The
Accordingly, the
Hereinafter, the application registration process (S720) will be described.
The
In addition, the
The
Next, the container creation process (S730) will be described. The
The
The
The
Finally, the process of generating and storing actual data (S740) will be described.
When the user measures the weight using the scale, the
The
10 is a diagram for explaining a procedure for collecting data from a footprint sensor in which the wellness service is a partial standard terminal.
First, a description will be given of a process in which the
Next, the application registration process (S820) will be described. The
When the terminal app (DA) resource is created in the
Then, when the
The container generation process (S830) will be described below. The
Accordingly, when the container resource is created at the lower end of the newly generated terminal appara- tus DA, the
When the
Then, the
Accordingly, the
When the user connects the shoe to the gateway after activating the footwear with the footprint sensor, the
The
The
The data collection procedure described with reference to FIG. 10 assumes that the footwear sensor to be used by the wellness service and the gateway knows in advance which gateway to access. In other words, knowing that the footprint sensor will be connected to the gateway having the address http: // gateway # 1.public.com , the wellness service will send a notification request to the gateway, such as S823, S833, and S839.
In order to automatically inform the application service (NA) when the application resource of the non-part standard standard terminal (d, D ') is created, the non-part standard standard terminal (d, (GA) or a standard terminal application (DA) is required for the terminal application (DA) of the terminal (D).
Therefore, in the present invention, as shown in Table 1 below, it is proposed to add a parameter for identifying the terminal app to the attribute of the <application> resource.
(The standard application terminal D and the nonstandard specification terminal d, the terminal application of the partial standard terminal D ', and the gateway application of the gateway G)
This attribute is only used in the case where the location information is provided by a network-based location server (eg a 3GPP location server). It will be provided to the location server if the content is required for the location information retrieval.
The format of this attribute shall be provided in conformity with the provided location server (eg MSISDN for a 3GPP location server).
Referring to Table 1, an attribute indicating the terminal, for example, a terminal type (orgDeviceType) is added. This attribute is an attribute that identifies the type of source terminal of the application resource. It is used to distinguish the terminal / gateway application of the standard standard terminal D, the nonstandard standard terminal d, the partial standard terminal D 'and the gateway G . The attribute for the terminal can be provided by including it as a primitive attribute in the application resource creation request in the terminal app.
FIG. 14 is a diagram for explaining a process of generating an application resource <application> for application registration of ETSI TS 690 9.3.2.82, and FIG. 15 is a diagram for explaining a procedure of generating an application resource <application> according to the present invention.
15, in order to guarantee the mobility of the non-standard standard terminal d and D ', an application service (NA) having access authority to data in the case of a non-standard standard terminal is automatically A step of transmitting a notification message may be added.
An
Local SCL is the SCL that receives the initial request from the issue. For example, the local SCL of the application service (NA) is the server platform (NSCL), the local SCL of the gateway application (GA) is the gateway platform (GSCL) The local SCL of the terminal application DS of the partial standard compliant terminal D 'can be the terminal platform DSCL of the terminal application DS of the partial standard compliant terminal D' And the local SCL of the terminal platform (DSCL) can be the gateway platform (GSCL) or the server platform (NSCL). Thus, a hosting SCL can be a gateway platform (GSCL), a server platform (NSCL), or a terminal platform (DSCL).
The hosting
If the stored application resource <application> corresponds to the terminal application DA of the non-standard standard terminal, the hosting
At this time, the hosting
16 is a diagram for explaining a procedure for collecting data from a footprint sensor in which the wellness service is a partial standard terminal.
Referring to FIG. 16, for example, in the case of a footprint sensor, since the wellness service is not known to which gateway the footprint sensor is connected to according to the movement of the footprint sensor, the wellness service does not perform the step S1621 as in step S823 shown in FIG. 10 .
15, when the issue human-
After S1627 step is done automatically,
In the past, when a non-part standard terminal was moved, it was not known which gateway / standard-compliant terminal it was connected to, so all application services (NA) using non-part standard compliant terminals would send a notification request to all public gateways Respectively.
Therefore, whenever a non-standard standard terminal is connected to a common gateway, a notification message is transmitted to all application services (NA), and all application services (NA) must be connected to the corresponding gateway.
According to the present invention, when a non-part / standard-compliant terminal is connected to a gateway / standard-compliant terminal, the terminal / app standard (DA) registration method for providing the mobility of the gateway / It is possible to effectively receive the mobility of the non-part standard standard terminal by automatically transmitting the notification message to the application service (NA) having the access right to the terminal.
The foregoing description is merely illustrative of the technical idea of the present invention, and various changes and modifications may be made by those skilled in the art without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas falling within the scope of the same shall be construed as falling within the scope of the present invention.
510: Wellness service 550: Footprint sensor 560: Weight scale
Claims (12)
Receiving an application resource creation request from an issuer in a hosting service capability layer;
Creating the application resource in the hosting service capability layer and confirming attribute information of the issue word; And
And transmitting a resource creation notification message to an application service having access right to the issue word if the issue word corresponds to the non-standard specification terminal or the partial standard specification terminal according to the attribute information. Application registration method.
Receiving a notification request message from the application service when the resource of the lower layer of the generated resource is generated in the hosting service capability layer; And
And transmitting a notification message for the lower layer resource creation to the application service when the resource is generated in the lower layer.
And transmitting data stored in the resource upon receipt of a request for the resource from the application service through a response to the notification message for lower layer resource creation.
And attribute information of the issue word is stored as attribute information of the application resource.
Wherein the attribute information of the issue word is information indicating that the issue corresponds to one of a standard specification terminal, a non-standard specification terminal, a partial standard specification terminal, and a gateway.
Wherein the step of generating a resource application resource of the lower layer checks whether the resource is authorized to create the resource, and generates the application resource when the resource has the right to create the resource.
Upon receipt of an application resource creation request from an issuer, generates the application resource, checks the attribute information of the issue language, and if the issue language corresponds to the non-standard specification terminal or the partial standard specification terminal according to the attribute information, And transmits a resource creation notification message to the application service having the access right for the M2M terminal application.
Upon receipt of a notification request message when a resource of a lower layer of the generated resource is generated from the application service, when a resource is generated in the lower layer, a notification message for generating the lower layer resource is transmitted to the application service The M2M terminal application registering device.
And transmits the data stored in the resource upon receiving a request for the resource from the application service through a response to the notification message for lower layer resource generation.
And attribute information of the issue word is stored as attribute information of the application resource.
Wherein the attribute information of the issue word is information indicating that the issue corresponds to one of a standard specification terminal, a non-standard specification terminal, a partial standard specification terminal and a gateway.
When the resource application resource of the lower layer is created, whether or not the resource of the issue resource is authorized to be created, and generates the application resource when the resource resource has the resource creation right.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR1020120124486 | 2012-11-05 | ||
| KR20120124486 | 2012-11-05 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| KR20140058307A true KR20140058307A (en) | 2014-05-14 |
| KR102045905B1 KR102045905B1 (en) | 2019-11-18 |
Family
ID=50888733
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| KR1020130028500A KR102045905B1 (en) | 2012-11-05 | 2013-03-18 | A Method for Registering Device Application for Providing Device Mobility and An Apparatus therefor |
Country Status (1)
| Country | Link |
|---|---|
| KR (1) | KR102045905B1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20150136210A (en) * | 2014-05-26 | 2015-12-07 | 전자부품연구원 | IoT Device Replacement Method |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012118711A2 (en) * | 2011-03-03 | 2012-09-07 | Interdigital Patent Holdings, Inc. | Method and apparatus for accessing services affiliated with a discovered service provider |
| US20120265983A1 (en) * | 2011-04-15 | 2012-10-18 | Samsung Electronics Co. Ltd. | Method and apparatus for providing machine-to-machine service |
| KR20120124345A (en) * | 2011-05-03 | 2012-11-13 | 주식회사 케이티 | A Method and Apparatus of managing connection between M2M communication entities based on connection state confirmation event |
| KR20120125091A (en) * | 2011-05-06 | 2012-11-14 | 주식회사 케이티 | Device, Gateway, Data Transferring Method of Device and Gateway, and Network Application Server |
-
2013
- 2013-03-18 KR KR1020130028500A patent/KR102045905B1/en active IP Right Grant
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012118711A2 (en) * | 2011-03-03 | 2012-09-07 | Interdigital Patent Holdings, Inc. | Method and apparatus for accessing services affiliated with a discovered service provider |
| US20120265983A1 (en) * | 2011-04-15 | 2012-10-18 | Samsung Electronics Co. Ltd. | Method and apparatus for providing machine-to-machine service |
| KR20120124345A (en) * | 2011-05-03 | 2012-11-13 | 주식회사 케이티 | A Method and Apparatus of managing connection between M2M communication entities based on connection state confirmation event |
| KR20120125091A (en) * | 2011-05-06 | 2012-11-14 | 주식회사 케이티 | Device, Gateway, Data Transferring Method of Device and Gateway, and Network Application Server |
Non-Patent Citations (1)
| Title |
|---|
| ETSI TS 102 690 V1.1.1 (2011.10.25.) * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20150136210A (en) * | 2014-05-26 | 2015-12-07 | 전자부품연구원 | IoT Device Replacement Method |
Also Published As
| Publication number | Publication date |
|---|---|
| KR102045905B1 (en) | 2019-11-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Petrolo et al. | Towards a smart city based on cloud of things, a survey on the smart city vision and paradigms | |
| JP6629392B2 (en) | Device trigger | |
| US10492048B2 (en) | Service layer resource propagation across domains | |
| KR101973298B1 (en) | Publication and discovery of m2m-iot services | |
| CN107211232B (en) | Interworking of lightweight machine-to-machine protocols and device management protocols | |
| CN102882990B (en) | A kind of wireless sensor network identification analytic method | |
| CN101374249B (en) | Method for obtaining terminal real time accurate geographic position based on the mobile terminal IP address | |
| JP2017152040A (en) | Semantic naming model | |
| KR20210027527A (en) | Service layer resource management for generic interworking and extensibility | |
| CN102427451A (en) | Method and system for acquiring service application | |
| EP3469782A1 (en) | System and methods for service layer cache management | |
| CN103703474A (en) | Handling device generated data | |
| Wang et al. | Scalable identifier system for industrial internet based on multi-identifier network architecture | |
| KR20130126444A (en) | A method for forming container resource discriminated with user awareness information and recording medium and apparatus thereof | |
| CN106789965A (en) | A kind of Internet of Things data exchange method and system | |
| CN103533094B (en) | Coding all-in-one and coding system | |
| CN104854930B (en) | Method, control node, gateway and the computer program that device for allowing with newly detecting is communicated | |
| KR102045905B1 (en) | A Method for Registering Device Application for Providing Device Mobility and An Apparatus therefor | |
| WO2015149530A1 (en) | M2m application service method, device and system | |
| KR20170025550A (en) | Gateway and control method thereof | |
| KR102165820B1 (en) | METHOD for controlling REsource access over the web network of things | |
| KR101963907B1 (en) | GW-based ID Management Method in Open M2M System | |
| Vercher et al. | An Experimental Platform for large-scale research facing FI-IoT scenarios | |
| KR20150074428A (en) | M2M application service system | |
| KR20140103532A (en) | A method for transmitting data of M2M system and apparatus therefor |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| E902 | Notification of reason for refusal | ||
| E701 | Decision to grant or registration of patent right | ||
| GRNT | Written decision to grant |