KR20110117030A - Device management method and system for providing device-to-device services and device thereof - Google Patents

Abstract

The present invention relates to a method and system for managing a device for providing a device to device (M2M) service, and a device thereof, and to a method for managing a device for providing a device to device (M2M) service according to the present invention. Transmitting a device registration request message requesting the device to register the device after the device providing the M2M service is connected to the wired / wireless network, and receiving the device registration request message. A service server performing authentication on the device, analyzing the information on the device, and setting the M2M service providing information, which is information necessary to provide the M2M service to the device, if the device is a first registered device; The device included in the device registration request message by the service server. Storing device profile information including device registration information and M2M service provision information in a user / device repository, generating reference information for the user / device repository to refer to the device profile information; And obtaining, by the service server, the reference information from the user / device repository.

Description

DEVICE MANAGEMENT METHOD AND SYSTEM FOR SERVING A MACHINE TO MACHINE SERVECE AND APPARATUS THEREOF

The present invention relates to a method and a system for managing a device for providing a device to device (MCHINE TO MACHINE: M2M) service and an apparatus thereof.

With the development of current technology, users' desire for machine-to-machine services (M2M) is increasing. M2M means communication between the electronic device and the electronic device. In a broad sense, it means wired or wireless communication between electronic devices or communication between a device controlled by a person and a machine. However, in recent years, a general term refers to wireless communication between electronic devices and electronic devices, that is, between devices. In other words, M2M is a remote management and control solution that supports communication for data transmission between a device and a server using wired or wireless communication. M2M is implemented as a module for connection with a device that does not include a communication function. do.

Various types of devices may be connected to the M2M module, and various applications may be driven according to the type of devices to be connected.

Therefore, a procedure for registering and managing a device with a service server is needed to provide an M2M service.

The present invention provides a method and system for managing a device for supporting a device to device (MCHINE TO MACHINE: M2M) service and the device.

The present invention provides a method, system and apparatus for providing an application suitable for a device for providing an M2M service.

Method for managing a device that provides a machine to machine (M2M) service according to the present invention, after the device providing the M2M service to the user is completed the connection setting with the wired / wireless network, Transmitting a device registration request message requesting device registration; and a service server receiving the device registration request message performs authentication on the device, and analyzes information on the device to register the device for the first time. If it is a device, the process of setting the M2M service providing information that is information necessary to provide the M2M service to the device, the service server includes the device registration information and the M2M service providing information included in the device registration request message Device Device Information Storing in a repository, generating reference information for the user / device repository to refer to the device profile information, and the service server performing the reference information from the user / device repository. It includes a process of obtaining.

Method for managing a device that provides a machine to machine (M2M) service according to the present invention, after the device providing the device to the device service to the user is completed connection setting with the wired / wireless network Transmitting an application registration request message requesting to register an application to be provided by the device; and a service server receiving the application registration request message authenticates the device and executes the registration requested application. Determining whether capability information of the device is required to perform the step; if the capability information is required, obtaining, by the service server, capability information of the device; and The device using the obtained capability information Determining whether the registration requested application is subdivided according to the characteristics of the M2M service or the characteristics of the M2M service; and if the registration requested application is subdivided, the service server may perform the sub-applications. Obtaining a sub-application identifier corresponding to at least one sub-application corresponding to a characteristic of a device or a characteristic of the service; and transmitting the obtained sub-application identifier to the device.

The system for managing a device providing a device to device service (M2M) according to the present invention, after providing the M2M service to a user and establishing a connection with a wired / wireless network is completed, device registration. If the device is the first device that receives a device for transmitting a request message, the device registration request message, authenticates the device, and analyzes information about the device, the device provides the M2M service to the device. Setting M2M service providing information which is information necessary to provide, storing device registration information included in the device registration request message and device profile information including the M2M service providing information in a user / device repository, and storing the user The device from the device / device repository With reference to reference the file information is information including the service server to obtain the (reference information).

The system for managing a device for supporting a machine to machine (M2M) service according to the present invention provides a device to device service to a user, and after setting up a connection with a wired / wireless network is completed. A device for transmitting an application registration request message requesting to register an application to be provided to the user, and when the application registration request message is received, authenticate the device and execute the application for which the registration is requested. It is determined whether the capability information of the device is necessary, and if the capability information is needed, the capability information of the device is obtained, and the acquired capability information is used to obtain the capability information of the device. The registration requested application according to a property or a property of the M2M service It is determined whether the application is subdivided, and if the application requested to be registered is subdivided, corresponding to at least one sub-application corresponding to the characteristic of the device or the characteristic of the M2M service among the sub-applications corresponding to the application. And a service server for obtaining an identifier and transmitting the identifier to the device.

