Implementing dynamic service flows in cable convergence network

Abstract

Embodiments of the present disclosure relate to implementing dynamic service flows in a cable convergence network. An access gateway function (AGF) device receives quality of service (QoS) information associated with a packet data unit (PDU) session of a cable modem device from an access and mobility management function (AMF) device of a core network. The AGF device determines QoS matching criterion information based on the QoS information. The AGF device sends a service flow creation message to a cable modem termination system (CMTS) associated with the cable modem device over an interface between the AGF device and the CMTS, such as a General Open Policy Service (COPS) interface, the service flow creation message including QoS matching criterion information. Sending a service flow creation message enables the CMTS to create a first service flow between the CMTS and the cable modem device, and enables the cable modem device to create a second service flow between the cable modem device and the CMTS.

Description

[0001] Cross Reference to Related Applications

[0002] This patent application claims priority to Indian Patent Application No. 202441053279, filed July 12, 2024, entitled “ENABLING DYNAMIC SERVICE FLOWS IN CABLE CONVERGENCE NETWORKS,” and U.S. Patent Application 18 / 816,675, filed August 27, 2024. The disclosures of which are considered part of the disclosure of this patent application and are hereby incorporated by reference into this patent application. BACKGROUND

[0003] A cable convergence network (CCN) refers to a modern cable network architecture that integrates multiple services, such as television, Internet, and voice, over a single, unified infrastructure. A CCN can be integrated with a core network, such as a Fifth Generation (5G) core network, to provide more capabilities to the CCN. SUMMARY

[0004] In some implementations, an access gateway function (AGF) device includes one or more memories and one or more processors to: receive, from an access and mobility management function (AMF) device of a core network, quality of service (QoS) information associated with a packet data unit (PDU) session of a cable modem device; determine, based on the QoS information, QoS matching criteria information; and send, to a cable modem termination system (CMTS) associated with the cable modem device, a service flow creation message including the QoS matching criteria information.

[0005] In some implementations, a non-transitory computer-readable medium stores a set of instructions, the set of instructions including one or more instructions that, when executed by one or more processors of an access gateway function (AGF) device, cause the AGF device to: receive, from a core network, quality of service (QoS) information associated with a packet data unit (PDU) session of a cable modem device; and send, to a cable modem termination system (CMTS) associated with the cable modem device, a service flow creation message including QoS matching criteria information associated with the QoS information.

[0006] In some implementations, a method includes obtaining, by an access gateway function (AGF) device, quality of service (QoS) information associated with a packet data unit (PDU) session of a cable modem device; and sending, by the AGF device, a service flow creation message to a cable modem termination system (CMTS) associated with the cable modem device and based on the QoS information. BRIEF DESCRIPTION OF DRAWINGS

[0007] Figures 1A-1D is a schematic diagram of an example implementation associated with implementing dynamic service flows in a CCN.

[0008] Figure 2 is a schematic diagram of an example environment in which systems and / or methods described herein can be implemented.

[0009] Figure 3 is a schematic diagram of example components of a device associated with implementing dynamic service flows in a CCN.

[0010] Figure 4 is a schematic diagram of example components of a device associated with implementing dynamic service flows in a CCN.

[0011] Figure 5 is a flow diagram of an example process associated with implementing dynamic service flows in a CCN. DETAILED DESCRIPTION

[0012] The following detailed description of example implementations refers to the accompanying drawings. The same reference numbers in different drawings can identify the same or similar elements.

[0013] In a cable convergence network (CCN), a cable modem is connected to a cable modem termination system (CMTS) through a wireline connection (e.g., information is transmitted through a physical element such as a fiber optic cable, a coaxial cable, a twisted pair cable, etc.). Typically, the wireline connection supports a default downstream service flow (e.g., supports transmission of data packets from the CMTS to the cable modem) and a default upstream service flow (e.g., supports transmission of data packets from the cable modem to the CMTS). Without any further configuration of the cable modem and the CMTS, all data packets transmitted between the cable modem and the CMTS are transmitted through these default service flows (e.g., through the wireline connection), and thus are provided with the same quality of service (QoS) treatment. This can not be optimal or best, such as when the CCN includes a core network (e.g., a 5G core network) that implements QoS differentiation for different types of traffic (e.g., voice traffic, video traffic, video conference traffic, or other types of traffic).

[0014] In some cases, the cable modem and the CMTS can be configured to support additional service flows (e.g., in addition to the default service flow) over the cable connection. For example, the cable modem and the CMTS can be configured to support pairs of service flows (e.g., up / down service flow pairs) that are capable of meeting different QoS criteria. However, these additional service flows are typically created at the initialization of the cable connection, and thus have statically defined QoS characteristics that can not be adjusted to provide preferred or optimal QoS treatment for particular data packet flows. Moreover, even when these additional service flows are not being used, computing resources (e.g., processing resources, memory resources, communication resources, and / or power resources, etc.) of the cable modem and the CMTS are consumed to maintain the service flows.

[0015] Some implementations described herein include a CCN that includes a cable modem device, a CMTS, and an access gateway function (AGF) device. The AGF device is connected to a core network (e.g., a 5G core network), and receives QoS information associated with a packet data unit (PDU) session of the cable modem device (e.g., indicating a QoS flow identifier (QFI) associated with a packet flow of the PDU session of the cable modem device, and optionally, indicating one or more QoS parameters associated with the packet flow). The AGF device determines QoS matching criteria information based on the QoS information (e.g., indicating a service flow identifier associated with the QFI, and optionally, indicating QoS policy information associated with the one or more QoS parameters), and sends a service flow creation message including the QoS matching criteria information to the CMTS. This enables the CMTS to create a first non-default service flow (e.g., a first non-default down service flow) between the CMTS and the cable modem device, and enables the cable modem device to create a second service flow (e.g., a second non-default up service flow) between the cable modem device and the CMTS.

