A method performed by a Next Generation Node B (gNB) in a communications system implementing User Datagram Protocol (UDP) comprises indicating that a data packet comprises a multi-transport network context-identifier (MTNC-ID) corresponding to a forwarding path and being associated with a set of resource provisioning requirements for one or more transport networks on the forwarding path to provision transport resources for traffic forwarding on the forwarding path, inserting the MTNC-ID into a Generic UDP Encapsulation (GUE) header of the data packet, and transmitting the data packet to a network element (NE) in the communications system based on the forwarding path corresponding to the MTNC-ID.
Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
2. The method of claim 1, wherein the set of resource provisioning requirements comprises a quality of service (QoS) requirement, a class of service (CoS) requirement, a resilience requirement, and an isolation requirement.
3. The method of claim 1, wherein each of the one or more transport networks comprises NEs configured to implement at least one of Multiprotocol Label Switching (MPLS), Segment Routing over Internet Protocol (IP) version 6 (IPv6) data plane (SRv6), IP transport, or Enhanced Virtual Private Network.
4. The method of claim 1, further comprising storing a forwarding table comprising a mapping between the MTNC-ID and the forwarding path.
A system and method for managing network traffic in a mobile telecommunications network involves identifying a mobile terminal network capability identifier (MTNC-ID) associated with a mobile device and determining a forwarding path for the device based on the MTNC-ID. The forwarding path is selected from multiple available paths to optimize network performance, such as reducing latency or improving reliability. The system dynamically updates the forwarding path in response to changes in network conditions or device capabilities. Additionally, the system stores a forwarding table that maps the MTNC-ID to the selected forwarding path, allowing for efficient lookup and routing of traffic. This approach enables adaptive routing decisions based on device-specific capabilities and network conditions, improving overall network efficiency and user experience. The forwarding table is maintained to ensure accurate and up-to-date routing information, supporting seamless traffic management across the network.
5. The method of claim 1, further comprising providing, in a “C” flag field of the GUE header, a second indication that the data packet carries a data message, and wherein the first field is a “M” flag field comprising a value indicating that the data packet comprises the MTNC-ID.
This invention relates to wireless communication systems, specifically to methods for transmitting data packets that include identification information for mobile terminals in a network. The problem addressed is the need for efficient and standardized ways to convey mobile terminal network controller identifiers (MTNC-ID) and other data message indicators within packet headers to ensure proper routing and processing in the network. The method involves modifying a packet header, specifically the GUE header, to include two distinct flag fields. The first flag field, labeled "M," contains a value that indicates whether the packet includes the MTNC-ID. This allows the network to identify and process packets associated with specific mobile terminals. The second flag field, labeled "C," provides an additional indication that the packet carries a data message, distinguishing it from other types of packets that may not contain application or user data. By using these flag fields, the system ensures that packets are correctly classified and routed based on their content and purpose, improving network efficiency and reliability. The method is particularly useful in scenarios where multiple types of packets are transmitted over the same network, requiring clear differentiation to prevent misrouting or processing errors.
6. The method of claim 1, wherein the GUE header comprises a “C” flag field set to indicate that the data packet carries a control message, and wherein the first field is a proto/ctype field comprising a value indicating that the data packet comprises the MTNC-ID.
7. The method of claim 1, further comprising encapsulating the data packet to further comprise an outer Internet Protocol (IP) header, a UDP extension header, a General Packet Radio Service Tunneling Protocol (GTP)-User Data Tunneling (GTP-U) header, and an inner IP header, wherein the UDP extension header comprises the UDP header and the GUE header carrying the MTNC-ID.
9. The method of claim 8, wherein the set of resource provisioning requirements comprises a quality of service (QoS) requirement, a class of service (CoS) requirement, a resilience requirement, and an isolation requirement.
This invention relates to resource provisioning in networked systems, specifically addressing the challenge of dynamically allocating and managing computational, storage, or network resources based on diverse operational requirements. The method involves defining a set of resource provisioning requirements that include quality of service (QoS) parameters, class of service (CoS) specifications, resilience criteria, and isolation constraints. QoS requirements ensure performance metrics such as latency, throughput, or reliability are met. CoS requirements categorize traffic or workloads into priority levels to optimize resource allocation. Resilience requirements specify redundancy or failover mechanisms to maintain system availability during disruptions. Isolation requirements enforce security or operational boundaries between different workloads or users. The method dynamically adjusts resource allocation based on these requirements, ensuring that system performance, reliability, and security are maintained under varying conditions. This approach is particularly useful in cloud computing, virtualized environments, or distributed systems where resource demands fluctuate and must be managed efficiently. The invention improves resource utilization, reduces operational overhead, and enhances system adaptability to changing workloads.
10. The method of claim 8, wherein each of the one or more transport networks comprises NEs configured to implement at least one of Multiprotocol Label Switching (MPLS), Segment Routing over Internet Protocol (IP) version 6 (IPv6) data plane (SRv6), IP transport, or Enhanced Virtual Private Network.
11. The method of claim 8, wherein the GUE header comprises a “C” flag field set to indicate that the data packet carries a data message, and wherein the first field is an “M” flag field comprising a value indicating that the data packet comprises the MTNC-ID.
12. The method of claim 8, wherein the GUE header comprises a “C” flag field set to indicate that the data packet carries a control message, and wherein the first field is a proto/ctype field comprising a value indicating that the data packet comprises the MTNC-ID.
13. The method of claim 8, wherein the data packet comprises an outer Internet Protocol (IP) header, a UDP extension header, a General Packet Radio Service Tunneling Protocol (GTP)-User Data Tunneling (GTP-U) header, and an inner IP header, wherein the UDP extension header comprises the UDP header and the GUE header carrying the MTNC-ID.
15. The gNB of claim 14, wherein the set of resource provisioning requirements comprises a quality of service (QoS) requirement, a class of service (CoS) requirement, a resilience requirement, and an isolation requirement.
16. The gNB of claim 14, wherein each of the one or more transport networks comprises NEs configured to implement at least one of Multiprotocol Label Switching (MPLS), Segment Routing over Internet Protocol (IP) version 6 (IPv6) data plane (SRv6), IP transport, or Enhanced Virtual Private Network.
17. The gNB of claim 14, wherein the instructions further prompt the gNB to store a forwarding table comprising a mapping between the MTNC-ID and the forwarding path.
In wireless communication systems, particularly in 5G networks, efficient handling of mobile termination (MT) nodes is critical for seamless connectivity. A challenge arises in managing communication paths for MT nodes, especially when they are in a non-access stratum (NAS) idle state, requiring optimized routing to maintain service continuity. To address this, a base station, specifically a gNB (next-generation NodeB), is configured to manage forwarding paths for MT nodes. The gNB includes instructions that enable it to receive a message containing a mobile termination node communication identifier (MTNC-ID) and determine a forwarding path for the MT node based on this identifier. The gNB then stores a forwarding table that maps the MTNC-ID to the corresponding forwarding path, allowing for quick retrieval and routing of subsequent communications. This ensures that data packets are correctly directed to the MT node, even when it is in an idle state, improving network efficiency and reducing latency. The forwarding table dynamically updates as MT nodes move or change states, ensuring accurate routing at all times. This solution enhances the reliability and performance of 5G networks by streamlining the management of MT node communications.
18. The gNB of claim 14, wherein the GUE header comprises a “C” flag field set to indicate that the data packet carries a data message, and wherein the first field is an “M” flag field comprising a value indicating that the data packet comprises the MTNC-ID.
19. The gNB of claim 14, wherein the GUE header comprises a “C” flag field set to indicate that the data packet carries a control message, and wherein the first field is a proto/ctype field comprising a value indicating that the data packet comprises the MTNC-ID.
This invention relates to wireless communication systems, specifically to enhancements in the gNB (next-generation NodeB) for handling data packets in a 5G or NR (New Radio) network. The problem addressed is the efficient transmission of control messages and identification information within data packets to reduce overhead and improve communication reliability. The gNB processes data packets received from a user equipment (UE) or other network nodes. The data packets include a GUE header, which contains metadata about the packet. The GUE header includes a "C" flag field that is set to indicate whether the packet carries a control message. When the "C" flag is set, the packet is identified as containing a control message rather than user data. Additionally, the GUE header includes a proto/ctype field, which specifies the type of control message or protocol being used. In this case, the proto/ctype field is set to a value that indicates the packet contains an MTNC-ID (Mobile Terminal Network Controller Identifier), a unique identifier for the UE or another network entity. This allows the gNB to quickly identify and process the packet accordingly, improving efficiency in control message handling and reducing unnecessary overhead in the network. The invention ensures that control messages and identifiers are transmitted in a structured and optimized manner, enhancing overall network performance.
20. The gNB of claim 14, wherein the gNB further retrieves and executes the computer instructions from the memory to encapsulate the data packet to further comprise an outer Internet Protocol (IP) header, a UDP extension header, a General Packet Radio Service Tunneling Protocol (GTP)-User Data Tunneling (GTP-U) header, and an inner IP header, wherein the UDP extension header comprises the UDP header and the GUE header carrying the MTNC-ID.
22. The NE of claim 21, wherein the set of resource provisioning requirements comprises a quality of service (QoS) requirement, a class of service (CoS) requirement, a resilience requirement, and an isolation requirement.
This invention relates to network resource provisioning, specifically addressing the challenge of dynamically allocating and managing network resources to meet diverse service requirements. The system defines a set of resource provisioning requirements that includes quality of service (QoS) parameters, class of service (CoS) specifications, resilience criteria, and isolation constraints. QoS requirements ensure performance metrics such as bandwidth, latency, and jitter are maintained. CoS requirements categorize traffic into different service classes to prioritize handling. Resilience requirements specify redundancy and failover mechanisms to maintain service continuity. Isolation requirements enforce traffic separation to prevent interference between different services or users. The system evaluates these requirements to allocate network resources efficiently, ensuring that each service receives the necessary capacity and protection while optimizing overall network utilization. This approach enables flexible and scalable network management, accommodating varying demands from different applications and users while maintaining performance and reliability.
23. The NE of claim 21, wherein each of the one or more transport networks comprises NEs configured to implement at least one of Multiprotocol Label Switching (MPLS), Segment Routing over Internet Protocol (IP) version 6 (IPv6) data plane (SRv6), IP transport, or Enhanced Virtual Private Network.
24. The NE of claim 21, wherein the GUE header comprises a “C” flag field set to indicate that the data packet carries a data message, and wherein the first field is an “M” flag field comprising a value indicating that the data packet comprises the MTNC-ID.
25. The NE of claim 21, wherein the GUE header comprises a “C” flag field set to indicate that the data packet carries a control message, and wherein the first field is a proto/ctype field comprising a value indicating that the data packet comprises the MTNC-ID, and wherein the MTNC-ID field carries the MTNC-ID.
This invention relates to wireless communication systems, specifically to the transmission of control messages between network entities and user equipment (UE) in a mobile network. The problem addressed is the efficient and standardized encoding of control messages within data packets to ensure proper routing and processing in the network. The invention describes a method for encoding a control message in a data packet header, where the header includes a "C" flag field set to indicate that the packet carries a control message. The header further includes a proto/ctype field that specifies the type of control message, in this case identifying the packet as containing a Mobile Terminal Network Controller Identifier (MTNC-ID). The MTNC-ID field within the packet then carries the actual MTNC-ID value, allowing the network to identify and process the control message appropriately. This approach ensures that control messages are distinguishable from regular data packets and that the specific type of control message is clearly indicated, facilitating proper handling by network components. The use of a dedicated flag and type field improves efficiency and reduces ambiguity in message processing. The invention is particularly useful in scenarios where multiple types of control messages are transmitted over the same communication channel, requiring clear differentiation and routing instructions.
26. The NE of claim 21, wherein the data packet comprises an outer Internet Protocol (IP) header, a UDP extension header, a General Packet Radio Service Tunneling Protocol (GTP)-User Data Tunneling (GTP-U) header, and an inner IP header, wherein the UDP extension header comprises the UDP header and the GUE header carrying the MTNC-ID.
This invention relates to packet data transmission in wireless communication networks, specifically addressing the need for efficient and secure tunneling of user data between network elements. The system involves a data packet structure designed for use in mobile networks, particularly those employing General Packet Radio Service (GPRS) and related protocols. The packet includes an outer Internet Protocol (IP) header for routing, a User Datagram Protocol (UDP) extension header, a GTP-U header for tunneling, and an inner IP header for the payload. The UDP extension header uniquely includes both a standard UDP header and a GUE (GPRS User Extension) header, which carries a Mobility Tunnel Control Node Identifier (MTNC-ID). This identifier facilitates tracking and management of data tunnels between network nodes, ensuring proper routing and security. The structure enables seamless interoperability between different network elements while maintaining low latency and high reliability in data transmission. The invention improves upon existing tunneling methods by integrating the MTNC-ID directly into the packet header, reducing overhead and enhancing tunnel management efficiency. This approach is particularly useful in scenarios requiring dynamic tunnel establishment and termination, such as handover procedures in mobile networks. The solution addresses challenges in maintaining consistent data flow during mobility events while minimizing signaling overhead.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
April 3, 2020
October 25, 2022
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.