[go: up one dir, main page]

WO2018066926A1 - Procédé de transmission de message de demande dans un système m2m, et appareil associé - Google Patents

Procédé de transmission de message de demande dans un système m2m, et appareil associé Download PDF

Info

Publication number
WO2018066926A1
WO2018066926A1 PCT/KR2017/010961 KR2017010961W WO2018066926A1 WO 2018066926 A1 WO2018066926 A1 WO 2018066926A1 KR 2017010961 W KR2017010961 W KR 2017010961W WO 2018066926 A1 WO2018066926 A1 WO 2018066926A1
Authority
WO
WIPO (PCT)
Prior art keywords
request message
response type
parameter
type parameter
response
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/KR2017/010961
Other languages
English (en)
Korean (ko)
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.)
KT Corp
Original Assignee
KT Corp
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
Priority claimed from KR1020170059520A external-priority patent/KR20180039551A/ko
Priority claimed from KR1020170063937A external-priority patent/KR20180039552A/ko
Application filed by KT Corp filed Critical KT Corp
Publication of WO2018066926A1 publication Critical patent/WO2018066926A1/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
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications

Definitions

  • MOT typically does not directly perform communication and application control
  • a procedure for transmitting and receiving response information may be set differently for each MTC device or for each request message, a specific procedure for receiving the response information is not disclosed at all according to the transmission and reception procedure of the MTC device transmitting the request message. . Therefore, there is a problem in that an error may occur due to a difference in procedures in transmitting and receiving information between different MTC devices having different message transmission / reception procedures.
  • the present embodiment devised in the above-described background proposes a specific method and apparatus for setting a response type parameter so that no error occurs in the process of receiving and transmitting a request message by the M2M device.
  • FIG. 5 is a diagram illustrating a resource handling procedure for a request message.
  • Application Entity (AE) 110 provides application logic for an end-to-end M2M solution.
  • it may be a collective tracking application such as a vehicle, a remote blood sugar monitoring application, or a remote power metering and controlling application.
  • Application Entity provides Application logic for the end-to-end M2M solutions.Examples of the Application Entities can be fleet tracking application, remote blood sugar monitoring application, or remote power metering and controlling application.
  • the common service entity (CSE) 120 is a set of service functions, and these service functions are functions commonly used in an M2M environment. This service function is exposed to other functions through Reference Points Mca and Mcc, and uses the base network service using the reference point Mcn.
  • the originator 300 proceeds with the general procedure for receiving the response message according to the response message processing procedure of each receiver 310 (S330). For example, the originator 300 may check the response type parameter of the request message and receive the response message in a different procedure for each response type parameter.
  • the delivery M2M device 601 transmits a request message to the hosting M2M device at a predetermined period or at a designated time since the hosting M2M device 602 selects a response type as synchronous nonblocking (S755).
  • the hosting M2M device 602 transmits a response message to the request message (S760).
  • the delivery M2M device 601 updates the request resource using the content of the response message received from the hosting M2M device 602 (S765).
  • the hosting M2M device 602 performs a designated operation using the parameters of the received request message and updates the request resource (S850).
  • the delivery M2M device and the hosting M2M device may select different response type parameters. This will be described with reference to FIGS. 9 and 10.
  • the delivery M2M device 601 passes the error according to the time delay to the originator 600 after a predetermined time elapses (S1170).
  • the M2M device may determine the response type parameter according to whether the non-blocking response type is supported. If the M2M device does not support the non-blocking response scheme, the response type parameter may be determined as either blocking or flex blocking.
  • the flex blocking may be limited so that the notification target is set to be excluded.
  • the response status code value may be used to indicate rejection of the request message.
  • Table 2 is a table illustrating an example in which a FLEX_BLOCKIG_REQUEST_NOT_SUPPORTED error code is added to the response status code for the check operation of FIG. 15.
  • 16 is a diagram for describing a configuration of an M2M device according to another embodiment.
  • the controller 1610 may determine a response type parameter according to whether an asynchronous message can be received. If the M2M device cannot receive the asynchronous message, the controller 1610 may determine the response type parameter by any one of blocking, synchronous nonblockingRequestSynch, and flexBlocking.
  • the flex blocking may be limited so that the notification target is set to be excluded.
  • the transmitter 1620 and the receiver 1630 are used to transmit and receive signals, messages, and data necessary to perform the above-described embodiments with the originator or other M2M device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne une technique de communication de machine à machine (M2M) et, plus précisément, un procédé de traitement d'un procédé de communication de blocage de flexibilité pour une gestion de ressource efficace dans une CSE de récepteur. Un mode de réalisation concerne un appareil et un procédé, consistant : à recevoir, au moyen d'un appareil de communication de machine à machine (M2M), un message de demande ; à identifier un paramètre de type de réponse correspondant au message de demande ; et à déterminer un paramètre de type de réponse conformément au paramètre de type de réponse, le paramètre de type de réponse étant réglé à un blocage de flexibilité.
PCT/KR2017/010961 2016-10-07 2017-09-29 Procédé de transmission de message de demande dans un système m2m, et appareil associé Ceased WO2018066926A1 (fr)

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
KR20160129590 2016-10-07
KR10-2016-0129590 2016-10-07
KR10-2017-0059520 2017-05-12
KR1020170059520A KR20180039551A (ko) 2016-10-07 2017-05-12 Receiver CSE에서 효율적인 자원관리 위해 flexBlocking communication method를 처리하는 방법
KR10-2017-0063937 2017-05-24
KR1020170063937A KR20180039552A (ko) 2016-10-07 2017-05-24 Receiver CSE에서 효율적인 자원관리 위해 flexBlocking communication method를 처리하는 방법
KR1020170126022A KR101913965B1 (ko) 2016-10-07 2017-09-28 M2m 시스템에서 요청 메시지를 전달하는 방법 및 그 장치
KR10-2017-0126022 2017-09-28

