Apparatus, method, and non-transitory computer-readable storage medium for network access to a residential gateway - Patents.com

By employing PFCP messages to manage QoS features on CUPS BNG systems, the solution addresses the challenge of dynamic QoS management in 5G networks, ensuring efficient and high-quality network access for residential gateways.

JP7673158B2Active Publication Date: 2025-05-08NOKIA SOLUTIONS & NETWORKS OY
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2023191274
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2022-11-15
Filing Date
2023-11-09
Publication Date
2025-05-08
Estimated Expiration
2043-11-09

AI Technical Summary

Technical Problem

Existing technologies face challenges in providing effective quality of service (QoS) management for subscriber sessions in 5G networks, particularly in updating QoS parameters dynamically and efficiently across all subscriber sessions.

Method used

The implementation of a mechanism that uses Packet Forwarding Control Protocol (PFCP) messages to program wired-based QoS features on Control and User Plane Separation in Broadband Network Gateway (CUPS BNG) systems, allowing for dynamic updates of QoS parameters and templates across subscriber sessions.

Benefits of technology

This solution enables efficient and dynamic management of QoS parameters, ensuring high-quality network access for residential gateways without disrupting existing connections, and supports scalable QoS updates across multiple subscriber sessions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007673158000001
    Figure 0007673158000001
  • Figure 0007673158000002
    Figure 0007673158000002
  • Figure 0007673158000003
    Figure 0007673158000003
Patent Text Reader

Abstract

To provide methods, apparatuses and / or non-transitory computer-readable storage media that facilitate network access to a network through residential gateways.SOLUTION: A method causes a network element to: establish a packet transfer control protocol (PFCP) session between a residential gateway and a network, the PFCP session hosting a set of rules for forwarding data traffic between the control plane and the separate user plane, the set of rules including a classification index referencing a QoS template, the QoS template including a set of traffic classifiers and one or more sets of QoS parameters. The set of traffic classifiers is associated with the classification index, each of the sets of QoS parameters is associated with a respective QoS rule index, and each traffic classifier is associated with a QoS rule index.SELECTED DRAWING: Figure 2
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] One or more exemplary embodiments relate to a method, apparatus, and / or non-transitory computer-readable storage medium for providing network access to a residential gateway. [Background technology]

[0002] 3rd Generation Partnership Project (3GPP) fifth generation (5G) technology is the next generation of wireless systems and network architectures that can bring extreme broadband and ultra-robust low latency connectivity. 5G technology will help improve various telecommunication services offered to end users and support massive broadband delivering gigabytes of bandwidth / s on demand for both uplink and downlink transmissions.

[0003] 5G networks may support IP services such as IP television (IPTV) services for residential gateways (RGs), such as fifth-generation RGs (5G-RGs) served by a 5G core (5GC). Summary of the Invention

[0004] The scope of protection sought for various exemplary embodiments is indicated by the independent claims. Exemplary embodiments and / or features described herein that do not fall within the scope of the independent claims should, if any, be interpreted as examples useful for understanding the various embodiments.

[0005] A Broadband Network Gateway (BNG) is an access point where network subscribers connect to a core network, such as 5GC. CUPS BNG (Control and User Plane Separation in Broadband Network Gateway) is an example of a separated BNG. CUPS BNG is defined in the Broadband Forum (BBF) technical report TR-459.

[0006] It is a function of the BNG to provide Quality of Service (QoS) for each subscriber session. One or more exemplary embodiments provide a mechanism for programming wire-based QoS features on the CUPS BNG utilizing Packet Forwarding Control Protocol (PFCP) messages.

[0007] One or more example embodiments also provide mechanisms for updating QoS parameters of a subscriber session mid-session (sometimes referred to as QoS override), for updating QoS templates across all subscriber sessions (e.g., via a PFCP association message), and / or for selectively updating QoS parameters included in the QoS templates as needed per subscriber. In one example, QoS parameters of a subscriber session may be updated without losing connectivity with the core network.

[0008] One or more example embodiments also provide a format for expressing QoS templates that enables QoS parameter updates for individual subscriber sessions (e.g., via a PFCP Session Modify message) and / or across all subscriber sessions that share the QoS template (e.g., via a PFCP Association message).

[0009] At least one example embodiment provides a method for network access by a residential gateway in a control and user plane split architecture. The method includes establishing a packet forwarding control protocol session between the residential gateway and a network via an aggregate gateway function, the packet forwarding control protocol session hosting a set of forwarding rules for forwarding data traffic between the control plane and the split user plane, the set of forwarding rules including a classification index that references a Quality of Service (QoS) template. The QoS template includes a set of traffic classifiers and one or more sets of QoS parameters, the set of traffic classifiers being associated with (e.g., indexed by) the classification index, and each of the one or more sets of QoS parameters being associated with (e.g., indexed by) a respective QoS rule index of the one or more QoS rule indexes. Each traffic classifier in the set of traffic classifiers is associated with a QoS rule index of the one or more QoS rule indexes to facilitate network access by the residential gateway in accordance with the packet forwarding control protocol session via the aggregate gateway function.

[0010] At least one other example embodiment provides a non-transitory computer-readable storage medium storing computer-executable instructions that, when executed by at least one processor in a network element, cause the network element to perform a method for network access by a residential gateway in a control and user plane split architecture. The method includes establishing a packet forwarding control protocol session between a residential gateway and a network via an aggregate gateway function in the network element, the packet forwarding control protocol session hosting a set of forwarding rules for forwarding data traffic between the control plane and the split user plane, the set of forwarding rules including a classification index that references a Quality of Service (QoS) template. The QoS template includes a set of traffic classifiers and one or more sets of QoS parameters, the set of traffic classifiers being associated with (e.g., indexed by) the classification index, and each of the one or more sets of QoS parameters being associated with (e.g., indexed by) a respective QoS rule index of the one or more QoS rule indexes. Each traffic classifier in the set of traffic classifiers is associated with a QoS rule index of the one or more QoS rule indexes. and facilitating network access by the residential gateway pursuant to the packet forwarding control protocol session via the aggregate gateway function.

