Tech-invite 3GPPspace IETFspace

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

Content for TS 32.501 Word version: 17.0.0

0… 2…

2 References p. 6

3 Definitions and abbreviations p. 6

3.1 Definitions p. 6

3.2 Abbreviations p. 7

4 Concepts and background p. 7

4.1 Self-Configuration Concept p. 7

4.1.1 Logical Function Blocs p. 7

4.1.1.1 Address Allocation Function (AAF): p. 7

4.1.1.2 OAM Connectivity Establishment Function (OAM CO_EF): p. 7

4.1.1.3 Software Management Function (SW_MF): p. 7

4.1.1.4 Inventory Update Function (Inv_UF): p. 7

4.1.1.5 Self-Test Function (ST_F): p. 8

4.1.1.6 Self-Configuration Monitoring and Management Function (SC_MMF): p. 8

4.1.1.6.1 Self-Configuration Monitoring and Management Function (SC_MMF_NM): p. 8

4.1.1.6.2 Self-Configuration Monitoring and Management Function (SC_MMF_EM): p. 8

4.1.1.7 Call Processing Link (CPL) Set Up Function (CPL_SUF): p. 8

4.1.1.8 Radio Network Configuration Data Function (R_CD_F): p. 8

4.1.1.9 Transport Network Configuration Data Function (T_CD_F): p. 8

4.1.1.10 NRM IRP Update Function (NRM_UF): p. 8

4.1.1.11 Radio Network and Transport Network Configuration Data Preparation Function p. 8

4.2 Automatic Radio Configuration Data handling Function (ARCF) Concept p. 8

4.2.1 Definitions p. 8

4.3 Multi-Vendor Plug and Play eNB connection to network Concept p. 9

4.3.1 General description p. 9

4.3.2 Network Scenarios p. 9

4.3.2.1 eNB connected via a Non-Secure, Operator Controlled Network p. 9

4.3.2.2 eNB connected via an External Network p. 10

4.3.2.3 eNB connection to the OAM Network and multiple CNs via separate SeGWs p. 10

4.3.3 Security Aspects p. 11

4.3.3.1 Root Certificate Acquisition: p. 11

4.3.3.2 Number of CA servers p. 12

4.3.3.3 Number of OAM SeGWs p. 12

5 Business Level Requirements p. 13

5.1 Self- Configuration of eNodeB's p. 13

5.1.1 Actor roles p. 13

5.1.2 Telecommunications resources p. 13

5.1.3 High-level use cases p. 13

5.2 Business Requirements for Multi Vendor Plug and Play eNB connection to network p. 13

6 Specification level requirements p. 15

6.1 General p. 15

6.2 Actor roles p. 15

6.3 Telecommunications resources p. 15

6.4 Use cases p. 15

6.4.1 Use case for Automatic Radio Network Configuration Data Handling p. 15

6.4.1.1 Use case radio network configuration data request, transfer and validity check p. 15

6.4.2 Use case Self-configuration of a new eNodeB p. 15

6.4.3 Use case Multi Vendor Plug and Connect eNB to network p. 18

6.5 Requirements p. 19

6.5.1 Automatic Radio Network Configuration Data Handling p. 19

6.5.2 Self-configuration of a new eNodeB p. 19

6.5.2.1 Self-Configuration Management and Monitoring p. 20

6.5.2.1.1 Management Part p. 20

6.5.2.1.2 Monitoring Part p. 20

6.5.2.2 Software Management p. 20

6.5.2.3 Address Allocation and OAM Connectivity Establishment p. 21

6.5.2.4 Inventory Update p. 21

6.5.2.5 Self-Test p. 21

6.5.2.6 Radio Configuration Data p. 21

6.5.2.7 Transport Configuration Data p. 21

6.5.2.8 Call Processing Link Set-Up p. 21

6.5.2.9 NRM IRP Update p. 21

6.5.3 Specification Requirements for Multi-Vendor Plug and Play eNB connection to network p. 21

7 Functions and Architecture p. 22

7.1 Self-Configuration Logical Architecture p. 22

7.2 Self-Configuration Reference Model p. 23

A Graphical representation of the PnC Use Case p. 24

$ Change History p. 29