An apparatus for managing a device that provides a Machine to Machine (M2M) service according to the present invention includes a receiving unit that receives a device registration request message from a device that provides the M2M service to a user, and the received device M2M, which is information required to provide the M2M service to the device, if the device is the first registered device by performing authentication on the device using the information included in the registration request message and analyzing the information on the device. Set service providing information, transmit device registration information included in the device registration request message and device profile information including the M2M service providing information to a user / device repository, and transmit the device from the user / device repository. profile Obtaining reference information (reference information) to reference the information to a control unit for storing in the storage unit.

An apparatus for managing a device for supporting a Machine to Machine (M2M) service according to the present invention requests a user to register an application to be provided to the user from a device that provides the device to device service. A device that transmits an application registration request message, and when the application registration request message is received, authentication of the device is performed, and whether capability information of the device is required to execute the registration requested application; Determine whether or not the capability information is required, obtain the capability information of the device, and use the acquired capability information to request the registration according to the characteristic of the device or the characteristic of the M2M service. Application is segmented If the registration request application is subdivided, the identifier corresponding to the at least one sub-application corresponding to the characteristic of the device or the characteristic of the service among the sub-applications corresponding to the application is obtained and sent to the device. And a control unit for controlling the transmitter to transmit.

According to the present invention, by collecting the services of application service providers for providing the M2M service, it is possible to manage the devices for providing the M2M service.

1 is a diagram illustrating an architecture of a system for supporting M2M service according to an embodiment of the present invention;
2 is a view for explaining the operation of the service sharing engine according to an embodiment of the present invention;
3 is a signal flow diagram illustrating a process of registering a device with a service server according to a first embodiment of the present invention;
4 is a signal flow diagram illustrating a process of registering an application to be provided in a device with a service server according to a second embodiment of the present invention;
5 is a block diagram of a service sharing engine 500 according to an embodiment of the present invention;
6 is an operation flowchart of a service sharing engine unit 304a according to the first embodiment of the present invention;
7 is an operation flowchart of the service sharing engine unit 404a according to the second embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be noted that the same components in the figures represent the same numerals wherever possible.

In addition, specific details are set forth in the following description, which is provided to help a more general understanding of the present invention, and it is obvious to those skilled in the art that the present invention may be practiced without these specific details. Will do. In the following description of the present invention, detailed descriptions of related well-known functions or configurations will be omitted when it is determined that the detailed descriptions may unnecessarily obscure the subject matter of the present invention.

1 is a diagram illustrating an architecture of a system for supporting an M2M service according to an embodiment of the present invention.

The present invention proposes a functional entity called a service sharing engine unit 100 as shown in FIG. 1. This supports the service interworking between the applications 102 when two or more different applications 102 interoperate with the service server 110, thereby providing a service sharing engine unit 100. Supports the composition of new services through the service and automatically configures and deploys services that can be differentiated and provide services to devices by themselves, rather than services provided by third party service providers. Do it.

Next, a detailed description of a service sharing engine unit proposed by the present invention will be given with reference to FIG. 2.

2 is a view for explaining the operation of the service sharing engine 200 according to an embodiment of the present invention.

In FIG. 2, the service sharing engine unit 200 supports service interworking between the applications 202 when two or more different applications 202 interoperate with a server, thereby sharing the service. It supports the configuration of new services through the engine unit 200, and automatically configures services that can be differentially provided by configuring the devices themselves, rather than services provided by third party service providers, and deflation. It supports the ability to deploy. The service sharing engine unit 200 acquires information required for configuration of a new service and configuration of the information from internal or external repositories 204, 206, 208, and 210 through interworking between these services. To perform the operation.

The service server 212 may be implemented as the same physical entity as the service sharing engine unit 200 or may be implemented as a separate physical entity. A collection of functional entities. The service server 212 registers and authenticates an application level, device information registration, location information registration, etc. required for using a service after the device 120 registers with the mobile communication network or the wired communication network 130. In other words, it is a collection of functions that have the necessary functions before connecting to a real application server and providing services.

The Device Capability Repository 204 maintains and manages hardware characteristics of the device, firmware / software characteristics, and manufacturer information of the device.

The User Profile Repository 206 may selectively be provided to a user's application service subscription information, a charging policy at the time of subscription, other general policies except the charging policy, and the user. Maintains and manages application condition information for a specific application.