[0011] According to an example embodiment, one or more QoS rule indexes and a set of one or more QoS parameters may be represented as an information element.

[0012] The one or more sets of QoS parameters may include at least one of rate information or priority information for the data traffic.

[0013] The method may include updating at least one of the one or more sets of QoS parameters based on residential gateway level wireline access characteristics (RG-LWAC) from the network.

[0014] The method may include updating the QoS template to change at least one of (i) a first QoS parameter of the one or more sets of QoS parameters, or (ii) a QoS rule index, based on the RG-LWAC.

[0015] The updating may include sending a Packet Forwarding Control Protocol Session Modify message from the control plane to the split user plane, the Packet Forwarding Control Protocol Session Modify message including a QoS rule index and a reference to one or more QoS parameters to be updated, and updating the QoS parameters based on the Packet Forwarding Control Protocol Session Modify message.

[0016] The method may further include programming a QoS template in the split user plane prior to establishing the packet forwarding control protocol session.

[0017] At least one exemplary embodiment provides a network element for facilitating network access by a residential gateway in a control and user plane split architecture. The network element includes at least one processor and at least one memory. The at least one memory stores instructions that, when executed by the at least one processor, cause the network element to: establish a packet forwarding control protocol session between the residential gateway and a network, the packet forwarding control protocol session hosting a set of forwarding rules for forwarding data traffic between the control plane and the split user plane, the set of forwarding rules including a classification index that references a Quality of Service (QoS) template, the QoS template including a set of traffic classifiers and one or more sets of QoS parameters. When the set of traffic classifiers is associated with (e.g., indexed by) the classification index, each of the one or more sets of QoS parameters is associated with (e.g., indexed by) a respective QoS rule index of the one or more QoS rule indexes. Each traffic classifier in the set of traffic classifiers is associated with a QoS rule index of the one or more QoS rule indexes to facilitate network access by the residential gateway according to the packet forwarding control protocol session.

[0018] At least one example embodiment provides a network element for facilitating network access by a residential gateway in a control and user plane split architecture, the network element including means for establishing a packet forwarding control protocol session between the residential gateway and a network, the packet forwarding control protocol session hosting a set of forwarding rules for forwarding data traffic between the control plane and the split user plane, the set of forwarding rules including a classification index that references a Quality of Service (QoS) template, the QoS template including a set of traffic classifiers and one or more sets of QoS parameters, and means for facilitating network access by the residential gateway in accordance with the packet forwarding control protocol session, where the set of traffic classifiers is associated with (e.g., indexed by) the classification index, each of the one or more sets of QoS parameters is associated with (e.g., indexed by) a respective QoS rule index of the one or more QoS rule indexes, and each traffic classifier in the set of traffic classifiers is associated with a QoS rule index of the one or more QoS rule indexes,

[0019] According to an example embodiment, the at least one memory may store instructions that, when executed by the at least one processor, cause the network element to update at least one of the one or more QoS parameters based on the RG-LWAC from the network.

[0020] The at least one memory may store instructions that, when executed by the at least one processor, cause the network element to update at least one of the one or more QoS parameters by modifying the QoS template based on the RG-LWAC.

[0021] The at least one memory may store instructions that, when executed by the at least one processor, cause the network element to update a QoS template to change at least one of (i) a first QoS parameter of the first set of QoS parameters or (ii) a QoS rule index based on the RG-LWAC.

[0022] The at least one memory may store instructions that, when executed by the at least one processor, cause the network element to send a packet forwarding control protocol session modify message from the control plane to the user plane, the packet forwarding control protocol session modify message including a QER index and a reference to the one or more QoS parameters to be updated, and update the QoS parameters based on the packet forwarding control protocol session modify message.

[0023] The at least one memory may store instructions that, when executed by the at least one processor, cause the network element to program a QoS template in a split user plane prior to establishing a packet forwarding control protocol session.

[0024] As the illustrative embodiments will become more fully understood from the following detailed description and the accompanying drawings, in which like elements are represented by like reference numerals, these reference numerals being provided for purposes of illustration only and not for purposes of limitation of the present disclosure. [Brief description of the drawings]

[0025] [Figure 1] FIG. 1 is a block diagram illustrating a portion of a system architecture for wireless core network access, in accordance with an example embodiment. [Diagram 2] FIG. 4 is a signal flow diagram illustrating a method according to an exemplary embodiment. [Diagram 3] FIG. 4 is a signal flow diagram illustrating another method according to an exemplary embodiment. [Figure 4] FIG. 1 illustrates a quality of service (QoS) template according to an example embodiment. [Diagram 5] FIG. 1 illustrates an exemplary embodiment of a network node in which an integration gateway function (AGF) may be implemented.

[0026] It should be noted that these figures are intended to illustrate the general features of methods, structures, and / or materials utilized in some exemplary embodiments, as well as to supplement the descriptions provided below. However, these figures are not to scale, may not precisely reflect the exact structure or performance characteristics of any given embodiment, and should not be construed as defining or limiting the range of values ​​or properties encompassed by the exemplary embodiments. The use of similar or identical reference numbers in the various figures is intended to indicate the presence of similar or identical elements or features. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0027] Various exemplary embodiments will now be described more fully with reference to the accompanying drawings, in which several exemplary embodiments are shown.

