[go: up one dir, main page]
More Web Proxy on the site http://driver.im/

WO2019231020A1 - Method for managing request reachability in m2m platform - Google Patents

Method for managing request reachability in m2m platform Download PDF

Info

Publication number
WO2019231020A1
WO2019231020A1 PCT/KR2018/006222 KR2018006222W WO2019231020A1 WO 2019231020 A1 WO2019231020 A1 WO 2019231020A1 KR 2018006222 W KR2018006222 W KR 2018006222W WO 2019231020 A1 WO2019231020 A1 WO 2019231020A1
Authority
WO
WIPO (PCT)
Prior art keywords
entity
resource
request message
poas
present
Prior art date
Application number
PCT/KR2018/006222
Other languages
French (fr)
Korean (ko)
Inventor
정승명
김재호
안일엽
최성찬
Original Assignee
전자부품연구원
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 전자부품연구원 filed Critical 전자부품연구원
Priority to PCT/KR2018/006222 priority Critical patent/WO2019231020A1/en
Publication of WO2019231020A1 publication Critical patent/WO2019231020A1/en

Links

Images

Classifications

    • 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
    • H04L65/40—Support for services or applications

Definitions

  • the present invention relates to a Machine to Machine (M2M) / Internet of Things (IoT) technology, and more particularly, to a method for managing Request Reachability (RR) in the M2M platform.
  • M2M Machine to Machine
  • IoT Internet of Things
  • RR Request Reachability
  • Request Reachability is information indicating whether an application entity (AE) or a common service entity (CSE) can receive a request message from another entity (AE / CSE).
  • the AE stores its RR information in the ⁇ AE1> resource and the CSE in the ⁇ CSEBase> resource and the ⁇ remoteCSE> resource. Specifically, as shown in FIG. 1,
  • CSE2 can confirm that its RR information is stored in the ⁇ CSE2base> resource created in it and the ⁇ CSE2> resource created in ⁇ CSE1base> of "CSE1".
  • the ⁇ AE1> resource and the ⁇ remoteCSE> resource are stored in different CSEs. As shown in FIG. 2, it is assumed that the corresponding AE / CSE updates its RR information and keeps the RR information up to date. This is not a requirement of the M2M specification.
  • an object of the present invention is to provide a method for managing the RR information of other entities stored in the host entity in a way for effective management, such as updating the RR information. Is in.
  • the RR management method includes the steps of: generating, by a first entity, its own resource at a second entity; And managing, by the second entity, the RR stored in the resource of the first entity.
  • the management step may attempt to transmit a request message through the PoA of the first entity and manage the RR stored in the resource of the first entity according to success or failure.
  • the management step may include changing the RR to FALSE if the request message transmission fails for all of the PoAs of the first entity when the RR is TRUE.
  • the step of changing the RR to TRUE may include.
  • the RR management method may further include deleting a PoA that fails to transmit a request message among PoAs of the first entity.
  • the RR management method may further include changing the order of PoAs that fail to transmit a request message among PoAs of the first entity.
  • the RR management method may further include the step of changing the order of the PoA successful in the transmission of the request message of the PoA of the first entity;
  • the RR management system Communication unit for communicating with the external electronic device is installed; And a processor in which a second entity in which a resource of the first entity is generated is installed and manages the RR stored in the resource of the first entity as the second entity.
  • the hosting entity manages the RR information of other entities stored therein, so that the hosting entity may not update its own RR information stored in the hosting entity. This makes it possible to update to the latest RR information.
  • FIG. 3 is a view provided to explain a concept of the RR management method in the M2M platform according to an embodiment of the present invention
  • FIG. 4 is a flowchart provided to explain an RR management method according to an embodiment of the present invention.
  • FIG. 5 is a flowchart provided to explain an RR management method according to another embodiment of the present invention.
  • FIG. 6 is a diagram illustrating an M2M / IoT system to which the present invention is applicable.
  • FIG. 7 is an internal block diagram of the electronic devices illustrated in FIG. 6.
  • FIG. 3 is a view provided to explain a concept of the RR management method in the M2M platform according to an embodiment of the present invention.
  • a hosting CSE provides a method of managing up to RR information of another entity stored in a resource of another entity (AE / CSE) created therein.
  • CSE1 manages RR information of "AE1” stored in ⁇ AE1> resource created by "AE1” in ⁇ CSE1base> resource
  • CSE2 refers to ⁇ CSE1base>.
  • CSE2 manages the RR information of "CSE1" stored in the ⁇ CSE1> resource created by the "CSE1" in the ⁇ CSE2base> resource.
  • the RR management method according to an embodiment of the present invention does not exclude existing assumptions that the entity manages its RR information stored in the hosting CSE. That is, the RR management method according to the embodiment of the present invention may be parallel to existing assumptions. Therefore, the RR information stored in the hosting CSE may be managed by the corresponding entity and / or the hosting CSE. 3, only the RR management method according to the embodiment of the present invention corresponding to the new management method performed by the hosting CSE is shown.
  • FIG. 4 is a flowchart provided to explain the RR management method in the M2M platform according to an embodiment of the present invention.
  • the hosting CSE first gets a request to send / forward to the corresponding entity (AE / CSE) (S110), and requests the request.
  • the RR of the corresponding entity to be transmitted / delivered is checked (S120).
  • the hosting CSE sends / receives the request sequentially through the Point of Access (PoA) of the entity. (S130 & S140).
  • PoA Point of Access
  • the hosting CSE changes the RR of the entity to "FALSE" [the hosting CSE cannot send / deliver the request to the entity]. (S150).
  • the hosting CSE sets the PoA that successfully transmits the request message to be placed first (S160).
  • step S120 even if the RR is "FALSE" [hosting CSE can not send / forward the request to the entity] (S120-FALSE), the hosting CSE is The request is transmitted / delivered (S170 & S180).
  • the RR of the entity is maintained as "FALSE".
  • the hosting CSE changes the RR of the corresponding entity to "TRUE" (the hosting CSE may transmit / deliver the request to the entity) (S190).
  • the hosting CSE sets the PoA that successfully transmits the request message to be placed first (S160).
  • FIG. 5 is a view provided to explain the RR management method in the M2M platform according to another embodiment of the present invention.
  • an additional procedure is performed in steps S130 and S140 and steps S170 and S180 indicated by boxes.
  • steps S130, S140, S170, and S180 in the process of sequentially transmitting / delivering requests through PoAs of the corresponding entity, an invalid PoA that fails to transmit / deliver the request message is deleted or last. To deploy.
  • Whether to delete or change the deployment can be determined according to the service provider (SP) policy, and when deleting, the hosting CSE can be implemented to notify the entity of the deletion.
  • SP service provider
  • This policy may be applied collectively or selectively for those entities. For example, a policy of deleting invalid PoA for "CSE2" but invalid PoA for "AE1" can be applied last.
  • deletions or deployment changes can be implemented by those entities that are not hosting CSEs.
  • the M2M / IoT system to which the present invention is applicable includes a server 200-1, a gateway 200-21, 200-22, and a device 200-31, 200-32, 200-33.
  • Various electronic devices such as 200-34 are connected to each other so as to communicate with each other.
  • the number of electronic devices shown in FIG. 6, for example, the server 200-1, the gateways 200-21, 200-22, and the devices 200-31, 200-32, and 200-constituting the M2M / IoT system. 33, 200-34) is an example, the technical spirit of the present invention can be applied to different implementations.
  • connection structure of the electronic devices shown in FIG. 6 may also be replaced in other ways as necessary.
  • All electronic devices shown in FIG. 6 may perform the function of the hosting CSE of the M2M platform. That is, the server 200-1, the gateways 200-21, 200-22, and the devices 200-31, 200-32, 200-33, and 200-34 are all hosting CSEs, which are shown in FIGS. 4 and 5. You can manage the RR of other entities stored in it.
  • FIG. 7 is an internal block diagram of the electronic devices illustrated in FIG. 6. Configurations necessary for implementing an embodiment of the present invention are the server (200-1), gateways (200-21, 200-22), devices (200-31, 200-32, 200-33, 200-34) Is common. Therefore, in Fig. 7, these are referred to collectively as "200", which will be referred to collectively as electronic devices hereinafter.
  • electronic devices include a communication unit 210, a processor 220, a storage unit 230, and a function block 240.
  • the communication unit 210 is a communication interface means for communicating with an external device and accessing an external network.
  • the processor 220 includes at least one Application Entitr (AE) and Common Service Entity (CSE). Depending on the type and function of the electronic device, the AE may not be included.
  • AE Application Entitr
  • CSE Common Service Entity
  • the processor 220 performs the RR management algorithm shown in FIGS. 4 and 5, and the storage unit 230 provides the storage space necessary for the processor 220 to perform the RR management.
  • the function block 240 performs an inherent function of the electronic device. For example, when the electronic device is the server 200-1, virtual machines providing a service correspond to the function block 240.
  • the technical idea of the present invention can be applied to a computer-readable recording medium containing a computer program for performing the functions of the apparatus and method according to the present embodiment.
  • the technical idea according to various embodiments of the present disclosure may be implemented in the form of computer readable codes recorded on a computer readable recording medium.
  • the computer-readable recording medium can be any data storage device that can be read by a computer and can store data.
  • the computer-readable recording medium may be a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical disk, a hard disk drive, or the like.
  • the computer-readable code or program stored in the computer-readable recording medium may be transmitted through a network connected between the computers.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer And Data Communications (AREA)