[0016] Notably, each non-default service flow can be configured to provide preferred or optimal QoS treatment (e.g., based on the QoS policy information) for a data packet flow associated with the service flow identifier. In this way, the performance of the CCN is improved (e.g., by providing preferred or optimal transmission of data packet flows). Moreover, the non-default service flows can be dynamically created (and dynamically terminated, as further described herein), and thus computing resources (e.g., processing resources, memory resources, communication resources, and / or power resources, etc.) of the cable modem and the CMTS are not wasted to maintain unused, non-optimal, statically configured service flows.

[0017] Furthermore, the AGF device can be configured to connect to the CMTS via a Common Open Policy Services (COPS) interface (or a similar interface). The CMTS is natively configured to support the COPS interface (e.g., when communicating with Packet Cable Multimedia (PCMM) devices), thus requiring no additional configuration. Accordingly, the AGF device can provide service flow creation messages as COPS messages, which the CMTS can process (e.g., without further CMTS configuration) to enable the creation of non-default service flows. In this way, some implementations described herein enable dynamic service flows within the CCN without requiring any physical (e.g., hardware) changes to the devices and / or systems within the CCN.

[0018] Figures 1A-1D This is a schematic diagram of example implementation 100 associated with implementing dynamic service flows in a CCN. For example... Figures 1A-1D As shown, example implementation 100 includes a limited modem device, a CMTS, an AGF device, an Access and Mobility Management Function (AMF) device, and / or a Session Management Function (SMF) device. The following will combine... Figures 2-4 These devices are described in more detail. These devices can be associated with a CCN, where AMF devices and / or SMF devices can be included in the CCN's core network (e.g., a 5G network).

[0019] A cable modem device can be connected to a CMTS via a cable connection. The cable connection can include, for example, a cable network connection or other types of cable connections. The cable connection (and the cable modem device and the CMTS) can support various service flows. Service flows can be, for example, uplink service flows (e.g., supporting the transmission of data packets from the cable modem device to the CMTS), or downlink service flows (e.g., supporting the transmission of data packets from the CMTS to the cable modem device).

[0020] like Figure 1A As shown, and indicated by reference numeral 105, the AGF device can acquire QoS information. This QoS information can be associated with a PDU session of the cable modem device. For example, the QoS information can indicate the QFI associated with a packet stream of the PDU session of the cable modem device, and optionally, indicate one or more QoS parameters associated with that packet stream. The one or more QoS parameters can indicate, for example, bandwidth requirements, latency requirements, priority requirements, and / or similar requirements. In some implementations, the QoS information can be referred to as 5G QoS information (e.g., when the core network is a 5G core network and the PDU session is associated with a 5G core network).

[0021] In some implementations, the AGF device can obtain QoS information from the core network. For example, an AMF device (or an SMF device connected to an AMF device) can provide QoS information (such as association with the Router Gateway-Level Cable Access Characteristics (RG-LWAC) registration procedure) to the AGF device. Correspondingly, the AMF device can send QoS information to the AGF device through an interface of the core network (such as the N2 interface of the core network, defined by the 3rd Generation Partnership Project (3GPP)). In other words, the AGF device can receive QoS information from the core network (e.g., from the AMF device) through an interface of the core network.

[0022] As shown by reference numeral 110 in the attached figure, the AGF device can determine QoS matching criterion information. The QoS matching criterion information may indicate a service flow identifier associated with a QFI (e.g., indicated by QoS information), and optionally, QoS policy information associated with one or more QoS parameters (e.g., indicated by QoS information). The service flow identifier may include at least one of, for example, Internet Protocol (IP) Differential Service Code Point (DSCP) or Virtual Local Area Network (VLAN) Priority Code Point (PCP) (e.g., these code points would be included in data packets transmitted between the cable modem device and the CMTS). The QoS policy information may indicate, for example, the quality of service level that a data packet should receive when transmitting data packets between the cable modem device and the CMTS (e.g., when the data packet is associated with a service flow identifier).

[0023] AGF devices can determine QoS matching criteria information based on QoS information. For example, an AGF device can process QoS information to map QFI to a service flow identifier (or, alternatively, to map QFI to a 5G QoS identifier (5QI) and 5QI to a service flow identifier), and / or to map one or more QoS parameters to QoS policy information. In this way, an AGF device can maintain a mapping from QFI to service flow identifiers (e.g., associated with a service flow between a cable modem device and a CMT).

[0024] As shown by reference numeral 115 in the attached figure, the AGF device may (e.g., to the CMTS) send a service flow creation message. This service flow creation message may include QoS matching criteria information (or at least a portion of it). For example, the service flow creation message may indicate the creation of a first service flow (e.g., a downlink service flow) and a second service flow (e.g., an uplink service flow) between the cable modem device and the CMTS, wherein each service flow is associated with a service flow identifier and provides a quality of service level associated with QoS policy information.

[0025] In some implementations, the AGF device and the CMTS can connect via the COPS interface between the AGF device and the CMTS. Therefore, the AGF device can send service flow creation messages to the CMTS through the COPS interface. Accordingly, the service flow creation message can be a COPS message.