The service profile repository 208 is a device and user subscription condition necessary for application and application of information on an application service currently registered in the service server 212. Maintains information about and manages summary information about currently available application services.

The Contents Profile Repository 210 manages a summary of the data requested for registration from the user in a short-term / mid-term / long-term, and is not shown. It supports easy retrieval of user contents and contents from an application stored in a content storage.

Although not shown, the device according to the present invention may display its own characteristic information (processing speed of the central processing unit (CPU), whether input / output means are provided, and display) during registration with the service server 212. Device registration information such as information on the presence / absence) and its own device type information is stored in the device capability repository 204 through the service server 212. In addition to the information on the device during the registration process, information on the application available on the device and information on the user who uses the application is displayed on the service server (Service Server) 212, and related information is registered in a User Profile Repository 206. In this case, depending on the type of application, a user may be defined as one or two or more groups.

Example 1

In the first embodiment of the present invention, the device 300 is registered in the service server 304, and the device 300 is authenticated and the device 300 is authenticated. Identifier (Device Id). Device type information, product serial information, hardware specification information, and module related information in the device may be connected to the service server 304 and the service server 304 / Define a process of storing in the device repository (306). In FIG. 3, the user / device repository 306 stores information related to users and devices needed to provide M2M services to users.

3 is a signal flow diagram illustrating a process of registering a device 300 with a service server 304 according to a first embodiment of the present invention.

In order to interface with the service server 304, the device 300 may primarily provide a DSL (Digital Subscriber Line) and an IP (Internet Protocol) network connection. An asynchronous mobile communication network such as Mobile Communications (GSM) / Wideband Code Division Multiple Access (WCDMA) / Long Term Evolution (LTE) and a wireless carrier network 302 such as Code Divisional Multiple Access (CDMA) or WiMAX should be connected. To this end, the device 300 establishes a connection with an access network and a core network in step 310. In FIG. 3, the device 300 may be a digital still camera (DSC). In addition, the device 300 may be a digital photo frame (DPF).

When the connection setup with the wired / wireless network is completed in step 310, the device 300 sends a device registration request message including device registration information to register itself with the service server 304. Forward to 304. The device registration information includes device identifier information (eg, virtually assigned) device id. and / or serial number, etc.) and device type (e.g., whether it is a smart meter device, a home appliance device, an entertainment CE device, a health and well-being device, etc.) Class information or type information appropriate to the service purpose, detailed hardware information of the device (e.g. screen size, supported codec, supported access technology) technology), supported media types, etc.) and information about a user or group (eg, user id, and / or group id). Here, the group identifier (ID) is used when it is necessary to classify several users into their respective groups.

In step 312, the service server 304 receiving the device registration request message including the device registration information from the device 300 performs a procedure for authenticating the device 300. In this case, the service server 304 may include an authentication server such as an AAA (Authentication, Authorization & Accounting) server by itself, and simply serves as an authentication server that relays an authentication procedure between the device 300 and the AAA server. You may also be in charge. Through such a device authentication process, the device 300 generates security key information required for the performance of a service and an application in the future. The mechanism used in this process can be based on AKA (Authentication and Key Agreement) based schemes used in asynchronous systems such as GSM / WCDMA / LTE, or AAA based schemes used in synchronous systems such as CDMA / 1X DO, or IP. Certificate methods in use in the underlying network, or IPSec / IKE (IPSecurity / Internet Key Exchage) can be used for these systems.

When the authentication and security key assignment for the device 300 is completed, the service server 304 may service the device registration information included in the device registration request message received from the device 300 in step 316. It passes to the part 304a. When the device registration request message is received in step 316, the service sharing engine unit 304a analyzes information on the corresponding device 300 based on the device ID included in the device registration information in step 318. . In this case, the service sharing engine unit 304a is a device that the device 300 accesses the service sharing engine unit 304a for the first time, and a service policy and a charging policy for the device. information about whether a charging policy is allocated and whether there is firmware and software information to be added to the device 300. The information analyzing operation of the device 300 in step 318 may be handled by the service sharing engine unit 304a by itself, or may be performed by interworking with an external functional entity or repository 306. have.

When the device 300 connects to the service sharing engine unit 304a for the first time, in step 320, the service sharing engine unit 304a registers the registration information related to registering the device 300 and a charging policy to be applied to the device 300. (service policy) corresponding to a device determined according to a charging policy, a type of the device 300, and a hardware characteristic of the device, and accessibility information about the device 300. M2M service provision information is set. The M2M service provision information setting in step 320 may be performed in the service sharing engine unit 304a itself, and may be linked with other functional entities (not shown) in the service server 304. It can also be done through.

