WO2025013058A1

WO2025013058A1 - Method and system for dynamic identification and deletion of stale guaranteed bit rate (gbr) flows

Info

Publication number: WO2025013058A1
Application number: PCT/IN2024/051125
Authority: WO
Inventors: Mukesh Singh; Vipin Bhosale; Aayush Bhatnagar; Shashi SHEKHAR; Bhupinder Singh; Manohar NADIMINTI; Akash Pandey; Kalpak CHANDEKAR; Harshit Kumar VERMA; Birendra Singh Bisht; Harbinder Pal Singh; Pravesh Aggarwal; Priyanka Singh; Rohit Soren; Bidhu Sahu
Original assignee: Jio Platforms Ltd
Current assignee: Jio Platforms Ltd
Priority date: 2023-07-12
Filing date: 2024-07-09
Publication date: 2025-01-16
Anticipated expiration: 2026-01-12

Abstract

The present disclosure relates to a method and a system for dynamic identification and deletion of stale guaranteed bit rate flows. The method comprising checking, by a Session Management Function (SMF) [108], a usage report received from a User Plane Function (UPF) [128] corresponding to one or more GBR flows in the network. Further, the method encompassing identifying, by the SMF [108], a session as a stale session if a usage in the usage report corresponding to an Audio/Video call in the one or more GBR flows is indicated as zero. Furthermore, the method comprises deleting, by the SMF [108], the identified stale session by sending a set of instructions to at least one network component of a plurality of network components to release one or more system resources occupied by the stale session.

Description

METHOD AND SYSTEM FOR DYNAMIC IDENTIFICATION AND DELETION OF STALE GUARANTEED BIT RATE

(GBR) FLOWS

FIELD OF INVENTION

[0001] The present disclosure relates generally to the field of wireless communication systems. In particular, the present disclosure relates to dedicated or Guaranteed Bit Rate (GBR) Quality of Service (QoS) flow sessions in a core network. More particularly, the present disclosure relates to method and system for dynamic identification and deletion of stale dedicated or GBR flows in a core network.

BACKGROUND

