Liaison statement
LS on adding transport information in 3GPP NRM to facilitate Cross-domain OAM coordination

State Posted
Submitted Date 2020-07-16
From Group 3GPP-TSG-SA-WG5
From Contact Susanna Kooistra
To Group teas
To Contacts Vishnu Pavan Beeram
Lou Berger
CcLou Berger
Vishnu Beeram
Alvaro Retana
Traffic Engineering Architecture and Signaling Discussion List
Deborah Brungard
Martin Vigoureux
Response Contact 3GPPLiaison@etsi.org
Purpose For information
Attachments S5-203420 Rel-16 28.541 CR add transport information and slice mapping on backhaul endpoints
S5-203419 TD proposal to add transport endpoint in NRM
S5-203262 LS on adding transport information in 3GPP NRM to facilitate Cross-domain OAM coordination
Body
1. Overall Description:

When providing an end to end communication service, the network may use
non-3GPP parts (e.g. Data center network (DCN), Transport network (TN)) in
addition to the network components defined in 3GPP. Therefore, in order to
ensure the performance of a communication service according to the business
requirements, the 3GPP management system has to coordinate with the management
systems of the non-3GPP parts (e.g., MANO system, IETF defined transport
system) when preparing a network slice instance for this service. This
coordination may include obtaining capabilities of the non-3GPP parts and
providing the slice specific requirements and other requirements on the
non-3GPP parts. Figure 4.7.1 illustrates an example for the coordination with
management of TN part (e.g., directly or via MANO system).

3GPP management system identifies the requirements on involved network domains,
such as RAN, CN and non-3GPP parts of a slice by deriving them from the
customer requirements to the services supported by the network slice. The
derived requirements are sent to the corresponding management systems. The
coordination may also include related management data exchange between those
management systems and the 3GPP management system (see clause 4.7 of TS 28.530).

Figure 4.7.1: Example of coordination between 3GPP and TN management systems

The 3GPP management system maintains the network topology and the related QOS
requirements. (see clause 4.4.1 of 3GPP  TS 28.530).

3GPP SA5 would like to inform you that 3GPP Management System consumes
interface(s) produced by TN Domain Manager(s) for the support of network
slicing. At SA5#117 meeting (Jan. 2018), 3GPP SA5 has sent out an LS (in
S5-181456) to BBF, ETSI NFV, ITU-T SG15 and ETSI ZSM to ask for the
availability of any TN Domain Manager interface(s) for the support of network
slicing. So far SA5 has got a) a reply from ETSI NFV and b) an update from IETF
on the network slicing information indicating their ongoing work status in
2018. 3GPP SA5 has not received further update on the availability of the TN
Domain Manager interface(s) for the support of network slicing.

3GPP SA5 would like to inform you that in SA5#131 e-meeting, contributions to
add transport endpoint in 3GPP NRM (S5-203419, S5-203420) were agreed, that
enables exchanging transport network topology requirements and related QoS
requirements between 3GPP and TN management systems.

2. Actions:
To GSMA NEST group.
ACTION:         3GPP SA5 kindly asks IETF TEAS WG to take the above information
into account and update 3GPP with the availability of the TN Domain Manager
interface(s) for the support of network slicing, and consider to specify TN
Domain Manager interface(s) for the support of network slicing.

3. Date of Next TSG-SA WG5 Meetings:
SA5#132e        24 – 28 August 2020     e-meeting
SA5#133 12 – 16 October 2020    US