[0026] Alternatively, the AGF device and the CMTS can connect via other types of interfaces between the AGF device and the CMTS (e.g., both the AGF device and the CMTS are configured to support such interfaces). This interface can be, for example, a Representational State Transfer (REST) ​​interface, a Generic Control Plane (GCP) interface, a Simple Network Management Protocol (SNMP) interface, a Hypertext Transfer Protocol (HTTP) interface, an HTTP Secure (HTTPS) interface, a proprietary interface (e.g., an interface specifically configured to connect the AGF device and the CMTS), or a similar type of interface. Therefore, the AGF device can send service flow creation messages to the CMTS via a REST interface, GCP interface, SNMP interface, HTTP interface, HTTPS interface, proprietary interface, or a similar type of interface. Accordingly, the service flow creation message can be a REST message, GCP message, SNMP message, HTTP message, HTTPS message, proprietary message, or a similar type of message.

[0027] As shown by reference numeral 120 in the attached figure, the CMTS can send a service flow creation message (e.g., to a cable modem device). In some implementations, the CMTS and the cable modem device can connect via a first default service flow (e.g., a default downlink service flow) and a second default service flow (e.g., a default uplink service flow), so the CMTS can send the service flow creation message to the cable modem device via the first default service flow. Each default service flow in the default service flow can be associated with a cable network protocol (such as the Cable Data Service Interface Specification (DOCSIS) protocol or other cable connection protocols), so the CMTS can send the service flow creation message as a message associated with the cable network protocol (e.g., as a DOCSIS message).

[0028] like Figure 1BAs shown, and indicated by reference numeral 125, the CMTS can create (e.g., based on a service flow creation message received from an AGF device) a first non-default service flow (e.g., between the CMTS and the cable modem device). The first non-default service flow can support the transmission of data packets from the CMTS to the cable modem device (e.g., the first non-default service flow can be a non-default downlink service flow). The first non-default service flow can be associated with a service flow identifier and can provide a quality of service level associated with QoS policy information. In some implementations, the first non-default service can be associated with a cable network protocol (e.g., the first non-default service can be associated with the DOCSIS protocol).

[0029] As shown by reference numeral 130 in the attached figure, the cable modem device can create a second non-default service flow (e.g., between the cable modem device and the CMTS). This second non-default service flow can support the transmission of data packets from the cable modem device to the CMTS (e.g., the second non-default service flow could be a non-default uplink service flow). The second non-default service flow can be associated with a service flow identifier and can provide a quality of service level associated with QoS policy information. In some implementations, the second non-default service can be associated with a cable network protocol (e.g., the second non-default service can be associated with the DOCSIS protocol).

[0030] like Figure 1C As shown, and indicated by reference numeral 135, the AGF device can acquire additional QoS information. This additional QoS information can be associated with the PDU session of the cable modem device. For example, the additional QoS information may indicate the QFI associated with a packet flow of the PDU session of the cable modem device, and optionally, it may indicate one or more QoS parameters associated with that packet flow. In some implementations, the additional QoS information may indicate that any service flow associated with the QFI and / or one or more QoS parameters should be terminated. In some implementations, the additional QoS information may be referred to as additional 5G QoS information (e.g., when the core network is a 5G core network and the PDU session is associated with a 5G core network).

[0031] In some implementations, AGF devices can obtain additional QoS information from the core network (e.g., to match the information discussed in this article). Figure 1A (Similar to the manner described by reference numeral 105 in the attached figure). For example, an AMF device (or an SMF device via an AMF device) can provide additional QoS information to an AGF device through the core network interface. Accordingly, the AGF device can receive additional QoS information from the core network (e.g., from the AMF device) through the core network interface.

[0032] As shown by reference numeral 140 in the attached figure, the AGF device can determine additional QoS matching criteria information. Additional QoS matching criteria may indicate a service flow identifier associated with a QFI (e.g., indicated by other QoS information), and optionally, QoS policy information associated with one or more QoS parameters (e.g., indicated by other QoS information). In some implementations, additional QoS matching criteria may indicate that any service flow associated with the service flow identifier and / or QoS policy information should be terminated.

[0033] The AGF device can determine additional QoS matching criteria based on other QoS information. For example, the AGF device can process other QoS information to map QFI to a service flow identifier (or, alternatively, to map QFI to 5QI and 5QI to a service flow identifier), and / or to map one or more QoS parameters to QoS policy information. Additionally, the AGF device can cause other QoS matching criteria to indicate that any service flow associated with the service flow identifier and / or QoS policy information should be terminated (e.g., indicating that any service flow associated with QFI and / or one or more QoS parameters should be terminated based on other QoS information).

[0034] As shown by reference numeral 145 in the attached figure, the AGF device can (e.g., to the CMTS) send a service flow termination message. Service flow creation termination may include other QoS matching criteria information (or at least a portion of other QoS matching criteria information). For example, the service flow termination message may instruct a first service flow (e.g., a downlink service flow) and a second service flow (e.g., an uplink service flow) to terminate between the cable modem device and the CMTS, wherein each service flow is associated with a service flow identifier and a quality of service level associated with QoS policy information. In some implementations, the AGF device may send the service flow termination message to the CMTS through the interface between the AGF device and the CMTS. Accordingly, the service flow termination message may be a COPS message, a REST message, a GCP message, an SNMP message, an HTTP message, an HTTPS message, or a proprietary message.

