Transporting MTNC-ID over SRV6-enabled dataplane for 5G transport

1. A method performed by a next generation node B (gNB) for transporting a multi-transport network context identifier (MTNC-ID) over a segment routing version 6 (SRV6) enabled data plane for fifth generation (5G) transport, the method comprising:

setting an indicator in a flags field of a SRV6 header of a data packet that an MTNC-ID type-length-value (TLV) is included in a TLV field of the SRV6 header;

inserting the MTNC-ID TLV for the MTNC-ID in the TLV field of the SRV6 header of the data packet; and

transmitting the data packet over the SRV6 enabled data plane to a next node along a forwarding path corresponding to the MTNC-ID, wherein the MTNC-ID is associated with a set of resource provisioning requirements for one or more transport networks on the forwarding path to provision transport resources for forwarding traffic on the forwarding path.

2. The method of claim 1 , wherein the MTNC-ID TLV is 32 bits.

3. The method of claim 1 , wherein the MTNC-ID TLV comprises an MTNC-ID type field, a length field, and a 2 octets (16 bits) MTNC-ID field.

4. The method of claim 1 , wherein the set of resource provisioning requirements comprises a combination of quality of service (QoS) requirements, class of service (CoS) requirements, a resilience requirement, or an isolation requirement, according to which transport resources of a transport network from the one or more transport networks are provisioned for routing the traffic between two service end points.

5. The method of claim 1 , wherein the MTNC-ID for each domain and for each traffic class are established by a domain orchestrator (DO).

6. A method performed by an egress autonomous system boundary router (ASBR) for transporting a multi-transport network context identifier (MTNC-ID) over segment routing version 6 (SRV6) enabled data plane for fifth generation (5G) transport, the method comprising:

receiving a data packet having a SRV6 header comprising a segment list;

processing the segment list;

after processing a last segment of the segment list, determining whether a type-length-value (TLV) field of the SRV6 header of the data packet includes an MTNC-ID TLV associated with the segment list;

responsive to a determination that the TLV field of the SRV6 header of the data packet includes the MTNC-ID TLV, extracting an MTNC-ID from the MTNC-ID TLV associated with the segment list;

inserting the MTNC-ID into a data plane header of the data packet; and

transmitting the data packet with the MTNC-ID in the data plane header of the data packet to an ASBR of a next domain based on a forwarding path corresponding to the MTNC-ID, wherein the MTNC-ID is associated with a set of resource provisioning requirements for one or more transport networks on the forwarding path to provision transport resources for forwarding traffic on the forwarding path.

7. The method of claim 6 , wherein the data plane header is a Network Service Header (NSH), and wherein inserting the MTNC-ID into the data plane header of the data packet comprises prefixing the MTNC-ID as part of the NSH of the data packet.

8. The method of claim 6 , wherein the data plane header is a User Datagram Protocol (UDP) header, and wherein inserting the MTNC-ID into the data plane header of the data packet comprises encapsulating the MTNC-ID in the UDP header of the data packet.

9. The method of claim 6 , wherein the forwarding path is created by a software-defined network (SDN) controller, and wherein the MTNC-ID is binded to the forwarding path by the SDN controller.

10. The method of claim 6 , wherein the set of resource provisioning requirements comprises a combination of quality of service (QoS) requirements, class of service (CoS) requirements, a resilience requirement, or an isolation requirement, according to which transport resources of a transport network from the one or more transport networks are provisioned for routing the traffic between two service end points.

11. A system for transporting a Multi-Transport Network Context Identifier (MTNC-ID) over a Segment Routing Version 6 (SRV6) enabled data plane for fifth generation (5G) transport, the system comprising:

a memory comprising instructions; and

a processor in communication with the memory, the processor executing the instructions to:

set an indicator in a flags field of a SRV6 header of a data packet that an MTNC-ID type-length-value (TLV) is included in a TLV field of the SRV6 header;

insert the MTNC-ID TLV for the MTNC-ID in the TLV field of the SRV6 header of the data packet; and

transmit the data packet over the SRV6 enabled data plane to a next node along a forwarding path corresponding to the MTNC-ID, wherein the MTNC-ID is associated with a set of resource provisioning requirements for one or more transport networks on the forwarding path to provision transport resources for forwarding traffic on the forwarding path.

12. The system of claim 11 , wherein the MTNC-ID TLV is 32 bits.

13. The system of claim 11 , wherein the MTNC-ID TLV comprises an MTNC-ID type field, a length field, and a 2 octets (16 bits) MTNC-ID field.

14. The system of claim 11 , wherein the set of resource provisioning requirements comprises a combination of quality of service (QoS) requirements, class of service (CoS) requirements, a resilience requirement, or an isolation requirement, of which transport resources of a transport network from the one or more transport networks are provisioned for routing the traffic between two service end points.

15. The system of claim 11 , wherein the MTNC-ID for each domain and for each traffic class are established by a domain orchestrator (DO).

16. The system of claim 11 , wherein the system is a Next Generation Node B (gNB).

17. A system for transporting a Multi-Transport Network Context Identifier (MTNC-ID) over Segment Routing Version 6 (SRV6) enabled data plane for fifth generation (5G) transport, the system comprising:

a memory comprising instructions; and

a processor in communication with the memory, the processor executing the instructions to:

receive a data packet having a SRV6 header comprising a segment list;

process the segment list;

after processing a last segment of the segment list, determining whether a type-length-value (TLV) field of the SRV6 header of the data packet includes an MTNC-ID TLV associated with the segment list;

responsive to a determination that the TLV field of the SRV6 header of the data packet includes the MTNC-ID TLV, extract an MTNC-ID from the MTNC-ID TLV associated with the segment list;

insert the MTNC-ID into a data plane header of the data packet; and

transmit the data packet with the MTNC-ID in the data plane header of the data packet to an autonomous system boundary router (ASBR) of a next domain based on a forwarding path corresponding to the MTNC-ID, wherein the MTNC-ID is associated with a set of resource provisioning requirements for one or more transport networks on the forwarding path to provision transport resources for forwarding traffic on the forwarding path.

18. The system of claim 17 , wherein the data plane header is a Network Service Header (NSH), and wherein inserting the MTNC-ID into the data plane header of the data packet comprises prefixing the MTNC-ID as part of the NSH of the data packet.

19. The system of claim 17 , wherein the data plane header is a User Datagram Protocol (UDP) header, and wherein inserting the MTNC-ID into the data plane header of the data packet comprises encapsulating the MTNC-ID in the UDP header of the data packet.

20. The system of claim 17 , wherein the forwarding path is created by a software-defined network (SDN) controller, and wherein the MTNC-ID is binded to the forwarding path by the SDN controller.

21. The system of claim 17 , wherein the set of resource provisioning requirements comprises a combination of quality of service (QoS) requirements, class of service (CoS) requirements, a resilience requirement, or an isolation requirement, of which transport resources of a transport network from the one or more transport networks are provisioned for routing the traffic between two service end points.

22. The system of claim 17 , wherein the system is an egress ASBR.