X50 20111019 015r1 5 ZTE M2M Study Report Architecture Reference Model

Document Sample
X50 20111019 015r1 5 ZTE M2M Study Report Architecture Reference Model Powered By Docstoc
					                                                                                                                                                       Style Definition: Normal: Indent: Left: 0"




Title:                            M2M Architecture Reference Model

Abstract:                         This contribution proposes the Architecture Reference Model for
                                  “cdma2000 networks enhanced for M2M services”.




Source:                           Rajesh Bhalla (rabhalla@zteusa.com)




Date:                             October 19, 2011

Recommendation:                   Review and adopt.



Notice


ZTE grants a free, irrevocable license to 3GPP2 and its Organization Partners to incorporate text or other copyrightable material contained in the
contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partner’s name any
Organizational Partner’s standards publication even though it may include portions of the contribution; and at the Organization Partner’s sole
discretion to permit others to reproduce in whole or in part such contributions or the resulting Organizational Partner’s standards publication.
ZTE is also willing to grant licenses under such contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for
purpose of practicing an Organizational Partner’s standard which incorporates this contribution


This document has been prepared by ZTE to assist the development of specifications by 3GPP2. It is proposed to the Committee as a basis for
discussion and is not to be construed as a binding proposal on the contributor. ZTE 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 the
contributor other than provided in the copyright statement above.
- Introduction



                 * * * Start of Changes * * *
2           3GPP2 M2M Architecture
[Editor's Note: This section is intended to list the architectural requirements necessary to support the objectives of
the WID. Service requirements are to be listed in TBD.]

      2.1         Architectural Requirements                                                                             Formatted: Indent: Left: 0.25", Space
                                                                                                                         Before: 0 pt, After: 8 pt, No widow/orphan
[Editor’s Note: Contributions to this section should follow after agreements are achieved in the Required                control, Tab stops: 0.86", List tab + Not at
Functionality sub-clauses of individual Key Issues. Add titles for sub-sections]


2.2         Architectural Principles




2.3         Architectural Model



      2.4         Architectural Reference Model for M2M Services                                                         Formatted: Indent: Left: 0.25", Space
                                                                                                                         Before: 0 pt, After: 8 pt, No widow/orphan
            End-to-end services between the M2M Applications at the UEs used for M2M and the M2M Applications            control, Tab stops: 0.86", List tab + Not at
            in the external network use services provided by the 3GPP2 system, and optionally services provided by       Formatted: (none)
            an M2M Server. The 3GPP2 system provides transport and communication services (including 3GPP2
            bearer services, IMS and SMS) and various optimizations that can facilitate M2M type of
            servicescommunications.

            Figure 2.4-1 shows a UE used for M2M connecting to a 3GPP2 network (1x, HRPD , eHRPD etc.) via the
            Um interface. This reference architecture covers various architectural models described in Section 2.3
            above.

              -    Direct Model – Direct Communication provided by the 3GPP2 Network Operator:
                   The M2M Applications in the external network connects directly to the M2M Applications in the
                   UEs used for M2M device viain the 3GPP2operator network without the use of any M2M Server;

              -    Indirect Model – M2M Service Provider controlled communication:
                   Uses an M2M Server that is an entity outside the 3GPP2 network operator domain for enabling
                   communications between the Applications in the external network and at the UEs used for M2M.
                   Interfaces M2Mip, M2Mspctl and M2Msms are external interfaces that the third party M2M
                   Server supports with the entities that are in the 3GPP2 network domain;

              -    Indirect Model – 3GPP2 Operator controlled communication:
                   Uses an M2M Server that is an entity inside the 3GPP2 network operator domain for enabling
                   communications between the Applications in the external network and at the UEs used for M2M.
                   Interfaces M2Mip, M2Mspctl and M2Msms are internal interfaces that the 3GPP2 network
                   operator controlled M2M Server supports with other entities within the 3GPP2 network domain;

              -    Hybrid Model:
                   Direct and Indirect models are used simultaneously in the hybrid model i.e., performingdoing
                   Control Plane signalling using the Indirect Model and connecting the Applications in the external
                   network and at the UEs used for M2M over User Plane using the Direct Model.
                                                              Legacy SMS
                                                                                            SMS
                                                                                            -SC
                                                 AAA
                                                                                                         M2Msms          M2M Service Provider Controlled


                                                               Internal                                                                 3GPP2 Operator Controlled
                                                              Interfaces                M2M -
                                                                (TDB)                    IWF
                                 Um
                                                                                        c           M2Msp
   M2M Device                                                  Internal                                        1
      M2M
                                         RAN                  Interfaces                 HA/                                M2M                             M2M         M2M
                                                                                        LMA/                               Server                         Application   User
    Application
                                                                                        PDSN              IP                                API


                                                                                                                                                    2
                                                                                                     IP
                                             Indirect Model         1

                                              Direct Model          2
    Control Plane
    User Plane
                                                                                                                3GPP2
                                             Hybrid Model           1    +      2
                                                                                                               Boundary

                                                                Legacy SMS
                                                                                                                                                                               Formatted: Centered, Indent: Left: 0", First
                                                                                            SMS
                                                                                            -SC
                                                                                                                                                                               line: 0"
                                                       AAA
                                                                                                    M2Msms         M2M Service Provider Controlled
                                                                         Px
                                                                                                                               3GPP2 Operator Controlled
                                                                Pyz                         M2M -
                                                                                             IWF
                                                                              M2Mtgr

                                        Um                                                          M2Mctl
                                                RAN/                                                                                1
                     MTC                                                                     HA/                       M2M                    M2M           MTC
                   Application   UE              AN                     PDSN/
                                                                        HSGW                LMA/                      Server                Application     User
                                                         M2Ma10                             P-GW    M2Mip                      API


                                                   Indirect Model         1                                                             2
                                                                                                    IP
                                                    Direct Model          2
                        Control Plane
                                                    Hybrid Model          1     +   2                       3GPP2
                           User Plane
                                                                                                           Boundary


                  Figure 2.4-1: 3GPP2 Architecture Reference Model for M2M Communications                                                                                      Formatted: Highlight

          Editor’s Note: The Architecture Reference Model above is a high level illustration thatand is intended to                                                            Formatted: Highlight
          evolve into several separate referencearchitecture models illustrations based on the IP Addressing Mode                                                              Formatted: Highlight
          (SIP, (P)MIP) , the type of 3GPP2 access network technology, and home routed/local breakout roaming                                                                  Formatted: Highlight
          scenarios etc. Details of interfaces within the 3GPP2 network such separate architecture illustrations are
                                                                                                                                                                               Formatted: Indent: Left: 0.5"
          FFS.
                                                                                                                                                                               Formatted: Highlight

          Editor’s Note: Support of EPC entities such as P-GW via cdma2000 eHRPD access is FFS and is not                                                                      Formatted: Highlight
          shown in the architecture reference model above.                                                                                                                     Formatted: Highlight
                                                                                                                                                                               Formatted: Highlight