[0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.

[0004] In the existing technology, there is no standard mechanism with which the User Plane Function (UPF) can report the presence of stale dedicated or Guaranteed Bit Rate (GBR) Quality of Service (QoS) flow sessions. This lack of reporting capabilities makes it difficult for the core network to efficiently manage its resources. Stale flows resulting from inactive or lost messages can lead to the unnecessary occupation of system resources, such as memory and CPU. This can reduce the overall efficiency of the network and restrict its capacity. The previous systems may lack automated mechanisms to identify and delete stale dedicated/GBR QoS flows. This can lead to manual intervention being necessary to clean up these resources, making the process more timeconsuming and potentially error-prone. Without an efficient way of identifying and removing stale flows, system capacity may not be optimized. These stale flows occupy resources that could otherwise be utilized for active and necessary processes.

[0005] Thus, there exists an imperative need in the art to provide a method and system for dynamic identification and deletion of stale dedicated bearer resource flows. The proposed invention addresses these problems by providing an innovative method for the Session Management Function (SMF) to identify and delete stale dedicated/GBR QoS flows using usage reports from the UPF, thus improving resource utilization and system capacity optimization.

OBJECTS OF THE INVENTION

[0006] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.

[0007] It is an object of the present disclosure to provide a method and system for dynamic identification and deletion of stale dedicated bearer resource flows in a core network.

[0008] It is another object of the present disclosure to provide a method and system for dynamic identification and deletion of stale dedicated bearer resource flows that aims to identify stale dedicated or GBR Quality of Service (QoS) flows in the core network. These are sessions that have become inactive or stale due to the loss of certain messages or other unforeseen reasons.

[0009] It is yet another object of the present disclosure to provide a method and system for dynamic identification and deletion of stale GBR bearer resource flows in a core network that deletes stale sessions from the system. This process helps in freeing up the resources that were being occupied by the stale flows. [0010] It is yet another object of the present disclosure to provide a method and system for dynamic identification and deletion of stale GBR bearer resource flows in a core network that seeks to free up system resources such as memory and CPU. This improves the overall efficiency of the system and makes better use of available resources.

[0011] It is yet another object of the present disclosure to provide a method and for dynamic identification and deletion of stale GBR bearer resource flows in a core network that improves system capacity by freeing up occupied resources. By eliminating unnecessary occupancy from stale sessions, more system resources are made available for active and necessary operations.

[0012] It is yet another object of the present disclosure to provide a method and system for dynamic identification and deletion of stale GBR bearer resource flows in a core network that improve system capacity by freeing up occupied resources. By eliminating unnecessary occupancy from stale sessions, more system resources are made available for active and necessary operations.

SUMMARY

[0013] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.

[0014] According to an aspect of the present disclosure, a method for dynamic identification and deletion of stale GBR flows in a core network is disclosed. The method comprising checking, by a Session Management Function (SMF), a usage report received from a User Plane Function (UPF) corresponding to one or more GBR flows in the network. Further, the method encompassing identifying, by the SMF, a session as a stale session if a usage in the usage report corresponding to an Audio/Video call in the one or more GBR flows is indicated as zero. Furthermore, the method comprises deleting, by the SMF, the identified stale session by sending a set of instructions to at least one network component of a plurality of network components to release one or more system resources occupied by the stale session.

[0015] In an aspect, checking of the usage report received from the UPF is performed periodically.

[0016] In an aspect, the periodic checking is based on a predetermined time period. [0017] In an aspect, the method further comprises releasing system resources occupied by the identified stale session.

[0018] In an aspect, the usage report comprises any or a combination of information on resource utilization by the one or more GBR flows in the core network, comprising data transmitted over a specified period, duration of calls, and type of resources used.

[0019] In an aspect, the SMF performs the periodic check at regular intervals, wherein the intervals are adjustable based on network traffic and system resources.

[0020] In an aspect, the plurality of network components comprises at least one of the User Plane Function (UPF), a Data Network (DN), an Access and Mobility Management Function (AMF), and a Network Repository Function (NRF).

[0021] According to another aspect of the present disclosure, a system for dynamic identification and deletion of stale GBR flows in a core network is disclosed. The system comprises a Session Management Function (SMF), configured to check a usage report received from a User Plane Function (UPF) corresponding to one or more different GBR flows in the network. Further, the SMF is configured to identify a session as a stale session if the usage report corresponding to an Audio/Video call in the one or more GBR flows is indicated as zero. Furthermore, the SMF is configured to delete the identified stale session by sending a set of instructions to at least one network component of a plurality of network components to release one or more system resources occupied by the stale session.

[0022] According to yet another aspect of the present disclosure, a non-transitory computer readable storage medium storing instruction for dynamic identification and deletion of stale dedicated GBR flows in a core network is disclosed. The instructions include executable code which, when executed by one or more units of a system, causes: a Session Management Function (SMF) to check a usage report received from a User Plane Function (UPF) corresponding to one or more GBR flows in the network; the SMF to identify a session as a stale session if a usage in the usage report corresponding to an Audio/Video call in the one or more GBR flows is indicated as zero; the SMF to delete the identified stale session by sending a set of instructions to at least one network component of a plurality of network components to release one or more system resources occupied by the stale session. [0023] According to yet another aspect of the present disclosure may relate to a user equipment (UE). The UE comprising: a transmitter unit configured to transmit a request to a system for dynamic identification and deletion of stale GBR bearer resource flows; a receiver unit, configured to receive from the system a response to the request, wherein the response comprises an indication of identification and deletion of stale GBR bearer resource flows, and wherein the response is generated by the system based on: checking, by a Session Management Function (SMF), a usage report received from a User Plane Function (UPF) corresponding to one or more GBR flows in the network; identifying, by the SMF, a session as a stale session if a usage in the usage report corresponding to an Audio/Video call in the one or more GBR flows is indicated as zero; deleting, by the SMF, the identified stale session by sending a set of instructions to at least one network component of a plurality of network components to release one or more system resources occupied by the stale session.

DESCRIPTION OF THE DRAWINGS

[0024] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0025] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.

[0026] FIG. 2 illustrates a system for dynamic identification and deletion of stale GBR flows in a core network, in accordance with exemplary embodiments of the present disclosure.

[0027] FIG. 3 illustrate an exemplary sequence flow diagram for dynamic identification and deletion of stale GBR flows in a core network, in accordance with exemplary embodiments of the present disclosure. [0028] FIG. 4 illustrate an exemplary method flow diagram for dynamic identification and deletion of stale GBR flows in a core network, in accordance with exemplary embodiments of the present disclosure.

[0029] FIG. 5 illustrates an exemplary block diagram of a computing device upon which an embodiment of the present disclosure may be implemented.

[0030] The foregoing shall be more apparent from the following more detailed description of the disclosure.

DETAILED DESCRIPTION

[0031] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.

[0032] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0033] It should be noted that the terms "mobile device", "user equipment", "user device", “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

[0034] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0035] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.

[0036] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive — in a manner similar to the term “comprising” as an open transition word — without precluding any additional or other elements.

[0037] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.

[0038] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.

[0039] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data transfer are also expected to evolve and replace the older generations of technologies. In the field of wireless data communications, the dynamic advancement of various generations of cellular technology are also seen. The development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), and now fifth generation (5G), and more such generations are expected to continue in the forthcoming time.