[0028] Detailed exemplary embodiments are disclosed herein. However, the specific structural and functional details disclosed herein are merely representative for purposes of describing the exemplary embodiments. However, the exemplary embodiments may be configured in many alternative forms and should not be construed as being limited to only the embodiments described herein.

[0029] It is to be understood that there is no intention to limit the exemplary embodiments to the particular forms disclosed. The exemplary embodiments may encompass all modifications, equivalents, and alternatives falling within the scope of this disclosure. Like reference characters refer to like elements throughout the description of the figures.

[0030] Although one or more exemplary embodiments may be described in terms of functions or network elements, such as a network node, an Aggregation Gateway Function (AGF) node, a Residential Gateway (RG), a server, etc., it should be understood that one or more exemplary embodiments discussed herein may be performed by one or more processors (or processing circuits) in an applicable device, apparatus, network node, network element, or system. For example, according to one or more exemplary embodiments, at least one memory may store instructions that, when executed by one or more processors, cause a network element / network node, etc., to perform operations described herein.

[0031] As discussed herein, the term "mechanism" may, in addition to its plain and ordinary meaning, refer to a method, an apparatus, and / or a non-transitory computer-readable storage medium, where applicable.

[0032] As discussed herein, the terms "one or more" and "at least one" may be used interchangeably.

[0033] It will be understood that several exemplary embodiments may be used in combination.

[0034] As discussed herein, the term "subscriber" refers to a purchaser or subscriber of broadband service who utilizes a residential gateway (RG) to access the service. The term "user" refers to a user of an end user device or customer premises equipment (CPE) that transmits or receives user traffic through an RG. Although used in this manner for clarity, a user may also be referred to as a subscriber.

[0035] As described herein, a packet data unit (PDU) session refers to an IP-based PDU session. An IP-based PDU session (sometimes referred to as an IP session) refers to an IP connection established between an RG (e.g., a 5th Generation-Residential Gateway (5G-RG)) and a wireless core network, such as a 5GC, where the wireless core network assigns one or more IP addresses to the RG for use in transmitting and receiving traffic (e.g., data and control traffic). In operation, the RG utilizes the assigned IP address or IP prefix to connect to the Internet (or other data network). In at least some examples, the RG may obtain several different IP addresses / prefixes for different types of services, each representing a different IP session. An IP-based PDU session includes a single IPv4 session, a single IPv6 session, or a single dual-stack IP session. Although discussed herein with respect to an IP session for illustrative purposes, the illustrative embodiments should not be limited to these examples. Rather, the illustrative embodiments may be applicable to other PDU session types.

[0036] In a Control and User Plane Separation in Broadband Network Gateway (CUPS BNG) architecture, the PFCP protocol is used to program traffic forwarding rules from the control plane or control plane function (e.g., the Aggregated Gateway Function Control Plane (AGF-CP)) to the user plane or user plane function (e.g., the AGF-User Plane (AGF-UP)) and vice versa. Each set of traffic forwarding rules that can be used for one or more PDU sessions from a single RG is called a PFCP session.

[0037] Generally speaking, the control plane is responsible for maintaining session state and providing instructions to the user plane, which is responsible for moving packets from ingress to egress through the system by following the traffic rules programmed by the control plane and interacting independently with other nodes in the network via various routing protocols (e.g., Ethernet Virtual Private Network (EVPN), Border Gateway Protocol (BGP), Interior Gateway Protocol (IGP), etc.).

[0038] In the context of wired access to 5GC, the 5G-RG may be served by the 5GC. The 5G-RG operates as a full 3GPP user equipment (UE) that is assumed to terminate 3GPP non-access stratum (NAS) signaling and support User Equipment Route Selection Policy (URSP) rules transmitted to the UE by the 5GC.

[0039] The PFCP protocol programs forwarding rules, including queues or policers per traffic or forwarding class, per subscriber. In most broadband use cases, Internet Service Providers (ISPs) (or service providers) offer a limited set of service offerings (or services) based on bandwidth. Therefore, subscribers often share the same QoS template (including a programmed set of QoS parameters) when paying for the same service, rather than the control plane programming the user plane with individual QoS parameters for each subscriber. QoS parameters can be statically or dynamically provisioned. Static provisioning of QoS parameters involves the use of static QoS templates, whereas dynamic provisioning involves programming QoS parameters, etc., in real time. QoS templates can be programmed on the user plane by the control plane using PFCP associations, and the QoS templates themselves utilize QoS enforcement rules (QERs) with indexes.

[0040] 1 is a block diagram illustrating a portion of a system architecture for wireless core network access by 5G-RG according to an example embodiment. In the example shown in FIG. 1, the system architecture incorporates a CUPS BNG architecture.

[0041] 1, a communication network includes a plurality of 5G-RGs 102-1, 102-2, 102-3, a plurality of access networks (ANs) 104-1, 104-2, 104-3 (also referred to as access nodes or AN nodes), an integrated gateway function (AGF) node 10, a wireless core network 110, and a data network (DN), e.g., the Internet 100. In this example, the wireless core network 110 is a 5GC, and each of the 5G-RGs 102-1, 102-2, 102-3 is served by a corresponding one of the ANs 104-1, 104-2, 104-3. However, the exemplary embodiment should not be limited to this example.

[0042] Each of the ANs 104-1, 104-2, 104-3 may include one or more of a next generation radio access network (NG-RAN) or a wireline 5G access network (W-5GAN).