Abstract

A method for managing request reachability (RR) in an M2M platform is provided. In a method for managing RR according to an embodiment of the present invention, when a first entity creates its own resource in a second entity, the second entity manages RR stored in the resource of the first entity. A hosting entity thereby manages RR information of other entities stored therein, so that even when the entities cannot update their own RR information stored in the hosting entity, the hosting entity can update the entities to the latest RR information.

Description

M2M 플랫폼에서 Request Reachability 관리 방법How to Manage Request Reachability in the M2M Platform
본 발명은 M2M(Machine to Machine)/IoT(Internet of Things) 기술에 관한 것으로, 더욱 상세하게는 M2M 플랫폼에서 RR(Request Reachability)을 관리하는 방법에 관한 것이다.The present invention relates to a Machine to Machine (M2M) / Internet of Things (IoT) technology, and more particularly, to a method for managing Request Reachability (RR) in the M2M platform.
RR(Request Reachability)은, AE(Application Entity) 또는 CSE(Common Service Entity)가 다른 엔티티(AE/CSE)로부터 요청 메시지(Request Message)를 수신할 수 있는지 여부를 나타내는 정보이다.Request Reachability (RR) is information indicating whether an application entity (AE) or a common service entity (CSE) can receive a request message from another entity (AE / CSE).
방화벽 또는 NAT(Network Address Translation) 환경에 있을 경우 외부로부터 요청 메시지를 직접 수신하지 못할 수 있음을 반영한 것이다.This is a reflection of the fact that you may not receive request messages directly from outside when you are in a firewall or NAT (Network Address Translation) environment.
도 1은 RR의 설명에 제공되는 도면이다. 도 1에 도시된 바와 같이, AE는 <AE1> 리소스에, CSE는 <CSEBase> 리소스와 <remoteCSE> 리소스에 자신의 RR 정보를 저장한다. 구체적으로, 도 1에 도시된 바에 따르면,1 is a diagram provided to explain the RR. As shown in FIG. 1, the AE stores its RR information in the <AE1> resource and the CSE in the <CSEBase> resource and the <remoteCSE> resource. Specifically, as shown in FIG. 1,
1) "AE1"은 <CSE1base> 리소스에 생성한 <AE1> 리소스에 자신의 RR 정보를 저장하였고,1) "AE1" stored its RR information in the <AE1> resource created in the <CSE1base> resource.
2) "CSE1"은 자신에 생성한 <CSE1base> 리소스와 "CSE2"의 <CSE2base>에 생성한 <CSE1> 리소스에 자신의 RR 정보를 저장하였으며,2) "CSE1" saved its RR information in the <CSE1base> resource created in itself and the <CSE1> resource created in <CSE2base> of "CSE2".
3) "CSE2"는 자신에 생성한 <CSE2base> 리소스와 "CSE1"의 <CSE1base>에 생성한 <CSE2> 리소스에 자신의 RR 정보를 저장하였음을 확인할 수 있다.3) "CSE2" can confirm that its RR information is stored in the <CSE2base> resource created in it and the <CSE2> resource created in <CSE1base> of "CSE1".
이와 같이, <AE1> 리소스와 <remoteCSE> 리소스는 다른 CSE에 저장되는데, 도 2에 도시된 바와 같이 해당 AE/CSE가 자신의 RR 정보를 갱신하는 것이 가정 사항이며, RR 정보를 최신으로 유지하는 것은 M2M 규격에서 필수적으로 요구하는 사항이 아니다.As described above, the <AE1> resource and the <remoteCSE> resource are stored in different CSEs. As shown in FIG. 2, it is assumed that the corresponding AE / CSE updates its RR information and keeps the RR information up to date. This is not a requirement of the M2M specification.
이와 같은 실정에서, 네트워크 단절 등의 상황이 발생한 경우 해당 AE/CSE가 자신의 RR 정보를 갱신하는 것은 어렵다는 문제가 있다.In this situation, there is a problem that it is difficult for the AE / CSE to update its RR information when a situation such as network disconnection occurs.
본 발명은 상기와 같은 문제점을 해결하기 위하여 안출된 것으로서, 본 발명의 목적은, RR 정보 갱신 등의 효과적인 관리를 위한 방안으로, 호스팅 엔티티가 자신에 저장된 다른 엔티티의 RR 정보를 관리하는 방법을 제공함에 있다.The present invention has been made to solve the above problems, an object of the present invention is to provide a method for managing the RR information of other entities stored in the host entity in a way for effective management, such as updating the RR information. Is in.
상기 목적을 달성하기 위한 본 발명의 일 실시예에 따른, RR 관리 방법은, 제1 엔티티가, 제2 엔티티에 자신의 리소스를 생성하는 단계; 및 제2 엔티티가, 제1 엔티티의 리소스에 저장된 RR을 관리하는 단계;를 포함한다.According to an embodiment of the present invention for achieving the above object, the RR management method includes the steps of: generating, by a first entity, its own resource at a second entity; And managing, by the second entity, the RR stored in the resource of the first entity.
그리고, 관리 단계는, 제1 엔티티의 PoA를 통해 요청 메시지 전송을 시도하고, 성공 여부에 따라 제1 엔티티의 리소스에 저장된 RR을 관리할 수 있다.The management step may attempt to transmit a request message through the PoA of the first entity and manage the RR stored in the resource of the first entity according to success or failure.
또한, 관리 단계는, RR이 TRUE인 경우, 제1 엔티티의 PoA 모두에 대해 요청 메시지 전송이 실패하면, RR을 FALSE로 변경하는 단계;를 포함할 수 있다.The management step may include changing the RR to FALSE if the request message transmission fails for all of the PoAs of the first entity when the RR is TRUE.
그리고, 관리 단계는, RR이 FALSE인 경우, 제1 엔티티의 PoA들 중 적어도 하나에 대해 요청 메시지 전송이 성공하면, RR을 TRUE로 변경하는 단계;를 포함할 수 있다.And, if the RR is FALSE, if the request message transmission is successful for at least one of the PoAs of the first entity, the step of changing the RR to TRUE; may include.
또한, 본 발명의 일 실시예에 따른 RR 관리 방법은, 제1 엔티티의 PoA 중 요청 메시지 전송에 실패한 PoA를 삭제하는 단계;를 더 포함할 수 있다.The RR management method according to an embodiment of the present invention may further include deleting a PoA that fails to transmit a request message among PoAs of the first entity.
그리고, 본 발명의 일 실시예에 따른 RR 관리 방법은, 제1 엔티티의 PoA 중 요청 메시지 전송에 실패한 PoA의 순서를 뒤로 변경하는 단계;를 더 포함할 수 있다.The RR management method according to an embodiment of the present invention may further include changing the order of PoAs that fail to transmit a request message among PoAs of the first entity.
또한, 본 발명의 일 실시예에 따른 RR 관리 방법은, 제1 엔티티의 PoA 중 요청 메시지 전송에 성공한 PoA의 순서를 앞으로 변경하는 단계;를 더 포함할 수 있다.In addition, the RR management method according to an embodiment of the present invention, may further include the step of changing the order of the PoA successful in the transmission of the request message of the PoA of the first entity;
한편, 본 발명의 다른 실시예에 따른, RR 관리 시스템은, 제1 엔티티가 설치된 외부 전자기기와 통신하는 통신부; 및 제1 엔티티의 리소스가 생성된 제2 엔티티가 설치되어 있으며, 제2 엔티티로 제1 엔티티의 리소스에 저장된 RR을 관리하는 프로세서;를 포함한다.On the other hand, according to another embodiment of the present invention, the RR management system, Communication unit for communicating with the external electronic device is installed; And a processor in which a second entity in which a resource of the first entity is generated is installed and manages the RR stored in the resource of the first entity as the second entity.
이상 설명한 바와 같이, 본 발명의 실시예들에 따르면, 호스팅 엔티티가 자신에 저장된 다른 엔티티들의 RR 정보들을 관리함으로써, 엔티티들이 호스팅 엔티티에 저장된 자신의 RR 정보들을 갱신할 수 없는 상황에서도, 호스팅 엔티티에 의해 최신의 RR 정보로 갱신이 가능해진다.As described above, according to embodiments of the present invention, the hosting entity manages the RR information of other entities stored therein, so that the hosting entity may not update its own RR information stored in the hosting entity. This makes it possible to update to the latest RR information.
도 1은 RR의 설명에 제공되는 도면,1 is a diagram provided in the description of the RR;
도 2는 기존의 RR 정보 갱신 방법의 설명에 제공되는 도면,2 is a view provided to explain an existing method of updating RR information;
도 3은 본 발명의 일 실시예에 따른 M2M 플랫폼에서 RR 관리 방법의 개념 설명에 제공되는 도면,3 is a view provided to explain a concept of the RR management method in the M2M platform according to an embodiment of the present invention,
도 4는 본 발명의 일 실시예에 따른 RR 관리 방법의 설명에 제공되는 흐름도,4 is a flowchart provided to explain an RR management method according to an embodiment of the present invention;
도 5는 본 발명의 다른 실시예에 따른 RR 관리 방법의 설명에 제공되는 흐름도,5 is a flowchart provided to explain an RR management method according to another embodiment of the present invention;
도 6은 본 발명이 적용 가능한 M2M/IoT 시스템을 도시한 도면, 그리고,6 is a diagram illustrating an M2M / IoT system to which the present invention is applicable; and
도 7은, 도 6에 도시된 전자 기기들의 내부 블럭도이다.FIG. 7 is an internal block diagram of the electronic devices illustrated in FIG. 6.
이하에서는 도면을 참조하여 본 발명을 보다 상세하게 설명한다.Hereinafter, with reference to the drawings will be described the present invention in more detail.
도 3은 본 발명의 일 실시예에 따른 M2M 플랫폼에서 RR 관리 방법의 개념 설명에 제공되는 도면이다.3 is a view provided to explain a concept of the RR management method in the M2M platform according to an embodiment of the present invention.
본 발명의 실시예에서는, 도 3에 도시된 바와 같이, 호스팅 CSE(Hosting CSE)가 자신에 생성된 다른 엔티티(AE/CSE)의 리소스에 저장된 다른 엔티티의 RR 정보까지 관리하는 방법을 제시한다.According to an embodiment of the present invention, as shown in FIG. 3, a hosting CSE provides a method of managing up to RR information of another entity stored in a resource of another entity (AE / CSE) created therein.
구체적으로, 도 3에 도시된 바와 같이, "CSE1"은, "AE1"이 <CSE1base> 리소스에 생성한 <AE1> 리소스에 저장된 "AE1"의 RR 정보를 관리하고, "CSE2"가 <CSE1base> 리소스에 생성한 <CSE2> 리소스에 저장된 "CSE2"의 RR 정보를 관리하여 준다.Specifically, as shown in FIG. 3, "CSE1" manages RR information of "AE1" stored in <AE1> resource created by "AE1" in <CSE1base> resource, and "CSE2" refers to <CSE1base>. Manages RR information of "CSE2" stored in <CSE2> resource created in resource.
또한, "CSE2"는, "CSE1"이 <CSE2base> 리소스에 생성한 <CSE1> 리소스에 저장된 "CSE1"의 RR 정보를 관리하여 준다.In addition, "CSE2" manages the RR information of "CSE1" stored in the <CSE1> resource created by the "CSE1" in the <CSE2base> resource.
본 발명의 실시예에 따른 RR 관리 방법은, 해당 엔티티가 호스팅 CSE에 저장된 자신의 RR 정보를 관리하는 기존의 가정 사항을 배제하지 않는다. 즉, 본 발명의 실시예에 따른 RR 관리 방법은 기존의 가정 사항과 병행할 수 있다. 따라서, 호스팅 CSE에 저장된 RR 정보는 해당 엔티티 및/또는 호스팅 CSE에 의해 관리될 수 있는 것이다. 단, 도 3에는 호스팅 CSE에 의해 수행되는 새로운 관리 방법에 해당하는 본 발명의 실시예에 따른 RR 관리 방법만이 도시되어 있음에 유념하여야 한다.The RR management method according to an embodiment of the present invention does not exclude existing assumptions that the entity manages its RR information stored in the hosting CSE. That is, the RR management method according to the embodiment of the present invention may be parallel to existing assumptions. Therefore, the RR information stored in the hosting CSE may be managed by the corresponding entity and / or the hosting CSE. 3, only the RR management method according to the embodiment of the present invention corresponding to the new management method performed by the hosting CSE is shown.
도 4는 본 발명의 일 실시예에 따른 M2M 플랫폼에서 RR 관리 방법의 설명에 제공되는 흐름도이다.4 is a flowchart provided to explain the RR management method in the M2M platform according to an embodiment of the present invention.
RR 관리를 위해, 도 4에 도시된 바와 같이, 호스팅 CSE는 먼저 해당 엔티티(AE/CSE)에 전송/전달(send/forward)할 요청(request)을 획득(get) 하고(S110), 요청을 전송/전달할 해당 엔티티의 RR을 확인(check) 한다(S120).For RR management, as shown in FIG. 4, the hosting CSE first gets a request to send / forward to the corresponding entity (AE / CSE) (S110), and requests the request. The RR of the corresponding entity to be transmitted / delivered is checked (S120).
확인 결과 RR이 "TRUE"[호스팅 CSE가 해당 엔티티에 요청을 전송/전달할 수 있음] 이면(S120-TRUE), 호스팅 CSE는 해당 엔티티의 PoA(Point of Access)들을 통해 순차적으로 요청을 전송/전달한다(S130&S140).If the result of the check is that the RR is "TRUE" [hosting CSE can send / deliver the request to the entity] (S120-TRUE), the hosting CSE sends / receives the request sequentially through the Point of Access (PoA) of the entity. (S130 & S140).
해당 엔티티의 PoA들 모두에 대해 요청 메시지 전송이 실패하면(S140-no more PoA), 호스팅 CSE는 해당 엔티티의 RR을 "FALSE"[호스팅 CSE가 해당 엔티티에 요청을 전송/전달할 수 없음] 로 변경한다(S150).If the request message transmission fails for all PoAs of the entity (S140-no more PoA), the hosting CSE changes the RR of the entity to "FALSE" [the hosting CSE cannot send / deliver the request to the entity]. (S150).
반면, 해당 엔티티에 요청 메시지 전송이 성공하면(S140-works), 호스팅 CSE는 요청 메시지 전송을 성공한 PoA가 맨 처음에 배치되도록 설정한다(S160).On the other hand, if the request message is successfully transmitted to the corresponding entity (S140-works), the hosting CSE sets the PoA that successfully transmits the request message to be placed first (S160).
한편, S120단계에서 해당 엔티티의 RR을 확인한 결과, RR이 "FALSE"[호스팅 CSE가 해당 엔티티에 요청을 전송/전달할 수 없음] 인 경우도(S120-FALSE), 호스팅 CSE는 해당 엔티티의 PoA들을 통해 요청을 전송/전달한다(S170&S180).On the other hand, as a result of checking the RR of the entity in step S120, even if the RR is "FALSE" [hosting CSE can not send / forward the request to the entity] (S120-FALSE), the hosting CSE is The request is transmitted / delivered (S170 & S180).
해당 엔티티의 PoA들 모두에 대해 요청 메시지 전송이 실패하면(S180-no more PoA), 해당 엔티티의 RR은 "FALSE"로 유지된다.If the request message transmission fails for all PoAs of the entity (S180-no more PoA), the RR of the entity is maintained as "FALSE".
반면, 해당 엔티티에 요청 메시지 전송이 성공하면(S180-works), 호스팅 CSE는 해당 엔티티의 RR을 "TRUE"[호스팅 CSE가 해당 엔티티에 요청을 전송/전달할 수 있음] 로 변경한다(S190).On the other hand, if the request message is successfully transmitted to the corresponding entity (S180-works), the hosting CSE changes the RR of the corresponding entity to "TRUE" (the hosting CSE may transmit / deliver the request to the entity) (S190).
그리고, 호스팅 CSE는 요청 메시지 전송을 성공한 PoA가 맨 처음에 배치되도록 설정한다(S160).In addition, the hosting CSE sets the PoA that successfully transmits the request message to be placed first (S160).
도 5는 본 발명의 다른 실시예에 따른 M2M 플랫폼에서 RR 관리 방법의 설명에 제공되는 도면이다. 본 발명의 실시예에 따른 RR 관리 방법에서는, 박스로 표시된 S130단계와 S140단계 및 S170단계와 S180단계에서 추가적인 절차가 수행된다.5 is a view provided to explain the RR management method in the M2M platform according to another embodiment of the present invention. In the RR management method according to an embodiment of the present invention, an additional procedure is performed in steps S130 and S140 and steps S170 and S180 indicated by boxes.
구체적으로, S130단계와 S140단계 및 S170단계와 S180단계에서, 해당 엔티티의 PoA들을 통해 순차적으로 요청을 전송/전달하는 과정에서, 요청 메시지 전송/전달에 실패한 유효하지 않은 PoA를 삭제하거나 맨 마지막에 배치하는 것이다.Specifically, in steps S130, S140, S170, and S180, in the process of sequentially transmitting / delivering requests through PoAs of the corresponding entity, an invalid PoA that fails to transmit / deliver the request message is deleted or last. To deploy.
삭제 또는 배치 변경 여부는 SP(Service Provider)의 정책에 따라 결정되도록 할 수 있으며, 삭제 시에는 호스팅 CSE가 해당 엔티티에 삭제 사실을 통지하도록 구현할 수 있다.Whether to delete or change the deployment can be determined according to the service provider (SP) policy, and when deleting, the hosting CSE can be implemented to notify the entity of the deletion.
이 정책은 해당 엔티티들에 대해 일괄적으로 적용될 수도 있고 선택적으로 적용될 수 있다. 이를 테면, "CSE2"에 대해서는 유효하지 않은 PoA를 삭제하지만, "AE1"에 대해서는 유효하지 않은 PoA를 맨 마지막에 배치하는 정책을 적용할 수 있다.This policy may be applied collectively or selectively for those entities. For example, a policy of deleting invalid PoA for "CSE2" but invalid PoA for "AE1" can be applied last.
나아가, 삭제 또는 배치 변경은, 호스팅 CSE가 아닌 해당 엔티티가 수행하는 것으로 구현하는 것도 가능하다.Furthermore, deletions or deployment changes can be implemented by those entities that are not hosting CSEs.
도 6은 본 발명이 적용 가능한 M2M/IoT 시스템을 도시한 도면이다. 본 발명이 적용 가능한 M2M/IoT 시스템은, 도 6에 도시된 바와 같이, 서버(200-1), 게이트웨이(200-21, 200-22), 디바이스(200-31, 200-32, 200-33, 200-34)와 같은 다양한 전자 기기들이 상호 통신가능하도록 연결되어 구축된다.6 is a diagram illustrating an M2M / IoT system to which the present invention is applicable. As shown in FIG. 6, the M2M / IoT system to which the present invention is applicable includes a server 200-1, a gateway 200-21, 200-22, and a device 200-31, 200-32, 200-33. Various electronic devices such as 200-34 are connected to each other so as to communicate with each other.
도 6에 도시된 전자 기기들의 개수, 이를 테면, M2M/IoT 시스템을 구성하는 서버(200-1), 게이트웨이(200-21, 200-22) 및 디바이스(200-31, 200-32, 200-33, 200-34)의 대수는 예시적인 것이므로, 이와 다르게 구현하는 경우도 본 발명의 기술적 사상이 적용될 수 있다.The number of electronic devices shown in FIG. 6, for example, the server 200-1, the gateways 200-21, 200-22, and the devices 200-31, 200-32, and 200-constituting the M2M / IoT system. 33, 200-34) is an example, the technical spirit of the present invention can be applied to different implementations.
나아가, 도 6에 도시된 전자 기기들의 연결 구조 역시, 필요에 따라 다른 방식으로 대체될 수 있음은 물론이다.Furthermore, the connection structure of the electronic devices shown in FIG. 6 may also be replaced in other ways as necessary.
도 6에 도시된 모든 전자 기기들은, M2M 플랫폼의 호스팅 CSE의 기능을 수행할 수 있다. 즉, 서버(200-1), 게이트웨이(200-21, 200-22), 디바이스(200-31, 200-32, 200-33, 200-34) 모두 호스팅 CSE로써, 도 4와 도 5에 제시된 바에 따라 자신에 저장된 다른 엔티티들의 RR을 관리할 수 있는 것이다.All electronic devices shown in FIG. 6 may perform the function of the hosting CSE of the M2M platform. That is, the server 200-1, the gateways 200-21, 200-22, and the devices 200-31, 200-32, 200-33, and 200-34 are all hosting CSEs, which are shown in FIGS. 4 and 5. You can manage the RR of other entities stored in it.
도 7는, 도 6에 도시된 전자 기기들의 내부 블럭도이다. 본 발명의 실시예를 구현함에 있어 필요한 구성들은 서버(200-1), 게이트웨이(200-21, 200-22), 디바이스(200-31, 200-32, 200-33, 200-34) 모두가 공통된다. 따라서, 도 7에서는 이들을 참조 부호 "200"으로 통칭하여 도시하였으며, 이하에서 전자 기기로 통칭한다.FIG. 7 is an internal block diagram of the electronic devices illustrated in FIG. 6. Configurations necessary for implementing an embodiment of the present invention are the server (200-1), gateways (200-21, 200-22), devices (200-31, 200-32, 200-33, 200-34) Is common. Therefore, in Fig. 7, these are referred to collectively as "200", which will be referred to collectively as electronic devices hereinafter.
도 7에 도시된 바와 같이, 본 발명의 다른 실시예에 따른 전자 기기들은, 통신부(210), 프로세서(220), 저장부(230) 및 기능 블록(240)을 포함한다.As shown in FIG. 7, electronic devices according to another embodiment of the present invention include a communication unit 210, a processor 220, a storage unit 230, and a function block 240.
통신부(210)는 외부 기기와 통신하고 외부 네트워크에 액세스하기 위한 통신 인터페이스 수단이다.The communication unit 210 is a communication interface means for communicating with an external device and accessing an external network.
프로세서(220)는 적어도 하나의 AE(Application Entitr)와 CSE(Common Service Entity)를 포함한다. 전자 기기의 종류와 기능에 따라서는, AE가 포함되지 않을 수도 있다.The processor 220 includes at least one Application Entitr (AE) and Common Service Entity (CSE). Depending on the type and function of the electronic device, the AE may not be included.
프로세서(220)의 도 4와 도 5에 도시된 RR 관리 알고리즘을 수행하며, 저장부(230)는 프로세서(220)가 RR 관리를 수행함에 있어 필요한 저장 공간을 제공한다.The processor 220 performs the RR management algorithm shown in FIGS. 4 and 5, and the storage unit 230 provides the storage space necessary for the processor 220 to perform the RR management.
기능 블록(240)은 전자 기기 본연의 기능을 수행한다. 이를 테면, 전자 기기가 서버(200-1)인 경우, 서비스를 제공하는 가상 머신들이 기능 블록(240)에 해당한다.The function block 240 performs an inherent function of the electronic device. For example, when the electronic device is the server 200-1, virtual machines providing a service correspond to the function block 240.
한편, 본 실시예에 따른 장치와 방법의 기능을 수행하게 하는 컴퓨터 프로그램을 수록한 컴퓨터로 읽을 수 있는 기록매체에도 본 발명의 기술적 사상이 적용될 수 있음은 물론이다. 또한, 본 발명의 다양한 실시예에 따른 기술적 사상은 컴퓨터로 읽을 수 있는 기록매체에 기록된 컴퓨터로 읽을 수 있는 코드 형태로 구현될 수도 있다. 컴퓨터로 읽을 수 있는 기록매체는 컴퓨터에 의해 읽을 수 있고 데이터를 저장할 수 있는 어떤 데이터 저장 장치이더라도 가능하다. 예를 들어, 컴퓨터로 읽을 수 있는 기록매체는 ROM, RAM, CD-ROM, 자기 테이프, 플로피 디스크, 광디스크, 하드 디스크 드라이브, 등이 될 수 있음은 물론이다. 또한, 컴퓨터로 읽을 수 있는 기록매체에 저장된 컴퓨터로 읽을 수 있는 코드 또는 프로그램은 컴퓨터간에 연결된 네트워크를 통해 전송될 수도 있다.On the other hand, the technical idea of the present invention can be applied to a computer-readable recording medium containing a computer program for performing the functions of the apparatus and method according to the present embodiment. In addition, the technical idea according to various embodiments of the present disclosure may be implemented in the form of computer readable codes recorded on a computer readable recording medium. The computer-readable recording medium can be any data storage device that can be read by a computer and can store data. For example, the computer-readable recording medium may be a ROM, a RAM, a CD-ROM, a magnetic tape, a floppy disk, an optical disk, a hard disk drive, or the like. In addition, the computer-readable code or program stored in the computer-readable recording medium may be transmitted through a network connected between the computers.
또한, 이상에서는 본 발명의 바람직한 실시예에 대하여 도시하고 설명하였지만, 본 발명은 상술한 특정의 실시예에 한정되지 아니하며, 청구범위에서 청구하는 본 발명의 요지를 벗어남이 없이 당해 발명이 속하는 기술분야에서 통상의 지식을 가진자에 의해 다양한 변형실시가 가능한 것은 물론이고, 이러한 변형실시들은 본 발명의 기술적 사상이나 전망으로부터 개별적으로 이해되어져서는 안될 것이다.In addition, while the above has been shown and described with respect to preferred embodiments of the present invention, the present invention is not limited to the specific embodiments described above, the technical field to which the invention belongs without departing from the spirit of the invention claimed in the claims. Of course, various modifications can be made by those skilled in the art, and these modifications should not be individually understood from the technical spirit or the prospect of the present invention.