[0040] Radio Access Technology (RAT) refers to the technology used by mobile devices/ user equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base stations, which are responsible for providing the wireless connection. Further, each RAT has its own set of protocols and standards for communication, which define the frequency bands, modulation techniques, and other parameters used for transmitting and receiving data. Examples of RATs include GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System), LTE (Long-Term Evolution), and 5G. The choice of RAT depends on a variety of factors, including the network infrastructure, the available spectrum, and the mobile device's/device's capabilities. Mobile devices often support multiple RATs, allowing them to connect to different types of networks and provide optimal performance based on the available network resources.

[0041] gNodeB: (gNB) refers to the base station component in 5G (fifth-generation) wireless networks. It is an essential element of the Radio Access Network (RAN) responsible for transmitting and receiving wireless signals to and from user devices, such as smartphones, tablets, and Internet of Things (loT) devices. In 5G networks, there are similar components in other generations of wireless networks. Here are a few examples: Base Transceiver Station (BTS): In 2G (second-generation) networks, the BTS serves as the base station responsible for transmitting and receiving wireless signals. It connects mobile devices to the cellular network infrastructure. NodeB: In 3G (third-generation) networks, the NodeB is the base station component that enables wireless communication. It facilitates the transmission and reception of signals between user devices and the network. eNodeB: In 4G (fourth-generation) LTE (Long-Term Evolution) networks, the eNodeB serves as the base station. It supports high-speed data transmission, low latency, and improved network capacity. Access Point (AP): In Wi-Fi networks, an access point functions as a central hub that enables wireless devices to connect to a wired network. It provides a wireless interface for devices to access the network and facilitates communication between them. The examples illustrate the base station components in different generations of wireless networks, such as BTS in 2G, NodeB in 3G, eNodeB in 4G LTE, and gNodeB in 5G. Each component plays a crucial role in facilitating wireless connectivity and communication between user devices and the network infrastructure.

[0042] As used herein, dedicated or guaranteed bit rate (GBR) quality of service (QoS) flow refers to a guaranteed service with a minimum and/or maximum bit rate and dedicated resource allocation to ensure consistent quality in the network.

[0043] The GBR quality of service (QoS) flow is used for time-sensitive application such as audio or video voice calls, automotive application and real-time streaming applications. Through this, the network service provider may ensure a minimum speed for some services or user subscribed services, so that user experience may not suffer.

[0044] As used herein, Quality of Service (QoS) flow refers to data flow in a network with certain level of performance and quality control for ensuring the fulfilling the requirement of service or application (such as audio, video and data). [0045] As used herein, a stale dedicated, or GBR Quality of Service (QoS) flow session refers to a dedicated or GBR QoS flow has become inactive in the core network. This can occur due to the loss of some messages, a missed call release trigger, or any other unforeseen reason causing the session to stop transmitting data.

[0046] As used herein, a stale flow refers that data flow becomes inactive or stale in the network. There is no data flow activity observed for a service (e.g. audio, video and data) in the network for a certain period of time. The stale flow may occupy undesirable resources, which causes wastage of resources in the network.

[0047] As discussed in the background section, there's no standard mechanism with which the User Plane Function (UPF) [128] can report the presence of stale dedicated or Guaranteed Bit Rate (GBR) Quality of Service (QoS) flow sessions. This lack of reporting capabilities makes it difficult for the core network to efficiently manage its resources. Stale flows resulting from inactive or lost messages can lead to the unnecessary occupation of system resources, such as memory and CPU. This can reduce the overall efficiency of the network and restrict its capacity. The previous systems may lack automated mechanisms to identify and delete stale dedicated/GBR QoS flows. This can lead to manual intervention being necessary to clean up these resources, making the process more time-consuming and potentially error-prone. Without an efficient way of identifying and removing stale flows, system capacity may not be optimized. The stale flows occupy resources that could otherwise be utilized for active and necessary processes.

[0048] Thus, there exists an imperative need in the art to provide a method and system for dynamic identification and deletion of stale GBR flows in a core network. The proposed invention addresses these problems by providing an innovative method and system to identify and delete stale dedicated/GBR QoS flows in a core network, thus improving resource utilization and system capacity optimization.

[0049] The present disclosure relates generally to the field of wireless communication systems. In particular, the present disclosure relates to GBR flows in a core network. More particularly, the present disclosure relates to method and system for dynamic identification and deletion of stale GBR flows in a core network. The GBR bearer is also referred to as dedicated bearer resource. [0050] An aspect of the present disclosure provides a system for dynamic identification and deletion of stale GBR flows in a core network. The system checks a usage report received from a User Plane Function (UPF) [128] corresponding to one or more different GBR flows in the network using a Session Management Function (SMF) [108], Next, the system identifies a stale session in the core network if the usage corresponding to an Audio/Video call in the GBR flow is indicated as zero using the SMF [108], Next, the system initiate deletion of the identified stale session by sending a set of instructions to at least one network component of a plurality of network components to release one or more system resources occupied by stale session.