[0043] Each of the 5G-RGs 102-1, 102-2, and 102-3 can provide IP services to one or more end-user devices or customer premises equipment (CPE) (not shown in FIG. 1). In one example, an end-user device or CPE is understood to be a hardware device or equipment typically located in a customer's home or business. Exemplary end-user devices may include terminals or electronic devices such as mobile phones, laptops, computers, tablets, wireless (e.g., WiFi) access points, wireless network (e.g., WiFi) extenders, fixed wireless access units, small cell devices, and the like.

[0044] Although only a particular number of 5G-RGs and ANs are shown in Figure 1, the exemplary embodiments should not be limited to this example. Rather, any number of 5G-RGs may be served by a given AN and / or any number of ANs may be served by an AGF.

[0045] For illustrative purposes, one or more exemplary embodiments are described in more detail below with respect to 5G-RG102-1 and AN104-1. However, it should be understood that 5G-RG102-2 and 102-3 may have the same or substantially the same functionality as 5G-RG102-1. Similarly, it should be understood that AN104-2 and 104-3 may have the same or substantially the same functionality as AN104-1.

[0046] 5G-RG 102-1 is an RG that connects one or more end user devices or CPEs to the Internet (or other data network) 100 via 5GC 110. 5G-RG 102-1 registers and authenticates with 5GC 110 through the use of standard mobile 3GPP procedures. 5G-RG 102-1 processes control messages (e.g., 3GPP NAS messages) from 5GC 110 and access stratum (AS) messages from AGF 10.

[0047] Once authenticated with the 5GC 110, the 5G-RG 102-1 may be assigned one or more IP addresses upon request. The 5G-RG 102-1 may either utilize the assigned IP addresses as network address translation (NAT) public addresses (e.g., for IPv4) or assign prefixes directly to end user devices (e.g., for IPv6).

[0048] The 5G-RG102-1 can support multiple services, such as IPTV. In some embodiments, IPTV can be defined as multimedia services, such as television, video, audio, text media, graphics, data, combinations thereof, etc., delivered over an IP-based network that supports a required level of QoS, Quality of Experience (QoE), security, interactivity, reliability, etc.

[0049] 5G-RG102-1 is connected to 5GC110 via AN104-1 and a gateway (or gateway function) called AGF10. AGF10 is a function added to a wired access network (e.g., W-5GAN) that enables and / or allows connectivity to 5GC110 via a wired network.

[0050] The AGF 10 is separated to separate the control plane (AGF-Control Plane (AGF-CP) 106) and the user plane (AGF-User Plane (AGF-UP) 108).

[0051] Among other functions, as also discussed above, the AGF-CP 106 programs the AGF-UP 108 (e.g., per subscriber or PDU session or across subscribers or PDU sessions) via the PFCP protocol with forwarding rules and QoS parameters to facilitate network access by the 5G-RG 102-1 to the 5GC 110. Further functionality of the elements of FIG. 1 is discussed below with respect to FIGS. 2-3.

[0052] Figure 2 is a signal flow diagram illustrating a method for network access according to an exemplary embodiment. For illustrative purposes, the exemplary embodiment shown in Figure 2 will be described with respect to the architecture shown in Figure 1. However, it should be understood that the exemplary embodiment should not be limited to this example.

[0053] 2, at S20, the AGF-UP 108 receives an initiation (e.g., PADI) message from the 5G-RG 102-1 via the AN 104-1, requesting network access (e.g., to the Internet 100) via the 5G-RG 110. Upon receipt, at S22, the AGF-UP 108 forwards the initiation message to the AGF-CP 106 via a common control packet redirection tunnel between the AGF-UP 108 and the AGF-CP 106.

[0054] In step S23, the AGF-CP 106 and the AGF-UP 108 establish an active PFCP association by exchanging PFCP association setup messages. For example, the AGF-CP 106 sends a PFCP association setup request message to the AGF-UP 108, and the AGF-UP 108 responds by sending a PFCP association setup response message to the AGF-CP 106. Among other things, during the PFCP association setup in S23, the AGF-CP 106 utilizes the PFCP protocol to program one or more QoS templates in the AGF-UP 108 with an associated list of QoS policy names, QoS enforcement rules (QERs), and QoS parameters. In one example, a service provider may design QoS templates for each of the services provided to the 5G-RG 102-1. Each QoS template has a "name" (QoS policy name) and a list of QERs, each containing defined and / or predetermined QoS parameters (e.g., Peak Information Rate (PIR), Committed Information Rate (CIR), Priority, etc.). In this case, the QoS policy name is associated with a list of QERs containing the QoS parameters assigned to the service by the service provider. When updates to the QoS templates in the AGF-UP 108 are required (e.g., adding, deleting, and / or modifying a QoS template), the AGF-CP 106 may send a PFCP association update to the AGF-UP 108 to affect updates to the programmed QoS templates. Thus, the PFCP association message may be used to program and / or update QoS templates per service level and / or across subscribers associated with the QoS template or service.

[0055] More specifically, in accordance with at least one exemplary embodiment, a QoS template may include a list of traffic classifiers and a list of QoS parameters represented as QERs. Indexing is used for the traffic classifiers such that the traffic classifiers reference a QER index, which further references and / or includes a list (or set) of QoS parameters associated with the QER (e.g., referenced by the QER index). Although described herein with respect to QERs, it should be understood that one or more exemplary embodiments may apply to any QoS information element (IE) represented by one or more indexes.

[0056] FIG. 4 is a diagram illustrating a QoS template according to an example embodiment.

