tech-invite   World Map
3GPP     Specs     Glossaries     Architecture     IMS     UICC       IETF     RFCs     Groups     SIP     ABNFs       Search     Home
Top        in Index        Prev        Next

TS 32.152 (SA5)
Telecommunication management –
Integration Reference Point (IRP) Information Service (IS) Unified Modelling Language (UML) repertoire

|   ToC   |   3GPP‑Page   |   ETSI‑search   |   Help   |

(P) V14.1.0    2017/06    26 p.
(P) V13.2.0    2017/06    26 p.
(P) V12.1.0    2017/06    27 p.
(P) V11.2.0    2017/06    26 p.
(P) V10.1.0    2017/06    26 p.
(P) V9.3.0    2017/06    26 p.
(P) V8.0.0    2007/10    26 p.
(P) V7.1.0    2007/03    26 p.
(P) V6.3.0    2005/06    20 p.


Rapporteur:  Mr. Tse, Edwin
See also:  –


3GPP SA5 has chosen UML to capture systems behaviour in the IRP IS context.

UML provides a rich set of concepts, notations and model elements to model distributive systems. Usage of all UML notations and model elements is not necessary for the purpose of IRP IS specifications. This TS documents the necessary and sufficient set of UML notations and model elements, including the ones built by the UML extension mechanism <<stereotype>>, for use by 3GPP IRP IS authors. Collectively, this set of notations and model elements is called the 3GPP IRP IS modelling repertoire.

The selection of the UML notations and model elements in this repertoire is based on the needs of the existing 3GPP IRP IS specifications. Future IRP IS releases may require the use of additional UML notations or model elements.

IRP IS specifications shall employ the UML notation and model elements of this repertoire and may also employ other UML notation and model elements considered necessary. However, before any other UML notation and model elements may be employed in an approved 3GPP IRP specification, the other notation and model elements should be agreed for inclusion first in this repertoire.


 

Here        Top

 

 

1   Scope   PDF-p. 6
2   References
3   Definitions and abbreviations   PDF-p. 7
4   Requirements
5   Model Elements and Notations   PDF-p. 8
A   Samples of using <<ProxyClass>> to model Link related IOCs   PDF-p. 21
B  (Normative)   Application of <<InformationObjectClass>> and <SupportIOC>>   PDF-p. 23      Up
C   Change history   PDF-p. 24

Up        Top