[0051] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0052] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture [100], As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment (UE) [102] (alternatively referred to as user device [102] or one or more user devices [102] herein), a radio access network (RAN) [104], a plurality if network functions or network entities such as, an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data network (DN) [130], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.

[0053] The User Equipment (UE) [102] interfaces with the network via the Radio Access Network (RAN) [104]; the Access and Mobility Management Function (AMF) [106] manages connectivity and mobility, while the Session Management Function (SMF) [108] administers session control; the service communication proxy (SCP) [110] routes and manages communication between network services, enhancing efficiency and security, and the Authentication Server Function (AUSF) [112] handles user authentication; the NSSAAF [114] for integrating the 5G core network with existing 4G LTE networks i.e., to enable Non-Standalone (NSA) 5G deployments, the Network Slice Selection Function (NSSF) [116], Network Exposure Function (NEF) [118], and Network Repository Function (NRF) [120] enable network customization, secure interfacing with external applications, and maintain network function registries respectively; the Policy Control Function (PCF) [122] develops operational policies, and the Unified Data Management (UDM) [124] manages subscriber data; the Application Function (AF) [126] enables application interaction, the User Plane Function (UPF) [128] processes and forwards user data, and the Data Network (DN) [130] connects to external internet resources; collectively, these components are designed to enhance mobile broadband, ensure low-latency communication, and support massive machine-type communication, solidifying the 5GC as the infrastructure for next-generation mobile networks.

