WO2015046960A1 - M2m 시스템에서 통지 메시지 전달 방법 및 이를 위한 장치 - Google Patents
M2m 시스템에서 통지 메시지 전달 방법 및 이를 위한 장치 Download PDFInfo
- Publication number
- WO2015046960A1 WO2015046960A1 PCT/KR2014/009041 KR2014009041W WO2015046960A1 WO 2015046960 A1 WO2015046960 A1 WO 2015046960A1 KR 2014009041 W KR2014009041 W KR 2014009041W WO 2015046960 A1 WO2015046960 A1 WO 2015046960A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- resource
- notification message
- receiving device
- subscription
- notification
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/62—Establishing a time schedule for servicing the requests
-
- 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]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/12—Setup of transport tunnels
Definitions
- the present invention relates to a machine-to-machine communication system, and more particularly, to a method and apparatus for subscribing and notifying a specific resource in an M2M system.
- M2M communication refers to communication performed between a machine and a machine without human intervention, and is also referred to as machine type communication (MTC) or internet of things (IoT) communication.
- MTC machine type communication
- IoT internet of things
- a terminal used for M2M communication is referred to as an M2M device, which is generally low mobility, time tolerant or delay tolerant, and small data transmission. It is used in connection with M2M server that centrally stores and manages communication information between machines.
- M2M device when the M2M device is connected according to different communication methods, the M2M device and the M2M server are connected through the M2M gateway in a section in which the communication method is changed, thereby forming the entire M2M system.
- services such as tracking, power metering, automatic payment system, medical service, and remote control may be provided.
- the present invention relates to an M2M system.
- Another object of the present invention is to provide a method and apparatus for transmitting and receiving a notification message in an environment in which connection status between entities is not guaranteed in an M2M system.
- Another object of the present invention is to provide a method and apparatus for improving data transmission efficiency and overall system performance by not transmitting unnecessary notification messages in an M2M system.
- a method of performing a notification for a resource subscription (resource subscription) in a machine-to-machine device (M2M) includes a subscription target including a subscription resource as a child resource Detecting a change in resource; Generating a notification message including a value indicating an event category of the change according to second attribute information set in the subscription resource; And determining the reachability to the receiving device based on the scheduling information set in the scheduling resource for the M2M device and the scheduling information set in the scheduling resource for the receiving device.
- the notification message When it is determined that it is reachable, the notification message is immediately sent to the receiving device, and when it is determined that the receiving device is not reachable according to the scheduling information, the notification message indicates that the first attribute information set in the subscription resource is determined.
- the processed notification message may be transmitted to the receiving device after the receiving device recovers to an reachable state according to a value having a value.
- a Machine-to-Machine (M2M) device comprising: a Network Interface Unit; And a processor operatively connected with the network interface unit, the processor detecting a change in a subscription target resource including a subscription resource as a child resource, and according to the second attribute information set in the subscription resource.
- M2M Machine-to-Machine
- a notification message including a value indicating the event category of the change and reachability to the receiving device based on the scheduling information set in the scheduling resource for the M2M device and the scheduling information set in the scheduling resource for the receiving device And if the receiving device is determined to be reachable according to the scheduling information, the notification message is immediately sent to the receiving device, and if the receiving device is determined to be unreachable according to the scheduling information.
- the notification message may be processed in the M2M device according to a value of the first attribute information set in the subscription resource, and the processed notification message may be transmitted to the receiving device after the receiving device recovers to an reachable state.
- each of the subscription resource and the scheduling resource may represent a uniquely addressable data structure using a unique address.
- said second attribute information defines an event category for said notification message triggered by said subscription resource, and a value indicating an event category included in said notification message indicates that said receiving device correctly identifies said notification message. It can be used to handle.
- the first attribute information may indicate a processing operation of a notification message to be performed by the M2M device after a time interval that is not reachable to the receiving device according to the scheduling information.
- processing the notification message is equivalent to discarding the generated notification message if the first attribute information has a first value.
- the first attribute information has a second value, storing the generated notification message and discarding a previously stored notification message; and when the first attribute information has a third value, the generated notification message. It may include storing all.
- the receiving device may be determined to be reachable.
- the receiving device may be determined to be unreachable.
- a notification message can be transmitted and received in an environment in which the connection state between entities is not guaranteed in the M2M system.
- data transmission efficiency and overall system performance can be improved by not transmitting unnecessary notification messages in the M2M system.
- the present invention it is possible to preferentially transmit the important message set by the user by enabling the importance of the notification message to be set in the M2M system.
- FIG. 2 illustrates a layered structure of an M2M system.
- FIG. 3 illustrates a functional architecture of an M2M system.
- FIG. 5 illustrates a resource used in an M2M system.
- FIG. 6 illustrates a resource for a particular M2M application.
- FIG. 7 illustrates a communication flow of a typical M2M system.
- FIG 8 illustrates an example in which different entities interoperate in an M2M system.
- FIG. 9 illustrates a procedure related to a subscription resource.
- 11 and 12 illustrate the subscription and notification process in an environment where the connection state is not guaranteed.
- 13 through 16 illustrate a notification method according to notification policy information.
- FIG 17 illustrates a notification process in accordance with the present invention.
- FIG. 18 illustrates an embodiment of a notification process in accordance with the present invention.
- FIG. 19 illustrates a block diagram of an apparatus to which the present invention can be applied.
- an M2M device refers to a device for machine-to-machine communication.
- the M2M device may be fixed or mobile and may communicate with the M2M server to send and receive user data and / or control information.
- M2M devices may include a terminal equipment, a mobile station (MS), a mobile terminal (MT), a user terminal (UT), a subscriber station (SS), a wireless device, a personal digital assistant (PDA), and a wireless modem ( wireless modem, handheld device, and the like.
- the M2M server refers to a server for M2M communication and may be implemented as a fixed station or a mobile station.
- the M2M server may communicate with M2M devices and / or other M2M servers to exchange data and control information.
- the M2M gateway refers to a device that serves as a connection point for entering a network from one network to another when the network to which the M2M device is connected and the network to which the M2M server is connected are different.
- the M2M gateway may perform a function as an M2M device, for example, manage an M2M device connected to the M2M gateway, receive a message, and deliver the same or changed message to the connected M2M devices (message fanout). ), A function of message aggregation may be performed.
- the term M2M device may be used as a concept including an M2M gateway and an M2M server, and thus, the M2M gateway and the M2M server may be referred to as an M2M device.
- entity can be used herein to refer to hardware such as an M2M device, an M2M gateway, an M2M server, or software of the M2M application layer and the M2M (common) service layer described below. It may be used to refer to a software component.
- the present invention will be described with reference to the M2M system, but the present invention is not limited to the M2M system, and the same applies to a system according to a client-server (or sender-responder) model. Similarly it can be applied.
- FIG. 1 illustrates an M2M system.
- 1 illustrates an M2M system according to the European Telecommunications Standards Institute (ETSI) Technical Specification (TS).
- ETSI European Telecommunications Standards Institute
- TS Technical Specification
- the M2M system according to the ETSI TS M2M technical standard defines a common M2M service framework for various M2M applications.
- An M2M application may refer to a software component that implements an M2M service solution such as e-Health, City Automation, Connected Consumer, or Automotive.
- M2M service functions necessary in common for implementing such various M2M applications are provided, and the functions commonly required may be referred to as M2M service or M2M common service.
- the M2M service is provided in the form of a set of Service Capabilities (SC), and the M2M application accesses a set of Service Capabilities (SCs) or a Service Capability (SC) through an open interface. You can use M2M service or function provided by.
- the SC can provide the capabilities to configure M2M services (eg device management, location, discovery, group management, registration, security, etc.), and the SC Layer (Service Capabilities Layer) or SC Entity (Service Capability Entity) A set of functions for M2M services that can be used when provided on this service framework.
- SC Service Capability
- x may be expressed as one of N / G / D, and indicates where SC (Service Capability) exists among a network (and / or a server), a gateway, and a device.
- NSC Service Capability
- GSC Service Capability
- M2M applications can reside on a network, gateway, or device.
- An M2M application present on a network or directly connected to a server is referred to as an M2M network application and may be briefly referred to as a network application (NA).
- NA is software that is implemented by connecting directly to a server and may be responsible for communicating with and managing an M2M gateway or M2M device.
- the M2M application existing on the device is referred to as an M2M device application and may be briefly referred to as a device application (DA).
- the DA is software running on the M2M device, and may transmit sensor information and the like to the NA.
- the M2M application existing on the gateway is referred to as an M2M gateway application and may be briefly referred to as a gateway application (GA).
- the GA may also serve to manage an M2M gateway and provide DA with M2M services or capabilities (eg, Service Capabilities (SCs) or Service Capability (SC)).
- M2M application may collectively refer to an application entity (AE) and an application layer.
- an M2M system architecture may be divided into a network domain, a device, and a gateway domain.
- the network domain may include functions for M2M system management and functions for network management. Functions for M2M system management may be performed by M2M applications and M2M Service Capabilities (SCs) that manage devices existing in the device and gateway domains, and functions for network management may be performed by the core network and the access network. have.
- SCs M2M Service Capabilities
- the core network and access network provide connectivity between each entity rather than perform M2M functions.
- M2M communication can be performed between M2M Service Capabilities (M2M SCs) in the network domain and device and gateway domains through the core network and the access network, and M2M applications in each domain can receive signals or information through M2M Service Capabilities (SCs) in each domain. Can give and receive.
- M2M SCs M2M Service Capabilities
- SCs M2M Service Capabilities
- An access network is an entity that allows M2M devices and gateway domains to communicate with the core network.
- Examples of access networks include xDSL (Digital Subscriber Line), Hybrid Fiber Coax (HFC), satellite, GERAN, UTRAN, eUTRAN, Wireless LAN, WiMAX, and the like.
- a core network is an entity that provides functions such as Internet Protocol (IP) connectivity, service and network control, interconnection, and roaming.
- Core networks include 3rd Generation Partnership Project (3GPP) core networks, ETSI Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) core networks, and 3GPP2 core networks.
- 3GPP 3rd Generation Partnership Project
- TISPAN Internet converged Services and Protocols for Advanced Networking
- M2M Service Capability provides the M2M Common Service Function (CSF), which can be shared among multiple M2M network applications, and exposes M2M services through an open interface, allowing M2M applications to access M2M services. Make it available.
- the M2M Service Capability Layer may refer to a layer including such M2M SC entities or M2M common service functions.
- An M2M application is an entity that operates service logic and can use M2M SCs (Service Capabilities) through an open interface.
- An M2M application layer may refer to a layer that contains such M2M application and associated operational logic.
- the M2M device is an entity that operates an M2M device application through M2M SCs (Service Capabilities).
- the M2M device may directly communicate with an M2M server in a network domain, or may communicate with an M2M server in a network domain through an M2M gateway. When connected through an M2M gateway, the M2M gateway acts like a proxy.
- the M2M device may include an M2M application and / or M2M SCs (Service Capabilities).
- An M2M area network provides connectivity between M2M devices and M2M gateways.
- the network between the M2M gateway and the M2M server and the network between the M2M device and the M2M gateway may be different from each other.
- M2M area networks include Personal Area Network (PAN) technologies such as IEEE802.15.1, Zigbee, Bluetooth, IETF ROLL, ISA100.11a, Power Line Communication (M-BUS), Wireless It can be implemented using local network technologies such as M-BUS and KNX.
- PAN Personal Area Network
- M-BUS Power Line Communication
- the M2M gateway is an entity that manages M2M applications and provides services for M2M applications through M2M SCs (Service Capabilities).
- the M2M gateway may serve as a proxy between the M2M device and the network domain and provide a service to an ETSI non-compliant M2M device.
- the M2M gateway may refer to an entity having a gateway function among M2M devices.
- the M2M gateway may include M2M applications and / or M2M SCs (Service Capabilities).
- the M2M system architecture illustrated in FIG. 1 is merely an example and the names of each entity may be different.
- the M2M Service Capability (SC) may be referred to as an M2M common service function (CSF)
- the Service Capability Layer (SCL) may be a common service layer (CSL) or a common service entity (CSL).
- Common Service Entity (CSE)
- an M2M application may be referred to as an application entity (AE), and the M2M application layer may be referred to simply as an application layer.
- the name of each domain may also vary.
- a network domain may be referred to as an infrastructure domain and a device and gateway domain may be referred to as a field domain.
- an M2M system may be understood as a hierarchical structure including an M2M application layer and an M2M Service Capability (SC) layer for M2M communication.
- SC M2M Service Capability
- FIG. 2 illustrates a layered structure of an M2M system.
- an M2M system may include an application layer 202, a common service layer 204, and an underlying network services layer 206.
- the application layer 202 may correspond to the M2M application layer
- the common service layer 204 may correspond to the M2M SCL.
- the underlying network service layer 206 provides services to the common service layer 204, such as device management, location services, and device triggering, present in the core network.
- the M2M system architecture includes an application entity (AE) 302, a common service entity (CSE) 304, an underlying network service entity (NSE) 306. ) May be included.
- Each entity 302, 304, 306 may communicate via a reference point supported by the common service entity 304.
- the reference point serves to specify a communication flow between the entities 302, 304, and 306.
- the reference point can be expressed as Mcx and Mc means “M2M communications”.
- Mca reference point, the Mcc reference point, and the Mcn reference point may be denoted as Mca, Mcc, and Mcn, respectively.
- the Mca reference point 312 specifies the communication flow of the application entity (AE) 302 and the common service entity (CSE) 304.
- the Mca reference point 312 enables the AE 302 to use the services provided by the CSE 304 and allows the CSE 304 to communicate with the AE 302.
- the Mca reference point 312 may refer to an interface between the M2M application layer and the M2M common service layer (or entity).
- the Mcc reference point 314 specifies the flow of communication between different common service entities (CSEs) 304.
- CSEs common service entities
- the Mcc reference point 314 allows the CSE 304 to use the services of another CSE when providing the necessary functions. Services provided via the Mcc reference point 314 may depend on the functions supported by the CSE 304.
- the Mcc reference point 314 may refer to an interface between M2M common service layers.
- Mcn reference point 316 specifies the communication flow between the CSE 304 and the underlying network service entity (NSE) 306. Mcn reference point 316 enables CSE 304 to use the services provided by underlying NSE 306 to provide the required functions. Mcn reference point 316 may refer to an interface between the M2M common service layer and the M2M underlying network layer.
- the CSE 304 may provide various common service functions (CSFs).
- CSFs common service functions
- the CSE 304 may include application and service layer management functions, communication management and delivery handling functions, data management and storage functions, devices, and the like.
- Device Management Function Group Management Function, Discovery Function, Location Function, Network Service Exposure / Service Execution and Triggering Function, Registration ), A security function, a service charging and accounting function, a service session management function, and a subscription / notification function.
- CSE 304 points to an instance of the common service functions and provides a subset of common service functions that M2M applications can use and share.
- the common service functions are briefly described as follows.
- ASM Application and Service Layer Management
- CMDH Communication Management and Delivery Handling
- DMR Data Management and Repository
- DMG Device Management: Manages device functions for devices existing in M2M area networks as well as M2M gateways and M2M devices.
- the DMG function can perform application installation and configuration, firmware update, logging, monitoring, diagnostics, and network topology management.
- Discovery, DIS searches for information, such as information and resources, on request within a given range and condition.
- GMG Group Management
- a group may be created by binding a resource, an M2M device, or an M2M gateway to handle a group related request.
- the M2M application plays a role of obtaining location information of the M2M device or the M2M gateway.
- Network Service Exposure / Service Execution and Triggering Enables communication of the underlying network and enables the use of services or features provided by the underlying network.
- Registration An M2M application or other CSE handles registration to a specific CSE. Registration is performed to use the M2M service function of a specific CSE.
- SEC Handles sensitive data such as security keys, establishes security associations, authenticates, authorizes, and protects identity.
- SCA Service Charging and Accounting
- SSM Service Session Management
- Subscription / Notification When a subscription is made to a change to a specific resource, it plays a role of notifying when the resource is changed.
- a node refers to an entity including one or more M2M applications or an entity including one CSE and zero or more M2M applications.
- An application dedicated node may refer to a node having at least one application entity (AE) but no common service entity (CSE).
- the ADN may communicate with one middle node (MN) or one infrastructure node (IN) through Mca.
- MN middle node
- I infrastructure node
- ADN may be referred to as an M2M device having a constrained capability, where an M2M device with limited capabilities does not include a common service layer or a common service entity (CSE). May be referred to.
- An M2M device with limited capabilities may be referred to simply as a constrained M2M device.
- An application service node may refer to a node having at least one common service entity (CSE) and at least one M2M application entity (AE).
- CSE common service entity
- AE M2M application entity
- the ASN may communicate with one middle node or one infrastructure node through Mcc.
- Mcc common service entity
- ASN may be referred to as an M2M device.
- a middle node may refer to a node having one common service entity (CSE) and zero or more M2M application entities (AEs).
- CSE common service entity
- AEs M2M application entities
- the MN can communicate with one infrastructure node (IN) or another intermediate node (MN) via Mcc, can communicate with IN / MN / ASN via Mcc, or can communicate with ADN via Mca. have.
- MN may be referred to as M2M gateway.
- An infrastructure node may refer to a node having one common service entity (CSE) and zero or more application entities (AEs).
- the IN may communicate with at least one intermediate node (MN) via Mcc and / or may communicate with at least one ASN.
- the IN may communicate with one or more ADN through Mca.
- IN may be referred to as an M2M server.
- Example 1 illustrates communication between ADN and IN.
- the ADN may be an M2M device with limited capabilities.
- the ADN since the ADN does not have a CSE or a common service layer, the ADN may communicate with the CSE of the IN through Mca. Also, in this case, since the ADN does not have a CSE or common service layer, data generated at the AE or application layer cannot be stored / shared to another entity. Thus, in Example 1, data generated at the AE or the application layer of the ADN may be stored and shared in the CSE of the IN.
- Example 2 illustrates the communication between ADN and MN.
- ADN can also be an M2M device with limited capabilities.
- ADN may operate similarly to Example 1 except that the ADN communicates with the CSE of the MN. That is, the ADN may communicate with the CSE of the MN through the Mca.
- ADN since ADN does not have a CSE or common service layer, data generated at the AE or application layer cannot be stored / shared to other entities. Therefore, data generated at the AE or the application layer of the ADN may be stored and shared in the CSE of the MN.
- the MN may communicate with the IN via the MN.
- MN and MN, and MN and IN can communicate through Mcc. It is also possible for the MN to communicate with IN directly without passing through the MN.
- Example 3 illustrates the communication between ASN and MN. Unlike example 1 or example 2, since the ASN has a CSE or common service layer, data generated at the AE or application layer of the ASN can be stored in its CSE or common service layer. In addition, the AE of the ASN may communicate with the CSE of the MN through the CSE of the ASN.
- Example 4 illustrates the communication between ASN and MN.
- the CSE of the ASN can communicate with the CSE of the IN directly without going through the MN.
- the IN may be located in an infrastructure domain or a network domain and may include one CSE and zero or more AEs.
- the INs can communicate with each other via Mcc.
- 5 illustrates a resource or resource used in an M2M system.
- an application entity a CSE, data, etc.
- a resource refers to a uniquely addressable entity using a unique address (eg, a Universal Resource Identifier or Uniform Resource Identifier (URI)).
- resources are represented as specific data structures, and each resource can be logically connected to each other. Resources may be managed and stored by the CSE or common service layer. Thus, the CSE or common service layer of the M2M device, the M2M gateway, the M2M server may have these resources.
- the AE or application layer of the M2M system may not have such a resource structure.
- Each resource has a child resource and attributes.
- a root resource may have an attribute and a child resource.
- resources can be represented as a tree structure.
- the type of the root resource may be represented as ⁇ baseURI> or ⁇ CSEBase>.
- the type of resource may be indicated by " ⁇ " and ">".
- M2M applications can communicate based on resources whose resource types are instantiated. For example, it can be used to perform M2M services such as registering an application and reading sensor values.
- Each resource is given unique address information (e.g. URI) when an instance of that resource type is created, and can have the same properties and child resources as the root resource.
- Each resource is addressed using unique address information.
- the specific resource type defines the child resources and attributes that the resource can have when instantiated. In a specific resource instantiation, a resource may have attributes and child resources defined in the resource type of the resource.
- Child resources can have their own attributes and their own child resources.
- child resources include remote CSE resources, application entity resources, access control resources, container resources, group resources, subscription resources, and so on.
- the remote CSE resource contains information of other CSEs registered (connected) to the CSE.
- the type of the remote CSE resource may be indicated as ⁇ entity> or ⁇ remoteCSE>.
- Application entity resources of the root resource e.g. ⁇ baseURI> / ⁇ application> or ⁇ CSEBase> / ⁇ AE>
- remote CSE resources of the root resource e.g. ⁇ baseURI> / ⁇ entity> or ⁇ CSEBase
- ⁇ remote CSE> e.g. ⁇ remote CSE>
- the information of the registered application entity is stored, and the information of the application entities registered in the specific remote CSE when it exists under the remote CSE resource (eg, ⁇ baseURI> / ⁇ entity> or ⁇ CSEBase> / ⁇ remote CSE>) of the root resource. Save it.
- the type of application entity resource may be indicated as ⁇ application> or ⁇ AE>.
- -Access Control Resource Resource that stores information related to access authority. Authorization may be performed using the access right information included in the resource.
- the type of access control resource may be represented as ⁇ accessRight> or ⁇ accessControlPolicy>.
- -Container resource Stores data generated for each CSE or AE.
- the type of container resource may be represented as ⁇ container>.
- -Group Resource Provides a function to group several resources together and process them together.
- the type of group resource may be indicated as ⁇ group>.
- -Subscription resource This function informs the status of resource change through notification.
- the type of the subscription resource may be indicated as ⁇ subscription>.
- resources for a specific M2M application may be stored in an Application Resource in a resource of a CSE or a common service layer of the M2M Gateway.
- Resources for a particular M2M application may have attributes and child resources similar to the entire resource.
- the child resource is defined as a type (eg, denoted by “ ⁇ ”, “>”), and the actual name is given and stored when materialized.
- FIG. 7 illustrates a communication flow of a typical M2M system.
- the operation of the M2M system is performed based on the data exchange.
- a specific device may transmit a corresponding command in the form of data to another device to stop the operation of another device.
- a specific type of data structure is used to store data in the device, which is called a resource. Resources can be accessed using unique addresses (eg URIs).
- a Request and Response Scheme is used in the connection between the AE and the CSE or in the connection between the CSEs.
- the originator may send a request message to request a resource stored in a receiver and receive a response message in response.
- the recipient may receive a message requesting a resource from the sender and send a response message to the sender in response.
- a request message may be abbreviated as a request and a response message may be abbreviated as a response.
- the request message transmitted from the sender to the receiver may include the following information.
- op the type of operation to be performed. It may be one of Create / Retrieve / Update / Delete / Notify.
- information corresponding to an operation may be referred to as a command.
- URI Uniform Resource Identifier
- the event category indicates the event category used to handle the request.
- the event category may affect how requests that access remote hosted resources will be handled at the recipient (eg, the recipient's CMDH CSF).
- the event category may indicate information indicating the importance of the caller request.
- the ec of the request message may be set to, for example, 'immediate', 'bestEffort', 'latest', and the like. If ec is set to 'immediate', requests in this category are sent as soon as possible because they represent important requests and no further CMDH processing is performed. For example, if communication over the underlying network is possible, these requests may be sent without being stored in the CMDH buffer.
- requests in this category may be stored in the CMDH buffer for any time at the discretion of the CSE and delivered on Mcc on a best effort basis. If ec is set to 'latest', requests in this category go through normal CMDH processing, and if requests are pending, older requests are replaced by recent requests within the maximum buffer size.
- the response message may include the following information.
- the response message may include at least one of the following information, or may include only the result value rs.
- identification information (or ID) of the originator that created the request
- rs the result of the request (e.g. Okay, Okay and Done, Okay and in progress)
- the response message may include the following information.
- a sender may refer to a sender device or sender entity (or CSE or AE therein), and a receiver may refer to a receiver device or receiver entity (or CSE or AE therein).
- an entity that relays a message transmitted from the originator device to the recipient device in the middle may be referred to as a relay device or a relay entity (or CSE therein).
- a device having a resource (or CSE therein) may be referred to as a hosting device or hosting entity (or hosting CSE).
- FIG 8 illustrates an example in which different entities interoperate in an M2M system.
- the M2M device may include a sensor that is a physical device, and the AE registered in the IN may read the sensor value of the M2M device.
- the AE (application1) existing on the M2M device reads the value from the sensor and stores the read value in the form of a resource (eg, ⁇ container> resource) in the CSE (dcse) registered by the sensor. To this end, the AE (application1) existing on the M2M device must first register with the CSE present in the M2M device. As illustrated in FIG. 8, when registration is completed, M2M application related information registered in the form of a dcse / applications / application1 resource is stored.
- a resource eg, ⁇ container> resource
- an AE application2 registered in an IN (Infrastructure Node) may access the value.
- AE application2 must be registered in the CSE (ncse) of the IN (Infrastructure Node) in order to access the M2M device. This is stored in the ncse / applications / application2 resource information about the AE (application2), such as how the AE (application1) is registered in the CSE (dcse).
- the AE (application1) may communicate directly with the intermediate CSE (ncse) and CSE (dcse) rather than directly communicating with the AE (application2).
- CSE (ncse) and CSE (dcse) must be mutually registered.
- CSE (dcse) registers with CSE (ncse) dcse related information (eg, Link) is stored under ncse / cses / dcse resource.
- the AE (application2) obtains a path for accessing the information of the AE (application1) and can read the value of the sensor through the corresponding path.
- FIG. 9 illustrates a procedure related to a subscription resource.
- an entity that is interested in a change of a resource according to a change of a resource may subscribe to a notification of the change.
- a resource for subscription in order to subscribe to the notification, a resource for subscription must be set.
- the resource for the subscription may be referred to as a subscription resource or a ⁇ subscription> resource.
- the device (or entity) for which a subscription resource is set up and / or containing a subscription target resource is referred to as a hosting device (or hosting entity).
- a subscription target resource may exist in the CSE of the M2M gateway.
- the M2M gateway may be referred to as a hosting device and the CSE of the M2M gateway may be referred to as a hosting CSE.
- the subscription resource may be used to perform a subscription procedure in a resource-oriented manner.
- a subscription resource can be created to subscribe to a specific subscription target resource, a subscription condition can be changed by modifying the subscription resource, and the subscription resource can be deleted when the subscription is no longer desired.
- the subscription resource includes information about subscribed-to resources.
- the relationship between the subscription target resource and the subscription resource may be expressed as a parent-child relationship.
- a ⁇ container> resource including a subscription target resource may have a ⁇ subscription> resource as a child resource.
- the parent subscription target resource is deleted, the ⁇ subscription> resource may be deleted.
- the subscription resource is a child resource
- an entity indicating a change in the status of the parent resource according to the configuration (attribute setting) of the subscription resource is specified in the address information (e.g., notificationURI or contact attribute) in the subscription resource. Can be passed to.
- the sender has a RETRIEVE (or READ) permission on a subscribeable resource, the sender may create a subscription resource.
- the sender of a subscription resource becomes a resource subscriber. If there is a modification to a subscription target resource, the modification is compared to a specific attribute (eg, notificationCriteria attribute) to determine whether a notification is sent to the resource subscriber.
- a specific attribute eg, notificationCriteria attribute
- Subscription resources can have various attributes and child resources.
- a subscription resource eg, a ⁇ subscription> resource
- R / W represents read / write permission of the property and may be one of READ / WRITE (RW), READ ONLY (RO), and WRITE ONLY (WO).
- Table 1 is only an example and the properties of the subscription resource may be configured differently from Table 1.
- the filtering attribute (eg, notificationCriteria) is a list of conditions for modification / change of the subscription target resource, and each condition may be in a logical AND relationship.
- the filtering attribute eg, notificationCriteria
- the filtering attribute includes two conditions
- a notification may be sent when the modification / change of the subscription target resource satisfies both conditions.
- the filtering attribute includes two conditions
- the amount of the notification message can be adjusted, and when the set filtering attribute is satisfied, the notification can be sent to the notification target entity, thereby preventing the notification message from overflowing.
- Table 2 illustrates the conditions that may be included in the filtering attribute.
- the subscription resource may have a scheduling resource (eg, ⁇ schedule>) resource including scheduling information as a child resource.
- a scheduling resource eg, ⁇ schedule>
- the scheduling resource represents scheduling information in the context of the parent resource.
- a scheduling resource (eg, ⁇ schedule>) defines reachability schedule information of a corresponding node.
- the scheduling resource is realized as a child resource of the subscription resource, it may be referred to as a notification scheduling resource (eg, notificationSchedule resource).
- a scheduling resource or a notification scheduling resource (eg, a ⁇ schedule> or notificationSchedule resource) may be referred to simply as a scheduling resource.
- the scheduling information set in the scheduling resource may indicate scheduling information for notification of the subscription resource. Scheduling information may be referred to herein as reachability schedule information.
- Reachable herein may refer to a state in which messages can be sent or received between nodes
- unreachable unreachable or non-reachable refers to a state in which messages cannot be sent or received between nodes. May be referred to.
- a particular node may be referred to as being in reachable mode when the particular node is in a reachable state.
- a particular node may be referred to as in an unreachable mode if the particular node is in an unreachable state.
- reachability schedule information may indicate the time at which message transmission and reception can occur between nodes.
- the connection state between nodes may be referred to as reachability.
- the scheduling resource may have various attributes.
- the scheduling resource may include attributes such as resource type, resourceID, parentID, expirationTime, creationTime, and lastModifiedTime (see Table 3).
- RW / RO / WO represents the read / write permission of the property and can be one of READ / WRITE (RW), READ ONLY (RO), and WRITE ONLY (WO). Can be.
- the frequency of occurrence indicates the number of times a corresponding attribute can occur in a ⁇ schedule> resource.
- Table 3 is only an example and the attributes of the scheduling resource may be configured differently from Table 3.
- the scheduling resource may include an attribute (eg, scheduleElement) for scheduling time information.
- the attribute for scheduling time information may represent a time defined by seconds, minutes, hours, days, months, years, etc., may represent a repetition of time, and may be expressed as a wildcard (eg '*'). have.
- the attribute for scheduling time information may indicate a time interval in which a specific node is in reachable mode or may indicate a time interval in which a specific node is in unreachable mode. For example, if the attribute for scheduling time information indicates a time interval in which a specific node is in reachable mode, the node may send and receive messages and connect with other nodes during the time interval specified in the attribute for scheduling time information. Can be in a state.
- an attribute for scheduling time information indicates a time interval in which a node is in an unreachable mode
- the node cannot transmit or receive a message during the time interval specified in the attribute for scheduling time information, and a connection with other nodes is not possible. May be in a missing state.
- device 1 910 may perform the procedure illustrated in FIG. 9 to subscribe to a specific resource of device 2 920.
- the device 1 910 may or may not be the target of notification of the change in the subscription target resource.
- a specific resource corresponds to a subscription target resource
- device 2 920 may correspond to a hosting device (or entity) because the device 2 920 includes a subscription target resource.
- the device 1 910 may transmit a request for a subscription resource to the device 2 920 to subscribe to a specific resource.
- the request for a subscription resource may be any one of a generation request, a collection request, a deletion request, and an update request of a subscription resource.
- Each request may have the form of a request message according to the request-response scheme described with reference to FIG. 7.
- the request for the subscription resource may include op information having C (Create), cn information including attribute information (eg, notificationURI, filterCriteria, expirationTime, etc.) of the subscription resource, and a device.
- the request for the subscription resource may include all or part of the information described with reference to FIG. 7.
- the device 2 920 processes the request if it can validate and process the request for the subscription resource. For example, when device 2 920 receives a creation request, whether the subscription target resource specified in the to information is available for subscription, and the request originator (eg, 910) has a RETRIEVE permission on the subscription target resource. Whether or not the address information (e.g. notificationURI) of the subscription resource does not point to the request originator (e.g. 910), the request originator (e.g. 910) notifies the entity or device specified in the address information (e.g. notificationURI) of the subscription resource.
- the address information e.g. notificationURI
- the host device or entity e.g., 920
- the subscription resource's address information e.g. notificationURI
- device 2 920 validates whether the request originator (eg, 910) has a DELETE permission, and if so, Delete a subscription resource.
- the request originator eg, 910
- the device 2 920 may process a request for a subscription resource, and then transmit a response message to the device 1 910.
- the response message of S906 may have the same / similar form as the response message described with reference to FIG. 7.
- the response message may include information to be returned.
- the sender may be a device or entity (eg, 920) that is hosting a subscription resource.
- the receiver may be a device (or entity) indicated by address information (eg, notificationURI) set in the subscription resource.
- Predetermined policy information may be set for the procedure for notification and the sender may be set to send a notification message (eg NOTIFY) when the policy information is satisfied.
- a notification message (eg NOTIFY) is a message triggered by a subscription resource.
- the notification message can be sent to the receiver indicated by the address information (eg, notificationURI) set in the subscription resource when the change of the subscription target resource including the subscription resource as a child resource satisfies the filtering attribute (eg, notificationCriteria) set in the subscription resource.
- the recipient of the notification message may be the same or different from the device or entity that created / set the subscription resource according to the setting of the subscription resource.
- device 1 910 may be the same entity as device 3 930 or may be a different entity.
- the notification message may include the following information.
- fr identification or ID of the sender (eg 920)
- Address information configured in the subscription resource e.g. notificationURI
- cn data indicating the modified content of the subscribed resource and / or subscription reference information (e.g., the URI of the subscription resource) and / or other additional information that generated this notification message.
- subscription reference information e.g., the URI of the subscription resource
- the sender 920 may detect / detect a change in a subscription target resource.
- the subscribed resource is the parent resource of the subscribed resource, and if a resource or attribute at the same level as the subscribed resource is modified / changed under the subscribed resource, the sender 920 (see, for example, SUB CSF or CSE FIG. 3) It can be recognized as a change of a subscription target resource.
- an event may be generated.
- step S1004 the sender 920 checks whether the change matches a specific attribute (eg, notificationCriteria) set in the subscription resource.
- the particular attribute may include, for example, at least one of the attributes illustrated in Table 2. If the change in the subscription target resource does not satisfy all of the conditions included in the filtering attribute, the sender 920 may ignore the change.
- the sender 920 transmits a notification message to the entity 930 indicated by address information (eg, notificationURI) set in the subscription resource.
- the notification message of S1006 may include, for example, identification information of the caller 920, data indicating a change of the subscription target resource, and / or subscription reference information that generated the notification message. If the change of the subscription target resource does not satisfy any of the conditions included in the filtering attribute, the sender 920 may not transmit the generated notification message.
- FIG. 11 illustrates a subscription and notification process in an environment where the connection state is not guaranteed.
- a subscription and notification process occurs in a situation composed of two entities (eg, entity 1 and entity 2).
- a subscription service may be performed as follows.
- Entity 2 performs a subscription process for a specific resource of entity 1 (eg, “Resource n”). Through this process, entity2 may set up a subscription resource for a specific resource of entity1 (eg, “resource n”).
- the entity 1 monitors a specific resource (eg, “resource n”) to which a subscription resource is set, and when a change occurs in the monitored resource, the entity 1 sends a notification message indicating the change of the entity. Can be sent to 2.
- a specific resource eg, “resource n”
- the notification message is transmitted to an address (eg, contact attribute in ETSI M2M, notificationURI attribute in oneM2M) set during the subscription process.
- an address eg, contact attribute in ETSI M2M, notificationURI attribute in oneM2M
- a connection state may not be guaranteed between entities due to a network failure, a device failure, a reachability schedule, or the like.
- Notification messages generated in such an environment may not be transmitted from an originator (eg, entity 1) to a receiver (eg, entity 2). Therefore, in the prior art, in order to process notification messages generated when the connection status is not guaranteed, the generated notification messages are temporarily stored in the originator as shown in Fig. 12, and then transmitted to the receiver when the connection is restored. Can be.
- FIG. 12 illustrates a method for sending messages to a recipient after a connection is recovered.
- notification 1 to notification n occurs in a state where the connection state is not guaranteed
- the caller returns a notification aggregation of the generated notification 1 to notification n. You can send to the receiver at once.
- the sender may transmit the generated notification 1 to notification n one by one to the receiver one by one. .
- notification messages sent after the connection is restored may not be needed at the receiver side.
- the connection between the entities was lost at a certain time (eg, 1 pm to 3 pm) and then the connection was restored.
- the data desired by the user at the time the connection is restored may be the latest data after 3 o'clock, or the data for the last 30 minutes.
- the user When using the method illustrated in FIG. 12, the user must receive all data generated during a time when the connection state is not guaranteed. This method can reduce unnecessary data transmission efficiency and further reduce the performance of the entire system by sending and receiving unnecessary messages not only from the sender but also from the receiver side.
- notification messages generated in an environment where the connection state is not guaranteed For example, suppose that the user has set up an emergency message when the temperature is higher than a certain temperature (eg, 30 degrees) as well as the room temperature. In the method illustrated in FIG. 12, since the priority for all the notification messages is set to be the same, there is no method of preferentially processing the important messages among the messages generated during the disconnection.
- a certain temperature eg, 30 degrees
- the present invention proposes attributes and a transmission algorithm for selectively processing a notification message generated during a time when there is no connection state between devices.
- the examples according to the present invention are described around an M2M environment, but can be equally / similarly applied to other systems having a client-server (or sender-receiver) structure.
- a subscriber may refer to an entity requesting a subscription and a hosting entity may refer to an entity having a monitored resource (or a subscription target resource).
- the sender may refer to the entity transmitting the notification message
- the receiver may refer to the entity finally receiving the notification message.
- the hosting entity in the subscription process and the sender in the notification process may be the same entity.
- connection state when the connection state is not guaranteed, the sender may not transmit the generated notification message to the receiver, and may be referred to as a connectionless state. Failure to guarantee connection status can occur for a variety of reasons, such as network failures, device failures, and reachability schedules. Meanwhile, when the connection state is guaranteed, it means a state in which the sender can normally transmit a notification message generated to the receiver, and may be referred to as a connected state or a connected state. In addition, the connection state may be referred to herein as reachability.
- attribute information indicating the sender's notification policy is suggested. Attribute information indicating the sender's notification policy may be referred to as pendingNotification as a non-limiting example. Attribute information indicating the sender's notification policy may be set as one attribute of a subscription resource. Thus, attribute information indicating the sender's notification policy can be used in the subscription / notification process together with or separately from the attribute information illustrated in Table 1. For convenience of description, the attribute information indicating the sender's notification policy herein may be referred to as notification policy information and may be referred to as first attribute information.
- the notification policy information (eg, pendingNotification attribute) indicates the action that the sender should take for the notification message during the unreachable period.
- the unreachable time may be determined according to scheduling information indicated by the scheduling resource or the reachability schedule resource (see the description of FIG. 9).
- notification policy information eg, pendingNotification attribute
- Table 4 illustrates notification policy information (eg, pendingNotification attribute) according to the present invention.
- RW / RO / WO represents the read / write permission of the property and can be one of READ / WRITE (RW), READ ONLY (RO), and WRITE ONLY (WO). Can be.
- the number of occurrences (multiplicity) indicates the number of times a corresponding attribute can occur in a ⁇ subscription> resource.
- notification policy information eg, pendingNotification attribute
- both read / write may be allowed.
- notification policy information (eg, pendingNotification attribute) may have four values. According to the value set in the notification policy information (eg, pendingNotification attribute), the sender processes notification messages generated when there is no connection state as follows. If there is no separate setting, for example, sendNone may be set as a default value among four illustrated values. In this specification, sendNone may be referred to as a first value, sendLatest is a second value, sendAllPending is a third value, and sendManual is a fourth value.
- the sender does not store any notification messages that occur during times when the connection status is not guaranteed. In this case, all notification messages generated during a time when the connection state is not guaranteed may be discarded (not transmitted). When the sender recovers reachability, there is no stored notification message, so the sender does not need to send a notification message generated during a time when the connection state is not guaranteed.
- This setting can be used when no pending notification is needed. For example, it can be applied to an application service that monitors the temperature of the current room.
- notification policy information eg, pendingNotification attribute
- notification 1 to notification n may occur according to the change of the subscription resource, and if there is no connection status between the sender and the receiver, a notification message is sent from the sender to the receiver. Can not.
- the generated notification messages may be processed according to notification policy information (eg, pendingNotification attribute).
- notification policy information eg, pendingNotification attribute
- notification policy information eg, pendingNotification attribute
- sendNone since notification policy information (eg, pendingNotification attribute) is set to sendNone, all notification messages generated while the connection status is not guaranteed are ignored and not stored. Therefore, it is not sent to the receiver even after recovering the connection state.
- a notification message eg, notification n + 1 occurs in the connected state, it may be sent to the receiver.
- the sender stores only the most recent message among the notification messages that occurred during times when the connection status is not guaranteed. In this case, the previously stored notification message is deleted. That is, the sender can save a new notification message and discard the remaining notification messages.
- the sender may send the most recently stored notification message to the recipient when recovering reachability. This setting can be used when the most recent generated notification message among the residual notification messages is needed. For example, it may be applied to an application service that receives a report related to a device update.
- the notification policy information eg, pendingNotification attribute
- the ec value of the notification message may be set to 'latest' (see description related to FIG. 7).
- notification policy information eg, pendingNotification attribute
- notification 1 to notification n may occur according to the change of the subscription resource, and when the connection status between the sender and the receiver is not guaranteed, the notification message is sent from the sender to the receiver. It cannot be sent.
- the generated notification messages may be processed according to notification policy information (eg, pendingNotification attribute).
- notification policy information eg, pendingNotification attribute
- the notification policy information eg, pendingNotification attribute
- the most recently generated message eg, notification n
- the newly generated message may be stored and the previously stored message may be discarded.
- a notification message eg, notification n + 1 occurs in the connected state, it may be sent to the receiver.
- the sender stores notification messages generated during times when the connection status is not guaranteed.
- the notification message sent may be determined differently depending on what the sender can temporarily store.
- the sender may send all stored notification messages to the receiver upon regainability. This setting can be used when all generated notification messages are needed. For example, it can be used for application services (car black boxes) that require statistical data or data analysis.
- notification policy information eg, pendingNotification attribute
- notification 1 to notification n may occur according to the change of the subscription resource, and when the connection status between the sender and the receiver is not guaranteed, the notification message is sent from the sender to the receiver. It cannot be sent.
- the generated notification messages may be processed according to notification policy information (eg, pendingNotification attribute).
- notification policy information eg, pendingNotification attribute
- sendAllPending messages generated in a state where the connection state is not guaranteed may be stored.
- all stored messages can be sent to the recipient after recovering the connection state.
- all stored message aggregations are sent to the receiver since all generated notifications 1 through n are stored.
- a notification message eg, notification n + 1 occurs in the connected state, it may be sent to the receiver.
- the sender stores the notification message (s) arbitrarily set by the subscriber among all notification messages generated during the time when the connection state is not guaranteed.
- a criterion that is arbitrarily set may be set, for example, such as a time (for example, 11 o'clock to 12 o'clock), a specific notification message designation (for example, 10 notification messages from a disconnected time point), and the like.
- This setting may be used when setting subscriber's arbitrary criteria for the case that it cannot be processed by sendNone, sendLatest, and sendAllPending. For example, it may be used for a monitoring application service requesting a notification message generated between 18:00 and 16:00.
- notification policy information eg, pendingNotification attribute
- notification 1 to notification n may occur according to the change of the subscription resource, and when the connection status between the sender and the receiver is not guaranteed, the notification message is sent from the sender to the receiver. It cannot be sent.
- the generated notification messages may be processed according to notification policy information (eg, pendingNotification attribute).
- notification policy information eg, pendingNotification attribute
- notification policy information is set to sendManual, only notification messages satisfying the set criteria among messages generated in a state where the connection state is not guaranteed may be stored. In addition, only messages stored after recovering the connection state can be sent to the recipient. In the example of FIG.
- the set criteria indicate the notification messages generated after t 0 as relating to time, so that notifications 2 to n generated after t 0 can be stored and sent to the receiver after recovering the connection state. Can be.
- the notification message bundle may be sent to the receiver based on the set criteria.
- attribute information for setting the importance of a notification message generated at the sender.
- attribute information eg, notificationEventCat attribute
- notification importance information may be referred to as notification importance information and may be referred to as second attribute information.
- the importance of the notification message may be set by dividing it into a specific number of event categories, and thus the importance of the notification message may be determined according to the corresponding event category.
- notification importance information (eg, notificationEventCat attribute) defines an (event) category for the notification message triggered by the subscription resource.
- notification importance information may indicate an event category to be included in the notification message to enable the receiver to correctly handle the notification message.
- the notification importance information may be used in conjunction with pre-defined policy information for a specific system.
- the notification importance information (eg, notificationEventCat attribute) may be set as one attribute of a subscription resource.
- attribute information indicating the sender's notification policy can be used in the subscription / notification process together with or separately from the attribute information illustrated in Table 1.
- notification importance information (eg, notificationEventCat attribute) may be set by the subscriber.
- notification importance information may be defined as 'High', 'Medium' and 'Low'.
- the notification message may be processed in preference to other notification messages.
- Table 5 illustrates notification importance information (eg, notificationEventCat attribute) in accordance with the present invention.
- notificationEventCat attribute the multiplicity of notification importance information (eg, notificationEventCat attribute) is 0 or 1
- notification importance information eg, notificationEventCat attribute
- both read / write may be allowed.
- Figure 17 illustrates a notification process in accordance with the present invention.
- the notification message may be transmitted in consideration of attribute information proposed by the present invention.
- the reasons why the connection status between the entities is not guaranteed may be classified into network failures, device failures, and reachability schedules. If the connection is lost due to network and device failure, there is no way to recover it normally from the entity's perspective. However, if the connection status is due to the reachability schedule, the entity (eg, the sender) can send a message generated after changing the connection status. Therefore, in the present invention, when it is confirmed that the connection state is disconnected due to the reachability schedule in the notification process for the subscription, the attribute information (eg, notification policy information (eg, pendingNotification attribute) and / or notification importance information (eg, according to the present invention) , notificationEventCat property)).
- notification policy information eg, pendingNotification attribute
- notificationEventCat property notificationEventCat property
- notification policy information eg, pendingNotification attribute
- notification importance information eg, notificationEventCat attribute
- the reachable mode and non-reachable mode described in the present invention may be defined as follows.
- Reachable mode refers to a state in which a corresponding entity is in a normal operation state and can be connected to another entity or can transmit and receive messages with another entity.
- the non-reachable mode refers to a state in which another entity cannot connect or cannot transmit or receive a message with another entity because of a limitation in the operation state of the corresponding entity.
- an event may occur when a change occurs in a resource (or a subscription target resource) to which a subscription process is set.
- An event may occur when a change of a subscription target resource is detected / detected.
- a subscription resource may be preset as a child resource of a subscription target resource.
- the sender checks the importance of the event occurred.
- the sender can check the importance of the event generated based on the notification importance information (eg, notificationEventCat attribute) (refer to Table 5 related description).
- the case of high importance may include a case where notificationEventCat is set to an immediate value.
- the case where the importance level is not high may include a case where notificationEventCat is set to a value other than the immediate value (eg, bestEffort).
- the sender may check the importance of the event and then set, for example, the ec value of the notification message to a value indicated by the notification importance information (eg, notificationEventCat attribute).
- the notification importance information e.g., notificationEventCat attribute
- at least one of other attributes (e.g., Table 1) and / or conditions (e.g., Table 2) set in the subscription resource together with notification importance information (e.g., notificationEventCat attribute) Can be used.
- a notification message is generated after the process related to the attribute for event processing is finished. At this time, since the notification message is composed of event (s), the event category may be the same as the importance of the notification message.
- the caller may proceed to step S1706 or S1714 according to the event importance. If the event importance is high at step S1704, the caller may proceed to step S1706. If the event importance is not high at step S1704, the caller may proceed to step S1714.
- the caller may confirm / determine a connection state between the originator and the counterpart entity (or the receiver).
- the connection state (or reachability) of the sender and the receiver may be determined based on scheduling resources (or scheduling information set therein) for each entity or device.
- step S1706 or step S1714 the caller goes through a process of checking whether the status of the caller and the receiver are in reachable or unreachable mode. If there is no information to confirm the state of the entity, the caller may determine that the entity is in reachable mode.
- the caller may check scheduling information (or reachability schedule information) through scheduling resources and check / determine a connection state (or reachability mode) through scheduling information of the corresponding entity.
- the scheduling resource for the caller may be set as a child resource (eg, notificationSchedule resource) of the subscription resource.
- the scheduling resource for the receiver may be set as a separate scheduling resource.
- the scheduling resource eg, ⁇ schedule> or notificationSchedule resource
- the caller can check the reachable or unreachable mode (and / or time interval) by using scheduling information (or an attribute (eg, scheduleElement) for scheduling time information) set in each scheduling resource. For example, if a sender checks a scheduling resource (eg, notificationSchedule resource) set as a child resource of a subscription resource and the caller corresponds to a time interval indicated by the scheduling information contained therein and the scheduling resource indicates an reachable time interval, the caller arrives. It may be determined that it is possible.
- a scheduling resource eg, notificationSchedule resource
- the receiver may be determined to be reachable. Can be. Similarly, whether the sender or the receiver is unreachable can be determined.
- a separately set scheduling resource eg, ⁇ schedule> resource
- connection status between entities can be classified into four types as follows.
- step S1706 if it is determined that the generated notification message satisfies the "critical message" condition and there is no connection state (that is, case 1-both reachable mode of the sender and the receiver), the process may proceed to step S1708, respectively.
- the process may proceed to step S1708, respectively.
- it means that there is a connection state between the two entities, so the sender immediately sends the generated notification message to the receiver.
- the generated notification message is an important message, the corresponding message may be processed in preference to other messages.
- notification importance information eg, notificationEventCat attribute
- the "important message” condition will cause the notification message with the ec value of the notification message set to 'immediate'.
- ‘Immediate’ is only an example, and the “critical message” condition may be expressed in other values.
- notification importance information such as the notificationEventCat attribute
- the 'critical message' condition is It may mean a notification message in which the ec value is set to 'High'.
- step S1706 if the generated notification message satisfies the "critical message" condition and there is no connection state (ie, Case 2-caller reachable mode, caller unreachable mode / Case 3-caller and caller unreachable mode), S1710 You can proceed to step.
- the "critical message" condition ie, Case 2-caller reachable mode, caller unreachable mode / Case 3-caller and caller unreachable mode
- the sender may process the notification messages generated according to a specific operation (for example, according to a value set in notification policy information (eg, pendingNotification attribute)) set for notification messages generated while the connection state is not established. .
- the notification message processed according to the notification policy information (eg, pendingNotification attribute) may be sent to the receiver after the connection with the receiver is restored (see related description of Table 4). In this case, since the generated notification message is an important message, it may be processed in preference to other messages.
- step S1706 if the generated notification message satisfies the "critical message" condition and there is no connection state (Case 4-caller unreachable mode, receiver reachable mode), step S1712 may be performed.
- the generated notification message is an important message
- the generated notification message may not be transmitted when there is no connection state between the two entities.
- the sender may temporarily change the state of the originator from the unreachable mode to the reachable mode in order to transmit the notification message first.
- the sender can send a notification message generated to the receiver and switch to the originally set device connection state (ie, unreachable mode) when the transmission is completed.
- step S1716 may proceed.
- the sender since there is a connection state between the two entities, the sender may immediately send the generated notification message to the receiver. In this case, since the importance of the generated notification message may be relatively low, the notification message may be processed at a low priority accordingly.
- notification importance information eg, notificationEventCat attribute
- 'immediate' which means that the ec value of the notification message is 'immediate' It may mean a notification message set to a value other than this. ‘Immediate’ is only an example, and the “critical message” condition may be expressed in other values.
- notification importance information e.g., notificationEventCat attribute
- notificationEventCat attribute is defined as 'High', 'Medium', or 'Low', it will not satisfy the 'critical message' condition. In this case, the ec value of the notification message may be set to 'Medium' or 'Low'.
- step S1704 If the notification message in step S1704 does not satisfy the "critical message" condition, and it is determined in step S1714 that there is no connection state (that is, Case 2-caller reachable mode, caller not reachable mode / Case 3-caller and receiver reached Unavailable Mode / Case 4-Caller Unreachable, Callable Reachable), and proceeds to step S1718.
- connection state that is, Case 2-caller reachable mode, caller not reachable mode / Case 3-caller and receiver reached Unavailable Mode / Case 4-Caller Unreachable, Callable Reachable
- step S1718 the notification message generated when there is no connection state between the two entities may not be transmitted. Therefore, in step S1718, the sender may process the notification messages generated according to a specific operation (for example, according to the value set in the notification policy information (eg, pendingNotification attribute)) set for the notification messages generated while there is no connection state. (See description in Table 4).
- the notification message processed according to the notification policy information (eg, pendingNotification attribute) may be sent to the receiver after the connection with the receiver is restored. At this time, since the importance of the generated notification message is relatively low, it can be processed with low priority accordingly.
- FIG. 18 illustrates an embodiment of a notification process in accordance with the present invention.
- FIG. 18 illustrates a specific embodiment of a caller operation performed in S1712 of FIG. 17.
- a value representing “important message” to be processed first by the sender is “immediate”, and it is assumed that there is no connection state from t0 to t3 due to the preset unreachable mode of the sender.
- the receiver may be in reachable mode.
- the sender temporarily reaches the unreachable mode at time t1. It can be switched to the enabled mode and can send the corresponding notification message.
- the sender can switch from reachable mode to unreachable mode at time t2. Only when there is an important message can the caller's connection be temporarily recovered to send the message, and after returning to the preset connection state after sending the important message.
- the M2M gateway, M2M server or M2M device may operate as the transmitter 10 or the receiver 20, respectively.
- the transmitter 10 and the receiver 20 are radio frequency (RF) units 13 and 23 capable of transmitting or receiving radio signals carrying information and / or data, signals, messages, and the like, and in a wireless communication system. It is operatively connected with components such as the memory (12, 22), the RF unit (13, 23) and the memory (12, 22) for storing a variety of information related to communication, by controlling the component
- the apparatus comprises processors 11 and 21, respectively, configured to control the memory 12 and 22 and / or the RF units 13 and 23 to perform at least one of the embodiments of the invention described above.
- the memories 12 and 22 may store programs for processing and control of the processors 11 and 21, and may store information input / output.
- the memories 12 and 22 may be utilized as buffers.
- the memories 12 and 22 may be used to store resources including various setting information and data.
- the processors 11 and 21 typically control the overall operation of the various modules in the transmitter or receiver. In particular, the processors 11 and 21 may perform various control functions for carrying out the present invention.
- the processors 11 and 21 may also be called controllers, microcontrollers, microprocessors, microcomputers, or the like.
- the processors 11 and 21 may be implemented by hardware or firmware, software, or a combination thereof.
- application specific integrated circuits ASICs
- DSPs digital signal processors
- DSPDs digital signal processing devices
- PLDs programmable logic devices
- FPGAs field programmable gate arrays
- the firmware or software when implementing the present invention using firmware or software, may be configured to include a module, a procedure, or a function for performing the functions or operations of the present invention, and configured to perform the present invention.
- the firmware or software may be provided in the processors 11 and 21 or stored in the memory 12 and 22 to be driven by the processors 11 and 21.
- the processor 11 of the transmission apparatus 10 is predetermined from the processor 11 or a scheduler connected to the processor 11 and has a predetermined encoding and modulation on a signal and / or data to be transmitted to the outside. After performing the transmission to the RF unit 13.
- the signal processing of the receiver 20 is the reverse of the signal processing of the transmitter 10.
- the RF unit 23 of the receiving device 20 receives a radio signal transmitted by the transmitting device 10.
- the processor 21 may decode and demodulate a radio signal received through a reception antenna to restore data originally transmitted by the transmission apparatus 10.
- the RF units 13, 23 have one or more antennas.
- the antenna transmits a signal processed by the RF units 13 and 23 to the outside under the control of the processors 11 and 21, or receives a radio signal from the outside to receive the RF unit 13. , 23).
- the transmitter and the receiver are respectively communicated through the RF unit, but it is also possible for the transmitter and the receiver to communicate through a wired network.
- the RF unit may be replaced with a network interface unit (NIU).
- NNIU network interface unit
- each component or feature is to be considered optional unless stated otherwise.
- Each component or feature may be embodied in a form that is not combined with other components or features. It is also possible to combine some of the components and / or features to form an embodiment of the invention.
- the order of the operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is obvious that the claims may be combined to form an embodiment by combining claims that do not have an explicit citation relationship in the claims or as new claims by post-application correction.
- Certain operations described in this document as being performed by a base station may in some cases be performed by an upper node thereof. That is, it is obvious that various operations performed for communication with the terminal in a network including a plurality of network nodes including a base station may be performed by the base station or other network nodes other than the base station.
- a base station may be replaced by terms such as a fixed station, a Node B, an eNode B (eNB), an access point, and the like.
- the terminal may be replaced with terms such as a user equipment (UE), a mobile station (MS), a mobile subscriber station (MSS), and the like.
- Embodiments according to the present invention may be implemented by various means, for example, hardware, firmware, software, or a combination thereof.
- an embodiment of the present invention may include one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), FPGAs ( field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, and the like.
- ASICs application specific integrated circuits
- DSPs digital signal processors
- DSPDs digital signal processing devices
- PLDs programmable logic devices
- FPGAs field programmable gate arrays
- processors controllers, microcontrollers, microprocessors, and the like.
- the present invention may be implemented by software code or instructions including a form of a module, procedure, function, etc. that performs the functions or operations described above.
- the software code or instructions may be stored in a computer readable medium and driven by the processor and may perform operations according to the present invention when driven by the processor.
- the computer readable medium may be located inside or outside the processor or remotely connected to the processor through a network, and may exchange data with the processor.
- the present invention can be used in communication devices such as terminals, servers, gateways, and the like.
Abstract
Description
Claims (14)
- M2M(Machine-to-Machine) 디바이스에서 자원 구독(resource subscription)을 위한 통지(notification)를 수행하는 방법으로서,구독 자원을 자녀 자원으로서 포함하는 구독 대상 자원의 변화를 검출하는 단계;상기 구독 자원에 설정된 제2 속성 정보에 따라 상기 변화의 이벤트 카테고리를 지시하는 값을 포함하는 통지 메시지를 생성하는 단계; 및상기 M2M 디바이스를 위한 스케줄링 자원에 설정된 스케줄링 정보 및 수신 디바이스를 위한 스케줄링 자원에 설정된 스케줄링 정보를 기반으로 상기 수신 디바이스로의 도달가능성을 판별하는 단계를 포함하되,상기 스케줄링 정보에 따라 상기 수신 디바이스가 도달가능하다고 판별되는 경우, 상기 통지 메시지는 즉시 상기 수신 디바이스로 전송되고,상기 스케줄링 정보에 따라 상기 수신 디바이스가 도달가능하지 않다고 판별되는 경우, 상기 통지 메시지는 상기 구독 자원에 설정된 제1 속성 정보가 가지는 값에 따라 상기 M2M 디바이스에서 처리되고 상기 처리된 통지 메시지는 상기 수신 디바이스가 도달가능한 상태로 회복된 후 상기 수신 디바이스로 전송되는, 방법.
- 제1항에 있어서,상기 구독 자원과 상기 스케줄링 자원 각각은 고유한 주소를 이용하여 고유하게 어드레싱 가능한 데이터 구조를 나타내는, 방법.
- 제1항에 있어서,상기 제2 속성 정보는 상기 구독 자원에 의해 트리거링되는 상기 통지 메시지를 위한 이벤트 카테고리를 정의하며,상기 통지 메시지에 포함된 이벤트 카테고리를 지시하는 값은 상기 수신 디바이스가 상기 통지 메시지를 핸들링하는 데 이용되는, 방법.
- 제1항에 있어서,상기 제1 속성 정보는 상기 스케줄링 정보에 따라 상기 수신 디바이스로 도달가능하지 않은 시간 구간이 지난 다음 상기 M2M 디바이스가 수행할 통지 메시지의 처리 동작을 지시하는, 방법.
- 제4항에 있어서,상기 스케줄링 정보에 따라 상기 수신 디바이스가 도달가능하지 않다고 판별되는 경우, 상기 통지 메시지를 처리하는 것은상기 제1 속성 정보가 제1 값을 갖는 경우, 상기 생성된 통지 메시지를 폐기하는 것과,상기 제1 속성 정보가 제2 값을 갖는 경우, 상기 생성된 통지 메시지를 저장하고 이전에 저장된 통지 메시지를 폐기하는 것과,상기 제1 속성 정보가 제3 값을 갖는 경우, 상기 생성된 통지 메시지를 모두 저장하는 것을 포함하는, 방법.
- 제1항에 있어서,상기 M2M 디바이스의 스케줄링 정보가 도달가능함을 지시하고 상기 수신 디바이스의 스케줄링 정보가 도달가능함을 지시하는 경우, 상기 수신 디바이스는 도달가능하다고 판별되는, 방법.
- 제1항에 있어서,상기 M2M 디바이스의 스케줄링 정보가 도달불가함을 지시하거나 상기 수신 디바이스의 스케줄링 정보가 도달불가함을 지시하는 경우, 상기 수신 디바이스는 도달불가하다고 판별되는, 방법.
- M2M(Machine-to-Machine) 디바이스에 있어서, 상기 M2M 디바이스는네트워크 인터페이스 유닛(Network Interface Unit); 및상기 네트워크 인터페이스 유닛과 동작시 연결되는(operatively connected) 프로세서를 포함하며, 상기 프로세서는구독 자원을 자녀 자원으로서 포함하는 구독 대상 자원의 변화를 검출하고,상기 구독 자원에 설정된 제2 속성 정보에 따라 상기 변화의 이벤트 카테고리를 지시하는 값을 포함하는 통지 메시지를 생성하고,상기 M2M 디바이스를 위한 스케줄링 자원에 설정된 스케줄링 정보 및 수신 디바이스를 위한 스케줄링 자원에 설정된 스케줄링 정보를 기반으로 상기 수신 디바이스로의 도달가능성을 판별하도록 구성되며,상기 스케줄링 정보에 따라 상기 수신 디바이스가 도달가능하다고 판별되는 경우, 상기 통지 메시지는 즉시 상기 수신 디바이스로 전송되고,상기 스케줄링 정보에 따라 상기 수신 디바이스가 도달가능하지 않다고 판별되는 경우, 상기 통지 메시지는 상기 구독 자원에 설정된 제1 속성 정보가 가지는 값에 따라 상기 M2M 디바이스에서 처리되고 상기 처리된 통지 메시지는 상기 수신 디바이스가 도달가능한 상태로 회복된 후 상기 수신 디바이스로 전송되는, M2M 디바이스.
- 제8항에 있어서,상기 구독 자원과 상기 스케줄링 자원 각각은 고유한 주소를 이용하여 고유하게 어드레싱 가능한 데이터 구조를 나타내는, M2M 디바이스.
- 제8항에 있어서,상기 제2 속성 정보는 상기 구독 자원에 의해 트리거링되는 상기 통지 메시지를 위한 이벤트 카테고리를 정의하며,상기 통지 메시지에 포함된 이벤트 카테고리를 지시하는 값은 상기 수신 디바이스가 상기 통지 메시지를 핸들링하는 데 이용되는, M2M 디바이스.
- 제8항에 있어서,상기 제1 속성 정보는 상기 스케줄링 정보에 따라 상기 수신 디바이스로 도달가능하지 않은 시간 구간이 지난 다음 상기 M2M 디바이스가 수행할 통지 메시지의 처리 동작을 지시하는, M2M 디바이스.
- 제8항에 있어서,상기 스케줄링 정보에 따라 상기 수신 디바이스가 도달가능하지 않다고 판별되는 경우, 상기 통지 메시지를 처리하는 것은상기 제1 속성 정보가 제1 값을 갖는 경우, 상기 생성된 통지 메시지를 폐기하는 것과,상기 제1 속성 정보가 제2 값을 갖는 경우, 상기 생성된 통지 메시지를 저장하고 이전에 저장된 통지 메시지를 폐기하는 것과,상기 제1 속성 정보가 제3 값을 갖는 경우, 상기 생성된 통지 메시지를 모두 저장하는 것을 포함하는, M2M 디바이스.
- 제8항에 있어서,상기 M2M 디바이스의 스케줄링 정보가 도달가능함을 지시하고 상기 수신 디바이스의 스케줄링 정보가 도달가능함을 지시하는 경우, 상기 수신 디바이스는 도달가능하다고 판별되는, M2M 디바이스.
- 제8항에 있어서,상기 M2M 디바이스의 스케줄링 정보가 도달불가함을 지시하거나 상기 수신 디바이스의 스케줄링 정보가 도달불가함을 지시하는 경우, 상기 수신 디바이스는 도달불가하다고 판별되는, 방법.
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP14849785.2A EP3051849B1 (en) | 2013-09-27 | 2014-09-26 | Method for delivering notification message in m2m system and devices for same |
JP2016538869A JP6254702B2 (ja) | 2013-09-27 | 2014-09-26 | M2mシステムにおける通知メッセージ伝達方法及びこのための装置 |
KR1020167002529A KR102208119B1 (ko) | 2013-09-27 | 2014-09-26 | M2m 시스템에서 통지 메시지 전달 방법 및 이를 위한 장치 |
US14/909,633 US10051404B2 (en) | 2013-09-27 | 2014-09-26 | Method for delivering notification message in M2M system and devices for same |
CN201480053463.2A CN105580396B (zh) | 2013-09-27 | 2014-09-26 | 用于在m2m系统中传送通知消息的方法及其装置 |
Applications Claiming Priority (18)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201361883194P | 2013-09-27 | 2013-09-27 | |
US61/883,194 | 2013-09-27 | ||
US201461935846P | 2014-02-05 | 2014-02-05 | |
US61/935,846 | 2014-02-05 | ||
US201461937621P | 2014-02-10 | 2014-02-10 | |
US61/937,621 | 2014-02-10 | ||
US201461950230P | 2014-03-10 | 2014-03-10 | |
US61/950,230 | 2014-03-10 | ||
US201461952851P | 2014-03-13 | 2014-03-13 | |
US61/952,851 | 2014-03-13 | ||
US201461989536P | 2014-05-07 | 2014-05-07 | |
US61/989,536 | 2014-05-07 | ||
US201462011036P | 2014-06-12 | 2014-06-12 | |
US62/011,036 | 2014-06-12 | ||
US201462023886P | 2014-07-13 | 2014-07-13 | |
US62/023,886 | 2014-07-13 | ||
US201462025022P | 2014-07-16 | 2014-07-16 | |
US62/025,022 | 2014-07-16 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2015046960A1 true WO2015046960A1 (ko) | 2015-04-02 |
Family
ID=52743972
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2014/009041 WO2015046960A1 (ko) | 2013-09-27 | 2014-09-26 | M2m 시스템에서 통지 메시지 전달 방법 및 이를 위한 장치 |
PCT/KR2014/009042 WO2015046961A1 (ko) | 2013-09-27 | 2014-09-26 | M2m 시스템에서 통지 메시지 전달 방법 및 이를 위한 장치 |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2014/009042 WO2015046961A1 (ko) | 2013-09-27 | 2014-09-26 | M2m 시스템에서 통지 메시지 전달 방법 및 이를 위한 장치 |
Country Status (6)
Country | Link |
---|---|
US (2) | US10051404B2 (ko) |
EP (1) | EP3051849B1 (ko) |
JP (1) | JP6254702B2 (ko) |
KR (2) | KR101769386B1 (ko) |
CN (2) | CN105580327B (ko) |
WO (2) | WO2015046960A1 (ko) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106341775A (zh) * | 2015-07-10 | 2017-01-18 | 华为技术有限公司 | 一种数据传输方法及装置 |
WO2017155162A1 (ko) * | 2016-03-07 | 2017-09-14 | 엘지전자 주식회사 | 무선 통신 시스템에서 접근 제어 정책 자원을 어나운스하기 위한 방법 및 이를 위한 장치 |
CN107295554A (zh) * | 2016-03-30 | 2017-10-24 | 中兴通讯股份有限公司 | 一种管理应用状态的方法和装置 |
KR20180082555A (ko) * | 2015-11-16 | 2018-07-18 | 콘비다 와이어리스, 엘엘씨 | M2m 서비스 계층에 대한 교차 리소스 가입 |
JP2018528689A (ja) * | 2015-08-26 | 2018-09-27 | クアルコム,インコーポレイテッド | マシンツーマシン通信のためのカスタマイズされたリソースタイプ |
EP3393085A4 (en) * | 2015-12-31 | 2018-10-24 | Huawei Technologies Co., Ltd. | Method and device for time sequence data detection |
JP2019527955A (ja) * | 2016-07-14 | 2019-10-03 | コンヴィーダ ワイヤレス, エルエルシー | サブスクリプションおよび通知サービス |
Families Citing this family (37)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104683289A (zh) * | 2013-11-26 | 2015-06-03 | 中兴通讯股份有限公司 | 公共业务实体注册方法和系统 |
US10015684B2 (en) * | 2013-12-01 | 2018-07-03 | Lg Electronics Inc. | Method and apparatus for managing specific resource in wireless communication system |
CN103618800B (zh) * | 2013-12-05 | 2017-11-03 | 华为技术有限公司 | 订阅通知的实现方法和装置 |
CN104796922B (zh) * | 2014-01-22 | 2019-07-09 | 中兴通讯股份有限公司 | Cse的触发管理方法及装置、cse、承载网网元 |
CN106471465B (zh) * | 2014-04-09 | 2019-10-22 | 康维达无线有限责任公司 | 服务启用器功能 |
CN105578381A (zh) * | 2014-10-10 | 2016-05-11 | 中兴通讯股份有限公司 | 一种创建订阅资源的方法和装置 |
WO2016123778A1 (zh) * | 2015-02-05 | 2016-08-11 | 华为技术有限公司 | M2m数据处理方法、设备及系统 |
CN108141727B (zh) * | 2015-08-03 | 2021-05-04 | 康维达无线有限责任公司 | 用户设备的移动核心网络服务暴露 |
US10555170B2 (en) * | 2015-09-04 | 2020-02-04 | Huawei Technologies Co., Ltd. | Method and apparatus for authentication of wireless devices |
WO2017155161A1 (ko) * | 2016-03-09 | 2017-09-14 | 엘지전자 주식회사 | 무선 통신 시스템에서 요청을 리-타겟팅(re-target)하기 위한 방법 및 이를 위한 장치 |
US10452414B2 (en) * | 2016-06-30 | 2019-10-22 | Microsoft Technology Licensing, Llc | Assistive technology notifications for relevant metadata changes in a document |
CN109478153B (zh) * | 2016-07-07 | 2022-02-22 | 康维达无线有限责任公司 | 机器到机器服务层通信中的消息重定向 |
CN113159910A (zh) | 2016-07-29 | 2021-07-23 | 京东方科技集团股份有限公司 | 进行通知的方法、装置和系统 |
CN106231538B (zh) * | 2016-07-29 | 2019-12-27 | 海尔优家智能科技(北京)有限公司 | 一种OneM2M架构设备绑定的方法和装置 |
WO2018019281A1 (zh) * | 2016-07-29 | 2018-02-01 | 京东方科技集团股份有限公司 | 进行通知的方法、装置和系统 |
US10650621B1 (en) | 2016-09-13 | 2020-05-12 | Iocurrents, Inc. | Interfacing with a vehicular controller area network |
WO2018067924A1 (en) * | 2016-10-06 | 2018-04-12 | Convida Wireless, Llc | Service layer mobility management of applications |
CN117170876A (zh) | 2016-10-07 | 2023-12-05 | 康维达无线有限责任公司 | 用于通用互通和可扩展性的服务层资源管理 |
JP6957632B2 (ja) | 2017-03-09 | 2021-11-02 | グーグル エルエルシーGoogle LLC | コンピューティング装置の通知のための通知チャネル |
US20180270896A1 (en) * | 2017-03-20 | 2018-09-20 | Qualcomm Incorporated | Enhanced session and mobility management interaction for mobile initiated connection only mode user equipments |
CN106973118B (zh) * | 2017-05-12 | 2021-04-27 | 京东方科技集团股份有限公司 | 生成和订阅通知的方法和装置 |
US10687279B2 (en) * | 2017-08-25 | 2020-06-16 | Verizon Patent And Licensing Inc. | System and method of optimizing user equipment reachability notifications |
CN109495524B (zh) * | 2017-09-11 | 2022-03-04 | 华为云计算技术有限公司 | 一种物联网资源订阅的方法、设备和系统 |
KR102260656B1 (ko) * | 2018-03-15 | 2021-06-04 | 한국전자기술연구원 | M2m 시스템에서의 통지 메시지 실시간 전달 방법 |
KR102402145B1 (ko) * | 2018-03-15 | 2022-05-26 | 한국전자기술연구원 | M2m 시스템에서의 이벤트 기반 메시지 재전달 방법 |
CN110505591B (zh) | 2018-05-18 | 2022-09-30 | 京东方科技集团股份有限公司 | 订阅服务实体、订阅终端及信息订阅方法和系统 |
KR102465844B1 (ko) * | 2018-07-02 | 2022-11-09 | 현대자동차주식회사 | M2m 시스템에서 통지 실패시 통지 메시지를 처리하는 방법 및 장치 |
KR102465843B1 (ko) * | 2018-07-10 | 2022-11-09 | 현대자동차주식회사 | M2m 시스템에서 누적 통지 메시지를 전송하는 방법 및 장치 |
CN110731074B (zh) * | 2018-12-13 | 2023-01-31 | Oppo广东移动通信有限公司 | 订阅消息的处理方法、装置、计算机设备和存储介质 |
KR102598045B1 (ko) * | 2019-02-11 | 2023-11-02 | 현대자동차주식회사 | 구독 및 통지를 수행하는 방법 및 장치 |
KR102647498B1 (ko) * | 2019-03-18 | 2024-03-15 | 주식회사 케이티 | M2m 시스템에서 통지 메시지 전송 방법 및 그 장치 |
KR20210041488A (ko) * | 2019-10-07 | 2021-04-15 | 현대자동차주식회사 | M2m 시스템에서 주기적인 통지를 송수신하는 방법 및 장치 |
JP2023524367A (ja) * | 2020-03-17 | 2023-06-12 | オッポ広東移動通信有限公司 | モノのインターネットの通信方法及び装置 |
CN116918363A (zh) * | 2021-03-01 | 2023-10-20 | Oppo广东移动通信有限公司 | 信息传输方法、装置、设备及存储介质 |
US11792165B2 (en) | 2021-06-04 | 2023-10-17 | Bank Of America Corporation | Supporting data processing transactions using machine to machine (M2M) data transfer |
US11784981B2 (en) | 2021-06-04 | 2023-10-10 | Bank Of America Corporation | Data processing transactions using machine to machine (M2M) data transfer |
US11265370B1 (en) | 2021-07-27 | 2022-03-01 | Bank Of America Corporation | Machine to machine (M2M) data transfer between data servers |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012068465A1 (en) * | 2010-11-19 | 2012-05-24 | Interdigital Patent Holdings, Inc. | Machine-to-machine (m2m) interface procedures for announce and de-announce of resources |
US20120170451A1 (en) * | 2011-01-05 | 2012-07-05 | Harish Viswanathan | System and method for communicating data between an application server and an m2m device |
WO2012121552A2 (ko) * | 2011-03-08 | 2012-09-13 | 엘지전자 주식회사 | M2m 기기를 위한 제어정보를 송수신하는 방법 및 이를 위한 장치 |
WO2012150778A2 (ko) * | 2011-05-03 | 2012-11-08 | 주식회사 케이티 | 연결 상태 확인 이벤트에 기반하여 m2m 통신 개체간 연결을 관리하는 방법 및 장치 |
KR20120127050A (ko) * | 2011-05-13 | 2012-11-21 | 주식회사 케이티 | M2m 통신에서 네트워크를 선택하는 방법 및 장치 |
Family Cites Families (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5696486A (en) * | 1995-03-29 | 1997-12-09 | Cabletron Systems, Inc. | Method and apparatus for policy-based alarm notification in a distributed network management environment |
JP4714025B2 (ja) | 2006-01-06 | 2011-06-29 | 株式会社日立製作所 | センサノード、基地局、センサネット及びセンシングデータの送信方法 |
JP2008245102A (ja) * | 2007-03-28 | 2008-10-09 | Hitachi Kokusai Electric Inc | ネットワーク通信方法 |
US8553883B2 (en) * | 2008-02-22 | 2013-10-08 | Telefonaktiebolaget L M Ericsson (Publ) | Method and apparatus for managing subscription credentials in a wireless communication device |
US8560835B2 (en) * | 2008-06-12 | 2013-10-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for machine-to-machine communication |
ES2670371T3 (es) * | 2009-07-17 | 2018-05-30 | Koninklijke Kpn N.V. | Transmisión de información en una red de telecomunicaciones entre máquinas |
KR101601869B1 (ko) * | 2009-10-08 | 2016-03-09 | 에스케이텔레콤 주식회사 | 망 정보 알림 서비스 시스템 및 망 정보 알림 서비스 방법 |
WO2011101032A1 (en) * | 2010-02-19 | 2011-08-25 | Telefonaktiebolaget Lm Ericsson (Publ) | Apparatuses and methods for handling machine-to-machine communications |
TWI569615B (zh) * | 2010-03-01 | 2017-02-01 | 內數位專利控股公司 | 機器對機器閘道器 |
CN102907068A (zh) | 2010-03-09 | 2013-01-30 | 交互数字专利控股公司 | 支持机器对机器通信的方法和设备 |
EP2375849B1 (en) * | 2010-03-29 | 2015-08-12 | Vodafone Holding GmbH | Connection management for M2M device in a mobile communication network |
US8792341B2 (en) | 2010-10-27 | 2014-07-29 | Futurewei Technologies, Inc. | System and method for machine-to-machine application based congestion control |
US8943132B2 (en) | 2011-09-12 | 2015-01-27 | Telefonaktiebolaget L M Ericsson (Publ) | Systems and methods for optimization of subscriptions to resource changes in machine-to-machine (M2M) systems |
US9324055B2 (en) * | 2011-12-08 | 2016-04-26 | Microsoft Technology Licensing, Llc | Techniques to manage remote events |
US20150055557A1 (en) * | 2012-03-22 | 2015-02-26 | Interdigital Patent Holdings, Inc. | Method and apparatus for supporting machine-to-machine caching at a service capability layer |
EP3720170A1 (en) | 2013-02-15 | 2020-10-07 | NEC Corporation | Core network control parameter determination method and corresponding core network control node |
JP6269649B2 (ja) | 2013-03-01 | 2018-01-31 | 日本電気株式会社 | 通信システム、サービスプラットフォーム、通信方法及びプログラム |
KR101472397B1 (ko) * | 2013-04-04 | 2014-12-12 | 주식회사 팬택 | 휴대용 단말 및 노티피케이션 정보 처리 방법 |
EP2997761B1 (en) * | 2013-05-14 | 2019-01-02 | Telefonaktiebolaget LM Ericsson (publ) | A node and a method for small data communications |
CN111405493B (zh) | 2014-07-07 | 2022-08-12 | 康维达无线有限责任公司 | 用于基于机器类型通信组的服务的协调分组 |
-
2014
- 2014-09-26 KR KR1020167002528A patent/KR101769386B1/ko active IP Right Grant
- 2014-09-26 WO PCT/KR2014/009041 patent/WO2015046960A1/ko active Application Filing
- 2014-09-26 JP JP2016538869A patent/JP6254702B2/ja active Active
- 2014-09-26 KR KR1020167002529A patent/KR102208119B1/ko active IP Right Grant
- 2014-09-26 US US14/909,633 patent/US10051404B2/en active Active
- 2014-09-26 EP EP14849785.2A patent/EP3051849B1/en active Active
- 2014-09-26 US US14/909,651 patent/US9723429B2/en active Active
- 2014-09-26 CN CN201480053464.7A patent/CN105580327B/zh active Active
- 2014-09-26 WO PCT/KR2014/009042 patent/WO2015046961A1/ko active Application Filing
- 2014-09-26 CN CN201480053463.2A patent/CN105580396B/zh active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2012068465A1 (en) * | 2010-11-19 | 2012-05-24 | Interdigital Patent Holdings, Inc. | Machine-to-machine (m2m) interface procedures for announce and de-announce of resources |
US20120170451A1 (en) * | 2011-01-05 | 2012-07-05 | Harish Viswanathan | System and method for communicating data between an application server and an m2m device |
WO2012121552A2 (ko) * | 2011-03-08 | 2012-09-13 | 엘지전자 주식회사 | M2m 기기를 위한 제어정보를 송수신하는 방법 및 이를 위한 장치 |
WO2012150778A2 (ko) * | 2011-05-03 | 2012-11-08 | 주식회사 케이티 | 연결 상태 확인 이벤트에 기반하여 m2m 통신 개체간 연결을 관리하는 방법 및 장치 |
KR20120127050A (ko) * | 2011-05-13 | 2012-11-21 | 주식회사 케이티 | M2m 통신에서 네트워크를 선택하는 방법 및 장치 |
Non-Patent Citations (1)
Title |
---|
See also references of EP3051849A4 * |
Cited By (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106341775A (zh) * | 2015-07-10 | 2017-01-18 | 华为技术有限公司 | 一种数据传输方法及装置 |
CN106341775B (zh) * | 2015-07-10 | 2019-11-01 | 华为技术有限公司 | 一种数据传输方法及装置 |
JP2018528689A (ja) * | 2015-08-26 | 2018-09-27 | クアルコム,インコーポレイテッド | マシンツーマシン通信のためのカスタマイズされたリソースタイプ |
KR102116401B1 (ko) * | 2015-11-16 | 2020-05-29 | 콘비다 와이어리스, 엘엘씨 | M2m 서비스 계층에 대한 교차 리소스 가입 |
US11012839B2 (en) | 2015-11-16 | 2021-05-18 | Convida Wireless, Llc | Cross-resource subscription for M2M service layer |
KR20180082555A (ko) * | 2015-11-16 | 2018-07-18 | 콘비다 와이어리스, 엘엘씨 | M2m 서비스 계층에 대한 교차 리소스 가입 |
EP3378217B1 (en) * | 2015-11-16 | 2024-01-03 | Convida Wireless, LLC | Cross-resource subscription for m2m service layer |
CN108353094A (zh) * | 2015-11-16 | 2018-07-31 | 康维达无线有限责任公司 | 用于m2m服务层的跨资源订阅 |
US11711682B2 (en) | 2015-11-16 | 2023-07-25 | Convida Wireless LLC | Cross-resource subscription for M2M service layer |
CN108353094B (zh) * | 2015-11-16 | 2021-09-14 | 康维达无线有限责任公司 | 用于m2m服务层的跨资源订阅 |
EP3393085A4 (en) * | 2015-12-31 | 2018-10-24 | Huawei Technologies Co., Ltd. | Method and device for time sequence data detection |
US10911970B2 (en) | 2015-12-31 | 2021-02-02 | Huawei Technologies Co., Ltd. | Method and apparatus for detecting time series data |
WO2017155162A1 (ko) * | 2016-03-07 | 2017-09-14 | 엘지전자 주식회사 | 무선 통신 시스템에서 접근 제어 정책 자원을 어나운스하기 위한 방법 및 이를 위한 장치 |
EP3439354A4 (en) * | 2016-03-30 | 2019-10-30 | ZTE Corporation | METHOD AND DEVICES FOR MANAGING AN APPLICATION STATUS |
CN107295554A (zh) * | 2016-03-30 | 2017-10-24 | 中兴通讯股份有限公司 | 一种管理应用状态的方法和装置 |
US10798198B2 (en) | 2016-07-14 | 2020-10-06 | Convida Wireless, Llc | Subscription and notification service |
US11153398B2 (en) | 2016-07-14 | 2021-10-19 | Convida Wireless, Llc | Subscription and notification service |
US11582306B2 (en) | 2016-07-14 | 2023-02-14 | Convida Wireless, Llc | Subscription and notification service |
US11750702B2 (en) | 2016-07-14 | 2023-09-05 | Convida Wireless, Llc | Subscription and notification service |
JP2019527955A (ja) * | 2016-07-14 | 2019-10-03 | コンヴィーダ ワイヤレス, エルエルシー | サブスクリプションおよび通知サービス |
Also Published As
Publication number | Publication date |
---|---|
KR20160061965A (ko) | 2016-06-01 |
WO2015046961A1 (ko) | 2015-04-02 |
CN105580396A (zh) | 2016-05-11 |
CN105580327A (zh) | 2016-05-11 |
JP2016535532A (ja) | 2016-11-10 |
CN105580396B (zh) | 2019-04-16 |
KR102208119B1 (ko) | 2021-01-27 |
EP3051849A1 (en) | 2016-08-03 |
US10051404B2 (en) | 2018-08-14 |
US20160192111A1 (en) | 2016-06-30 |
EP3051849B1 (en) | 2018-11-07 |
CN105580327B (zh) | 2018-12-18 |
KR101769386B1 (ko) | 2017-08-18 |
KR20160039612A (ko) | 2016-04-11 |
EP3051849A4 (en) | 2017-04-12 |
US9723429B2 (en) | 2017-08-01 |
US20160205217A1 (en) | 2016-07-14 |
JP6254702B2 (ja) | 2017-12-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2015046960A1 (ko) | M2m 시스템에서 통지 메시지 전달 방법 및 이를 위한 장치 | |
WO2014185754A1 (ko) | M2m 통신 시스템에서 구독 및 통지를 위한 방법 및 이를 위한 장치 | |
WO2015069038A1 (ko) | M2m 통신 시스템에서 구독 및 통지를 위한 방법 및 이를 위한 장치 | |
WO2014129802A1 (ko) | M2m 서비스 설정 변경 방법 및 이를 위한 장치 | |
WO2019199028A1 (en) | Method and device using network slicing in mobile communication system | |
WO2014200292A1 (ko) | M2m 시스템에서 위치 측정 방법 및 이를 위한 장치 | |
WO2014109597A1 (ko) | M2m(machine-to-machine)시스템에서 게이트웨이 변경 방법 및 이를 위한 장치 | |
WO2018199649A1 (en) | Method and apparatus for registration type addition for service negotiation | |
WO2020226360A1 (en) | Apparatus and method for supporting burst arrival time reference clock based on time-sensitive communication assistance information in wireless communication network | |
WO2016195199A1 (ko) | 무선 통신 시스템에서 폴링 채널을 통해 요청을 처리하기 위한 방법 및 이를 위한 장치 | |
EP3574693A1 (en) | Method and apparatus for registration type addition for service negotiation | |
WO2021091307A1 (ko) | 무선 통신 시스템에서 mbs 서비스 제공에 대한 mbs 서비스 세션의 설정을 위한 장치 및 방법 | |
WO2012081882A2 (ko) | 이동통신 시스템에서 셀 방송 기술을 이용한 신뢰성 있는 그룹 멀티캐스트 전송 방법 및 장치 | |
WO2021167277A1 (ko) | 에지 컴퓨팅 시스템에서 무선 통신 네트워크 타입에 따른 서비스 제공 장치 및 방법 | |
EP4008117A1 (en) | Method and apparatus for providing policy of user equipment in wireless communication system | |
WO2021225389A1 (ko) | 네트워크 슬라이스를 이용하여 에지 컴퓨팅 서비스를 제공하는 장치 및 방법 | |
WO2016068548A1 (ko) | 무선 통신 시스템에서 통지 메시지를 처리하기 위한 방법 및 이를 위한 장치 | |
WO2016126021A1 (ko) | 무선 통신 시스템에서 통지 수신 중단 요청을 처리하기 위한 방법 및 이를 위한 장치 | |
WO2021141291A1 (ko) | 무선 통신 시스템에서 네트워크 트래픽을 수집하는 방법 및 장치 | |
WO2017073876A1 (ko) | 무선 통신 시스템에서 서비스 요청을 처리하기 위한 방법 및 이를 위한 장치 | |
WO2016064235A2 (ko) | 무선 통신 시스템에서 그룹 멤버의 자식 자원을 관리하기 위한 방법 및 이를 위한 장치 | |
WO2020256484A1 (ko) | 네트워크장치 및 네트워크장치에서 수행되는 엣지서비스 검색 방법 | |
EP4085700A1 (en) | Method and apparatus for registering with network slice in wireless communication system | |
WO2020111761A1 (ko) | M2m 시스템에서 메시지 반복 전송 방법 및 장치 | |
WO2023075214A1 (en) | Method and apparatus for supporting edge computing service for roaming ue in wireless communication system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201480053463.2 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14849785 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 20167002529 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14909633 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2016538869 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REEP | Request for entry into the european phase |
Ref document number: 2014849785 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2014849785 Country of ref document: EP |