TR50-20120508-005
Title: Proposed Outgoing Correspondence
Distribution: TR 50
PN: Not applicable
Source: Chair, TR-50
Contact: Peter W. Nurse, Sigma Delta Communications, Inc.
peter.nurse@sigmadelta.com
Abstract: This contribution proposes text for proposed outgoing correspondence.
Intended Purpose of 
Document: 

For incorporation into TIA publication
For information
Other: Review, amend as appropriate and approve.
Notices:
The document to which this cover statement is attached is submitted to a Formulating Group or sub-element
thereof of the Telecommunications Industry Association (TIA) in accordance with the provisions of Sections
6.4.1-6.4.6 inclusive of the TIA Engineering Manual dated October 2009, all of which provisions are hereby
incorporated by reference.
This document has been prepared by Sigma Delta Communications, Inc. to assist the TIA Engineering
Committee. It is proposed to the Committee as a basis for discussion and is not to be construed as a binding
proposal on Sigma Delta Communications, Inc. Sigma Delta Communications, Inc. specifically reserves the
right to amend or modify the material contained herein and nothing herein shall be construed as conferring
or offering licenses or rights with respect to any intellectual property of Sigma Delta Communications, Inc.
other than provided in the copyright statement above.
© Copyright Sigma Delta Communications, 2016
1
1)
OPC Foundation
2
3
4
To:
Thomas J. Burke
OPC Foundation President & Executive Director
5
6
7
8
9
10
11
Thank you for your correspondence dated 2012-02-22, which was entered into our record in
contribution TR50-20120305-004. Both your correspondence and your document, OPC Unified
Architecture for the Internet of Things, was made available to the membership of TR-50 during
our meeting of 2012-03-05 in Atlanta. Your document was further discussed during our meeting
of 2012-05-08, and our membership found it very useful.
12
13
14
15
We welcome further input from the OPC Foundation as a member of TR-50. Members of OPC
Foundation may wish to join TR-50 and provide input directly. Please let me know if I can help
with that process.
16
17
18
19
20
We share your belief in the tremendous value of a collaborative arrangement between OPC
Foundation and TR-50, and would be happy to collaborate in as efficient a manner as possible.
We also share your view that our Standards should lead to the development of real products and
real solutions.
21
1
1
2)
Broadband Forum
2
3
4
5
6
7
8
To:
Christophe Alter
Broadband Forum Technical Committee Chair
christophe.alter@orange.com
Copy: Tim Spets
Motorola Mobility
tspets@motorola.com
9
10
11
12
Thank you for your correspondence dated 2012-03-14, which was entered into our record in
contribution TR50-20120404-004.
13
14
« insert text from out-reach »
15
2
1
3)
Out-Reach
2
3
To:
« see potential recipient list. »
4
5
6
We wish to inform your organization of recent changes within Committee TR-50 and our
ongoing work in the M2M space.
7
8
9
10
a)
Changes within Committee TR-50
At our meeting that convened on 2012-01-26, all work was consolidated into Committee TR-50.
Consequently, Subcommittee TR-50.1 has been disbanded.
11
12
13
14
15
Since the creation of the Committee, the term machine-to-machine and its acronym M2M has
entered the vernacular and more closely describes the work of the Committee. At their meeting
of 2012-04-04, the Committee agreed to request a name change to M2M-Smart Device
Communications. This name change was approved by Technical Committee on 2012-04-26.
16
17
18
19
20
21
b)
Current Work Program
Having completed our initial work culminating in the publication of TIA-4940-005, Smart
Device Communications; Reference Architecture, in the fourth quarter of 2011, we have
embarked on the next phase of standards development. At our meeting of 2012-01-26, the
Committee adopted the work program outlined below.
22
23
24
25
i)
Reference Architecture
We have found it useful to note at the outset that our reference architecture assumes IP
connectivity.
26
27
28
29
30
31
To avoid any unnecessary delay in updating the Reference Architecture, we have initiated a
project to create a revision of part 005. If there is no identified need to change the document,
then the document need not be updated.
PN-4940-005-A M2M-Smart Device Communications;
Reference Architecture
32
33
34
35
36
37
ii)
Protocol Aspects
Although the work within the Committee is access network agnostic, it seems pragmatic to use
features in the underlying access network to optimize overall operation. We have initiated a
project to provide normative information regarding mechanisms to discover and invoke features
of the underlying transport network, PN-4940-021.
38
39
40
41
Our architecture attempts to impose no business model on implementations. We have initiated a
project to provide normative information regarding the secure deployment of applications into a
container that may belong to a third party, PN-4940-022.
42
43
44
45
46
In the informative Annex of TIA-4940-005 there is reference to REST-ful primitives, and their
mapping onto HTTP-based primitives. While representing only one of a number of possible
mappings, we have initiated a project to provide normative material for the mapping of REST-ful
primitives onto HTTP-based primitives, PN-4940-023.
3
1
2
3
4
5
6
7
8
9
10
11
12
13
14
The list of projects is as follows:
PN-4940-020
M2M-Smart Device Communications;
Protocol Aspects;
Introduction
PN-4940-021
M2M-Smart Device Communications;
Protocol Aspects;
Optimizing Access Network Capabilities
PN-4940-022
M2M-Smart Device Communications;
Protocol Aspects;
Deploying and Securing Applications
PN-4940-023
M2M-Smart Device Communications;
Protocol Aspects;
Using HTTP family
15
16
17
18
19
20
21
22
23
iii)
Capabilities
The work within the Committee is access network agnostic. Consequently, a realization of, for
example, the PoA entity in our reference architecture could rely on different and potentially
simultaneously active network connections and changes in that network environment would need
to be signaled to the applications. Consequently we have created a project to detail the
capabilities of the underlying software containers. The list of projects is as follows:
PN-4940-050
M2M-Smart Device Communications;
Capabilities
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
iv)
Standard Objects
The work within the Committee is agnostic to the application domain. In the informative Annex
of TIA-4940-005 there is reference to a standardized interface maintained by devices (aka device
abstraction) and applications: standard objects. We have initiated a series of projects to provide
normative information regarding standard objects, including specifying message syntax, message
semantics, and message exchange protocols. We have selected a small subset of sensors and
actuators, but this list may be expanded rapidly as we gain experience. The current list of
projects is as follows:
PN-4940-100
M2M-Smart Device Communications;
Standard Objects;
Introduction
PN-4940-101
M2M-Smart Device Communications;
Standard Objects;
Switches
PN-4940-102
M2M-Smart Device Communications;
Standard Objects;
Temperature Sensors and Controllers
PN-4940-103
M2M-Smart Device Communications;
Standard Objects;
Pressure Sensors and Controllers
PN-4940-104
M2M-Smart Device Communications;
Standard Objects;
Motion Sensors and Controllers
4
1
v)
Security Aspects
4
We also consider security aspects to be critically important to the nascent M2M space, and have
conducted a threat analysis, which we intend to publish as a Telecommunication Systems
Bulletin, TSB-4940.
5
c)
6
We welcome opportunities for collaboration in any areas of mutual interest.
2
3
Collaboration
7
8
5
1
4)
Potential recipients list:
Application
Automotive
Automotive
Automotive
Building
Automation
Building
Automation
Building
Automation
Health
Health
Industrial
Automation
Smart Grid
Organization
ATIS
Broadband Forum
CableLabs
Continental Automated Buildings Association
(CABA)
CTIA
ETSI TC M2M
HART Communication Foundation
Inmarsat
International Society of Automation
Internet Protocol for Smart Objects Alliance
ngConnect
Organization for the Advancement of Structured
Information Standards
ITS America
SAE International
TR-48
Building Automation and Control Networks
Home Gateway Initiative
Open Building Information Exchange, oBIX
Continua Health Alliance
TR-49
AIA – Automation Industry Association
Smart Grid Interop Group NIST
OMA
Cloud Security Alliance
TIA ETSC
TMforum
OMG
info@omg.org
2
3
6