[0054] Radio Access Network (RAN) [104] is the part of a mobile telecommunications system that connects user equipment (UE) [102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.

[0055] Access and Mobility Management Function (AMF) [106] (alternatively referred to as AMF unit [106]) is a 5G core network function responsible for managing access and mobility aspects, such as UE [102] registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.

[0056] Session Management Function (SMF) [108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) [128] for data forwarding and handles IP address allocation and QoS enforcement.

[0057] Service Communication Proxy (SCP) [110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.

[0058] Authentication Server Function (AUSF) [112] is a network function in the 5G core responsible for authenticating UEs [102] during registration and providing security services. It generates and verifies authentication vectors and tokens.

[0059] Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs [102] can access only the slices for which they are authorized. [0060] Network Slice Selection Function (NSSF) [116] is a network function responsible for selecting the appropriate network slice for a UE [102] based on factors such as subscription, requested services, and network policies.

[0061] Network Exposure Function (NEF) [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.

[0062] Network Repository Function (NRF) [120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.

[0063] Policy Control Function (PCF) [122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.

[0064] Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.

[0065] Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.

[0066] User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.

[0067] Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) [102] in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.

[0068] FIG. 2 illustrates an exemplary block diagram of a system [200] for dynamic identification and deletion of stale GBR flows in a core network, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 2, the system [200] comprises a Session Management Function (SMF [108]), and a User Plane Function (UPF) [128] for dynamic identification and deletion of stale dedicated GBR flows in a core network.

[0069] The Session Management Function (SMF) [108] is configured to check a usage report received from a User Plane Function (UPF) [128] corresponding to one or more GBR flows in the network. Further, the checking of the usage report received from the UPF [128] is performed periodically. Furthermore, the periodic checking is based on a predetermined time period. Furthermore, the SMF [108] is configured to release system resources occupied by the identified stale session. Furthermore, the SMF [108] performs the periodic check at regular intervals, the intervals being adjustable based on network traffic and system resources.

[0070] Further, the SMF [108] is configured to identify a session as a stale session if a usage in the usage report corresponding to an Audio/Video call in the one or more GBR flows is indicated as zero. Also, the usage report comprises any or a combination of information on resource utilization by the one or more GBR flows in the core network, includes data transmitted over a specified period, duration of calls, and type of resources used.

[0071] Furthermore, the SMF [108] performs the periodic check at regular intervals, wherein the intervals are adjustable based on network traffic and system resources. The SMF [108] identifies stale session of dedicated/GBR QoS flow using traffic usages report from UPF [128], On the basis of usage SMF [108] determines to release the stale dedicated/GBR QoS flow. The SMF [108] periodically checks usages report received from UPF [128] corresponding to one or more flows. If usages corresponding Audio/Video call received as zero, then SMF [108] identifies it as a stale session in the core network. SMF [108] initiates deletion for resources reserved at core end corresponding to Audio/Video call.

[0072] Furthermore, the SMF [108] is configured to delete the identified stale session by sending a set of instructions to at least one network component of a plurality of network components to release one or more system resources occupied by the stale session. Releasing system resources corresponds to freeing up memory and CPU that are occupied by the identified stale session. The plurality of network components comprises at least one of the User Plane Function (UPF) (128), a Data Network (DN) [130], an Access and Mobility Management Function (AMF) [106], and a Network Repository Function (NRF) [120], [0073] In an implementation, the system [200] may be configured for dynamic identification and deletion of stale GBR flows in the core network through several specific steps: a) Periodically Checking a Usage Report: The Session Management Function (SMF) [108] in the core network periodically checks usage reports received from the User Plane Function (UPF) [128], This periodic checking is to ensure that all the one or more GBR flows in the network are analysed. By doing so, the SMF [108] can identify any discrepancies in the usage, including stale or inactive flows. The period of this check can be predetermined based on the requirements of the network or adjusted dynamically based on network traffic and system resources. b) Identifying Stale Sessions: The SMF [108] identifies a stale session if the usage report received from the UPF [128] corresponding to an Audio/Video call is zero. A usage of zero indicates that there are no data transfers happening in the session, implying that the session is stale or inactive. This is an important step in the process as it helps identify unnecessary resource usage in the network, which could potentially be freed up and used more efficiently. c) Initiating Deletion of Stale Sessions: Once a stale session is identified, the SMF [108] initiates a process to delete or release these stale sessions. This involves sending commands or instructions to relevant network components to free up the system resources that the stale sessions are occupying. By deleting these stale sessions, the system can efficiently manage and reallocate its resources.

[0074] It would be appreciated by the person skilled in the art that the system effectively manages its resources and optimizes capacity by periodically checking usage reports, identifying stale sessions, and deleting them.

[0075] Referring to FIG. 3 an exemplary sequence flow diagram [300], a process for dynamic identification and deletion of stale GBR flows in a core network, in accordance with exemplary embodiments of the present invention is shown.

[0076] In a telecommunication network such as a 5G system, various network functions work together to ensure efficient data transmission and resource utilization. The SMF [108] is configured to manage sessions between the network and the user equipment (UE)/RAN [302], This includes tasks like session establishment, modification, and release. The UPF [128] on the other hand is responsible for handling the user plane traffic (the actual data traffic from users) and applies policies (like QoS or Quality of Service rules) as instructed by the SMF [108],

[0077] A usage report corresponds to a record or collection of data that provides information on how resources are being utilized by different flows in the network. For instance, the usage report could contain details about the amount of data transmitted over a certain period of time for an audio or video call, the duration of the call, the type of resources used, etc.

[0078] The process of periodically checking a usage report received from a UPF [128] refers to a routine or scheduled task performed by the SMF [108] where it examines these usage reports at regular intervals. For example, every few seconds, minutes, hours, or any other time duration, depending on the specific needs and configuration of the network. The SMF [108] checks the reports to monitor and manage the active sessions in the network. In this context, the usage reports are analysed for different GBR flows, which could represent different types of data traffic, such as audio calls, video calls, messaging, or internet browsing data. The aim is to identify any stale or inactive sessions that are not currently transmitting any data but are still occupying network resources. These stale sessions could be due to a lost connection, a missed call release trigger, or any other reason causing the session to become inactive. By periodically checking the usage reports, the SMF [108] can identify these stale sessions early and initiate a process to delete them, thereby freeing up the resources they were using and improving the overall efficiency and capacity of the network.

[0079] A "stale session" refers to a dedicated or Guaranteed Bit Rate (GBR) Quality of Service (QoS) flow that has become inactive in the core network. This can occur due to the loss of some messages, a missed call release trigger, or any other unforeseen reason causing the session to stop transmitting data. An important factor in identifying these stale sessions is the usage report received from the User Plane Function (UPF) [128], The usage report is a collection of data about the various active sessions in the network and the resources they are using. In these usage reports, each session will have corresponding usage data. For an Audio/Video call, this usage data could include metrics such as the amount of data transmitted over a certain period, the duration of the call, the type of resources used, and so on. In an event a trigger from UE/RAN [302] for release is received, subsequently, the PCF [122] transmits trigger to SMF [108] to release audio/video call.

[0080] The Session Management Function (SMF) [108] periodically checks these usage reports, it will analyse the usage data for each session. If it finds a session where the usage data for an Audio/Video call is received as zero, it means that no data is being transmitted for that particular session. In the context of the network, this indicates that the session has become inactive or stale. Upon identifying this, the SMF [108] will then categorize this session as a stale session. The SMF [108] can then initiate a process to delete this stale session from the network, freeing up the resources it was occupying and improving the overall efficiency and capacity of the network.

[0081] Once the Session Management Function (SMF) [108] has identified a stale session (a session with a usage of zero for an Audio/Video call), the next step is to free up the resources that this session is consuming. For example, the SMF [108] may initiate release. These resources are system memory and CPU that are reserved at the core end of the network for handling this specific session. Initiating deletion means that the SMF [108] initiates a process to release the resources that the stale session is holding. This involves sending commands or instructions to the relevant components such as the UE/RAN [302] via the Mobility Management Entity (MME)/AMF [306]) to terminate the session and release the allocated resources. These resources could include bandwidth reserved for the data flow of the session, memory space for storing session details, and CPU cycles that could have been allocated for managing the session. When a session becomes stale, these resources are effectively wasted as they are tied up without being used. By deleting the stale session, these resources are freed up and can be reallocated for other active sessions or network tasks. This enhances the efficiency of the network and allows for optimal utilization of system resources. This whole process is typically automated and is part of the network's resource management strategy. The deletion process might involve additional checks or procedures, like notifying other network components or updating relevant databases, to ensure the integrity of the network and the accuracy of network management data.