[0035] As shown by reference numeral 150 in the attached figure, the CMTS can send a service flow termination message (e.g., to a cable modem device). In some implementations, the CMTS can send a service flow creation message to the cable modem device via a first default service flow (e.g., a default downlink service flow) or a first non-default service flow (e.g., a non-default downlink service flow). The CMTS can send the service flow termination message as a message associated with the cable network protocol (e.g., as a DOCSIS message).

[0036] like Figure 1DAs shown, and indicated by reference numeral 155, the CMTS can terminate (e.g., based on a service flow termination message received from the AGF device) a first non-default service flow (e.g., between the CMTS and the cable modem device). For example, the CMTS can identify the first non-default service flow based on a service flow identifier and QoS policy information indicated by other QoS matching criteria information in the service flow termination message, and can terminate the first non-default service flow by indicating, based on other QoS matching criteria information in the service flow termination message, that any service flow associated with that service flow identifier and / or QoS policy information should be terminated.

[0037] As shown by reference numeral 160 in the attached figure, the cable modem device can terminate (e.g., based on a service flow termination message received from the CMTS) a second non-default service flow (e.g., between the cable modem device and the CMTS). For example, the cable modem device can identify the second non-default service flow based on a service flow identifier and QoS policy information indicated by other QoS matching criteria information in the service flow termination message, and can terminate the second non-default service flow by indicating, based on other QoS matching criteria information in the service flow termination message, that any service flow associated with that service flow identifier and / or QoS policy information should be terminated.

[0038] As indicated above, Figures 1A-1D Provided as an example only. Other examples may be related to... Figures 1A-1D The content described is different. Figures 1A-1D The number and arrangement of devices shown are provided as an example only. In practice, different arrangements may exist. Figures 1A-1D The equipment shown may be more, less, different, or arranged differently. Furthermore, Figures 1A-1D The two or more devices shown can be implemented within a single device, or Figures 1A-1D The single device shown can be implemented as multiple distributed devices. Additionally or alternatively, Figures 1A-1D The set of devices shown (e.g., one or more devices) can perform the functions provided by Figure 2 The other set of devices shown performs one or more functions.

[0039] Figure 2 This is a schematic diagram of example environment 200, in which the systems and / or methods described herein can be implemented. For example... Figures 1A-1D As shown, example environment 200 may include cable modem device 205, CMTS 210, AGF 215, core network 220, and data network 225. The devices and / or networks in example environment 200 can be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0040] Cable modem device 205 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information (such as the information described herein). Cable modem device 205 may be, may be similar to, or may include, the elements described herein. Figures 1A-1D The described cable modem device. Cable modem device 205 may include a cable modem or similar device. In some implementations, cable modem device 205 may include a residential gateway (e.g., a 5G residential gateway (5G-RG), a 5G cable residential gateway (5G-CRG), or other types of residential gateways), a client equipment (CPE), a user equipment (UE), a network device (e.g., a label switching router (LSR), a label edge router (LER), an ingress router, an egress router, a provider router, a virtual router, a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, a proxy server, a cloud server, a data center server, a load balancer, etc.) or similar devices. In some implementations, cable modem device 205 may (e.g., via CMTS210 and AGF 215) receive network traffic from and / or provide network traffic to core network 220. In some implementations, cable modem device 205 may be connected to CMTS210 and / or AGF 215 via a cable connection.

[0041] CMTS210 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information (such as the information described herein). CMTS210 may be, may be similar to, or may include the information described herein. Figure 2 The CMTS 210 is described. CMTS 210 can facilitate communication between cable modem device 205 and core network 220. CMTS 210 may include one or more stream modulators (e.g., one or more of uplink and downlink modulators) and / or one or more stream demodulators (e.g., one or more of uplink and downlink demodulators).

[0042] AGF 215 may include one or more devices located between the cable access infrastructure (e.g., including cable modem devices 205 and CMTS 210) and the core network 220, which may support residential gateways (e.g., cable modem devices 205) and cable-only residential gateways capable of supporting 5G Non-Access Stratum (NAS) signaling. AGF 215 is connected to one or more functional elements (e.g., AMF 230 and / or SMF 235) of the core network 220 via an N2 interface.

[0043] In some implementations, core network 220 may include example functional architectures in which the systems and / or methods described herein may be implemented. For example, core network 220 may include example architectures of 5G next-generation (NG) core networks included in 5G wireless telecommunications systems, and may include physical elements, virtual elements, or a combination of physical and virtual elements. Although Figure 2 The example architecture of the core network 220 shown can be an example of a service-based architecture, but in some implementations, the core network 220 can be implemented as a reference point architecture.

[0044] like Figure 2 As shown, the core network 220 may include multiple functional elements. These functional elements may include, for example, AMF 230 and SMF 235, as well as other functional elements. These functional elements can be communicatively connected via message bus 240. Figure 2 Each of the functional elements shown is implemented on one or more devices associated with a wireless telecommunications system. In some implementations, one or more functional elements may be implemented on physical devices (such as access points, base stations, gateways, etc.). In some implementations, one or more functional elements may be implemented on computing devices in a cloud computing environment.

[0045] AMF 230 includes one or more devices that serve as endpoints for NAS signaling, mobility management, etc. SMF 235 includes one or more devices that support the establishment, modification, and release of communication sessions in a wireless telecommunications system.

