[go: up one dir, main page]

WO2011132928A2 - Procédé et système de gestion pour un dispositif fournissant des services de communication entre machines (m2m), et appareil associé - Google Patents

Procédé et système de gestion pour un dispositif fournissant des services de communication entre machines (m2m), et appareil associé Download PDF

Info

Publication number
WO2011132928A2
WO2011132928A2 PCT/KR2011/002825 KR2011002825W WO2011132928A2 WO 2011132928 A2 WO2011132928 A2 WO 2011132928A2 KR 2011002825 W KR2011002825 W KR 2011002825W WO 2011132928 A2 WO2011132928 A2 WO 2011132928A2
Authority
WO
WIPO (PCT)
Prior art keywords
information
service
application
registration
user
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2011/002825
Other languages
English (en)
Korean (ko)
Other versions
WO2011132928A3 (fr
Inventor
배은희
장용
임형규
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Publication of WO2011132928A2 publication Critical patent/WO2011132928A2/fr
Publication of WO2011132928A3 publication Critical patent/WO2011132928A3/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H04W12/069—Authentication using certificates or pre-shared keys
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • 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.
  • 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.
  • 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.
  • MCHINE TO MACHINE: M2M M2M
  • 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.
  • M2M machine to machine
  • 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 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.
  • M2M machine to machine
  • 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 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.
  • 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 provides a device to device service to a user, and after setting up a connection with a wired / wireless network is completed.
  • 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 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 requests a user to register an application to be provided to the user from a device that provides the device to device service.
  • 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.
  • 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.
  • FIG. 1 is a diagram illustrating an architecture of a system for supporting M2M service according to an embodiment of the present invention
  • FIG. 2 is a view for explaining the operation of the service sharing engine according to an embodiment of the present invention.
  • FIG. 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
  • FIG. 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
  • FIG. 5 is a block diagram of a service sharing engine 500 according to an embodiment of the present invention.
  • FIG. 6 is an operation flowchart of a service sharing engine unit 304a according to the first embodiment of the present invention.
  • FIG. 7 is an operation flowchart of the service sharing engine unit 404a according to the second embodiment of the present invention.
  • FIG. 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.
  • FIG. 2 is a view for explaining the operation of the service sharing engine 200 according to an embodiment of the present invention.
  • the service sharing engine unit 200 supports service interworking between the applications 202 when two or more different applications 202 interoperate with a server to perform service sharing. 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.
  • the device 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.
  • 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.
  • a user may be defined as one or two or more groups.
  • 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).
  • the user / device repository 306 stores information related to users and devices needed to provide M2M services to users.
  • FIG. 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.
  • 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.
  • GSM Mobile Communications
  • WCDMA Wideband Code Division Multiple Access
  • LTE Long Term Evolution
  • CDMAX Code Divisional Multiple Access
  • the device 300 establishes a connection with an access network and a core network in step 310.
  • the device 300 may be a digital still camera (DSC).
  • the device 300 may be a digital photo frame (DPF).
  • 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).
  • the group identifier (ID) is used when it is necessary to classify several users into their respective groups.
  • 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.
  • 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.
  • AAA Authentication, Authorization & Accounting
  • the device 300 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.
  • AKA Authentication and Key Agreement
  • 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.
  • 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. .
  • 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.
  • 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.
  • 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.
  • 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.
  • the service sharing engine unit 304a 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. ) Or index information.
  • the user / device repository 306 transmits the generated reference information to the service sharing engine unit 304a.
  • the service sharing engine unit 304a stores the reference information received from the device / user repository 306.
  • the service sharing engine unit 304a 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.
  • FIG. 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.
  • 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.
  • the second embodiment of the present invention may be performed after the device is registered with the service server according to the first embodiment.
  • the device 400 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.
  • 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.
  • step 412 the service server 404 receiving the device application registration request message from the device 400 registers the device application 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.
  • the service server 404 transmits the device application registration request message to the service sharing engine unit 404a in step 416.
  • 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, and application protocol information supported by the device 400 when the device 400 uses one or more application protocols. information).
  • connection 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.
  • a connection technology such as wifi / wcdma, wifi / cdma, wifi / wimax, wimax / wcdma, wifi / wcdma / wimax may be used.
  • 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.
  • the service sharing engine unit 404a 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.
  • the service sharing engine unit 404a in step 420. Is a device for acquiring 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.
  • 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.
  • 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.
  • the technology information and the application protocol (application protocol) information to be used for the execution of the application (application) may be used for the execution of the application (application)
  • 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.
  • the service sharing engine unit 404a needs to confirm the information on the connection technology specified in FIG. 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.
  • the application is defined as being subdivided.
  • 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.
  • 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.
  • 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.
  • 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.
  • the user / device repository 406 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.
  • ACK acknowledgment
  • 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).
  • 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.
  • 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.
  • 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. Given.
  • FIG. 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 generates a new application service by interworking at least two or more applications connected to the service servers 304 and 404, and transmits the information about the linked application service to the control unit 506.
  • 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 M2M service providing information that is necessary to provide the M2M service to the device, and sets the device registration information and the M2M service included in the device registration request message Reference information for transmitting the device profile information including the provision information to the user / device repository 306 through the transmitter 504 and refer to the device profile information from the user / device repository 306. information) is obtained and stored in the storage unit 508.
  • the controller 506 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.
  • the transmitter 504 is controlled to obtain a corresponding identifier and transmit the same to the device 400.
  • the controller 506 stores the device application information obtained from the application and service repository 408 in the storage unit 508.
  • FIG. 6 is a flowchart illustrating an operation of the service sharing engine unit 304a according to the first embodiment of the present invention.
  • 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.
  • 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.
  • 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. .
  • FIG. 7 is a flowchart illustrating an operation of the service sharing engine unit 404a according to the second embodiment of the present invention.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un procédé permettant de gérer un dispositif qui fournit des services M2M conformément à la présente invention comprend : un processus dans lequel un dispositif fournissant les services M2M à un utilisateur transmet un message de demande d'enregistrement de dispositif demandant que le dispositif soit enregistré, une fois que la configuration de la connexion avec un réseau câblé/sans fil est terminée; un processus dans lequel un serveur de service qui reçoit le message de demande d'enregistrement de dispositif effectue l'authentification pour le dispositif et analyse les informations concernant le dispositif pour configurer les informations du fournisseur de services M2M qui sont nécessaires pour fournir le service M2M au dispositif, à condition que le dispositif ait été enregistré pour la première fois; un processus dans lequel le serveur de service enregistre, dans un référentiel utilisateur/dispositif, les informations d'enregistrement du dispositif incluses dans le message de demande d'enregistrement de dispositif ainsi que les informations de profil du dispositif comprenant les informations du fournisseur de services M2M; un processus dans lequel le référentiel utilisateur/dispositif génère des informations de référence pour faire référence aux informations de profil du dispositif; et un processus dans lequel le serveur de service acquiert les informations de référence à partir du référentiel utilisateur/dispositif.