[0082] Referring to FIG. 4 an exemplary method flow diagram [400] for dynamic identification and deletion of stale GBR flows in a core network, in accordance with exemplary embodiments of the present invention is shown. In an implementation the method [400] is performed by the server. The method begins at step [402] and proceeds to step [404],

[0083] At step [404], the method comprising checking, by a Session Management Function (SMF) [108], a usage report received from a User Plane Function (UPF) [128] corresponding to one or more GBR flows in the network. The checking of the usage report received from the UPF [128] is performed periodically. The periodic checking is based on a predetermined time period. The SMF [108] performs the periodic check at regular intervals, the intervals being adjustable based on network traffic and system resources. The SMF [108] is primarily responsible for managing sessions between the network and the user equipment (UE)/RAN [302], This includes tasks like session establishment, modification, and release. The UPF [128] on the other hand is responsible for handling the user plane traffic (the actual data traffic from users) and applies policies (like QoS or Quality of Service rules) as instructed by the SMF [108],

[0084] Now, at step [406], the method encompasses identifying, by the SMF [108], a session as a stale session if a usage in the usage report corresponding to an Audio/Video call in the one or more GBR flows is indicated as zero. The stale session is identified based on a zero data transfer occurrence in the session.

[0085] A "stale session" refers to a dedicated or GBR Quality of Service (QoS) flow that has become inactive in the core network. The usage report comprises any or a combination of information on resource utilization by GBR flows in the core network, including data transmitted over a specified period, duration of calls, and type of resources used. The usage report is a collection of data about the various active sessions in the network and the resources they are using. In these usage reports, each session will have corresponding usage data.

[0086] Next, at step [408], the method comprising deleting, by the SMF [108], the identified stale session by sending a set of instructions to at least one network component of a plurality of network components to release one or more system resources occupied by the stale session. Further, releasing system resources corresponds to freeing up memory and CPU that were occupied by the identified stale session. The plurality of network components comprises at least one of the User Plane Function (UPF [128]), a Data Network (DN) [130], an Access and Mobility Management Function (AMF) [106], and a Network Repository Function (NRF) [120] but the present disclosure is not limited thereto. Once the Session Management Function (SMF) [108] has identified a stale session (a session with a usage of zero for say an Audio/Video call), the next step is to free up the resources that this session is consuming. These resources are system memory and CPU that are reserved at the core end of the network for handling this specific session. "Initiating deletion" means that the SMF [108] starts a process to release the resources that the stale session is holding.

[0087] Thereafter, the method [400] terminates at step [410],

[0088] Furthermore, the present disclosure encompasses a method of releasing system resources occupied by the identified stale session. [0089] Furthermore, the present disclosure encompasses, method of the usage report comprises any or a combination of information on resource utilization by the one or more GBR flows in the core network, comprising data transmitted over a specified period, duration of calls, and type of resources used.

[0090] Furthermore, the present disclosure encompasses, a method wherein the SMF [108] performs the periodic check at regular intervals, wherein the intervals are adjustable based on network traffic and system resources.

[0091] Furthermore, the present disclosure encompasses the plurality of network components comprises at least one of the User Plane Function (UPF) [128], a Data Network (DN) [130], an Access and Mobility Management Function (AMF) [106], and a Network Repository Function (NRF) [120],