The ‘M2M Application’ entity and the reference point ‘API’ in the figure above are outside of scope of 3GPP2.
                                                                                                                                                                               Formatted: Highlight
They are illustrated as abstracts to show the end-to-end view for M2M communications and to facilitate mapping to
M2M specifications of other standardization organizations.                                                                                                                     Formatted: Highlight
                                                                                                                                                                               Formatted: Highlight
In the roaming scenarios, the UE used for M2M obtains services by means of the Um interface provided by the                                                                    Formatted: Highlight
Visited operator domain.                                                                                                                                                       Formatted: Highlight
                                                                                                                                                                               Formatted: Highlight
                                                                                                                                                                               Formatted: Indent: Left: 0.5"
                                                                                                                                                                               Formatted: Highlight
The M2M Server is an entity which connects to the 3GPP2 network, via M2M-IWF or SMC-SC for device
triggering, to enable communicationse between Applications in the external network and at the with UEs used for
M2M. in the 3GPP2 network.

In the roaming scenarios, the UE used for M2M obtains services by means of the Um interface provided by the
Visited operator domain.

The ‘M2M Application’ entity and the reference point ‘API’ in the figure above are outside of scope of 3GPP2.
They are illustrated as abstracts to show the end-to-end view for M2M communications and to facilitate mapping to
M2M specifications of other standardization organizations.

    2.5         Reference Points                                                                                       Formatted: Heading 2,h2,h21,heading
                                                                                                                       21,h22,h23,THeading 2,H2,UNDERRUBRIK
                                                                                                                       1-2,R2,H21,E2,2nd level
 2.5.1         General

The following 3GPP2 reference points support the Indirect and Hybrid models for M2M type of communications.

 2.5.2         List of Reference Points

The description of the M2M services related reference points:

   M2Msms:            This is the reference point that an entity outside the 3GPP2 networksystem e.g., the M2M
                      Server uses to trigger communicationse with UEs used for M2M via SMS.
   M2Mspctl:          This is the reference point an entity outside the 3GPP2 networksystem e.g., the M2M Server
                      uses to trigger communicationse with UEs used for M2M viathe the M2M-IWF overvia control
                      plane signalling.
   M2Mtgr:            This is the reference point between M2M-IWF and PDSN/HSGW for the exchange of control
                      plane signalling e.g. device triggering related messages.
   Px:                This is the reference point between M2M-IWF and the AAA Server for the mapping of the
                      “chosen” external identifier of the UE used for M2M to its 3GPP specific identifier (i.e. ESN,
                      IMSI, UATI etc), and retrieving the information about the RAN/AN to be used for reaching the
                      UE.
   Pyz:               This is the (existing) reference point between the PDSN/HSGW and the AAA Server. Amongst         Formatted: Font: Not Bold, Check spelling and
                      other functions, this reference point is used by the PDSN/HSGW for updating the presence         grammar
                      information of the UE used for M2M at the AAA Server.
   M2Ma10:            This is the reference point that the PDSN/HSGW uses to communicate with the RAN/AN for           Formatted: Font: Not Bold, Check spelling and
                      the delivery of M2M device triggering information to the RAN/AN.                                 grammar


                                                                                                                       Formatted: Indent: Left: 0", First line: 0"
          Editor’s Note: The final set of reference points for supporting Indirect and Hybrid models for M2M
          services is FFS and is dependent on the solutions selected for addressing the M2M Key Issues.                Formatted: Not Highlight