Here, the reachability information may be determined whether the time when the device 300 receives a service is determined by the user's selection or whether there is data received by the device wake-up at a predetermined cycle. Information instructing to check.

After setting the M2M service providing information in step 320, in step 322, the service sharing engine unit 304a uses the device registration information and the M2M service providing information. Information about the device 308 is searched for and set as an application suitable for the corresponding device.

In operation 324, the service sharing engine unit 304a generates the device registration information and the M2M service providing information as device profile information, and generates the generated device profile information as a user / device repository 306. To save). That is, when the device 300 first accesses the service server 304, the service sharing engine unit 304a may use the device registration information and the M2M service providing information obtained by the device 300 during the first registration process. Since the device profile information is generated and stored in the user / device repository 306, even if the device 300 reconnects later, the device profile information stored in the user / device repository 306 may be referred to so that unnecessary registration procedure may be omitted. It becomes possible.

The user / device repository 306 that has received the device profile information in step 324 stores the device profile information in step 326 and generates reference information such as an index of the device profile information. do. The reference information is information for referring to device profile information corresponding to the device 300 among the device profile information stored in the user / device repository 306 by the service sharing engine unit 304a. The user / device repository 306 transmits the generated reference information to the service sharing engine unit 304a.

In operation 330, the service sharing engine unit 304a stores the reference information received from the device / user repository 306.

After the service sharing engine unit 304a stores the reference information in step 330, information about an application that can be serviced by the device 300 found in step 322, and a required application for registration are required. In step 332 to step 334, the service server 304 generates a registration response message including information about an application list and information on security credential to be used for signaling from the device 300. Transfer to the device 300 through.

[Example 2]

Hereinafter, a second embodiment of the present invention will be described with reference to FIG. 4. 4 is a signal flow diagram illustrating a process in which the device 400 registers an application with the service server 404 according to the second embodiment of the present invention. In the second embodiment of the present invention described below with reference to FIG. 4, the service sharing engine unit 404a registers an application for the device 400, and the registered application is subdivided according to the device 400. A process of conveying the identifier of the application to the device 400 will be described.

In addition, the second embodiment of the present invention may be performed after the device is registered with the service server according to the first embodiment.

In order to interwork with the service server 404, the device 400 first performs a wired carrier network or asynchronous mobile communication network such as GSM / WCDMA / LTE and CDMA that provide DSL and IP network connections. Wireless network, such as WiMAX. To this end, the device 400 establishes an access network connection and a core network connection in step 410.

The device 400 may include service policy information, billing policy information, and hardware capability information of the device 400 based on subscription information of a device and a user through the first embodiment of the present invention. On the basis of the service information and the application (application) and the device 400 to obtain the application information, such as essential to obtain. Based on the obtained information, the device 400 requests an application registration of the device 400 to the service server 404 to perform a process of registering an application to be provided to the user in step 412. The device application registration requeset message is delivered.

The device application registration request message includes identifier (id) information of the device 400, application identifier information, application technology information, and protocol information, which are application information of the device 400 to be registered. information) and credential information for signaling (ie, control plane) received by the device 400 in the first embodiment of the present invention are also included and transmitted to the service server 404.

The service server 404 that receives the device application registration request message from the device 400 in step 412 registers the device application by using the security credential information included in the device application registration request in step 414. Perform an authentication procedure on whether the request is from a normal device and user.

When authentication of the device application registration request message received from the device 400 is normally completed in step 414, the service server 404 transmits the device application registration request message to the service sharing engine unit 404a in step 416. In this case, the device application registration request message includes the device ID information, the device application ID information, and the application and service repository 408 in which the application is stored so that the device can receive the application. Access technology information, which is information about an access technology used to access an application protocol, and application protocol information supported by the device 400 when the device 400 uses one or more application protocols. information). In this case, one or more connection technologies may be specified as the connection technology used.

Here, the access technology is an access technology for the device 400 to access the service server 404 and is used for the purpose of informing that the device 400 wants to be serviced through any access technology when accessing the service server 404. As such a connection technology, a connection technology such as WIFI (Wireless Fidelity) / wcdma, wifi / cdma, wifi / wimax, wimax / wcdma, wifi / wcdma / wimax may be used.

When the registration request message for the device application is received in step 416, the service sharing engine unit 404a determines whether capability information of the device is required to execute the application for which the registration is requested in step 418. To judge.