[0092] In an example, a 5G core network system where an SMF (Session Management Function) [108] and a UPF (User Plane Function) [128] interact with each other to manage sessions and resources for different data flows. This could include flows for audio/video calls, internet data, messaging, and so on. Every hour, the SMF [108] initiates a procedure to check the usage reports it has received from the UPF [128], This procedure is automatically initiated by the system's processor. During one of these checks, the SMF [108] finds a usage report from the UPF [128] that indicates a zero usage for a video call session that was established a few hours ago. As there is zero usage, it means no data has been transmitted through this session for a while. Based on the detected zero usage, the SMF [108] determines this session as a stale session. The SMF [108] then initiates a deletion process for this stale session. The SMF [108] sends a command to the relevant components in the network to free up the system resources (like memory and CPU) that were being occupied by this stale session. After the deletion process, the system resources that were tied up to the stale session are now released and can be utilized for new, active sessions.

[0093] FIG. 5 illustrates an exemplary block diagram of a computing device [500] (also referred to herein as a computer system [500])) upon which an embodiment of the present disclosure may be implemented. In an implementation, the computing device implements the method for the process for dynamic identification and deletion of stale GBR flows in a core network, using the system [200], In another implementation, the computing device [500] itself implements the method for the process for dynamic identification and deletion of stale GBR flows in a core network using one or more units configured within the computing device [500], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.

[0094] The computing device [500] may include a bus [502] or other communication mechanism for communicating information, and a processor [504] coupled with bus [502] for processing information. The processor [504] may be, for example, a general-purpose microprocessor. The computing device [500] may also include a main memory [506], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [502] for storing information and instructions to be executed by the processor [504], The main memory [506] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [504], Such instructions, when stored in non-transitory storage media accessible to the processor [504], render the computing device [500] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [500] further includes a read only memory (ROM) [508] or other static storage device coupled to the bus [502] for storing static information and instructions for the processor [504],

[0095] A storage device [510], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [502] for storing information and instructions. The computing device [500] may be coupled via the bus [502] to a display [512], such as a cathode ray tube (CRT), for displaying information to a computer user. An input device [514], including alphanumeric and other keys, may be coupled to the bus [502] for communicating information and command selections to the processor [504], Another type of user input device may be a cursor controller [516], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [504], and for controlling cursor movement on the display [512], The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.

[0096] The computing device [500] may implement the techniques described herein using customized hard-wired logic, one or more application-specific integrated circuits (ASICs) or Field Programmable Gate Arrays (FPGAs), firmware and/or program logic which in combination with the computing device [500] causes or programs the computing device [500] to be a special-purpose machine. According to one embodiment, the techniques herein are performed by the computing device [500] in response to the processor [504] executing one or more sequences of one or more instructions contained in the main memory [506], Such instructions may be read into the main memory [506] from another storage medium, such as the storage device [510], Execution of the sequences of instructions contained in the main memory [506] causes the processor [504] to perform the process steps described herein. In alternative embodiments, hard-wired circuitry may be used in place of or in combination with software instructions.

[0097] The computing device [500] also may include a communication interface [518] coupled to the bus [502], The communication interface [518] provides a two-way data communication coupling to a network link [520] that is connected to a local network [522], For example, the communication interface [518] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [518] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [518] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.

[0098] The computing device [500] can send messages and receive data, including program code, through the network(s), the network link [520] and the communication interface [518], In the Internet example, a server [530] might transmit a requested code for an application program through the Internet [528], the Internet Service Provider (ISP) [526], the local network [522], host [524] and the communication interface [518], The received code may be executed by the processor [504] as it is received, and/or stored in the storage device [510], or other non-volatile storage for later execution.

[0099] Yet another aspect of the present disclosure provides a non-transitory computer readable storage medium storing instruction for dynamic identification and deletion of guaranteed bit rate (GBR) flows in a core network. The instructions include executable code which, when executed by one or more units of a system, causes: a Session Management Function (SMF) [108] to check a usage report received from a User Plane Function (UPF) [128] corresponding to one or more GBR flows in the network; the SMF [108] to identify a session as a stale session if a usage in the usage report corresponding to an Audio/Video call in the one or more GBR flow is indicated as zero; the SMF [108] to delete the identified stale session by sending a set of instructions to at least one network component of a plurality of network components to release one or more system resources occupied by the stale session. [0100] The present disclosure further according to yet another aspect may relate to a user equipment (UE). The UE comprising: a transmitter unit configured to transmit a request to a system for dynamic identification and deletion of stale GBR flows; a receiver unit, configured to receive from the system a response to the request, wherein the response comprises an indication of identification and deletion of stale GBR flows, and wherein the response is generated by the system based on: checking, by a Session Management Function (SMF) [108], a usage report received from a User Plane Function (UPF) [128] corresponding to one or more GBR flows in the network; identifying, by the SMF [108], a session as a stale session if a usage in the usage report corresponding to an Audio/Video call in the one or more GBR flows is indicated as zero; deleting, by the SMF [108], the identified stale session by sending a set of instructions to at least one network component of a plurality of network components to release one or more system resources occupied by the stale session.