Publications (1)

Publication Number Publication Date
WO2018066926A1 true WO2018066926A1 (fr) 2018-04-12

Family

ID=61831817

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/010961 Ceased WO2018066926A1 (fr) 2016-10-07 2017-09-29 Procédé de transmission de message de demande dans un système m2m, et appareil associé

Country Status (1)

Country Link
WO (1) WO2018066926A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015069038A1 (fr) * 2013-11-08 2015-05-14 엘지전자 주식회사 Procédé d'abonnement et de notification dans un système de communication m2m et dispositif associé
WO2016109967A1 (fr) * 2015-01-08 2016-07-14 华为技术有限公司 Procédé et dispositif de communication dans un système de machine à machine
US20160294886A1 (en) * 2013-11-26 2016-10-06 Zte Corporation Registration Method and System for Common Service Entity

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015069038A1 (fr) * 2013-11-08 2015-05-14 엘지전자 주식회사 Procédé d'abonnement et de notification dans un système de communication m2m et dispositif associé
US20160294886A1 (en) * 2013-11-26 2016-10-06 Zte Corporation Registration Method and System for Common Service Entity
WO2016109967A1 (fr) * 2015-01-08 2016-07-14 华为技术有限公司 Procédé et dispositif de communication dans un système de machine à machine

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"OneM2M Functional Architecture Baseline Draft", ONEM2M TECHNICAL SPECIFICATION, 6 August 2014 (2014-08-06), XP055224265, Retrieved from the Internet <URL:http://ftp.onem2m.org/Deliverables/20140801_Candidate> *
PRO-2016-0012-FLEXBLOCKING. PRO#21, ONEM2M, 12 January 2016 (2016-01-12), XP084014631, Retrieved from the Internet <URL:URL=http://member.onem2m.org/Application/documentapp/downloadimmediate/default.aspx?docID=15152> *

Similar Documents

Publication Publication Date Title
WO2018034494A1 (fr) Procédé et dispositif de partage d&#39;événement d&#39;utilisateur entre des chatbots (agents conversationnels)
KR102033999B1 (ko) 컨텐트 중심 네트워크에서의 통신 방법 및 장치
WO2019194536A1 (fr) Procédé et appareil pour fournir un service de réseau de données de zone locale sur la base d&#39;un modèle de non abonnement dans un système de communication sans fil
WO2017176013A1 (fr) Procédé pour traiter une requête d&#39;accès provenant d&#39;un équipement utilisateur (ue), et nœud de réseau
WO2018236136A1 (fr) Procédé et système de pull printing utilisant un serveur en nuage
WO2021141291A1 (fr) Procédé et appareil de collecte de trafic réseau dans un système de communication sans fil
WO2016195199A1 (fr) Procédé de traitement de requête par un canal d&#39;interrogation dans un système de communication sans fil et appareil associé
WO2019054779A1 (fr) Dispositif electronique pour traitement de message et procédé de fonctionnement de celui-ci
WO2016032291A1 (fr) Procédé et appareil pour transmettre et recevoir des données en référence croisée à des applications associées
WO2014077533A1 (fr) Station de base et pluralité de nœuds membres pour transmettre et recevoir un trafic multidiffusion basé sur le codage de réseau
WO2019235813A1 (fr) Dispositif électronique prenant en charge de multiples protocoles de communication sans fil et son procédé
WO2020036429A1 (fr) Procédé et appareil de gestion d&#39;une connexion de session de pdu
WO2014035194A1 (fr) Système et procédé de service de messages push
WO2018008831A1 (fr) Système de service de diffusion de village utilisant un réseau de communication et procédé à cet effet
WO2013183818A1 (fr) Procédé et système pour un service de messagerie dans un environnement à plusieurs dispositifs, et appareil associé
WO2015199271A1 (fr) Procédé et système de partage de fichiers sur p2p
WO2018066926A1 (fr) Procédé de transmission de message de demande dans un système m2m, et appareil associé
WO2018236137A1 (fr) Procédé de traitement de message de requête dans un système m2m et dispositif associé
WO2012150778A2 (fr) Procédé et un appareil de gestion d&#39;une connexion entre des objets de communication basée sur un événement de confirmation d&#39;état de connexion
KR101913965B1 (ko) M2m 시스템에서 요청 메시지를 전달하는 방법 및 그 장치
WO2012108678A2 (fr) Appareil et procédé de réglage de disposition relative à un partage de document
WO2018066917A1 (fr) Procédé de réception d&#39;un message de réponse dans un système m2m et dispositif associé
WO2018236179A1 (fr) Procédé de traitement de message dans un système m2m, et dispositif associé
WO2013172625A1 (fr) Procédé pour faire fonctionner un dispositif de serveur infonuagique, procédé pour faire fonctionner un dispositif client, et dispositif client
WO2015088268A1 (fr) Procédé de traitement de défaillance de dispositif de réseau dans un environnement de réseautage défini par logiciel (sdn)

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 31/07/2019)

122 Ep: pct application non-entry in european phase

Ref document number: 17858720

Country of ref document: EP

Kind code of ref document: A1