hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.10.2 Detailed Descriptions | The functionalities supported by the SEC CSF are as follows: • Sensitive data handling: - Provides the capability to protect the local credentials on which security relies during storage and manipulation. - Extends sensitive data handling functionality to other sensitive data used in the M2M Systems such as subscriptio... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.11 Service Charging and Accounting | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.11.1 General Concepts | The Service Charging and Accounting (SCA) CSF provides charging functions for the Service Layer. It supports different charging models which also include online real time credit control. The SCA CSF manages service layer charging policies and configuration capturing service layer chargeable events, generating charging ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.11.2 Detailed Descriptions | The SCA CSF performs information recording corresponding to a chargeable event based on the configured charging policies. The SCA CSF sends the charging information transformed from the specific recorded information to the billing domain by the use of a standard or proprietary interface for charging purposes. The SCA C... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.12 Subscription and Notification | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.12.1 General Concepts | The Subscription and Notification (SUB) CSF provides notifications pertaining to a subscription that tracks event changes on a resource (e.g. deletion of a resource). A subscription to a resource is initiated by an AE or a CSE, and is granted by the Hosting CSE subject to access control policies. During an active resou... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.2.12.2 Detailed Descriptions | The SUB CSF manages subscriptions to resources, subject to access control policies, and sends corresponding notifications to the address(es) where the resource subscribers want to receive them. An AE or a CSE is the subscription resource subscriber. AEs and CSEs subscribe to resources of other CSEs. A subscription Host... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.3 Security Aspects | The ETSI TR 118 508 [i.26] on Analysis of Security Solutions for the oneM2M System differentiates security domains related to the transport layer (Underlying Network), service layer (M2M common services) and Application Layer. It also considers possible trust scenarios involving these different security domains, and in... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.4 Intra-M2M SP Communication | Within the same SP domain a CSE shall perform registration with another CSE over the Mcc reference point to be able to use M2M Services offered by that CSE and to allow the other CSE to use its services. As a result of successful registration the CSEs establish a relationship allowing them to exchange information. An A... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.5 Inter-M2M SP Communication | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.5.1 Inter M2M SP Communication for oneM2M Compliant Nodes | To enable M2M entities (e.g. CSE, AE) in different M2M Service Provider (SP) domains to communicate, configuration within the M2M domain determines if such a communication is allowed. If allowed, the M2M System shall support routing of the traffic across the originating M2M SP domain and within the target M2M SP domain... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.5.1.1 Public Domain Names and CSEs | To enable the usage of public DNSs as described above, there is a need for a naming convention for public names for CSEs. This naming convention facilitates the creation of the necessary entries of the public domain names of CSEs in the DNS by the infrastructure node. CSEs public domain names shall be a sub-domain of t... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.5.2 Inter M2M SP Generic Procedures | This clause describes the behaviour of the M2M Nodes in support of inter-M2M SP procedures. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 41 |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.5.2.1 Actions of the Originating M2M Node in the Originating Domain | The Originator in the originating domain can be any M2M Node such as ADN, an MN, or an ASN, and shall send a request to the Registrar CSE to retrieve a resource located in another M2M SP domain. The Originator shall use any of the options defined in clause 9.3.1 to identify the target host and resource for that purpose... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.5.2.2 Actions of the Receiving CSE in the Originating Domain | The receiving CSE in the originating domain shall check if the addressed resource is locally available. If the addressed resource is not locally available, then the request shall be forwarded to the next hop. If the receiving CSE is on an IN, it shall check if the addressed resource is locally available within its doma... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.5.2.3 Actions in the IN of the Target Domain | The IN is the entry point of the target M2M SP domain. The IN shall check if the addressed resource is a local resource. If it is not a local resource it shall forward the request to the appropriate CSE, after identifying the Hosting CSE within its domain, using the pointOfAccess attribute. Once the request reaches the... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.5.3 DNS Provisioning for Inter-M2M SP Communication | As specified previously, any M2M SP supporting inter-M2M SP communication shall ensure that the public domain names for the CSEs whose functionality is available across domains are held in the M2M SP's DNS and shall always point to the IP address associated with the Infrastructure domain CSE (being the entry point) for... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.5.3.1 Inter-M2M SP Communication Access Control Policies | Additional M2M SP policies that further restrict access to CSEs to requests originating from configured M2M SPs only, can complement the DNS entries created by the IN-CSE. These policies are out of scope of the present document. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.5.4 Conditional Inter-M2M Service Provider CSE Registration | Inter-M2M Service Provider CSE registration shall be supported to enable M2M entities (e.g. CSE, AE) in peer M2M Service Provider (SP) domains with the ability to create and operate resources with the equivalent set of possibilities as offered in the intra-M2M Service Provider domain, subject to the following: • The AE... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 6.6 M2M Service Subscription | The M2M Service Subscription defines the technical part of the contract between an M2M Subscriber (typically an M2M Application Service Provider) and an M2M Service Provider. Each M2M Service Subscription shall have a unique identifier, the M2M-Sub-ID, as specified in clause 7.1.11. An M2M Service Subscription establis... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7 M2M Entities and Object Identification | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7.1 M2M Identifiers | This clause provides a list of identifiers required for the purpose of interworking within the oneM2M architectural model. An M2M identifier is a sequence of characters used to refer to an entity (such as CSE or an AE), a resource (such as defined in clause 9) or an object (such as an M2M Service Provider or an M2M Nod... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7.1.1 M2M Service Provider Identifier (M2M-SP-ID) | An M2M Service Provider shall be uniquely identified by the M2M Service Provider Identifier (M2M-SP-ID). This is a static value assigned to the Service Provider. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7.1.2 Application Entity Identifier (AE-ID) | An Application Entity Identifier (AE-ID) uniquely identifies an AE resident on an M2M Node, or an AE that requests to interact with an M2M Node. An AE-ID shall identify an Application Entity for the purpose of all interactions within the M2M System. The AE-ID is globally unique and when used internally within a specifi... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7.1.3 Application Identifier (App-ID) | An Application Identifier (App-ID) uniquely identifies an M2M Application in a given context. More precisely, there are two types of App-ID: registration authority defined App-ID (registered App-ID) and non-registered App-ID. The establishment of the registered App-ID is guaranteed to be globally unique; the non-regist... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7.1.4 CSE Identifier (CSE-ID) | A CSE shall be identified by a globally unique identifier, the CSE-ID, when instantiated within an M2M Node in the M2M System. The CSE-ID is globally unique. When used internally within a specific M2M SP domain. It is sufficient to be unique within that M2M Service Provider domain. It is extended to become globally uni... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7.1.5 M2M Node Identifier (M2M-Node-ID) | An M2M Node, hosting a CSE and/or Application(s) shall be identified by a globally unique identifier, the M2M-Node-ID. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 44 The M2M System shall allow the M2M Service Provider to set the CSE-ID and the M2M-Node-ID to the same value. The M2M-Node-ID enables the M2M Service Provider to... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7.1.6 M2M Service Subscription Identifier (M2M-Sub-ID) | The M2M-Sub-ID enables the M2M Service Provider to bind application(s), M2M Nodes, CSEs and services identified by service identifiers, as well as administrative information, such as billing address, etc., to a particular M2M Service Subscription between an M2M subscriber and the M2M Service Provider. The M2M-Sub-ID is... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7.1.7 M2M Request Identifier (M2M-Request-ID) | The M2M-Request-ID tracks a Request initiated by an AE over the Mca reference point, and by a CSE over the Mcc reference point, if applicable, end to end. It is also included in the Response to the Request over the Mca or Mcc reference points. To enable an AE to track Requests and corresponding Responses over the Mca r... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7.1.8 M2M External Identifier (M2M-Ext-ID) | The M2M-Ext-ID is used by an M2M Service Provider (M2M SP) when services targeted to a CSE, identified by a CSE-ID, are requested from the Underlying Network. The M2M External Identifier allows the Underlying Network to identify the M2M Device (e.g. ASN, MN) associated with the CSE-ID. To that effect, the Underlying Ne... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7.1.9 Underlying Network Identifier (UNetwork-ID) | The UNetwork-ID is used for identifying an Underlying Network. UNetwork-ID is a static value and unique within a M2M Service Provider domain. One or more Underlying Networks may be available at an M2M Node offering different sets of capabilities, availability schedules etc. Based on the "policy" information at the Node... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7.1.10 Trigger Recipient Identifier (Trigger-Recipient-ID) | The Trigger-Recipient-ID is used when device triggering services are requested from the Underlying Network, to identify an instance of an ASN/MN-CSE on an execution environment, to which the trigger is routed. For example, when 3GPP device triggering is used, the Trigger-Recipient-ID maps to the Application-Port-Identi... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7.1.11 M2M Service Identifier (M2M-Serv-ID) | The M2M-Serv-ID is an identifier of a M2M Service offered by an M2M SP. It is an essential part of the M2M Service Subscription which stores a set of M2M-Serv-IDs pertaining to the set of subscribed services. Beyond the set of services depicted in the present document it shall be possible for an M2M Service Provider to... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7.1.12 Service Role identifier (SRole-ID) | In each M2M Service, one or multiple M2M Service Role(s) shall be defined by the M2M Service Provider. An M2M Service Role is defined as a create permission pertaining to resource types which are associated with M2M Service. See Annex G for examples of M2M Service Provider defined Service Roles. The Service Role Identi... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7.1.13 M2M Service Profile Identifier (M2M-Service-Profile-ID) | An M2M Service Profile Identifier defines M2M Service Roles (see annex G), as well as applicable rules governing the AEs registering with M2M Nodes and the AEs residing on these nodes. Every M2M Service Profile is allocated an identifier so it can be retrieved for verification purposes. The M2M-Service-Profile-ID enabl... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 7.3 M2M Identifiers lifecycle and characteristics | Table 7.3-1: M2M Identifiers lifecycle and characteristics Identifier Assigned by Assigned to Assigned during Lifetime Uniqueness Used during Remarks M2M Service Provider Identifier Out of scope AE, CSE Out of scope Out of scope Global Provisioning Application Entity Identifier AE or Registrar CSE AE AE start-up Applic... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8 Description and Flows of Reference Points | 8.1 General Communication Flow Scheme on Mca and Mcc Reference Points Procedures involving CSEs and AEs are driven by the exchange of messages across reference points according to the message flows described in this clause. Depending on the message operation, procedures may manipulate information in a standardized reso... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.1.1 Description | Figure 8.1.1-1 shows the general flow that governs the information exchange within a procedure, which is based on the use of Request and Response messages. The message applies to communications such as: • between an AE and a CSE (Mca reference point); and • among CSEs (Mcc reference point). Such communications can be i... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.1.2 Request | Requests over the Mca and Mcc reference points, from an Originator to a Receiver, shall contain mandatory and may contain optional parameters. Certain parameters may be mandatory or optional depending upon the Requested operation. In this clause, the mandatory parameters are detailed first, followed by those that are c... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.1.3 Response | The Response received by the Originator of a Request accessing resources over the Mca and Mcc reference points shall contain mandatory and may contain optional parameters. Certain parameters may be mandatory or optional depending upon the Requested operation (CRUDN) or the mandatory response code. In this clause, the m... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.2 Procedures for Accessing Resources | This clause describes the procedures for accessing the resources. The term "hop" in the descriptions here refers to the number of transit CSEs that forward a request from the Originator CSE to the Hosting CSE. All the descriptions and message flows in this clause are illustrative for the direction from a Registree acti... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.2.1 Accessing Resources in CSEs - Blocking Requests | For the procedures described herein, the addressed resource can be stored in different CSEs. Table 8.2.1-1 describes the possible scenarios, where the addressed resource may be on the Registrar CSE or on a CSE located elsewhere in the oneM2M System. In this clause - for simplicity - it is assumed that the Originator of... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.2.1.1 M2M Requests Routing Policies | CSEs can use policies to govern routing of M2M requests to the next hop towards its target. Routing, through these policies, can be based, for example, on the target CSE, target M2M domain, specific types of resources if applicable, priority of a request, etc. These policies are not defined in this release of the prese... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.2.2 Accessing Resources in CSEs - Non-Blocking Requests | 8.2.2.1 Response with Acknowledgement and optional Reference to Request Context and Capturing Result of Requested Operation In case the Originator of a Request has asked for only a response with an Acknowledgement indicating acceptance of the Request and an optional reference to the context where the result of the requ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.2.2.2 Synchronous Case | In the synchronous case, it is assumed that the Originator of a Request is not able to receive asynchronous messages, i.e. all exchange of information between Originator and Receiver CSE needs to be initiated by the Originator. In that case the information flow depicted in figure 8.2.2.2-1 is applicable. For the flow d... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.2.2.3 Asynchronous Case | In the asynchronous case, it is assumed that the Originator or other entities that need to know about the outcome of a Request are able to receive notification messages, i.e. the CSE carrying out the requested operation can send an unsolicited message to the Originator or to other indicated entities at an arbitrary tim... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.3 Description and Flows on Mcn Reference Point | Communications between the CSEs and the NSEs across the Mcn reference point include: • The CSE(s) accessing network service functions provided by Underlying Networks; and • Optimizing network service processing for Underlying Networks. Such services normally are more than just the general transport services. Communicat... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.4 Device Triggering | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.4.1 Definition and scope | Device Triggering is a means by which a node in the infrastructure domain (e.g. IN-CSE) sends information to a node in the field domain (e.g. ASN-CSE) to perform a specific task, e.g. to wake up the device, to establish communication from the field domain towards the infrastructure domain, or when IP address for the de... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.4.2 General Procedure for Device Triggering | This clause covers different scenarios for device triggering. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 73 |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.4.2.1 Triggering procedure for targeting ASN/MN-CSE | This case describes the scenario where IN-CSE targets an ASN/MN-CSE (which is registered with the IN-CSE) for the Device Triggering request. Figure 8.4.2.1-1 shows the general procedure for Device Triggering and, if required, for establishment of connectivity between IN-CSE and the Field Node. ASN/MN -CSE Device Trigge... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.5 Location Request | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.5.1 Definition and Scope | Location Request is a means by which a CSE requests the geographical or physical location information of a target CSE or AE hosted in a M2M Node to the location server located in the Underlying Network over Mcn reference point. This clause describes only the case of location request when the attribute locationSource is... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.5.2 General Procedure for Location Request | This procedure describes a scenario wherein an AE sends a request to obtain the location information of a target AE or CSE hosted in an M2M Node to the location server NSE, and the location server responses to the CSE with location information. Figure 8.5.2-1 shows the general procedure for Location Request. Figure 8.5... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.6 Connection Request | Connection request service is not defined in the present document. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 8.7 Device Management | See clause 6.2.4 for a detailed description on the interaction with a Device Management Server. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9 Resource Management | All entities in the oneM2M System, such as AEs, CSEs, data, etc. are represented as resources. A resource structure is specified as a representation of such resources. Such resources are uniquely addressable. Procedures for accessing such resources are also specified. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.1 General Principles | The following are the general principles for the design of the resource model. • The "type" of each resource shall be specified. New resource types shall be supported as the need for them is identified. • The root of the resource structure in a CSE shall be assigned an absolute address. See clause 9.3.1 for additional ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.2 Resources | This clause introduces the resources used in a CSE. A resource scheme is used for modelling the resource structure and associated relationships. Clause 9.5 provides guidelines on how to describe a resource. The present document identifies three categories of resources: • Normal resources (clause 9.2.1). • Virtual resou... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.2.1 Normal Resources | Normal resources include the complete set of representations of data which constitutes the base of the information to be managed. Unless qualified as either "virtual" or "announced", the resource types in the present document are normal resources. |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.2.2 Virtual Resources and Attributes | A virtual resource or a virtual attribute is used to trigger processing and/or retrieve results, but they do not have a permanent representation in a CSE. 9.2.3 Announced Resources An announced resource is a resource at a remote CSE that is linked to the original resource that has been announced, and it maintains some ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.3 Resource Addressing | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.3.1 Generic Principles | An address of a resource is a string of characters used to uniquely identify the targeted resource within the scope of a request to access the resources. The scope of a request can be: • CSE-relative: The request is targeting a resource that resides on the same CSE as the Receiver CSE of the request. In that case a CSE... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.3.2 Addressing an Application Entity | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.3.2.1 Application Entity Addressing | In M2M communication, the goal of M2M addressing is to reach the CSE with which the target AE is registered, and ultimately the target AE on the M2M Node on which the target AE is resident. This principle applies to all Application Entities. Reachability and routing from/to AEs on M2M Nodes is associated with the CSEs ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.3.2.2 Application Entity Reachability | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.3.2.2.1 CSE Point of Access (CSE-PoA) | The CSE-PoA shall be used by the M2M System to communicate with a CSE on an M2M Node. Once communication with a CSE is achieved, an AE registered with that CSE can be reached as long as the AE can be uniquely identified. The information included in the CSE-PoA as well as the refresh of the CSE-PoA, depends on the chara... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.3.2.2.2 Locating Application Entities | Locating an AE is a two-step process as follows: • Step 1: There is a need to locate the CSE where the AE is registered. Locating the CSE shall be accomplished as follows: - For AEs associated with ASNs/MNs/INs, the CSE-PoA of the ASN-CSE/MN-CSE/IN-CSE where the AE is registered shall be used. - For AEs associated with... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.3.2.2.3 Usage of CSE-PoA by the M2M System | The CSE-PoA holds the information used by the M2M System to locate routing information for a CSE. This information shall be provided by the CSE at registration time. However, the routing information related to a CSE (and ultimately to the target AE) in an M2M System depends on the characteristic of the Underlying Netwo... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.3.2.3 Notification Re-targeting | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.3.2.3.1 Application Entity Point of Access (AE-PoA) | A Notify request to an AE is sent by targeting <AE> resource on a Hosting CSE. If the Hosting CSE verifies access control privilege of the Originator, the Hosting CSE shall re-target the request to the address specified as AE-PoA (i.e. pointOfAccess attribute of <AE> resource). The AE-PoA may be initially configured in... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.4 Resource Structure | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.4.1 Relationships between Resources | CSE1 APP1 ACP1 CONT1 CONT2 ACP2 CSEBase1 Figure 9.4.1-1: Resource Relationships Example in a CSE NOTE: The resources shown in the above figure are: CSEBase1 is the name of a resource of type <CSEBase>. CSE1 is the name of a resource of type <remoteCSE>. APP1 is the name of a resource of type <AE>. CONT1 and CON... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.4.2 Link Relations | The following link relations are defined. Table 9.4.2-1: Link Relations Linked Resource Type (link destination) Linking Resource Types (link origin) Linking Method Description accessControPolicy Several (e.g. node, AE, remoteCSE, container) Attribute named accessControlPolicyIDs See clause 9.6.2 node CSEBase, remoteCSE... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.5 Resource Type Specification Conventions | The following conventions are used for the specification of resources. Resources are specified via a tabular notation and the associated graphical representation as follows: • The resources are specified in association with a CSE. The resources are the representation in the CSE of the components and elements within the... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6 Resource Types | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.1 Overview | |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.1.1 Resource Type Summary | Table 9.6.1.1-1 introduces the normal and virtual resource types and their related child or parent resource types. Details of each resource type follow in the remainder of this clause. Table 9.6.1.1-1 lists each specified <resourceType>. An addition of suffix "Annc" to such <resourceTypes> indicates the associated anno... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.1.2 Resource Type Specializations | Table 9.6.1.2-1 lists specializations of the <mgmtObj> resource Type in which the mgmtDefinition attribute contains an enumerated value that provides further definition of the resource. Table 9.6.1.2-1 Resource Types Specializations Resource specialization Short Description Child Resource Types Parent Resource Types Cl... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.1.3 Commonly Used Attributes | Some attributes described herein are present in all <resourceTypes>. Such attributes are described in clause 9.6.1.3.1 once in order to avoid duplicating the description for every <resourceType> and are referred to as "universal attributes". Some other attributes described herein are commonly used in multiple, but not ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.1.3.1 Universal attributes | The following attributes are universal to all resource types. Table 9.6.1.3.1-1: Universal Attributes Attribute Name Description resourceType Resource Type. This Write Once (assigned at creation time. and then cannot be changed) attribute identifies the type of the resource as specified in clause 9.6. Each resource sha... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.1.3.2 Common attributes | The following attributes are commonly used in multiple, but not all, resource types. NOTE: The list of attributes in table 9.6.1.3.2-1 is not exhaustive. Table 9.6.1.3.2-1: Common Attributes Attribute Name Description accessControlPolicyIDs The attribute contains a list of identifiers of an <accessControlPolicy> resour... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.2 Resource Type accessControlPolicy | The Access Control Policies (ACPs) shall be used by the CSE to control access to the resources as specified in the present document and in ETSI TS 118 103 [1]. The ACP is designed to fit different access control models such as access control lists, role or attribute based access control. The <accessControlPolicy> resou... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.2.1 accessControlOriginators | The accessControlOriginators is a mandatory parameter in an access-control-rule-tuple. It represents the set of Originators that shall be allowed to use this access control rule. The set of Originators is described as a list of parameters, where the types of the parameter can vary within the list. Table 9.6.2.1-1 descr... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.2.2 accessControlContexts | The accessControlContexts is an optional parameter in an access-control-rule-tuple that contains a list, where each element of the list, when present, represents a context that is permitted to use this access control rule. Each request context is described by a set of parameters, where the types of the parameters can v... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.2.3 accessControlOperations | The accessControlOperations is a mandatory parameter in an access-control-rule-tuple that represents the set of operations that are authorized using this access control rule. Table 9.6.2.3-1 describes the supported set of operations that are authorized by accessControlOperations. The following accessControlOperations s... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.3 Resource Type CSEBase | A <CSEBase> resource shall represent a CSE. The <CSEBase> resource shall be the root for all resources that are residing in the CSE. ETSI ETSI TS 118 101 V1.0.0 (2015-02) 95 <CSEBase> 0..1 cseType 1 CSE-ID 0..1 nodeLink <node> 0..n <AE> 0..n <container> 0..n <group> 0..n <subscription> 0..n <accessControlPolicy> 0..n <... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.4 Resource Type remoteCSE | A <remoteCSE> resource shall represent a Registree CSE that is registered to the Registrar CSE. <remoteCSE> resources shall be located directly under the <CSEBase> resource of Registrar CSE. Similarly <remoteCSE> resource shall also represent a Registrar CSE. <remoteCSE> resource shall be located directly under the <CS... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.5 Resource Type AE | An <AE> resource shall represent information about an Application Entity registered to a CSE. <AE> 0..1 (L) appName 1 App-ID 1 AE-ID 0..1 (L) pointOfAccess 0..1 ontologyRef nodeLink <subscription> 0..n <container> 0..n <group> 0..n <accessControlPolicy> 0..n <pollingChannel> 0..n 0..1 Figure 9.6.5-1: Structure of <AE> ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.6 Resource Type container | The <container> resource represents a container for data instances. It is used to share information with other entities and potentially to track the data. A <container> resource has no associated content. It has only attributes and child resources. <contentInstance> 0..n <subscription> 0..n <container> 0..n <container>... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.7 Resource Type contentInstance | The <contentInstance> resource represents a data instance in the <container> resource. The content of the contentInstance can be encrypted. Unlike other resources, the <contentInstance> resource shall not be modified once created. An AE shall be able to delete a contentInstance resource explicitly or it may be deleted ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.8 Resource Type subscription | The <subscription> resource contains subscription information for its subscribed-to resource. The <subscription> resource is a child of the subscribed-to resource. The <subscription> resource shall be represented as child resource of the subscribed-to resource. For example, <container> resource has <subscription> resou... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.9 Resource Type schedule | The <schedule> resource contains scheduling information. The usage of the <schedule> resource is slightly different depending on the associated resource type, such as follows: • A child <schedule> resource of the <CSEBase> and <remoteCSE> resources shall indicate the time periods when the CSE can send and receive the r... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.10 Resource Type locationPolicy | The <locationPolicy> resource represents the method for obtaining and managing geographical location information of an M2M Node. The actual location information shall be stored in a <contentInstance> resource which is a child resource of the <container> resource. The <container> resource includes the locationID attribu... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.11 Resource Type delivery | When a CSE is requested to initiate an operation (CRUDN) targeting resources on another CSE, then it needs to do scheduling and execution of delivery of data from the source CSE to the target CSE in line with the provisioned policies. It shall be in one of the following ways: • Using delivery aggregation (Delivery Aggr... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.12 Resource Type request | The use of <request> resource type is optional depending on the configuration. Creation of a <request> resource can only be done on a Receiver CSE implicitly when a Registree AE or a Registree/Registrar CSE issues a request to the Receiver CSE targeting any other resource type or requesting a notification. Creation of ... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.13 Resource Type group | The <group> resource represents a group of resources of the same or mixed types. The <group> resource can be used to do bulk manipulations on the resources represented by the memberIDs attribute. The <group> resource contains an attribute that represents the members of the group and a virtual resource (the <fanOutPoint... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.14 Resource Type fanOutPoint | The <fanOutPoint> resource is a virtual resource because it does not have a representation. It is the child resource of a <group> resource. Whenever a request is sent to the <fanOutPoint> resource, the request is fanned out to each of the members of the <group> resource indicated by the membersIDs attribute of the <gro... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.15 Resource Type mgmtObj | The <mgmtObj> resource contains management data which represents individual M2M management functions. It represents a general structure to map to external management technology e.g. OMA DM [i.4], BBF TR-069 [i.3] and LWM2M [i.5] data models. Each instance of <mgmtObj> resource shall be mapped to single external managem... |
2c349d1ce77517f6264df36b5ac18419 | 118 101 | 9.6.16 Resource Type mgmtCmd | The <mgmtCmd> resource represents a method to execute management procedures or to model commands and remote procedure calls (RPC) required by existing management protocols (e.g. BBF TR-069 [i.3]), and enables AEs to request management procedures to be executed on a remote entity. It also enables cancellation of cancell... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.