[0057] 4, the QoS template SGRP1 includes a classifier index (Classifier1) that references a table containing a list or set of traffic classifiers (Dot1p_NC and Default), each associated with a respective QER index (QER1, QER2, QER3) (also called QoS rule index). The QoS template further includes a list of QER indexes (QoS rule indexes) each associated with a respective set or list of QoS parameters (e.g., PIR, CIR, Prio). The QER indexes and QoS parameters are represented as information elements (IEs).

[0058] Still referring to FIG. 4, as shown, a PFCP session may include a list of packet detection rules (PDRs) and associated packet detection information (PDIs), where each PDR references a classifier index (e.g., classifier 1) and a forwarding action rule (FAR1, FAR2). The PDR identifies a particular forwarding rule, and the PDI is a grouping information element (IE) that specifies matching criteria using a source interface and traffic endpoint. The FAR specifies the forwarding action and destination of redirected control packets. The classifier index points to a table containing a set of traffic classifiers associated with a QER for the PDU session.

[0059] During programming of QoS templates in the AGF-UP 108 (e.g., during PFCP association), the AGF-CP 106 has knowledge of each classifier index and QER index for each QoS template. Thus, during a PDU session, the AGF-CP 106 can update one or more QoS parameters by referencing the respective indexes (e.g., classifier and / or QER index).

[0060] Returning to Figure 2, at S28 and S30, AGF 10 establishes a PFCP session including a set of forwarding rules for control messages between 5G-RG 102-1 and 5GC 110. In at least one exemplary embodiment, AGF 10 establishes a PFCP session to enable exchange of control signaling (or control messages) between AGF-UP 108 and AGF-CP 106. The control messages may be PPPoE control plane messages and / or NAS messages transported over a PPP vendor-specific network protocol (VSNP).

[0061] More specifically, for example, when a PFCP session is established in the AGF-CP 106, in S28, the AGF-CP 106 outputs a PFCP session establishment request message (PFCP session Est.Req.) to the AGF-UP 108. Based on the PFCP session establishment request message, the AGF-UP 108 establishes a PFCP session in the AGF-UP 108. Then, the AGF-UP 108 outputs a PFCP session establishment response message (PFCP session Est.Resp.) to the AGF-CP 106 (S30). The PFCP session establishment message for control signaling is generally known, and therefore further description is omitted.

[0062] At S32, the 5G-RG 102-1 completes registration with the 5GC 110 by exchanging control messages (e.g., NAS messages or PPPoE control plane messages) according to the established PFCP session (forwarding rules). During this process, the service provider identifies the 5G-RG 102-1 through its subscriber identity module (SIM) card and provides the initial RG level radio access characteristics (RG-LWAC) to the AGF-CP 106. The RG-LWAC is a QoS parameter associated with the subscriber or subscription. The RG-LWAC can carry real-time 5G QoS Identifier (5QI) to traffic class mappings, as well as other aggregate QoS information such as downlink (DL) aggregate rate, aggregate policy uplink (UL) and DL, 5QI to TC mappings for DL, where each TC has a queue profile and a policy profile. In at least one example embodiment, the RG-LWAC may include a QoS policy name that corresponds to a QoS template (programmed in S23) that the 5G-RG 102-1 should use for the service requested in the 5G-RG 102-1. The RG-LWAC information includes the QoS policy name that the 5G-RG 102-1 should use for all PDU sessions.

[0063] In step S34, 5G-RG102-1 initiates a service request or establishment of a new PDU session with 5GC110. As is commonly known, a service request may be used when 5G-RG102-1 needs and / or wants to re-establish control (e.g., NAS) signaling and PDU sessions. In this case, 5G-RG102-1 is still registered with 5GC110, but may have temporarily lost connection with AGF10 (e.g., when the line is disconnected). However, if the initiation message requests initial network access by 5G-RG102-1 to 5GC110, in S34, 5G-RG102-1 may establish a new (initial) PDU session with 5GC110. Such service request and PDU session establishment methods are well known, and therefore will not be described in detail.

[0064] After completing the registration process in S34, upon receiving a PDU session establishment request from the 5GC 110 in S36, the AGF 10 modifies the established PFCP session to add a set of data forwarding rules in S40 and S42. In doing so, the AGF 10 also specifies and / or updates QoS parameters for the PDU session to be established. More specifically, for example, the AGF-CP 106 and the AGF-UP 108 exchange PFCP session modification messages for the requested PDU session to add a set of forwarding rules for data traffic and specify QoS parameters to be used for the requested PDU session. In one example (e.g., using a static template), the QoS parameters may be specified by providing the AGF-UP 108 with a QoS policy name (e.g., QER1:template-1) for the PDU session to be established. The AGF-CP 106 may also include a QoS policy and a QER that includes a specific QoS parameter that may override the QER in the QoS policy. In the dynamic case, the AGF-CP 106 may specify individual QoS parameters (e.g., QER1:CIR10 PIR20, QER2:CIR20 PIR40, etc.) for the PDU sessions to be established. The AGF-UP 108 may update entries in the QoS template based on this information from the AGF-CP 106.

[0065] In more detail, upon modifying the PFCP session as required to add a set of required forwarding rules and to specify QoS parameters in the AGF-CP 106 (e.g., via a QoS template or by individual QoS parameters), the AGF-CP 106 sends a PFCP session modification request message (PFCP session Mod.Req.) to the AGF-UP 108, which specifies, among other things, the QoS parameters for the PDU or subscriber session (e.g., via a QoS policy name or by individual QoS parameters), at S40. Based on the PFCP modification request message, the AGF-UP 108 modifies the PFCP session as required to add a set of required forwarding rules and to specify QoS parameters for the PDU session in the AGF-UP 108. The AGF-UP 108 then sends a PFCP session modification response message (PFCP session Mod.Resp.) to the AGF-CP 106, indicating that the PFCP session has been modified in the AGF-UP 108, at S42. The PFCP modification message and the method for modifying the PFCP session are otherwise commonly known, and therefore further description is omitted.