[0046] Message bus 240 represents a communication structure for communication between functional elements. In other words, message bus 240 can allow communication between two or more functional elements. Message bus 240 can be a logical and / or physical communication structure for communication between functional elements. Accordingly, message bus 240 can allow communication between two or more functional elements, whether logical (e.g., using one or more application programming interfaces (APIs) and / or physical (e.g., using one or more wired and / or wireless connections).

[0047] Data network 225 includes one or more wired and / or wireless data networks. For example, data network 225 may include IP Multimedia Subsystem (IMS), Public Land Mobile Network (PLMN), Local Area Network (LAN), Wide Area Network (WAN), Metropolitan Area Network (MAN), Private Network (such as corporate intranet), Ad Hoc Network, Internet, Fiber-based Network, Cloud Computing Network, Third-Party Service Network, Carrier Service Network, and / or combinations of these or other types of networks.

[0048] Figure 2The number and arrangement of devices and networks shown are provided as examples only. In practice, different arrangements may exist. Figure 2 The equipment and / or networks shown may be more numerous, fewer, different, or arranged differently compared to other options. Furthermore, Figure 2 The two or more devices shown can be implemented within a single device, or Figure 3 The single device shown can be implemented as multiple distributed devices. Additionally or alternatively, a group of devices (e.g., one or more devices) in example environment 200 can perform one or more functions performed by another group of devices in example environment 200.

[0049] Figure 3 This is a schematic diagram of example components of device 300 associated with implementing dynamic service flows in a CCN. Device 300 may correspond to cable modem device 205, CMTS 210, AGF 215, AMF 230, and / or SMF 235. In some implementations, cable modem device 205, CMTS 210, AGF 215, AMF 230, and / or SMF 235 may include one or more devices 300 and / or one or more components of device 300. Figure 3 As shown, device 300 may include bus 310, processor 320, memory 330, input component 340, output component 350 and / or communication component 360.

[0050] Bus 310 may include one or more components that enable wired and / or wireless communication between components of device 300. Bus 310 may (e.g., via operative coupling, communicative coupling, electronic coupling, and / or electrical coupling) Figure 3 Two or more components are coupled together. For example, bus 310 may include electrical connections (e.g., wires, traces, and / or leads) and / or wireless buses. Processor 320 may include a central processing unit, graphics processing unit, microprocessor, controller, microcontroller, digital signal processor, field-programmable gate array, application-specific integrated circuit, and / or other types of processing components. Processor 320 may be implemented in hardware, firmware, or a combination of hardware and software. In some implementations, processor 320 may include one or more processors capable of being programmed to perform one or more operations or processes described elsewhere herein.

[0051] Memory 330 may include volatile memory and / or non-volatile memory. For example, memory 330 may include random access memory (RAM), read-only memory (ROM), hard disk drive, and / or other types of memory (e.g., flash memory, magnetic memory, and / or optical memory). Memory 330 may include internal memory (e.g., RAM, ROM, or hard disk drive) and / or removable memory (e.g., removable via a universal serial bus connection). Memory 330 may be a non-transient computer-readable medium. Memory 330 may store information related to the operation of device 300, one or more instructions, and / or software (e.g., one or more software applications). In some implementations, memory 330 may include one or more memories coupled (e.g., communicatively coupled) to one or more processors (e.g., processor 320) (such as via bus 310). The communicative coupling between processor 320 and memory 330 enables processor 320 to read and / or process information stored in memory 330 and / or to store information in memory 330.

[0052] Input component 340 enables device 300 to receive input, such as user input and / or sensed input. For example, input component 340 may include a touchscreen, keyboard, keypad, mouse, button, microphone, switch, sensor, GPS sensor, GNSS sensor, accelerometer, gyroscope, and / or actuator. Output component 350 enables device 300 to provide output (such as through a display, speaker, and / or light-emitting diode). Communication component 360 enables device 300 to communicate with other devices via wired and / or wireless connections. For example, communication component 360 may include a receiver, transmitter, transceiver, modem, network interface card, and / or antenna.

[0053] Device 300 can perform one or more operations or procedures described herein. For example, a non-transitory computer-readable medium (e.g., memory 330) can store a set of instructions (e.g., one or more instructions or code) for execution by processor 320. Processor 320 can execute the set of instructions to perform one or more operations or procedures described herein. In some implementations, one or more processors 320 executing the set of instructions causes one or more processors 320 and / or device 300 to perform one or more operations or procedures described herein. In some implementations, hardwired circuitry may be used in place of or in conjunction with instructions to perform one or more operations or procedures described herein. Additionally or alternatively, processor 320 may be configured to perform one or more operations or procedures described herein. Therefore, the implementations described herein are not limited to any particular combination of hardware circuitry and software.

[0054] Figure 3 The number and arrangement of components shown are provided as an example only. Device 300 may include components with... Figure 4 The components shown may be more numerous, fewer, different, or arranged differently. Additionally or alternatively, one set of components of device 300 (e.g., one or more components) may perform one or more functions performed by another set of components of device 300.

[0055] Figure 4 This is a schematic diagram of example components of device 400 associated with implementing dynamic service flows in a CCN. Device 400 may correspond to cable modem device 205, CMTS 210, AGF 215, AMF 230, and / or SMF 235. In some implementations, cable modem device 205, CMTS 210, AGF 215, AMF 230, and / or SMF 235 may include one or more devices 400 and / or one or more components of device 400. Figure 4 As shown, device 400 may include one or more input components 410-1 to 410-B (B≥1) (hereinafter collectively referred to as input components 410, individually referred to as input components 410), switching component 420, one or more output components 430-1 to 430-C (C≥1) (hereinafter collectively referred to as output components 430, individually referred to as output components 430), and controller 440.

[0056] Input component 410 may be one or more attachment points of a physical link and may be one or more entry points for incoming traffic (such as packets). Input component 410 may process incoming traffic (e.g., by performing data link layer encapsulation or decapsulation). In some implementations, input component 410 may send and / or receive packets. In some implementations, input component 410 may include an input line card that includes one or more packet processing components (e.g., in the form of integrated circuits), such as one or more interface cards (IFCs), packet forwarding components, line card controller components, input ports, processors, memory, and / or input queues. In some implementations, device 400 may include one or more input components 410.

[0057] Switching component 420 interconnects input component 410 with output component 430. In some implementations, switching component 420 may be implemented via one or more crossbar switches, via a bus, and / or utilizing shared memory. Shared memory may act as a temporary buffer to store packets from input component 410, which will eventually be scheduled for delivery to output component 430. In some implementations, switching component 420 enables input component 410, output component 430, and / or controller 440 to communicate with each other.

[0058] Output component 430 can store packets and schedule packets for transmission over the output physical link. Output component 430 can support data link layer encapsulation or decapsulation, and / or various higher-level protocols. In some implementations, output component 430 can send and / or receive packets. In some implementations, output component 430 may include an output line card comprising one or more packet processing components (e.g., in the form of integrated circuits), such as one or more IFCs, packet forwarding components, line card controller components, output ports, processors, memory, and / or output queues. In some implementations, device 400 may include one or more output components 430. In some implementations, input component 410 and output component 430 may be implemented from the same set of components (e.g., the input / output component may be a combination of input component 410 and output component 430).

[0059] Controller 440 includes processors of the following forms: central processing unit (CPU), graphics processing unit (GPU), accelerated processing unit (APU), microprocessor, microcontroller, digital signal processor (DSP), field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), or other types of processing components. The processor may be implemented in hardware, firmware, or a combination of hardware and software. In some embodiments, controller 440 may include one or more processors that can be programmed to perform functions.

