Tech-invite 3GPPspace IETF RFCs SIP

Quick 21 22 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 4‑5x

Content for TR 23.888 Word version: 11.0.0

1… 4… 6… 7…

...

4 Architectural Considerations Word‑p. 14

4.1 Architectural requirements

4.1A Architecture Principles

4.2 Architecture Model

4.3 Architectural Reference Model for MTC Word‑p. 16

4.4 Network Elements Word‑p. 19

4.4.1 General

4.4.2 MTC-IWF

4.4.3 HLR/HSS Word‑p. 20

4.4.4 GGSN/PGW

4.4.5 SGSN/MME

4.5 Reference Points

4.5.1 General

4.5.2 List of Reference Points Word‑p. 21

4.5.3 Reference Point Requirements

4.5.3.1 MTCsp Reference Point Requirements

4.5.3.2 T4 Reference Point Requirements

4.5.3.3 T5a/T5b Reference Point Requirements Word‑p. 22

4.5.3.4 S6m Reference Point Requirements

4.6 High Level Functions

4.6.1 General

4.7 Authorization and Security

4.8 Protocol Stacks Word‑p. 23

4.8.1 User plane

4.8.2 Control plane

4.8.2.1 MTC Server-MTC-IWF MTCsp reference point

4.8.2.2 MTC Server-SMS SC MTCsms reference point Word‑p. 24

5 Description of envisioned System Improvements for Machine Type Communication, use cases

5.1 Key Issue - Group Based Optimization

5.1.1 Use case description

5.1.2 Required Functionality

5.1.3 Evaluation

5.2 Key Issue - MTC Devices communicating with one or more MTC Servers

5.2.1 Use case description

5.2.2 Required Functionality Word‑p. 25

5.3 Key Issue - IP Addressing

5.3.1 Use case description

5.3.2 Required Functionality Word‑p. 26

5.3.3 Evaluation

5.4 Key Issue - Small Data Transmission Word‑p. 29

5.4.1 Use case description

5.4.2 Required Functionality

5.4.3 Evaluation Word‑p. 30

5.5 Void

5.6 Key Issue - Low Mobility

5.6.1 Use case description

5.6.2 Required Functionality

5.6.3 Evaluation

5.7 Key Issue - MTC Subscriptions

5.7.1 Use case description

5.7.2 Required Functionality

5.8 Key Issue - MTC Device Trigger Word‑p. 31

5.8.1 Use case description

5.8.2 Required Functionality Word‑p. 32

5.8.3 Evaluation Word‑p. 34

5.8.3.1 Comparison of the MTC Device Trigger solutions

5.8.3.2 Delivery of device trigger information from 3GPP system to UE Word‑p. 35

5.8.3.3 Submission of device trigger requests from MTC server to 3GPP system

5.8.3.4 3GPP system internal handling of device triggers

5.9 Key Issue -Time Controlled Word‑p. 36

5.9.1 Use case description

5.9.2 Required Functionality Word‑p. 37

5.9.3 Evaluation

5.10 Key Issue - MTC Monitoring

5.10.1 Use case description

5.10.2 Required Functionality

5.11 Key Issue - Decoupling MTC Server from 3GPP Architecture Word‑p. 38

5.11.1 Use Case Description

5.11.2 Required Functionality

5.12 Key Issue - Signalling Congestion Control

5.12.1 Use Case Description

5.12.2 Required Functionality Word‑p. 39

5.12.3 Evaluation Word‑p. 40

5.12.3.1 General

5.12.3.2 Evaluation for Congestion Control

5.12.3.3 Evaluation for Overload Control

5.12.3.4 Comparison of Each Solution Word‑p. 41

5.13 Key Issue - MTC Identifiers Word‑p. 43

5.13.1 Use Case Description

5.13.2 Required Functionality

5.13.3 Evaluation Word‑p. 44

5.14 Key Issue - Potential overload issues caused by Roaming MTC devices

5.14.1 Use Case Description

5.14.1.1 What is the likelihood of M2M devices being roamers?

5.14.1.2 What are the consequences if most M2M devices are roaming?

5.14.1.2.1 Commercial arrangements

5.14.1.2.2 Devices that only power-up/attach when they need to do something Word‑p. 45

5.14.1.2.3 Failure of "M2M partner" network

5.14.2 Required Functionality

5.14.3 Evaluation Word‑p. 46

5.14.3.1 Evaluation for M2M "access class barring" functionality

5.15 Key Issue - Low Power Consumption

5.15.1 Use case description

5.15.2 Required Functionality

5.15.3 Evaluation