[0101] The present disclosure offers numerous advantages over the existing art. The present disclosure provides a method and system for dynamic identification and deletion of stale GBR flows in a core network that seeks to free up system resources such as memory and CPU. This improves the overall efficiency of the system and makes better use of available resources.

[0102] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

[0103] While considerable emphasis has been placed herein on the disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

Claims

I/We Claim:

1. A method for dynamic identification and deletion of stale guaranteed bit rate (GBR) flows in a core network, the method comprising: checking, by a Session Management Function (SMF) [108], a usage report received from a User Plane Function (UPF) [128] corresponding to one or more GBR flows in the core network; identifying, by the SMF [108], a session as a stale session if a usage in the usage report corresponding to an Audio/Video call in the one or more GBR flows is indicated as zero; and deleting, by the SMF [108], the identified stale session by sending a set of instructions to at least one network component of a plurality of network components to release one or more system resources occupied by the stale session.

2. The method as claimed in claim 1, wherein the checking of the usage report received from the UPF [128] is performed periodically.

3. The method as claimed in claim 2, wherein the periodic checking is based on a predetermined time period.

4. The method as claimed in claim 1, further comprises releasing system resources occupied by the identified stale session.

5. The method as claimed in claim 1, wherein the usage report comprises any or a combination of information on resource utilization by the one or more GBR flows in the core network, comprising data transmitted over a specified period, duration of calls, and type of resources used.

6. The method as claimed in claim 2, wherein the SMF [108] performs the periodic checking at regular intervals, wherein the intervals are adjustable based on network traffic and system resources.

7. The method as claimed in claim 1, wherein the plurality of network components comprises at least one of the User Plane Function (UPF) [128], a Data Network (DN) [130], an Access and Mobility Management Function (AMF) [106], and a Network Repository Function (NRF) [120],

8. A system [200] for dynamic identification and deletion of stale Guaranteed bit rate (GBR) flows in a core network, the system comprising a Session Management Function (SMF) [108], configured to: check a usage report received from a User Plane Function (UPF) [128] corresponding to one or more GBR flows in the core network; identify, a session as a stale session if a usage in the usage report corresponding to an Audio/Video call in the one or more GBR flows is indicated as zero; and delete, the identified stale session by sending a set of instructions to at least one network component of a plurality of network components to release one or more system resources occupied by the stale session.

9. The system as claimed in claim 8, wherein the checking of the usage report received from the UPF [128] is performed periodically.

10. The system as claimed in claim 9, wherein the periodic checking is based on a predetermined time period.

11. The system as claimed in claim 8, wherein the SMF [108] is further configured to release system resources occupied by the identified stale session.

12. The system as claimed in claim 8, wherein the usage report comprises any or a combination of information on resource utilization by the one or more GBR flows in the core network, comprising data transmitted over a specified period, duration of calls, and type of resources used.

13. The system as claimed in claim 9, wherein the SMF [108] performs the periodic checking at regular intervals, wherein the intervals are adjustable based on network traffic and system resources.

14. The system as claimed in claim 8, wherein the plurality of network components comprises at least one of the User Plane Function (UPF) (128), a Data Network (DN) [130], an Access and Mobility Management Function (AMF) [106], and a Network Repository Function (NRF) [120],

15. A user equipment (UE) comprising: a transmitter unit configured to transmit a request to a system [200] for dynamic identification and deletion of stale guaranteed bit rate (GBR) flows; a receiver unit, configured to receive from the system [200] a response to the request, wherein the response comprises an indication of identification and deletion of stale GBR flows, and wherein the response is generated by the system [200] based on: o checking, by a Session Management Function (SMF) [108], a usage report received from a User Plane Function (UPF) [128] corresponding to one or more GBR flows in a core network; o identifying, by the SMF [108], a session as a stale session if a usage in the usage report corresponding to an Audio/Video call in the one or more GBR flow is indicated as zero; and o deleting, by the SMF [108], the identified stale session by sending a set of instructions to at least one network component of a plurality of network components to release one or more system resources occupied by the stale session.

16. A non-transitory computer readable storage medium storing instructions for dynamic identification and deletion of Guaranteed bit rate (GBR) flows in a core network, the instructions include executable code which, when executed by one or more units of a system, causes: a Session Management Function (SMF) [108] to check a usage report received from a User Plane Function (UPF) [128] corresponding to one or more different (GBR) flows in the core network; the SMF [108] to identify a session as a stale session if a usage in the usage report corresponding to an Audio/Video call in the one or more GBR flows is indicated as zero; and the SMF [108] to delete the identified stale session by sending a set of instructions to at least one network component of a plurality of network components to release one or more system resources occupied by the stale session.