[0060] In some implementations, controller 440 may include RAM, ROM and / or other types of dynamic or static storage devices (e.g., flash memory, magnetic memory, optical memory, etc.) that store information and / or instructions for use by controller 440.

[0061] In some implementations, controller 440 can communicate with other devices, networks, and / or systems connected to device 400 to exchange information about the network topology. Controller 440 can create routing tables based on the network topology information, create forwarding tables based on the routing tables, and forward the forwarding tables to input component 410 and / or output component 430. Input component 410 and / or output component 430 can use the forwarding tables to perform route looks for incoming and / or outgoing packets.

[0062] Controller 440 may perform one or more of the processes described herein. Controller 440 may perform these processes in response to executing software instructions stored on a non-transitory computer-readable medium. Computer-readable medium is defined herein as a non-transitory storage device. Storage devices include storage space within a single physical storage device or storage space distributed across multiple physical storage devices.

[0063] Software instructions can be read from another computer-readable medium or from another device via a communication interface into the memory and / or storage components associated with controller 440. When executed, the software instructions stored in the memory and / or storage components associated with controller 440 can cause controller 440 to perform one or more processes described herein. Additionally or alternatively, hardwired circuitry may be used in place of or in combination with the software instructions to perform one or more processes described herein. Therefore, the implementation described herein is not limited to any particular combination of hardware circuitry and software.

[0064] Figure 4 The number and arrangement of components shown are provided as examples only. In practice, device 400 may include components with... Figure 5 The components shown may be more, fewer, different, or arranged differently compared to other components. Additionally or alternatively, one set of components (e.g., one or more components) of device 400 may perform one or more functions performed by another set of components of device 400.

[0065] Figure 5 This is a flowchart of example process 500 associated with implementing dynamic service flows in a CCN. In some implementations, Figure 5 One or more process blocks in the process are executed by an AGF device (e.g., an AGF 215). In some implementations, Figure 5 One or more process blocks are executed by another device or group of devices that are separate from or include the client device, such as a cable modem device (e.g., cable modem device 205), a CMTS (e.g., CMTS 210), an AMF device (e.g., AMF 230), and / or an SMF device (e.g., SMF 235). Alternatively or additionally, Figure 5 One or more process blocks can be executed by one or more components of device 300, such as processor 320, memory 330, input component 340, output component 350, and / or communication component 360. Additionally or alternatively, Figure 5 One or more process blocks in the device 400 may be executed by one or more components of the device 400, such as input component 410, switching component 420, output component 430 and / or controller 440.

[0066] like Figure 5 As shown, process 500 may include receiving QoS information associated with a PDU session of a cable modem device (block 510). For example, the AGF device may receive QoS information associated with a PDU session of a cable modem device from the core network, as described above.

[0067] like Figure 5 As further shown, process 500 may include determining QoS matching criteria information (block 520). For example, the AGF device may determine QoS matching criteria information based on QoS information, as described above.

[0068] like Figure 5 As further shown, process 500 may include sending a service flow creation message that includes QoS matching criteria information (block 530). For example, the AGF device may send a service flow creation message including QoS matching criteria information to a CMTS associated with a cable modem device, as described above.

[0069] Process 500 may include other implementations, such as any single implementation or any combination of implementations described below, and / or in combination with one or more other processes described elsewhere in this document.

[0070] In the first implementation, sending a service flow creation message enables the CMTS to create a first service flow between the CMTS and the cable modem device, and enables the cable modem device to create a second service flow between the cable modem and the CMTS.