When the service sharing engine unit 404a combines two or more applications to configure a new application, the service sharing engine unit 404a should transmit information about the newly configured application to the device 400. In this way, when the service sharing engine unit 404a configures a new application, the service sharing engine unit 404a must check whether the device 400 has the appropriate capability to perform the newly configured application. do.

Therefore, the service sharing engine unit 404a according to the second embodiment of the present invention checks the capability information of the device 400 to check whether the capability of the device 400 for executing the newly configured application is appropriate. There is a need to check. As a result of the determination in step 418, when the device capability information needs to be checked in order for the device 400 to perform the device application requested to be registered, the service sharing engine unit 404a in step 420. Is a device for obtaining capability information of the device 400 from a user / device repository 406 using the device identifier information included in the device application registration request message received in step 416. Deliver user information request message to user / device repository 406.

In operation 422, the user / device repository 406 transmits a device / user information response message including the capability information of the device 400 to the service sharing engine unit 404a. The device capability information includes screen size information of a device, resolution information, codec information, and detailed information necessary for processing media in an application.

In step 422, the service sharing engine unit 404a that obtains device capability information from the user / device repository 406 may use an access technology that the device will use for the requested device application in step 424. After obtaining the technology information and the application protocol (application protocol) information to be used for the execution of the application (application), based on the registration information of the application requested from the device 400, the characteristics of the device 400 or service characteristics Therefore, check whether the application is granular.

The reason why the application protocol information to be used for the execution of the application is necessary. When there may be various connection technologies that can be supported by the device 400, among these various connection technologies, it is necessary to know the connection technology required for the execution of a specific application. Because there is a need. For example, when the device 400 can support two types of connection technologies such as WIFI and 3G, but it is necessary to use WIFI among two connection technologies to deliver high capacity medical image data of 500MB or more, The service sharing engine unit 404a should confirm the information on the established connection technology.

If the application is subdivided in step 424, the service sharing engine unit 404a determines device capability information and access technology information, which are characteristic information of the device 400, in step 426 to obtain the detailed application information. The application information request message including the application protocol information and the application identifier is transmitted to the application / service repository 408. In the present specification, for example, when an application is a video program for playing a video, and there are many sub-applications according to the resolution of the device 400, the application is defined as being subdivided.

In step 426, the application / service repository 408 that has received the application information request message receives the application identifier based on the device identifier and detailed information about the device capability in step 428. Application information corresponding to the information is divided into subdivisions according to the characteristics of the device 400 and additional information related to application execution is transmitted to the service sharing engine unit 404a through an application information response message.

That is, in FIG. 4, if the application requested to be registered by the device 400 is subdivided, the service sharing engine unit 404a indicates at least one sub-application corresponding to the characteristic of the device 400 or the characteristic of the M2M service. Sub-application ID information is obtained from the application and service repository 408 and transmitted to the device 400.

The reason why the application information registration response message is transmitted to the service sharing engine unit 404a in step 428 is that the new application 3 is configured by combining the application 1 and the application 2 in the service sharing engine unit 404a. This is because the service sharing unit 404a needs to know the device requirements, the policy information for the application (for example, the minimum credit requirements for the application execution, etc.), which are information necessary for the execution thereof.

In step 428, the service sharing engine unit 404a receiving the application information response message includes a device including user identifier information, device identifier information, sub-application information, protocol information, device capability information, and connection technology information. Request the user / device repository 406 to save the application information.

In step 430, when the device 400 requests execution of the device application requested to be registered in step 412, the service sharing engine unit 404a may request additional sub-application identifier information for the device application that is requested to be registered and the application of the application. The information necessary for execution is stored in the user / terminal repository 406 to avoid repetitive acquisition of the information. The step 430 is performed because, for example, when the service sharing engine unit 404a configures a new application 3 serviceable to the device through the application 1 and the application 2, information necessary for the execution of the application 3 should be stored. to be.

That is, by storing the device application information in the user / device repository 406 in advance, even if an application registration request is received from the device 400 in the future, it is necessary to request information about the requested application from the application and the service repository 408. There will be no.

If the device application information is normally stored in the user / device repository 406 in step 430, the user / device repository 406 returns an acknowledgment (ACK) message for successful storage to the service sharing engine 404a in step 432. do.

In step 432, the service sharing engine 404a that has received the response message, user ID information, device ID information, and connection, which the device 400 intends to use to perform an application, in step 434. Information such as sub-application identifiers, which are subdivided according to conditions such as access technology information, protocol information, and the like, are stored in a related functional entity in the service server 404 (not shown).