PCT/KR2011/002825 2010-04-20 2011-04-20 Procédé et système de gestion pour un dispositif fournissant des services de communication entre machines (m2m), et appareil associé Ceased WO2011132928A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR20100036635 2010-04-20
KR10-2010-0036635 2010-04-20

Publications (2)

Publication Number Publication Date
WO2011132928A2 true WO2011132928A2 (fr) 2011-10-27
WO2011132928A3 WO2011132928A3 (fr) 2012-03-08

Family

ID=44834635

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2011/002825 Ceased WO2011132928A2 (fr) 2010-04-20 2011-04-20 Procédé et système de gestion pour un dispositif fournissant des services de communication entre machines (m2m), et appareil associé

Country Status (2)

Country Link
KR (1) KR20110117030A (fr)
WO (1) WO2011132928A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015065013A1 (fr) * 2013-10-28 2015-05-07 삼성전자 주식회사 Procédé et appareil pour un réseau domestique multiutilisateur prenant en charge un dispositif basé sur l'application
EP4061039A1 (fr) * 2021-03-16 2022-09-21 Siemens Aktiengesellschaft Procédé de configuration d'un profil associé à un dispositif utilisateur dans une installation industrielle

Families Citing this family (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103188658A (zh) * 2011-12-30 2013-07-03 中兴通讯股份有限公司 终端连接建立方法、装置及系统
KR101317859B1 (ko) * 2012-01-25 2013-10-14 한남대학교 산학협력단 사물지능통신망에서 클러스터 기반 정보보안 방법
KR101871512B1 (ko) * 2012-02-23 2018-06-26 주식회사 케이티 자가 설치 ｍ2ｍ 플랫폼 장치 및 ｍ2ｍ 서비스 제공 방법
WO2013168911A1 (fr) * 2012-05-10 2013-11-14 주식회사 케이티 Procédé de formation d'une ressource de contenant à l'aide d'informations d'identification d'utilisateur, support d'enregistrement et dispositif correspondant
KR101998414B1 (ko) * 2012-05-18 2019-07-10 주식회사 케이티 Ｍ2ｍ 시스템에서 선택적으로 보안성 있는 시간 동기화를 위한 방법 및 장치
KR101453154B1 (ko) * 2012-05-30 2014-10-23 모다정보통신 주식회사 Ｍ2ｍ 통신에서 리소스 접근 권한 설정 방법
KR101453155B1 (ko) * 2012-05-30 2014-10-23 모다정보통신 주식회사 Ｍ2ｍ 통신에서 리소스 접근 권한 설정 방법
WO2013180476A1 (fr) * 2012-05-30 2013-12-05 삼성에스디에스 주식회사 Appareil et procédé pour des communications entre machines
US9602996B2 (en) 2012-06-28 2017-03-21 Lg Electronics Inc. Method and apparatus for carrying out device-to-device communication in wireless communications system
KR101643334B1 (ko) * 2012-08-06 2016-07-28 주식회사 케이티 결제 및 원격 모니터링을 통한 제어용 ｍ２ｍ 보안 게이트웨이 장치 및 통신 시스템
EP2929732B1 (fr) * 2012-12-10 2016-10-26 Telefonaktiebolaget LM Ericsson (publ) Algorithme d'optimisation intelligente d'énergie m2m
KR101478903B1 (ko) * 2013-04-05 2015-01-05 한국과학기술원 인스턴스 호스팅 환경에서 노드의 프로파일에 기반하여 노드의 정보를 처리하기 위한 방법 및 시스템
KR101478902B1 (ko) * 2013-04-05 2015-01-05 한국과학기술원 인스턴스 호스팅 환경에서 노드 별 특성에 따른 프로파일에 기초하여 서비스를 제공하는 방법 및 시스템
KR101470740B1 (ko) * 2013-06-05 2014-12-08 주식회사 웨이브엠 엠투엠 통합관제 시스템
US9867164B2 (en) 2013-09-09 2018-01-09 Lg Electronics Inc. Method and device for processing a specific request message in wireless communication system

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7249195B2 (en) * 2001-03-30 2007-07-24 Minor Ventures, Llc Apparatus and methods for correlating messages sent between services
US20030078965A1 (en) * 2001-08-22 2003-04-24 Cocotis Thomas A. Output management system and method for enabling printing via wireless devices
JP2005025337A (ja) * 2003-06-30 2005-01-27 Sony Corp 機器登録システム、機器登録サーバ、機器登録方法、機器登録プログラム、記憶媒体、及び端末機器
CA2603236C (fr) * 2005-04-18 2011-09-13 Research In Motion Limited Systeme et procede d'enregistrement dispositif-a-serveur

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015065013A1 (fr) * 2013-10-28 2015-05-07 삼성전자 주식회사 Procédé et appareil pour un réseau domestique multiutilisateur prenant en charge un dispositif basé sur l'application
KR20150048657A (ko) * 2013-10-28 2015-05-07 삼성전자주식회사 멀티 사용자들이 홈 네트워킹을 지원하는 어플리케이션 기반의 기기를 등록하는 방법 및 장치
US10142345B2 (en) 2013-10-28 2018-11-27 Samsung Electronics Co., Ltd Method and apparatus for multi-users registering home network supporting application based device
KR102269417B1 (ko) 2013-10-28 2021-06-28 삼성전자주식회사 멀티 사용자들이 홈 네트워킹을 지원하는 어플리케이션 기반의 기기를 등록하는 방법 및 장치
EP4061039A1 (fr) * 2021-03-16 2022-09-21 Siemens Aktiengesellschaft Procédé de configuration d'un profil associé à un dispositif utilisateur dans une installation industrielle

Also Published As

Publication number Publication date
KR20110117030A (ko) 2011-10-26
WO2011132928A3 (fr) 2012-03-08

Similar Documents

Publication Publication Date Title
WO2011132928A2 (fr) Procédé et système de gestion pour un dispositif fournissant des services de communication entre machines (m2m), et appareil associé
WO2011046393A2 (fr) Appareil et procédé d'établissement d'un réseau personnel permettant de fournir un service cpns
WO2014163383A1 (fr) Procédé et appareil d'acheminement de message de service basé sur la proximité dans un système de communication sans fil
WO2011049355A2 (fr) Procédé et appareil de fourniture de service par réseau personnel
CN105025044B (zh) 一种设备控制方法及系统
WO2012081941A1 (fr) Procédé et appareil destinés à l'authentification par dispositif m2m entre un fournisseur de services et un opérateur de réseau mobile
WO2013121362A2 (fr) Activation de services m2m sur des réseaux d'accès
WO2019027061A1 (fr) Système de serveur de passerelle connecté pour service de commande de véhicule en temps réel
WO2014185728A1 (fr) Procede et appareil pour effectuer une decouverte pour communication de dispositif a dispositif
WO2011043571A2 (fr) Procédé de contrôle d'accès local pour terminaux qui supportent des communications m2m dans un système de communication sans fil
WO2015026149A1 (fr) Système, appareil et procédé pour partager un dispositif électronique
WO2018066977A1 (fr) Procédé et dispositif de rattachement de terminal et de création d'une session pdu acheminée au rattachement dans un environnement d'itinérance prenant en charge une tranche de réseau
WO2011159040A2 (fr) Appareil et procédé permettant de configurer un réseau personnel au moyen d'une table de routage pn
WO2013100547A1 (fr) Procédé et appareil de gestion de la santé d'un individu
WO2014183260A1 (fr) Procédé, dispositif et système de traitement de service de données dans un scénario d'itinérance
WO2013039277A1 (fr) Procédé et dispositif de comptabilité pour l'itinérance en wifi basés sur une coopération d'ac et d'ap
WO2011159096A2 (fr) Appareil et procédé d'enregistrement d'un réseau personnel
WO2018070740A1 (fr) Procédé et dispositif pour relier une fonction d'exposition de capacité et des fonctions de réseau
WO2015133859A1 (fr) Procédé et système d'établissement d'une connexion entre un dispositif chercheur et un dispositif cible
WO2015002443A1 (fr) Dispositif mobile et procédé de commande d'émission vers un serveur web dans un dispositif mobile
WO2015020502A1 (fr) Technique de découverte de service dans un réseau de communication sans fil pour former un groupe p2p
US20100199333A1 (en) System and method for providing device management service to electronic device having no broadband communication module
KR20130064217A (ko) 장치 대 장치서비스를 제공하기 위한 제어모듈시스템 및 방법
BRPI0610990A2 (pt) métodos e equipamentos para hospedar simultaneamente múltiplos provedores de serviço em uma rede
WO2011118980A2 (fr) Dispositif relais et procédé permettant d'offrir un service de gestion de dispositif

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11772216

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11772216

Country of ref document: EP

Kind code of ref document: A2