Content for TS 28.315 Word version: 17.0.0
0 Introduction
1 Scope
2 References
3 Definitions of terms, symbols and abbreviations
3.1 Terms
3.2 Symbols
3.3 Abbreviations
4 Architecture for Plug and Connect
4.1 Functional architecture
4.2 Functional elements
...
...
0 Introduction p. 5
The present document is part of a TS family covering the 3rd Generation Partnership Project Technical Specification Group Services and System Aspects, Management and orchestration; as identified below:
TS 28.314:
"Plug and Connect; Concepts and requirements".
TS 28.315:
"Plug and Connect; Procedure flows".
TS 28.316:
"Plug and Connect; Data formats".
1 Scope p. 6
The present document specifies procedure flows for Plug and Connect NE in 3GPP systems.
2 References p. 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.
3 Definitions of terms, symbols and abbreviations p. 6
3.1 Terms p. 6
For the purposes of the present document, the terms given in TR 21.905, TS 28.314 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 and TS 28.314.
3.2 Symbols p. 6
Void.
3.3 Abbreviations p. 6
For the purposes of the present document, the abbreviations given in TR 21.905, TS 28.314 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 and in TS 28.314.
4 Architecture for Plug and Connect p. 6
4.1 Functional architecture p. 6
The functional architecture for plug-and-connect connection of NE to the network is described in TS 28.314, clause 4.1.2. It covers the scenarios where NE is connected to the Secure Operator Network either via an External Network or via a Non-Secure Operator Network.
The entities (functional elements) involved in the PnC are listed and described in detail in clause 4.2.
4.2 Functional elements p. 7
4.2.1 IP Autoconfiguration services p. 7
The IP Autoconfiguration services such as DHCP servers and Router Advertisements are used primarily to provide the NE with basic IP configuration information (e.g. IP address, netmask, default gateway, domain name, IP address(es) of DNS servers, time servers). IP Autoconfiguration services may recognize the NE as a client (using, for example, the vendor class identifier DHCP option) and provide with information such as IP address or FQDN of CA/RA server, IP address or FQDN of SeGW, IP address or FQDN of SCS, etc.
The specific data formats used by IP Autoconfiguration services for plug-and-connect procedures are described in TS 28.316.
From the plug-and-connect feature perspective, the IP Autoconfiguration services may be categorized into secure (those located within a Secure Operator Network) and public (those located either within a Non-Secure Operator Network or within an External Network).
4.2.2 DNS server p. 7
DNS servers are used to resolve FQDNs into IP addresses. The FQDNs used for plug-and-connect may be factory programmed, provided by IP Autoconfiguration services, configured by SCS, or derived/generated within the NE using the vendor information, operator network domain name and name of the functional element.
The specific FQDN formats used in plug-and-connect procedures are described in TS 28.316.
From the plug-and-connect feature perspective, the DNS servers may be categorized into secure (those located within a Secure Operator Network) and public (those located either within a
Non-Secure Operator Network or within an External Network).
The DNS server is an optional functional element and is only required if particular Operator deployment scenario relies on resolution of FQDNs (e.g. FQDNs are configured at the IP Autoconfiguration services, NE and/or SCS, while IP addresses are configured at DNS servers).
4.2.3 Certification Authority server p. 7
The Certification Authority server (CA/RA) is used in the in the plug-and-connect procedures for security certificate enrolment (e.g. to provision operator certificates at the NE using the factory-installed vendor certificates).
There could be one or more CA/RA depending on a particular operator deployment scenario (e.g. one CA/RA per vendor).
4.2.4 Software and Configuration Server (SCS) p. 7
The SCS is a vendor-specific functional element that is used in plug-and-connect procedures to provide the NE with correct software and configuration information.
There could be one or more SCS depending on a particular Operator deployment scenario (e.g. initial SCS, serving SCS).
The configuration may contain an IP address or FQDN of (another) SCS that this specific NE shall use as SCS.
The configuration may contain an IP address or FQDN of (another) SeGW that should be used before connecting to the SCS.
SCS can be implemented in EM in IRP based architecture or MnF in SBMA.
4.2.5 Security Gateway (SeGW) p. 7
The SeGW is used to establish a secure connection between the NE and the Secure Operator Network.
Depending on a particular operator deployment scenario, there could be separate SeGW for connection to the OAM network and to the CN. The OAM SeGW and CN SeGW may or may not be in practice separate physical entities.
Depending on a particular operator deployment scenario, there could be more than one OAM SeGW (e.g. one per vendor).
