Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 23.789  Word version:  13.0.0

Top   Top   None   None   Next
1…   5…

 

1  Scopep. 6

The present document studies and evaluates architectural enhancements required for 3GPP systems to provide monitoring service capability as per the service requirements defined in TS 22.368, clause 7.2.8 and TS 22.101, clause 29.2.
The end-to-end application layer aspects between UEs and Application servers including SCS (which can be located outside or inside the network operator's domain) are out of the scope of this study.
Up

2  Referencesp. 6

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.368: "Service Requirements for Machine-Type Communications".
[3]
TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[4]
[5]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[6]
TR 23.708: "Architecture Enhancements for Service Capability Exposure".
[7]
TS 23.203: "Policy and charging control architecture".
[8]
TS 23.271: "Functional stage 2 description of Location Services (LCS)".
[9]
TS 29.272: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol".
[10]
TS 22.101: "Service aspects; Service principles".
[11]
TS 32.422: "Telecommunication management; Subscriber and equipment trace; Trace control and configuration management".
Up

3  Definitions and abbreviationsp. 6

3.1  Definitionsp. 6

For the purposes of the present document, the terms and definitions given in TR 21.905 and TS 22.368 apply.

3.2  Abbreviationsp. 7

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
MTC
Machine Type Communications
M2M
Machine-to-Machine

4  Architectural Assumptionsp. 7

Monitoring feature is intended to use applicable architecture enhancements determined as part of AESE work item. Any new service capability exposure and interface should fit in Service Capability Exposure Framework defined in TR 23.708.

Up   Top   ToC