Claims (8)

  1. 제1 엔티티가, 제2 엔티티에 자신의 리소스를 생성하는 단계;Generating, by the first entity, its resources to the second entity;
    제2 엔티티가, 제1 엔티티의 리소스에 저장된 RR(Request Reachability)을 관리하는 단계;를 포함하는 것을 특징으로 하는 RR 관리 방법.And managing, by the second entity, Request Reachability (RR) stored in the resource of the first entity.
  2. 청구항 1에 있어서,The method according to claim 1,
    관리 단계는,The management phase is
    제1 엔티티의 PoA를 통해 요청 메시지 전송을 시도하고, 성공 여부에 따라 제1 엔티티의 리소스에 저장된 RR을 관리하는 것을 특징으로 하는 RR 관리 방법.Attempt to transmit a request message through the PoA of the first entity, and manages the RR stored in the resource of the first entity according to the success or failure.
  3. 청구항 2에 있어서,The method according to claim 2,
    관리 단계는,The management phase is
    RR이 TRUE인 경우, 제1 엔티티의 PoA 모두에 대해 요청 메시지 전송이 실패하면, RR을 FALSE로 변경하는 단계;를 포함하는 것을 특징으로 하는 RR 관리 방법.And when the RR is TRUE, changing the RR to FALSE if the request message transmission fails for all of the PoAs of the first entity.
  4. 청구항 2에 있어서,The method according to claim 2,
    관리 단계는,The management phase is
    RR이 FALSE인 경우, 제1 엔티티의 PoA들 중 적어도 하나에 대해 요청 메시지 전송이 성공하면, RR을 TRUE로 변경하는 단계;를 포함하는 것을 특징으로 하는 RR 관리 방법.If the RR is FALSE, if the request message transmission is successful for at least one of the PoAs of the first entity, changing the RR to TRUE.
  5. 청구항 2에 있어서,The method according to claim 2,
    제1 엔티티의 PoA 중 요청 메시지 전송에 실패한 PoA를 삭제하는 단계;를 더 포함하는 것을 특징으로 하는 RR 관리 방법.And deleting the PoA that failed to transmit the request message among the PoAs of the first entity.
  6. 청구항 2에 있어서,The method according to claim 2,
    제1 엔티티의 PoA 중 요청 메시지 전송에 실패한 PoA의 순서를 뒤로 변경하는 단계;를 더 포함하는 것을 특징으로 하는 RR 관리 방법.And changing the order of PoAs that fail to transmit the request message back to the PoA of the first entity.
  7. 청구항 2에 있어서,The method according to claim 2,
    제1 엔티티의 PoA 중 요청 메시지 전송에 성공한 PoA의 순서를 앞으로 변경하는 단계;를 더 포함하는 것을 특징으로 하는 RR 관리 방법.And forward changing the order of PoAs that have successfully transmitted the request message among PoAs of the first entity.
  8. 제1 엔티티가 설치된 외부 전자기기와 통신하는 통신부;A communication unit communicating with an external electronic device on which the first entity is installed;
    제1 엔티티의 리소스가 생성된 제2 엔티티가 설치되어 있으며, 제2 엔티티로 제1 엔티티의 리소스에 저장된 RR(Request Reachability)을 관리하는 프로세서;를 포함하는 것을 특징으로 하는 RR 관리 시스템.And a processor configured to install a second entity in which a resource of the first entity is generated, and manage a request reachability (RR) stored in the resource of the first entity as the second entity.
