IP Library Granted Patent US 12,335,838
Granted Patent B2
US 12,335,838 · App. 18/418,542 · Granted Jun 17, 2025

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

Inventors: Young Lee (Plano, TX); James Neil Guichard (Plano, TX); Kaippallimalil Mathew John (Plano, TX)
Assignee: Huawei Technologies Co., Ltd.
H04W40/12H04L69/22H04W28/0205H04W28/0236H04W72/543H04L69/26
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,335,838
App. No.
18/418,542
Granted
Jun 17, 2025
Kind
B2
Abstract

A method 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 includes 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. The MTNC-ID TLV for the MTNC-ID is inserted in the TLV field of the SRV6 header of the data packet. The data packet with the SRV6 header containing the MTNC-ID is transmitted over the SRV6 enabled data plane to a next node along a forwarding path corresponding to the MTNC-ID.

Claims (25)

1. A method for transporting multi-transport network context identifier (MTNC-ID) information, the method comprising:

encoding the MTNC-ID information into a User Datagram Protocol (UDP) header of a data packet; and

transmitting the data packet to a next node along a forwarding path, wherein the MTNC-ID information corresponds to an MTNC-ID that 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 data packet comprises a Segment Routing version 6 (SRV6) header containing the MTNC-ID information and is transmitted over an SRV6 enabled data plane to the next node along the forwarding path corresponding to the MTNC-ID information.

3. The method of claim 1 , wherein the method is performed by an egress autonomous system boundary router (ASBR) for transporting an MTNC-ID information over a SRV6 enabled data plane for fifth-generation (5G) transport.

4. The method of claim 1 , wherein the set of resource provisioning requirements comprises 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 associated with the MTNC-ID information for each domain and for each traffic class are established by a domain orchestrator (DO).

6. A method comprising:

receiving a data packet comprising multi-transport network context identifier (MTNC-ID) information in a User Datagram Protocol (UDP) header of the data packet;

determining a MTNC-ID corresponding to the MTNC-ID information; and

provisioning a set of resource requirements associated with the MTNC-ID for transmitting the data packet on a forwarding path.

7. The method of claim 6 , wherein the data packet which comprises a Segment Routing version 6 (SRV6) header containing the MTNC-ID information and is received over an SRV6 enabled data plane to a next node along the forwarding path corresponding to the MTNC-ID information.

8. The method of claim 6 , wherein the method is performed by an egress autonomous system boundary router (ASBR) for transporting an MTNC-ID information over a Segment Routing version 6 (SRV6) enabled data plane for fifth-generation (5G) transport.

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 requirements comprises 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 traffic between two service end points.

11. A system comprising:

a memory comprising instructions; and

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

encode multi-transport network context identifier (MTNC-ID) information into a User Datagram Protocol (UDP) header of a data packet; and

transmit the data packet to a next node along a forwarding path, wherein the MTNC-ID information corresponds to an MTNC-ID that 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 data packet comprises a Segment Routing version 6 (SRV6) header containing the MTNC-ID information and is transmitted over an SRV6 enabled data plane to a next node along the forwarding path corresponding to the MTNC-ID information.

13. The system of claim 11 , wherein the system is an egress autonomous system boundary router (ASBR) of a Segment Routing version 6 (SRV6) supported network.

