Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.682  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   4.2   4.3…   4.4…   4.5…   4.5.7…   4.5.14…   4.6…   5…   5.3…   5.5…   5.6…   5.6.2…   5.6.6…   5.7…   5.8…   5.9…   5.13…   5.14…   5.15   5.16   5.17…   5.18   5.19…   A…   C…

 

A  MTC Deployment ScenariosWord‑p. 126

In the indirect and hybrid models, the deployment of a SCS may be inside or outside the operator domain as illustrated in Figures A-1 and A-2. When the SCS is part of the operator domain (Figure A-1 C and Figure A-2), the SCS is considered a mobile operator internal network function, is operator controlled, and may provide operator value-added services. In this case, security and privacy protection for communication between the MTC-IWF and SCS is optional. When the SCS is deployed outside the operator domain (Figure A-1 B and A-2), the SCS is MTC Service Provider controlled. In this case, security and privacy protection for communication between the MTC-IWF and SCS is needed. In the direct model (Figure A-1 A), there may not be an external or internal SCS in the communication path.
(not reproduced yet)
Figure A-1: Deployment scenarios for direct and indirect model
Up
(not reproduced yet)
Figure A-2: Deployment scenarios for hybrid model
Up
An operator may deploy the hybrid model with a combination of no internal and external SCS (as in the Direct Model) and internal and/or external SCS (as in the Indirect Model). As shown in Figure A-2, a UE may be in communications with multiple SCSs in an HPLMN which can be made up of a combination of operator controlled and MTC service provider controlled SCSs. In that scenario, the MTC Service provider controlled SCS, and the 3GPP operator controlled SCS may offer different capabilities to the MTC Applications.
Though not illustrated, it is also possible that the deployment of an AS may be inside the operator domain and under operator control.
Up

BVoid


Up   Top   ToC