For example, if the address pool is different according to access technologies such as WIFI and WCDMA, information about the address pool should be delivered to the entity managing the address, and the specific application ( application) is divided into WIFI / CDMA / WCDMA, and sub-identity is assigned to each sub-application, and information about this is a functional entity that manages accessibility to the application. (functional entity), etc. The service sharing engine unit 404a is in charge of delivering each detailed information to a required functional entity, but a function definition part thereof is irrelevant to the present invention and thus will be omitted.

In operation 436, the service server 404 notifies the device 400 of the device application registration response message that the registration operation of the device application has been completed successfully, and is characterized by the characteristics of the application divided by the characteristics of the device 400. In accordance with the present invention, the newly allocated sub-application identity information is transmitted to the device 400. That is, the service sharing engine unit 404a notifies the device 400 of the identifier of the sub-application so as to inform only the applications applicable to the device having the reference number 400 among the applications applicable to the DSC in step 436. Is given.

5 is a block diagram of the service sharing engine 500 according to an exemplary embodiment of the present invention.

Receiving unit 502 is a message from other functional entities and user / device repository 306, 406 and application and service repository 408, not shown, of service server 304, 404 communicating with devices 300, 400. Receive Transmitter 504 sends messages to other functional entities and user / device repositories 306, 406 and application and service repository 408 of service servers 304, 404 that communicate with devices 300, 400. Send.

The service interworking unit 510 interoperates at least two or more applications connected to the service servers 304 and 404 to generate a new application service, and transmits the information about the linked application service to the control unit 506.

According to a first embodiment of the present invention, the controller 506 performs authentication on the device 300 by using information included in the device registration request message received through the receiver 502, and performs the device authentication. If the device is the first registered device by analyzing the information on the 300, set the M2M service providing information which is information necessary to provide the M2M service to the device 300, the device included in the device registration request message The device profile information including registration information and the M2M service provision information is transmitted to the user / device repository 306 through the transmitter 504, and the device profile information is referenced from the user / device repository 306. Reference information for obtaining the reference information is stored and stored in the storage unit 508.

On the other hand, when the controller 506 according to the second embodiment of the present invention receives an application registration request message through the receiver 502, the controller 506 authenticates the device 400 and executes the registration requested application. In order to determine whether the capability information of the device is required in order to obtain the capability information, and if the capability information is needed, the capability information of the device is obtained, and the acquired capability information is used to obtain the capability information. It is determined whether the registration requested application is subdivided according to the characteristics of the device or the characteristics of the M2M service, and if the registration requested application is subdivided, the characteristics of the device among the sub-applications corresponding to the application or the At least one sub-application corresponding to the characteristics of the service The transmitter 504 is controlled to obtain a corresponding identifier and transmit the same to the device 400. In this case, the controller 506 stores the device application information obtained from the application and service repository 408 in the storage unit 508.

6 is a flowchart illustrating an operation of the service sharing engine unit 304a according to the first embodiment of the present invention.

In step 600, the service sharing engine unit 304a receives the registration request message, and in step 602, if the device is the first registered device by analyzing information about the device, in step 604, the service sharing engine unit 304a provides the M2M service to the device. Sets M2M service provision information, which is necessary information.

In operation 606, the service sharing engine unit 304a checks information of an application that can be serviced by the device according to the device registration information and the M2M service provision information. In operation 608, the service sharing engine unit 304a registers the device included in the device registration request message. The device profile information including the information and the M2M service provision information is stored in the user / device repository 306.

In operation 610, the service sharing engine unit 304a obtains and stores reference information from the user / device repository 306, and then transfers the serviceable application information found in operation 606 to the device in operation 612. .

7 is a flowchart illustrating an operation of the service sharing engine unit 404a according to the second embodiment of the present invention.

When the service sharing engine unit 404a receives the device application registration request message in operation 700, the service sharing engine unit 404a determines whether capability information of the device 400 is required to perform the application for which registration is requested in operation 702. If the capability information is needed, the capability information of the device is obtained from the user / device repository 406 in step 704.

The service sharing engine unit 404a acquiring the capability information may use the acquired capability information in step 706 in accordance with the characteristics of the device 400 or the characteristics of the M2M service. If it is determined whether or not the granularity is determined, and the application requested to be registered is subdivided, in step 708, among the sub-applications corresponding to the application, it corresponds to at least one sub-application corresponding to the characteristic of the device or the characteristic of the M2M service. Acquire a sub application identifier.