[0071] In the second implementation, either alone or in combination with the first implementation, the QoS information indicates the QFI associated with the packet flow of the PDU session and one or more QoS parameters associated with the packet flow, and the QoS matching criteria information indicates the service flow identifier associated with the QFI and the QoS policy information associated with one or more QoS parameters.

[0072] In the third implementation, either alone or in combination with one or more of the first and second implementations, the service flow identifier includes at least one of IP DSCP or VLAN PCP.

[0073] In the fourth implementation, either alone or in combination with one or more of the first through third implementations, the service flow creation message is one of the following: COPS message, REST message, GCP message, SNMP message, HTTP message, HTTPS message, or proprietary message.

[0074] In the fifth implementation, either alone or in combination with one or more of the first to fourth implementations, the AGF device sends a service flow creation message through an interface between the AGF device and the CMTS, wherein the interface is one of the following: a COPS interface, a REST interface, a GCP interface, an SNMP interface, an HTTP interface, an HTTPS interface, or a proprietary interface.

[0075] In the sixth implementation, either alone or in combination with one or more of the first to fifth implementations, process 500 includes: receiving additional QoS information associated with a PDU session of a cable modem device from an AMF device in the core network; determining additional QoS matching criteria information based on the additional QoS information; and sending a service flow termination message to the CMTS, the service flow termination message including the additional QoS matching criteria information.

[0076] In the seventh implementation, a service flow termination message is sent, either alone or in combination with one or more of the first to sixth implementations, enabling the CMTS to terminate the first service flow between the CMTS and the cable modem device, and enabling the cable modem device to terminate the second service flow between the cable modem device and the CMTS.

[0077] although ​ An example block of process 500 is shown, but in some implementations, process 500 may include... ​ The blocks shown may be more, fewer, different, or arranged differently compared to other blocks. Alternatively or concurrently, two or more blocks in process 500 may be executed in parallel.

[0078] The foregoing disclosure provides explanations and descriptions, but is not intended to be exhaustive, nor is it intended to limit the implementation to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, as well as from practical implementation.

[0079] As used herein, traffic or content may include a set of packets. A packet can refer to a communication structure used to convey information, such as a PDU, a Service Data Unit (SDU), a network packet, a datagram, a segment, a message, a block, a frame (e.g., an Ethernet frame), a portion of any of the above, and / or other types of formatted or unformatted data units that can be transmitted over a network.

[0080] As used herein, the term "component" should be broadly understood to mean hardware, firmware, or a combination of hardware and software. It is evident that the systems and / or methods described herein can be implemented in various forms of hardware, firmware, and / or hardware and software combinations. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit these implementations. Therefore, the operation and behavior of the systems and / or methods described herein do not refer to any specific software code—it should be understood that software and hardware can be used to implement these systems and / or methods based on the description herein.

[0081] Even if a specific combination of features is declared in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various implementations. In fact, many of these features can be combined in ways not explicitly stated in the claims and / or disclosed in the specification. Although each dependent claim listed below may be directly dependent on only one claim, the disclosure of various implementations includes a combination of each dependent claim with all other claims in the claim set. As used herein, the phrase “at least one” in the list of items refers to any combination of these items, including a single item. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination of multiple identical items.

[0082] When the term "processor" or "one or more processors" (or other device or component, such as "controller" or "one or more controllers") is described or stated (within a claim or across multiple claims) as performing or configured to perform multiple operations, this language is intended to broadly encompass a wide range of processor architectures and environments. For example, unless explicitly stated otherwise (e.g., by using "first processor" and "second processor" or other language used to distinguish processors in the claims), this language is intended to cover a single processor performing or configured to perform all operations, a group of processors jointly performing or configured to perform all operations, a first processor performing or configured to perform a first operation and a second processor performing or configured to perform a second operation, or any combination of processors performing or configured to perform these operations. For example, when a claim takes the form "one or more processors: performing X; performing Y; and performing Z," the claim should be interpreted as "one or more processors performing X; one or more (possibly different) processors performing Y; and one or more (possibly different) processors performing Z."

[0083] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the article “a” (“a” and “an”) is intended to include one or more items and may be used interchangeably with “one or more”. Furthermore, as used herein, the article “the” is intended to include one or more items associated with the article “the” and may be used interchangeably with “the one or more”. Furthermore, as used herein, the term “set” is intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and may be used interchangeably with “one or more”. If referring to only one item, the phrase “only one” or a similar expression is used. Furthermore, as used herein, the terms “having,” “having,” “including,” etc., are intended to indicate open-ended terms. Furthermore, unless explicitly stated otherwise, the phrase “based on” is intended to mean “at least partially based on.” Furthermore, as used herein, the term “or” is intended to be inclusive in a series of uses and may be used interchangeably with “and / or” unless explicitly stated otherwise (e.g., in combination with “any” or “only one”).

Claims

1. An Access Gateway (AGF) device, comprising: One or more memory units; as well as One or more processors, used to: Receive Quality of Service (QoS) information associated with Packet Data Unit (PDU) sessions of cable modem devices from the Access and Mobility Management Function (AMF) equipment in the core network; Based on the QoS information, determine the QoS matching standard information; as well as A service flow creation message is sent to the cable modem terminal system (CMTS) associated with the cable modem device, the service flow creation message including the QoS matching standard information.

2. The AGF device according to claim 1, wherein sending the service flow creation message causes: The CMTS is capable of creating a first service flow between the CMTS and the cable modem device; and The cable modem device is capable of creating a second service flow between the cable modem device and the CMTS.