Protocol Assumptions:                                                                                                  Formatted: Indent: Left: 0"

    -     User plane communications between the M2M Applications at the M2M Devices and at the M2M Server              Formatted: B2, Bulleted + Level: 1 + Aligned
          for the Indirect model, and between the Applications at the M2M Devices and in the external network for      at: 0.25" + Indent at: 0.5"
          the Direct and Hybrid models are IP-packet based.


 2.5.3         Reference Point Requirements                                                                            Formatted: Heading 4,H4,h4,h41,heading
                                                                                                                       41,h42,heading 42,h43,H41,H42,H43,H411,h41
2.5.3.1         M2Msms Reference Point                                                                                 1,H421,h421,H44,h44,H412,h412,H422,h422,H4
                                                                                                                       31,h431,H45,h45,H413,h413,H423,h423,H432,h
The functions provided by the M2Msms reference point are FFS.                                                          432,H46,h46,H47,h47,E4,4H, Indent: Left: 0"
                                                                                                                       Formatted
2.5.3.2            M2Msp Reference Point

The M2Msp reference point shall fulfill the following requirements:

    -     Interface an M2M-IWF with one or more M2M Servers

    -     Support the following services:

              a.    Reception of device trigger requests from the M2M Server                                          Formatted

              b.    May report acknowledgment of device trigger requests to the M2M Server

              c.    Report success or failure of device trigger requests to the M2M Server

          Editor’s Note: Additional requirements for M2Msp reference point are FFS and are dependent on the
          solutions selected for addressing the M2M Key Issues.

    -     May support secure communications with the M2M Server



                                                                                                                      Formatted: Indent: Left: 0"


    2.6            Network Elements

 2.6.1         General

The following 3GPP2 network elements provide functionality to support the Indirect and Hybrid models for M2M
services. In addition, IMS network elements may provide functionality to support the Indirect and Hybrid models for
M2M services.

          NOTE: As further development of the M2M architecture takes place and as solutions related to M2M Key
          Issues and features are agreed to, further network elements and associated functionality may be defined.

 2.6.2         M2M-IWF

In order to support the Indirect and Hybrid models for M2M services, one or more instances of an M2M
InterWorking Function (M2M-IWF) is provided in the Home 3GPP2 network domain of the M2M Devices. An
M2M-IWF could be a standalone entity or a function provided by another 3GPP2 network element. The M2M-IWF
hides the internal topology of the 3GPP2 network from the M2M Server, and relays or translates the signaling
messages used over the M2Msp interface to invoke 3GPP2 network specific functionality.

          Editor’s Note: If the M2M Server connects to the M2M-IWF and the SMC-SC in the home 3GPP2 network           Formatted: Highlight
          domain only, or in the Visited network domain also of a roaming UE used for M2M is FFS.

The M2M-IWF provides the following functions:

    -     Terminates the M2Msp reference point

    -     May authenticate the M2M Server before initiating device trigger procedures with the 3GPP2 network

    -     May authorize the control plane messages from the M2M Server

    -     Support the following control plane messages with an M2M Server:

              a.    Receive device trigger request messages
             b.   May report device trigger request acknowledgment messages

             c.   Report device trigger delivery success and failure report messages

         Editor’s Note: The signaling protocol used over M2Msp interface is FFS. Such protocol is to be aligned
         with the protocol developed by the 3GPP SA2/CT working groups for the Tsp interface. Such protocol may
         be enhanced to support 3GPP2 specific functionality, if any, by way of 3GPP2 specific information
         elements/AVPs etc.

    -    Perform protocol translation, if necessary, and forward the device trigger request(s) received from the
         M2M Server towards the relevant 3GPP2 network entity.

    -    May support secure communications between the M2M Server and the 3GPP2 network

    -    Others <tbd>

 2.6.3        AAA

The AAA provides functions to support the Indirect and Hybrid models for M2M Services.

         Editor’s Note: M2M specific functions provided by the AAA is FFS and are dependent on the solutions
         selected for addressing the M2M Key Issues.

 2.6.4        HA/LMA

The HA/LMA provide functions to support the Indirect and Hybrid models for M2M Services.

         Editor’s Note: M2M specific functions provided by the HA/LMA is FFS and are dependent on the
         solutions selected for addressing the M2M Key Issues.

 2.6.5        PDSN

The PDSN provides functions to support the Indirect and Hybrid models for M2M Services.

         Editor’s Note: M2M specific functions provided by the PDSN is FFS and are dependent on the solutions
         selected for addressing the M2M Key Issues.

                                                                                                                   Formatted: Indent: Left: 0"


                                         * * * End Changes * * *

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:4
posted:9/29/2012
language:Latin
pages:7