[0066] In S44, when the PFCP session is modified, the AGF-CP 106 outputs a PDU session establishment response message (PDU session Est. Resp.) to the 5GC 110.

[0067] In step S46, 5G-RG102 completes establishment of the requested PDU session with 5GC110 and obtains the requested IP address and prefix for the PDU session from 5GC110.

[0068] Once the PDU session between 5G-RG102-1 and 5GC110 is established, AGF10 facilitates access by 5G-RG102-1 to 5GC110 according to the PFCP session and QoS parameters in AGF-CP106 and AGF-UP108.

[0069] One or more exemplary embodiments also provide a mechanism for selectively updating various QoS parameters for one or more PDU sessions in the middle of a session, such as is discussed below with respect to FIG.

[0070] Figure 3 is a signal flow diagram illustrating another method for network access according to an exemplary embodiment. As with Figure 2, for illustrative purposes, the exemplary embodiment shown in Figure 3 will be discussed with respect to the architecture shown in Figure 1. However, it should be understood that the exemplary embodiment should not be limited to this example.

[0071] 3, once 5G-RG 102-1 has completed registration with 5GC 110, at S300, AGF-UP 106 receives an RG-LWAC update message from 5GC 110 informing AGF-CP 106 of updates to the RG-LWAC for PDU sessions in 5G-RG 102-1. The RG-LWAC update message includes the updated RG-LWAC for 5G-RG 102-1.

[0072] Upon receiving the updated RG-LWAC, the AGF-CP 106 processes and / or analyzes the updated RG-LWAC to determine the QER to be updated, for example, for 5G-RG 102-1. Because the QERs are indexed as discussed above, the AGF-CP 106 can update the QER for a particular traffic classifier by referencing a particular QER index and updating a corresponding entry (e.g., QoS parameters) in the QoS template.

[0073] At S302, the AGF-CP 106 sends a PFCP Update Request message requesting an update of QoS parameters for one or more subscribers and / or PDU sessions. Based on the PFCP Update Request message, the AGF-UP 108 updates the QoS parameters as necessary in the AGF-UP 108. The AGF-UP 108 then sends a PFCP Session Update Response message to the AGF-CP 106 at S304, indicating that the QoS parameters have been updated in the AGF-UP 108.

[0074] In one example, to update per subscriber session, the PFCP update request message may be a PFCP session Mod.Req. message and the PFCP update response message may be a PFCP session Mod.Resp. message. The PFCP session change request message may include, for example, a reference to a QER index and one or more QoS parameters to be updated. Based on the PFCP modify request message, the AGF-UP 108 updates the QoS template for the PDU session in the AGF-UP 108.

[0075] In another example, to update across multiple subscriber sessions (e.g., on a per-service basis across all subscriber sessions), the PFCP update request message may be a PFCP association request message and the PFCP update response message may be a PFCP association response message. The PFCP association request message may, for example, include a reference to a QER index for the QoS template, which may update the QER for all subscriber sessions using the QoS template to be updated. Based on the PFCP modify request message, the AGF-UP 108 updates the QoS templates for the PDU sessions in the AGF-UP 108.

[0076] Still referring to FIG. 3, having updated the QoS parameters as necessary, AGF 10 then continues to facilitate access by 5G-RG 102-1 to 5GC 110 according to the PFCP session including the updated QoS templates in AGF-CP 106 and AGF-UP 108.

[0077] In accordance with one or more exemplary embodiments, the indexing and / or use of QoS templates in accordance with one or more exemplary embodiments may enable AGF-CP106 to update one or more QoS parameters during a session by referencing an index (e.g., directly), such as a QER and / or classifier index.

[0078] According to one or more example embodiments, the AGF-CP 106 may also selectively update QoS parameters for one or more PDU sessions (e.g., individually) while leaving QoS parameters for other PDU sessions unchanged, e.g., by updating QoS parameters associated with a QER index, updating a QER index associated with a given traffic classifier, and / or updating a classifier index included in a PFCP session for one or more PDU sessions.

[0079] According to one or more exemplary embodiments, the AGF-CP 106 may also update the QER for the QoS template, which may update the QER for all PDU sessions using the QoS template.

[0080] 5 is a diagram illustrating an exemplary embodiment of a network node in which an AGF may be implemented. The structure shown in FIG. 5 may also represent other network elements such as residential gateways, CPEs, etc.

[0081] As shown, the network node includes a memory 540, a processor 520 coupled to the memory 540, and various communication interfaces 560 coupled to the processor 520. The various interfaces 560 may constitute transceivers for transmitting / receiving data to / from other network elements (e.g., network nodes, routers, nodes, servers, BNG, etc.). As will be appreciated, depending on the implementation of the network node, the network node may include more components than those shown in FIG. 5. However, it is not necessary to show all of these generally conventional components to disclose the exemplary embodiments. For illustrative purposes, the exemplary embodiment shown in FIG. 5 is described with respect to the processor 520. However, it should be understood that the network node shown in FIG. 5 may include one or more processors or other processing circuitry, such as one or more application specific integrated circuits (ASICs).

[0082] The memory 540 may be a computer-readable storage medium that generally includes a random access memory (RAM), a read-only memory (ROM), and / or a permanent mass storage device such as a disk drive. The memory 540 also stores an operating system and any other routines / modules / applications for providing the functionality of the network node (including UPF, CPF, MPF, etc.) to be executed by the processor 520. These software components may also be loaded into the memory 540 from a separate computer-readable storage medium using a drive mechanism (not shown). Such separate computer-readable storage medium may include a disk, tape, DVD / CD-ROM drive, memory card, or other similar computer-readable storage medium (not shown). In some exemplary embodiments, the software components may be loaded into the memory 540 through one of the various interfaces 560 rather than through a computer-readable storage medium.