PCT/KR2018/006222 2018-05-31 2018-05-31 Method for managing request reachability in m2m platform WO2019231020A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/KR2018/006222 WO2019231020A1 (en) 2018-05-31 2018-05-31 Method for managing request reachability in m2m platform

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/KR2018/006222 WO2019231020A1 (en) 2018-05-31 2018-05-31 Method for managing request reachability in m2m platform

Publications (1)

Publication Number Publication Date
WO2019231020A1 true WO2019231020A1 (en) 2019-12-05

Family

ID=68698270

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2018/006222 WO2019231020A1 (en) 2018-05-31 2018-05-31 Method for managing request reachability in m2m platform

Country Status (1)

Country Link
WO (1) WO2019231020A1 (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20140099663A (en) * 2013-02-04 2014-08-13 주식회사 케이티 Method and Apparatus of resource management of M2M network
KR20160130306A (en) * 2014-03-18 2016-11-10 지티이 코포레이션 Resource and attribute management in machine to machine networks
KR20170033267A (en) * 2014-07-21 2017-03-24 엘지전자 주식회사 Method for processing request message in wireless communication system and apparatus therefor
KR101842830B1 (en) * 2017-03-29 2018-03-28 전자부품연구원 Request Reachability Management Method on M2M platform
KR20180038988A (en) * 2016-10-07 2018-04-17 주식회사 케이티 Methods for forwarding a request message in Machine to Machine communication system and Apparatuses thereof

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20140099663A (en) * 2013-02-04 2014-08-13 주식회사 케이티 Method and Apparatus of resource management of M2M network
KR20160130306A (en) * 2014-03-18 2016-11-10 지티이 코포레이션 Resource and attribute management in machine to machine networks
KR20170033267A (en) * 2014-07-21 2017-03-24 엘지전자 주식회사 Method for processing request message in wireless communication system and apparatus therefor
KR20180038988A (en) * 2016-10-07 2018-04-17 주식회사 케이티 Methods for forwarding a request message in Machine to Machine communication system and Apparatuses thereof
KR101842830B1 (en) * 2017-03-29 2018-03-28 전자부품연구원 Request Reachability Management Method on M2M platform

Similar Documents

Publication Publication Date Title
EP2797295B1 (en) Network address translation method, device and system
US10958725B2 (en) Systems and methods for distributing partial data to subnetworks
US6119121A (en) Method of maintaining login service parameters
WO2010074512A2 (en) System and method for supporting network mobility based on identifier-locator separation
WO2012086916A1 (en) Cloud computing system, traffic distribution method, and method for controlling same
CN111885046B (en) Linux-based transparent intranet access method and device
WO2019198885A1 (en) Decentralized service platform using multiple blockchain-based service nodes
CN111327668A (en) Network management method, device, equipment and storage medium
WO2012033283A2 (en) Method and apparatus for sharing wireless data service
CN112333733B (en) Network connection establishing method and electronic equipment
WO2020085528A1 (en) Subscription expiration management method and m2m system employing same
WO2019231020A1 (en) Method for managing request reachability in m2m platform
CN111885031A (en) Fine-grained access control method and system based on session process
CN107342972B (en) Method and device for realizing remote access
EP2673714A1 (en) Method and apparatus for managing content in a processing device
WO2019168219A1 (en) Method for semantic resource search in m2m system
WO2015182873A1 (en) Dns server selective block and dns address modification method using proxy
KR101842830B1 (en) Request Reachability Management Method on M2M platform
KR101703491B1 (en) Method for providing security service in cloud system and the cloud system thereof
WO2024005565A1 (en) Method, system, and non-transitory computer-readable recording medium for providing messenger service
WO2015037911A1 (en) Method, device, system and computer-readable recording medium for supporting communication between user terminal device and local host by using open flow
WO2023287002A1 (en) Method and system for managing address for application in lisp-based distributed container virtualization environment
WO2019022584A1 (en) Cross-resource subscription management method
WO2021080110A1 (en) System and method for managing and identifying affiliation of terminal in cloud environment
WO2022107931A1 (en) Data storage method for preventing data redundancy, and data platform using same

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: 18921072

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18921072

Country of ref document: EP

Kind code of ref document: A1