In operation 710, the service sharing engine unit 404a transmits the obtained sub-application identifier to the device 400.

Claims (28)

In the method for managing a device that provides a machine to machine (M2M) service,
Transmitting, by the device providing the M2M service, a device registration request message requesting the device to be registered after connection establishment with the wired / wireless network is completed;
The service server receiving the device registration request message authenticates the device, analyzes the information on the device, and if the device is the first registered device, M2M, which is information required to provide the M2M service to the device. Setting up service delivery information;
Storing, by the service server, device profile information included in the device registration request message and device profile information including the M2M service providing information in a user / device repository;
Generating reference information for the user / device repository to refer to the device profile information;
And obtaining, by the service server, the reference information from the user / device repository.
The method according to claim 1,
Checking, by the service server, information of an application that can be serviced by the device according to the device registration information and the M2M service providing information;
The service server may further include providing, to the device, information of an application that can be serviced by the searched device to the device.
The method according to claim 1,
The device registration information,
Device to device services, characterized in that it comprises at least one of a device identifier (Device Id), a device type (Device type), device capability (Device capability), a user identifier (User Id), a group identifier (Group Id) Device management method that provides.
The method according to claim 1,
The M2M service providing information,
And at least one of registration information of the device, service policy information corresponding to the device, charging policy information corresponding to the device, and accessibility information of the device. Device management method for providing device-to-device services, characterized in that.
The method according to claim 1,
The reference information,
And index information referring to the device profile information stored in the user / device repository.
The method of claim 4, wherein
The accessibility information,
And information indicating whether a time at which the device is to be provided with the service is determined by the user's selection or whether the device wakes up at predetermined intervals and whether there is data received. A device management method for providing a device to device service.
In the method for managing a device that provides a machine to machine (M2M) service,
Transmitting, by the device providing the device to device service, an application registration request message requesting the user to register an application to be provided by the device after the connection setting with the wired / wireless network is completed;
Determining, by the service server receiving the application registration request message, whether or not capability information of the device is required to execute authentication of the device and to execute the application for which registration is requested;
Obtaining the capability information of the device by the service server, if the capability information is needed;
Determining, by the service server, whether the requested application is subdivided according to the characteristics of the device or the characteristics of the M2M service using the obtained capability information;
If the application requested for registration is subdivided, the service server obtaining a sub-application identifier corresponding to at least one sub-application corresponding to a characteristic of the device or a characteristic of the service among sub-applications corresponding to the application; and,
And transmitting the obtained sub-application identifier to the device.
The method of claim 7, wherein
The application registration request message may include connection technology information that the device will use for the application for which the device has requested the registration, application protocol information necessary for executing the application, a device identifier for identifying the device, an identifier of the application for which the device has requested the registration, and a security certificate. Device management method for providing device-to-device services, characterized in that it comprises at least one of (Security Crudential).
The method of claim 7, wherein
Acquiring at least one application suitable for the characteristics of the device or the characteristics of the service,
Transmitting, by the service server, an application information request message requesting information on the appropriate applications to an application and a service repository;
And receiving, from the application and service repository, information on sub-applications, which are subdivided according to the characteristics of the device retrieved by using the information included in the application information request message. Device management method that provides services.
In the system for managing a device that provides a machine to machine service (M2M),
A device for providing the M2M service to a user and transmitting a device registration request message after the connection setting with the wired / wireless network is completed;
Receiving the device registration request message, performing authentication on the device, and analyzing the information on the device, if the device is the first registered device, providing the M2M service which is information required to provide the M2M service to the device Set information, store device registration information included in the device registration request message and device profile information including the M2M service provision information in a user / device repository, and store the device profile information from the user / device repository. Device management system for providing device-to-device services, characterized in that it comprises a service server to obtain reference information (reference information) for referencing.
The method of claim 10,
The service server checks the information of the application that can be serviced in the device according to the device registration information and the M2M service providing information, and the service server provides the device with information of the service that can be serviced in the searched device to the device. Device management system for providing device to device services.
The method of claim 10,
The device registration information,
Device to device services, characterized in that it comprises at least one of a device identifier (Device Id), a device type (Device type), device capability (Device capability), a user identifier (User Id), a group identifier (Group Id) Device management system to provide.
The method of claim 10,
The M2M service providing information,
And at least one of registration information of the device, service policy information corresponding to the device, charging policy information corresponding to the device, and accessibility information of the device. A device management system for providing device-to-device services.
The method of claim 10,
The reference information,
And device index information referring to the device profile information stored in the user / device repository.
The method of claim 13,
The accessibility information,
Information indicating whether a time at which the device is to be provided with the service is determined by the user's selection or whether the device wakes up at a predetermined cycle to check whether there is data received from the device. A device management system for providing device-to-device services.
In a system for managing a device to support a machine to machine (M2M) service,
A device for providing the device-to-device service to a user and transmitting an application registration request message for requesting to register an application to be provided to the user after the connection setting with the wired / wireless network is completed;
When the application registration request message is received, authentication of the device is performed, it is determined whether capability information of the device is required to execute the registration requested application, and the capability information is If necessary, obtain the capability information of the device, and determine whether the registration request application is subdivided according to the characteristics of the device or the characteristics of the M2M service using the obtained capability information, If the application for which registration is requested is subdivided, a service for acquiring an identifier corresponding to at least one sub-application corresponding to the characteristic of the device or the characteristic of the M2M service among the sub-applications corresponding to the application and transmitting it to the device. server Device management system for providing a device-to-device service comprising a.
The method of claim 16,
The application registration request message may include connection technology information that the device will use for the application for which the device has requested the registration, application protocol information necessary for executing the application, a device identifier for identifying the device, an identifier of the application for which the device has requested the registration, and a security certificate. Device management system for supporting device-to-device services, characterized in that it comprises at least one of (Security Crudential).
The method of claim 16,
The service server transmits an application information request message requesting information about the appropriate applications to an application and service repository, and uses information included in the application information request message from the application and service repository. And receiving information on a sub-application configured to be divided according to the characteristics of the searched device.
In the device for managing a device that provides a machine to machine (M2M) service,
A receiving unit which receives a device registration request message from a device providing the M2M service to a user;
Using the information included in the received device registration request message, perform authentication for the device, and analyze the information on the device to provide the M2M service to the device if the device is the first registered device. Set M2M service providing information, which is necessary information, and transmit device registration information included in the device registration request message and device profile information including the M2M service providing information to a user / device repository, and the user / device And a control unit which obtains reference information for referencing the device profile information from a repository and stores the reference information in a storage unit.
The method of claim 19,
The controller checks information of an application that can be serviced by the device according to the device registration information and the M2M service providing information, and the service server provides information of an application that can be serviced by the searched device to the device. Device management apparatus for providing device-to-device services.
The method of claim 19,
The device registration information,
Device to device services, characterized in that it comprises at least one of a device identifier (Device Id), a device type (Device type), device capability (Device capability), a user identifier (User Id), a group identifier (Group Id) Device management apparatus for providing.
The method of claim 19,
The M2M service providing information,
And at least one of registration information of the device, service policy information corresponding to the device, charging policy information corresponding to the device, and accessibility information of the device. Device management apparatus for providing a device-to-device service, characterized in that.
The method of claim 19,
The reference information,
And device index information referring to the device profile information stored in the user / device repository.
The method of claim 22,
The accessibility information is
And information indicating whether a time at which the device is to be provided with the service is determined by the user's selection or whether the device wakes up at predetermined intervals and whether there is data received. Device management apparatus for providing a device-to-device service.
The method of claim 19,
And a service interworking unit for interworking at least two or more application services for providing the device-to-device service.
In the device for managing a device to support a machine to machine (M2M) service,
A device for transmitting an application registration request message requesting a user to register an application to be provided to the user from a device providing the device to device service;
When the application registration request message is received, authentication of the device is performed, it is determined whether capability information of the device is required to execute the registration requested application, and the capability information is If necessary, obtain the capability information of the device, and determine whether the registration request application is subdivided according to the characteristics of the device or the characteristics of the M2M service using the obtained capability information, If the application for which registration is requested is subdivided, the transmitter is configured to acquire an identifier corresponding to at least one sub-application corresponding to the characteristic of the device or the characteristic of the service among the sub-applications corresponding to the application and transmit it to the device. My The device management apparatus to provide a device for the service device, characterized by a control unit also.
27. The method of claim 26,
The application registration request message may include connection technology information that the device will use for the application for which the device has requested the registration, application protocol information necessary for executing the application, a device identifier for identifying the device, an identifier of the application for which the device has requested the registration, and a security certificate. Device management apparatus for supporting device-to-device services, characterized in that it comprises at least one of (Security Crudential).
27. The method of claim 26,
The control unit transmits an application information request message requesting information about the appropriate applications to an application and service repository, and uses information included in the application information request message from the application and service repository. And receiving information on sub-applications which are defined and subdivided according to the characteristics of the searched device.

Images