[0083] The processor 520 or other processing circuitry may be configured to execute instructions of a computer program by performing system arithmetic, logical, and input / output operations. Instructions may be provided to the processor 520 by the memory 540.

[0084] The various communication interfaces 560 may be wired and may include components that interface the processor 520 with other input / output components. As will be appreciated, the various interfaces 560 and the programs stored in the memory 540 to describe the dedicated functions of the network node will vary depending on the implementation of the network node.

[0085] The interface 560 may also include one or more user input devices (eg, a keyboard, keypad, mouse, etc.) and user output devices (eg, a display, speakers, etc.).

[0086] Terms such as first, second, etc. may be used herein to describe various elements, but these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element can be called a second element, and similarly, a second element can be called a first element, without departing from the scope of the present disclosure. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0087] When an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element, or there may be intervening elements. In contrast, when an element is referred to as being "directly connected" or "directly coupled" to another element, there are no intervening elements. Other words used to describe relationships between elements should be construed in a similar manner (e.g., "between," "directly between," "adjacent," "directly adjacent," etc.).

[0088] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the singular forms "a", "an" and "the" are intended to include the plural unless the context clearly dictates otherwise. Furthermore, it will be understood that the terms "comprises", "comprising", "includes" and / or "including" as used herein specify the presence of stated features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.

[0089] Also, in some alternative implementations, the functions / acts described may occur out of the order noted in the figures. For example, two figures shown in succession may in fact be executed substantially concurrently or in the reverse order, depending on the functions / acts involved.

[0090] In the following description, specific details are provided to provide a thorough understanding of the exemplary embodiments. However, it will be understood by those skilled in the art that the exemplary embodiments may be practiced without these specific details. For example, systems may be shown in block diagrams to avoid obscuring the exemplary embodiments in unnecessary detail. In other instances, well-known processes, structures, and techniques may be shown without unnecessary detail to avoid obscuring the exemplary embodiments.

[0091] As described herein, the exemplary embodiments are described with reference to acts and symbolic representations of operations (e.g., in the form of flowcharts, flow diagrams, data flow diagrams, structure diagrams, block diagrams, etc.) that perform particular tasks or implement particular abstract data types and may be implemented using existing hardware, for example, in existing network nodes, BNGs, servers, ANs, CPEs, routers, or other network elements and / or hardware. Such existing hardware may be processing or control circuitry, such as, but not limited to, one or more processors, one or more central processing units (CPUs), one or more controllers, one or more arithmetic logic units (ALUs), one or more digital signal processors (DSPs), one or more microcomputers, one or more field programmable gate arrays (FPGAs), one or more systems on a chip (SoCs), one or more programmable logic units (PLUs), one or more microprocessors, one or more application specific integrated circuits (ASICs), or any other device or devices capable of responding to and executing instructions in a defined manner.

[0092] Although a flowchart may describe operations as a sequential process, many of the operations may be performed in parallel, simultaneously, or concurrently. Additionally, the order of operations may be rearranged. A process may be terminated when its operations are completed, but may have additional steps not included in the figures. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or a main function.

[0093] As disclosed herein, the terms "storage medium," "computer-readable storage medium," or "non-transitory computer-readable storage medium" may refer to one or more devices for storing data, including read-only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage media, optical storage media, flash memory devices, and / or other tangible, machine-readable media for storing information. The term "computer-readable medium" may include, but is not limited to, portable or fixed storage devices, optical storage devices, and various other media capable of storing, containing, or carrying instructions and / or data.

[0094] Furthermore, the exemplary embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented in software, firmware, middleware, or microcode, the program code or code segments for performing the necessary tasks may be stored in a machine-readable medium or computer-readable medium, such as a computer-readable storage medium. When implemented in software, one or more processors perform the necessary tasks. For example, as described above, according to one or more exemplary embodiments, at least one memory may include or store computer program code, and the at least one memory and computer program code may be configured to cause the at least one processor to perform the necessary tasks of the network element or network device. Furthermore, the processor, memory, and exemplary algorithms may be encoded as computer program code and act as a means for providing or causing the execution of the operations discussed herein.

[0095] A code segment of the computer program code may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and / or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable technique including memory sharing, message passing, token passing, network transmission, etc.

[0096] The terms "including" and / or "having" as used herein are defined as comprising (i.e., open language). The term "coupled" as used herein is defined as connected, although not necessarily directly and not necessarily mechanically. Terms derived from the term "indicate" (e.g., "indicate" and "indicate") are intended to encompass all the various techniques available for communicating or referencing the object / information being indicated. Some, but not all, examples of techniques available for communicating or referencing the object / information shown include conveying the object / information shown, conveying an identifier for the object / information shown, conveying information used to generate the object / information shown, conveying some part or portion of the object / information shown. Conveyance of some derivation of the object / information is shown, and conveyance of some symbol representing the object / information is shown.

[0097] According to an example embodiment, a network node, BNG, server, AN, CPE, router, or other network element may be (or may include) hardware, firmware, hardware executing software, or any combination thereof. Such hardware may include processing or control circuitry, such as, but not limited to, one or more processors, one or more CPUs, one or more controllers, one or more ALUs, one or more DSPs, one or more microcomputers, one or more FPGAs, one or more SoCs, one or more PLUs, one or more microprocessors, one or more ASICs, or any other device(s) capable of responding to and executing instructions in a defined manner.