14. The system of claim 11 , wherein the set of resource provisioning requirements comprises 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).

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 20, 2025
From: FUTUREWEI TECHNOLOGIES, INC.
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 070276/0599 →
Continuity (3)
Continuation 17589566 · Jan 31, 2022
Continuation PCTUS2019044416 · Jul 31, 2019
Related Publication 20240244503A1 · Jul 18, 2024
References Cited (88)
US 10230605B1 · Filsfils et al. · 2019 [cited by applicant]
US 10567245B1 · Patil et al. · 2020 [cited by applicant]
US 10715419B1 · Suryanarayana et al. · 2020 [cited by applicant]
US 11070463B2 · Torvi · 2021 [cited by examiner]
US 20060153111A1 · Roh et al. · 2006 [cited by applicant]
US 20080240120A1 · Kusama et al. · 2008 [cited by applicant]
US 20110271007A1 · Wang et al. · 2011 [cited by applicant]
US 20130054761A1 · Kempf et al. · 2013 [cited by applicant]
US 20130259038A1 · Anantharam et al. · 2013 [cited by applicant]
US 20130322451A1 · Wang et al. · 2013 [cited by applicant]
US 20150256456A1 · Previdi · 2015 [cited by examiner]
US 20160050125A1 · Mattson et al. · 2016 [cited by applicant]
US 20160142308A1 · Gage et al. · 2016 [cited by applicant]
US 20160156691A1 · Leeb et al. · 2016 [cited by applicant]
US 20160182400A1 · Ceccarelli et al. · 2016 [cited by applicant]
US 20160212050A1 · Yin et al. · 2016 [cited by applicant]
US 20160330114A1 · Gafni et al. · 2016 [cited by applicant]
US 20170019331A1 · Yong · 2017 [cited by applicant]
US 20170048739A1 · Jeong et al. · 2017 [cited by applicant]
US 20170063783A1 · Yong et al. · 2017 [cited by applicant]
US 20170187629A1 · Shalev et al. · 2017 [cited by applicant]
US 20170366454A1 · Liu · 2017 [cited by applicant]
US 20180241671A1 · Bosch et al. · 2018 [cited by applicant]
US 20180359176A1 · Nainar et al. · 2018 [cited by applicant]
US 20180375968A1 · Bashandy et al. · 2018 [cited by applicant]
US 20190104111A1 · Cidon et al. · 2019 [cited by applicant]
US 20190208040A1 · Boucadair et al. · 2019 [cited by applicant]
US 20190215267A1 · Filsfils et al. · 2019 [cited by applicant]
US 20190260657A1 · Filsfils et al. · 2019 [cited by applicant]
US 20190273678A1 · Peng · 2019 [cited by examiner]
US 20190394211A1 · Filsfils et al. · 2019 [cited by applicant]
US 20200044973A1 · Hei · 2020 [cited by applicant]
US 20200076719A1 · Filsfils · 2020 [cited by examiner]
US 20200099610A1 · Heron · 2020 [cited by examiner]
US 20200099611A1 · Filsfils et al. · 2020 [cited by applicant]
US 20200120022A1 · Stammers et al. · 2020 [cited by applicant]
US 20200145876A1 · Dao et al. · 2020 [cited by applicant]
US 20200195556A1 · Tang · 2020 [cited by examiner]
US 20200229042A1 · Srivastava et al. · 2020 [cited by applicant]
US 20200244573A1 · Cui et al. · 2020 [cited by applicant]
US 20200280516A1 · Gross, IV et al. · 2020 [cited by applicant]
US 20200314056A1 · Desmouceaux et al. · 2020 [cited by applicant]
US 20200329008A1 · Dao · 2020 [cited by applicant]
US 20200344662A1 · Maino · 2020 [cited by examiner]
US 20200351188A1 · Arora · 2020 [cited by examiner]
US 20200351766A1 · Young · 2020 [cited by applicant]
US 20200389397A1 · Stammers et al. · 2020 [cited by applicant]
US 20210083973A1 · Peng et al. · 2021 [cited by applicant]
US 20210092052A1 · Tantsura et al. · 2021 [cited by applicant]
US 20210099382A1 · Liu et al. · 2021 [cited by applicant]
US 20230155926A1 · Filsfils et al. · 2023 [cited by applicant]
CN 103039027A · 2013 [cited by applicant]
CN 107005556A · 2017 [cited by applicant]
CN 107006045A · 2017 [cited by applicant]
CN 108476208A · 2018 [cited by applicant]
CN 108880904A · 2018 [cited by applicant]
CN 109644186A · 2019 [cited by applicant]
CN 109688057A · 2019 [cited by applicant]
CN 109861924A · 2019 [cited by applicant]
DE 112013000839B4 · 2021 [cited by applicant]
EP 3334105A1 · 2018 [cited by applicant]
EP 3925190A1 · 2021 [cited by examiner]
KR 20150123747A · 2015 [cited by applicant]
WO 2016115850A1 · 2016 [cited by applicant]
WO WO2020225092A1 · 2020 [cited by examiner]
Lee, Y., et al., “Extended ACTN Architecture to Enable End-To-End 5G Transport Service Assurance,” 21st International Conference on Transparent Optical Networks, Jul. 9, 2019, XP033618028, 3 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Study on User Plane Protocol in 5GC (Release 16), Technical Report, 3GPP TR 29.892, V1.0.0, Mar. 2019, 37 pages. [cited by applicant]
Previdi, S. Ed., et al., “IPv6 Segment Routing Header (SRH),” draft-ietf-6man-segment-routing-header-06, Sep. 14, 2017, 35 pages. [cited by applicant]
Bashandy, A., Ed., et al., “IS-IS Extensions to Support Segment Routing over IPv6 Dataplane,” draft-bashandy-isis-srv6-extensions-00, Mar. 10, 2017, 16 pages. [cited by applicant]
Matsushima, S., et al., “Segment Routing IPV6 for Mobile User-Plane,” draft-matsushima-spring-dmm-srv-mobile-uplane-03, Nov. 12, 2017, 20 pages. [cited by applicant]
“Internet Protocol Darpa Internet Program Protocol Specification,” Sep. 1981, RFC 791, 51 pages. [cited by applicant]
Deering, et al., “Internet Protocol, Version 6 (IPv6) Specification,” RFC 8200, 42 pages. [cited by applicant]
Postel, “User Datagram Protocol,” RFC 768, 3 pages. [cited by applicant]
Herbert, et al., “Generic UDP Encapsulation,” draft-ietf-intarea-gue-07, Mar. 7, 2019, 155 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 16),” Technical Specification, 3GPP TS 23.502 v16.0.2 (Apr. 2019), 419 pages. [cited by applicant]
Filsfils, C., et al, “Segment Routing Policy Architecture,” draft-filsfils-spring-segment-routing-policy-06.txt, Spring Working Group Internet-Draft, May 21, 2018, 39 pages. [cited by applicant]
Li, R., et al, “Multi-constrained QoS Routing Algorithm in IPV6,” Computer Engineering, vol. 31, No. 4, Feb. 2005, with the English Abstract, 3 pages. [cited by applicant]
Negi, M., et al., “PCEP Extensions for Segment Routing leveraging the IPV6 data plane,” draft-ietf-pce-segment-routing-ipv6-00, PCE Working Group Internet-Draft, Mar. 10, 2019, 23 pages. [cited by applicant]
Cui, J., “Research on Quality of Service Based on DiffServ Over MPLS Architecture,” Science and Technology Information, No. 13, 2008, School of Physical Science and Information Engineering, Liaocheng University, with th… [cited by applicant]
Filsfils, C., et al, “SRv6 Network Programming,” draft-ietf-spring-srv6-network-programming-00, Spring Internet-Draft, Apr. 24, 2019, 48 pages. [cited by applicant]
Xu, W., “Research and Implementation of IPV6 Dataflow Reassembly,” A Dissertation Submitted for the Degree of Master, South China University of Technology, 2010, with the English Abstract, 71 pages. [cited by applicant]
Jia, Y., “Research of Wireless Network''s Access Technology Based On IPV6,” Dissertation Submitted to Hebei University of Technology for Master Degree Computer Applied Technology, Jan. 2006, with the English Abstract, 4… [cited by applicant]
3GPP TS 23.682 V15.5.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements to facilitate communications with packet data networks and applications (… [cited by applicant]
Wanfei, S., “Analyse and Application Research on Control Plane Protocol Stack of TD-LTE System,” Thesis Submitted to Tianjin University of Technology for the Master's Degree, Jun. 2018, with the English Abstract, 67 pag… [cited by applicant]
Rieger, C., et al., “Notional Examples and Benchmark Aspects Of a Resilient Control System,” 2010 3rd International Symposium on Resilient Control Systems, Oct. 14, 2010, 8 pages. [cited by applicant]
Rajalingham, G., “Quality-of-Service Differentiation for Smart Grid Neighbor Area Networks,” A thesis submitted to McGill University in partial fulfillment of the requirements for the degree of Master of Engineering, Ju… [cited by applicant]
Filsfils, C., et al, “Segment Routing Architecture,” Internet Engineering Task Force (IETF), Request for Comments: 8402, Jul. 2018, 32 pages. [cited by applicant]
Nokia et al, “Correcting AMF behaviour for Service Request that is not integrity protected,” S2-1903668, SS WG2 Meeting #132, Apr. 8-12, 2019, 376 pages. [cited by applicant]