TIA TR-50 Smart Device Communications: Standards Update and Security Enhancements

1. TIA M2M Standards UpdateTR-50 Smart Device Communications Jeffrey O. Smith, Ph.D. Chief Technical Officer of Numerex Chair of TIA TR-50

2. TIA TR-50 Smart Device Communications • Following presentation by Telecommunications Industry Association (TIA) delegation at GSC-14, TIA Engineering Committee on Smart Device Communications was launched in December 2009; Chair and Vice Chair were elected in February 2010. • TR-50.1 subcommittee on Requirements and Architecture was subsequently created; Chair and Vice Chair were elected in April 2010. • TR-50 Security Ad Hoc group was formed to support and enhance SDC architecture; Chair and Vice Chair were appointed by TIA TR-50 Chair in February 2011.

3. TIA TR-50 Scope(Chair: Jeffrey Smith, Numerex; Vice Chair: Jim Wert, ILS Technology) • Engineering Committee TR-50 Smart Device Communications is responsible for the development and maintenance of access agnostic interface standards for the monitoring and bi-directional communication of events and information between smart devices and other devices, applications or networks. • TR-50 will develop a Smart Device Communications framework that can operate over different underlying transport networks (wireless, wired, etc.) and can be adapted to a given transport network by means of an adaptation/convergence layer. • The TR-50 framework will make its functionality available to applications through a well-defined Application Programming Interface (API) that is agnostic to the vertical application domain (eHealth, Smart Grid, Industrial Automation, etc.)

4. TIA TR-50.1 ScopeRequirements and Architecture (Chair: Peter Nurse, Sigma Delta; Vice Chair: Mitch Tseng, Huawei) • Requirements shall be agnostic to the application (e.g. eHealth, Smart Grid, Industrial Automation, etc.), but shall reflect the requirements of the applications of interest. Examples of such publications include Use Cases and Stage-1 Descriptions. • System architecture shall be agnostic to the application, but shall reflect the requirements of the applications of interest, including their information models. • Data models requirements shall be agnostic to the application, but shall reflect the requirements of the applications of interest. • In its work, Subcommittee TR-50.1 shall take account of the following: Security (e.g., data content, authentication, signaling); End to End Performance and scalability of equipment and networks; and Device Management (incl. discovery and identity)

5. TR 50 Security Ad Hoc Scope(Chair: Chuck Bokath, Georgia Tech Research Institute; Vice Chair MihaiVoicu: ILS Technology ) • The scope of work within TR-50 SDC Security Ad Hoc includes the following: Participate with TR-50 and its other subcommittees to contribute requirements, architecture, protocols, etc. related to the topic of security in Smart Device Communications. Review and approve all ballots by TR-50 and its subcommittees to ensure that any architectures, protocols, or specifications meet the requirements set by the SDCSS for a secure solution. • Additional directives to be followed by the TR-50 SDCSG: The architecture, protocol, or specification should support options that can be exported without undue overhead from countries for which TIA serves as a regional Standards Development Organization (SDO). • Guidelines include the Cryptographic Interoperability Strategy that uses a multi layer approach enabling multiple zone security while data is in transit, security profiles to best “fit” each class of device, secured sharing suite that utilizes common standards, protocols and cipher algorithms, threat analysis and metrics to assess security issues and the creation of a security test bed for private and commercial use

6. Update (1) • SDC Standards in final stage of publication • Provide a reference architecture, describing functional elements and their interconnection. • Provide identified use cases and demonstrate the applicability of the reference architecture to the support of those use cases. • Ballot Resolution in October; Publication in December, 2011. • SDC Protocol Stack unchanged from GSC-15

7. Update (2) • Introduce SDC High-Level System Architecture • Introduce “Containers” concept to better describing functional elements and their logical interconnections. • Will continue work on “Convergence Layer” and harmonize with other standard entities.

8. Update (3) • Security: Guidance and Implementation documents for each logical level of the architecture • Data In Transit (Phase 2 of 2) • Multilayer Security • Finishing Security Zone Definitions • Data At Rest (Phase 1 of 2) • Trusted Environments • Draft Phase • Threat Analysis (Phase 2 of 2) • Risk Analysis • (Application, OS, User Data & Network) • Financial Impact • Finishing Attack Trees • GT M2M Testbed (Phase 1 of 3) • Assess selected M2M systems to identify cyber vulnerabilities. Testing is planned and conducted in collaboration with the interested industry partner and may be performed in the laboratory (test bed) environment or at the partner's site. • Provide M2M Security training through workshops that describe common cyber vulnerabilities found in M2M systems and effective methods for mitigation. • Share with appropriate standard's organizations information that can be used to support the development of improved industry standards applicable to control system security. • Participate in conferences that include M2M security topics to share information obtained through system assessments and analyses. • Underway

9. Other M2M-related Standard Work at TIA

10. Highlight of Current M2M Activities In TIA TR-45 Mobile and Personal Communications Systems • TR-45 M2M work is developed in partnership with 3GPP2 • M2M communication carried over cdma2000 1x or HRPD networks • cdma2000 role is largely confined to serve as a transport network, providing services to external M2M entities (M2M service layers and M2M applications) • M2M services may have their own specific characteristics which might be different from services in which humans directly influence communication flow. This may require some special handling or optimization on cdma2000 network for better support of M2M communications • Some of the M2M requirements apply to both M2M and H2H (Human-to-Human) devices

11. M2M Numbering and Addressing for cdma2000 Networks • Analyzing issues associated with M2M Numbering, Identification and Addressing aspects of M2M technologies and services using TIA specifications, including: • M2M numbering and addressing schemes • Investigation of Global M2M numbering issues with liaison with industry M2M committees and stakeholders • Evaluation of M2M numbering resources/methods and identifying impacts on legacy numbering and back office systems • Planned publication as TIA-4962 (3GPP2 SC.R4005-0) in 4Q2011

12. M2MSystems Requirements for cdma2000 Networks • System requirements for M2M communication using cdma2000 1x and HRPD are in development • The specification will guide the work of the enhancements required to the cdma2000 technology for the support of M2M communication. The intent is to provide guidance to which areas could require improvements and also to understand potential external coordination with other industry forums to assist in the development of the overall solution for M2M • Planned publication as TIA-4954 (3GPP2 S.R0146) in 2Q2012

13. Next Steps for cdma2000 Networks • Prioritize the key use cases and solutions • Operator needs • Vendor needs • Development of the appropriate specifications • New specification and/or new versions of existing documents as required • Completion for phase 1 specifications is to be determined • Continue work on the M2M Communication Systems Requirements for future phases. • M2M landscape is evolving • Continue work on the next set of use cases and solutions as part of the M2M Architecture and Enhancement Study for cdma2000 Networks

14. THANK YOU!