[0098] Benefits, other advantages, and solutions to problems have been described above with regard to specific embodiments of the invention. However, the benefits, advantages, solutions to problems, and any elements that may cause or result in such benefits, advantages, or solutions, or that may make such benefits, advantages, or solutions more significant, should not be construed as critical, necessary, or essential features or elements of any or all of the claims.

Claims

1. 1. A method for network access by a residential gateway in a control and user plane split architecture, the control and user plane split architecture including a control plane and a split user plane, the method comprising: establishing a packet data unit session between the residential gateway and a network via an aggregate gateway function having a packet forwarding control protocol session, the packet forwarding control protocol session hosting a set of forwarding rules for forwarding data traffic between the control plane and the separated user plane, the set of forwarding rules including a classification index referencing a Quality of Service (QoS) template, the QoS template including a set of traffic classifiers and one or more sets of QoS parameters; the set of traffic classifiers is associated with the classification index; each of the one or more sets of QoS parameters is associated with a respective QoS rule index of one or more QoS rule indexes; each traffic classifier in the set of traffic classifiers is associated with a QoS rule index in the one or more QoS rule indexes; The method further comprises: facilitating network access by said residential gateway according to said packet forwarding control protocol session via said aggregate gateway function.

2. 2. The method of claim 1, wherein the one or more QoS rule indexes and the set of one or more QoS parameters are represented as information elements.

3. 2. The method of claim 1, wherein the one or more sets of QoS parameters include at least one of rate information or priority information for the data traffic.

4. 2. The method of claim 1, further comprising: updating at least one of the one or more sets of the plurality of QoS parameters based on Residential Gateway-Level Wireless Access Characteristics (RG-LWAC) from the network.

5. 5. The method of claim 4, wherein the updating step updates at least one of the one or more sets of QoS parameters by modifying the QoS template based on the RG-LWAC.

6. 5. The method of claim 4, further comprising: updating the QoS template to change (i) one QoS parameter of a first set of the one or more sets of the plurality of QoS parameters, or (ii) at least one of the plurality of QoS rule indexes based on the RG-LWAC.

7. The updating step includes: sending a Packet Forwarding Control Protocol Session Modification message from the control plane to the split user plane, the Packet Forwarding Control Protocol Session Modification message including a QoS rule index and a reference to one or more QoS parameters to be updated; 5. The method of claim 4, further comprising: updating the QoS parameters based on the Packet Transmission Control Protocol Session Modification message.

8. 2. The method of claim 1, further comprising the step of programming the QoS template in the split user plane prior to the establishing step.

9. 1. A network element for facilitating network access by a residential gateway in a control and user plane split architecture, the control and user plane split architecture including a control plane and a split user plane, the network element comprising: means for establishing a packet data unit session between the residential gateway and a network via an aggregate gateway function having a packet forwarding control protocol session hosting a set of forwarding rules for forwarding data traffic between the control plane and the separated user plane, the set of forwarding rules including a classification index referencing a Quality of Service (QoS) template, the QoS template including a set of traffic classifiers and one or more sets of QoS parameters; the set of traffic classifiers is associated with the classification index; each of the one or more sets of QoS parameters is associated with a respective QoS rule index of one or more QoS rule indexes; each traffic classifier in the set of traffic classifiers is associated with a QoS rule index in the one or more QoS rule indexes; The network element further comprises:

13. A network element comprising: means for facilitating network access by said residential gateway in accordance with said packet forwarding control protocol session.

10. 10. The network element of claim 9, wherein the one or more QoS rule indexes and the set of one or more QoS parameters are represented as information elements.

11. 10. The network element of claim 9, wherein the one or more sets of QoS parameters include at least one of rate information or priority information for the data traffic.

12. The network element of claim 9, wherein at least one memory stores instructions that, when executed by at least one processor, cause the network element to update at least one of one or more sets of QoS parameters based on Residential Gateway-Level Wireless Access Characteristics (RG-LWAC) from the network.

13. 13. The network element of claim 12, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the network element to update at least one of the one or more sets of QoS parameters by modifying the QoS template based on the RG-LWAC.

14. 13. The network element of claim 12, wherein the at least one memory stores instructions that, when executed by the at least one processor, cause the network element to update the QoS template to change (i) one QoS parameter of a first set of the plurality of QoS parameters, or (ii) at least one of the plurality of QoS rule indexes based on the RG-LWAC.

15. 1. A non-transitory computer-readable storage medium storing computer-executable instructions that, when executed by at least one processor in a network element in a control and user plane split architecture, cause the network element to perform a method for network access by a residential gateway, the method comprising: Establishing a packet data unit session between the residential gateway and a network via an aggregate gateway function having a packet forwarding control protocol session, the packet forwarding control protocol session hosting a set of forwarding rules for forwarding data traffic between a control plane and a separated user plane, the set of forwarding rules including a classification index referencing a Quality of Service (QoS) template, the QoS template including a set of traffic classifiers and one or more sets of QoS parameters; the set of traffic classifiers is associated with the classification index; each of the one or more sets of QoS parameters is associated with a respective QoS rule index of one or more QoS rule indexes; each traffic classifier in the set of traffic classifiers is associated with a QoS rule index of the one or more QoS rule indexes; The method further comprises: facilitating network access by the residential gateway according to the packet forwarding control protocol session.

Citation Information

Patent Citations

  • Message processing method, UP device and CP device

    CN113852588A

  • Priority channels for distributed broadband network gateway control packets

    US20220061129A1

  • Functions and Methods for Handling Pre-Configured Profiles for Sets of Detection and Enforcement Rules

    US20220353336A1