3. The AGF device according to claim 1, wherein: The QoS information indicates the QoS flow identifier (QFI) associated with the packet flow of the PDU session and one or more QoS parameters associated with the packet flow; as well as The QoS matching criteria information indicates the service flow identifier associated with the QFI and the QoS policy information associated with the one or more QoS parameters.

4. The AGF device according to claim 3, wherein the service flow identifier includes at least one of the following: Internet Protocol IP Differential Service Code Point (DSCP), or VLAN Priority Code Point (PCP).

5. The AGF device according to claim 1, wherein the service flow creation message is one of the following: General Open Policy Service (COPS) messages Representational state transition REST messages, General Control Plane (GCP) messages, Simple Network Management Protocol (SNMP) messages, Hypertext Transfer Protocol (HTTP) messages, HTTP secure HTTPS messages, or Exclusive message.

6. The AGF device of claim 1, wherein the AGF device sends the service flow creation message via an interface between the AGF device and the CMTS, wherein the interface is one of the following: General Open Policy Service (COPS) interface, Representational State Transition REST Interface Universal Control Plane (GCP) interface Simple Network Management Protocol (SNMP) interface, Hypertext Transfer Protocol (HTTP) interface HTTP secure HTTPS interface, or Proprietary interface.

7. The AGF device of claim 1, wherein the one or more processors are further configured to: Receive additional QoS information associated with the PDU session of the cable modem device from the AMF device; Based on the aforementioned other QoS information, other QoS matching criteria information is determined; and Send a service flow termination message to the CMTS, the service flow termination message including the other QoS matching standard information.

8. The AGF device of claim 7, wherein sending the service flow termination message causes: The CMTS can terminate the first service flow between the CMTS and the cable modem device; and The cable modem device is capable of terminating the second service flow between the cable modem device and the CMTS.

9. A non-transient computer-readable medium storing an instruction set, the instruction set comprising: One or more instructions, which, when executed by one or more processors of an Access Gateway Function (AGF) device, cause the AGF device to: Receive Quality of Service (QoS) information associated with Packet Data Unit (PDU) sessions of cable modems from the core network; and A service flow creation message is sent to the cable modem terminal system (CMTS) associated with the cable modem device. The service flow creation message includes QoS matching standard information associated with the QoS information.

10. The non-transient computer-readable medium of claim 9, wherein sending the service flow creation message causes: The CMTS is capable of creating a first service flow between the CMTS and the cable modem device; and The cable modem device is capable of creating a second service flow between the cable modem device and the CMTS.

11. The non-transient computer-readable medium according to claim 9, wherein: The QoS information indicates the QoS flow identifier (QFI) associated with the packet flow of the PDU session; as well as The QoS matching criteria information indicates the service flow identifier associated with the QFI.

12. The non-transient computer-readable medium of claim 11, wherein the service flow identifier comprises at least one of the following: Internet Protocol IP Differential Service Code Point (DSCP), or VLAN Priority Code Point (PCP).

13. The non-transient computer-readable medium according to claim 9, wherein, The service flow creation message is one of the following: General Open Policy Service (COPS) messages Representational state transition REST messages, General Control Plane (GCP) messages, Simple Network Management Protocol (SNMP) messages, Hypertext Transfer Protocol (HTTP) messages, HTTP secure HTTPS messages, or Exclusive message.

14. The non-transient computer-readable medium of claim 9, wherein the AGF device sends the service flow creation message via an interface between the AGF device and the CMTS, wherein the interface is one of the following: General Open Policy Service (COPS) interface, Representational State Transition REST Interface Universal Control Plane (GCP) interface Simple Network Management Protocol (SNMP) interface, Hypertext Transfer Protocol (HTTP) interface HTTP secure HTTPS interface, or Proprietary interface.

15. The non-transient computer-readable medium of claim 9, wherein one or more instructions further cause the AGF to: Receive additional QoS information associated with the PDU session of the cable modem device from the core network; and Send a service flow termination message to the CMTS, the service flow termination message including other QoS matching criteria information associated with the other QoS information.

16. The non-transient computer-readable medium of claim 15, wherein sending the service flow termination message causes: The CMTS can terminate the first service flow between the CMTS and the cable modem device; and The cable modem device is capable of terminating the second service flow between the cable modem device and the CMTS.

17. A method comprising: The Access Gateway (AGF) device obtains Quality of Service (QoS) information associated with the Packet Data Unit (PDU) session of the cable modem device. as well as The AGF device sends a service flow creation message to the cable modem terminal system (CMTS) associated with the cable modem device, based on the QoS information.

18. The method of claim 17, wherein sending the service flow creation message causes: The CMTS is capable of creating a first service flow between the CMTS and the cable modem device; and The cable modem device is capable of creating a second service flow between the cable modem device and the CMTS.

19. The method of claim 17, wherein the service flow creation message is one of the following: General Open Policy Service (COPS) messages Representational state transition REST messages, General Control Plane (GCP) messages, Simple Network Management Protocol (SNMP) messages, Hypertext Transfer Protocol (HTTP) messages, HTTP secure HTTPS messages, or Exclusive message.

20. The method of claim 17, wherein the AGF device sends the service flow creation message via an interface between the AGF device and the CMTS, wherein the interface is one of the following: General Open Policy Service (COPS) interface, Representational State Transition REST Interface Universal Control Plane (GCP) interface Simple Network Management Protocol (SNMP) interface, Hypertext Transfer Protocol (HTTP) interface HTTP secure HTTPS interface, or Proprietary interface.

Images