FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR MANAGING DATA
TRAFFIC”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR MANAGING DATA TRAFFIC
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to wireless
communication systems. More particularly, embodiments of the present disclosure relate to management of data traffic.
BACKGROUND OF THE DISCLOSURE
[0002] The following description of the 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 is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the 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] Moreover, the 5G core networks are based on service based architecture
(SBA) that is centred around network function (NF) services. In said SBA, a set of interconnected NFs delivers the control plane functionality and common data repositories of the 5G network, where each NF is authorized to access services of other NFs. Particularly, each NF can register itself and its supported services to a Network Repository Function (NRF), which is used by other NFS for the discovery of NF instances and their services. The NRF therefore supports functions related to 1) maintaining the profiles of the available network function (NF) instances and their supported services in the 5G core network, 2) allowing NF instances to discover other NF instances in the 5G core network, and 3) allowing the NF instances to track the status of other NF instances.
[0005] The 5G Core Network consists of a multitude of Network Functions
(NFs) such as Policy Control Function (PCF), Binding Support Function (BSF), Charging Function (CHF), Network Repository Function (NRF), Access and Mobility Management Function (AMF) and Session Management Function (SMF). They perform their roles in ensuring end to end transfer of data, as well as controlling the access and availability of the network resources to the user. The CHF handles control plane signalling and management functions within the network. When a subscriber's device initiates a session or transaction that could incur charges (such as premium content access or data usage), the PCF or another relevant network element might query the CHF to retrieve the subscriber's current spending limit (data limit). The CHF provides the spending limit information to the PCF. This information is provided on the basis of Subscription Permanent Identifier (SUPI). In a scenario, a single building may have a single outdoor customer premise equipment (ODCPE). Now, that single ODCPE may be assigned a single subscription permanent identifier (SUPI) such that multiple home gateways (HGW) of multiple devices are connected to it utilizing the same SUPI. The HGWs may

initiate session management (SM) policy control by sending request to the policy control function (PCF) with same SUPI of the ODCPE. Since same SUPI may be assigned to multiple users connected with single ODCPE device, therefore there was need to find solutions to identify the subscriber device based on which spending limit of the subscriber is identified.
[0006] Thus, there exists an imperative need in the art to provide a solution for
managing data traffic, which the present disclosure aims to address.
SUMMARY OF THE DISCLOSURE
[0007] 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.
[0008] An aspect of the present disclosure may relate to a method for managing
data traffic. The method comprises receiving, by a transceiver unit, from a Session Management Function (SMF) at a Policy Control Function (PCF), a create session request comprising a MAC Identifier (MAC ID) and a Data Network name (DNN) parameter. Further, the method comprises determining, by a processing unit at the PCF, a valid MAC ID status associated with the MAC ID, based on the create session request. Further, the method comprises determining, by the processing unit at the PCF, a positive authorisation status associated with the DNN parameter based on the valid MAC ID status. Further, the method comprises determining, by the processing unit at the PCF, a valid DNN parameter status associated with the DNN parameter based on the positive authorisation status. Further, the method comprises transmitting, by the transceiver unit from the PCF to a charging function (CHF), a spending limit create request comprising the MAC ID, based on the valid DNN parameter. Further, the method comprises receiving, by the transceiver unit at the

PCF from the CHF, one or more Policy counter Identifiers (PCIDs) associated with the MAC ID, based on the spending limit create request. Further, the method comprises transmitting, by the transceiver unit at the PCF to the SMF, a Policy and Charging Control (PCC) rule associated with one or more PCIDs. Further, the method comprises managing, by the processing unit, a data traffic associated with the create session request based on the MAC ID and the PCC rule.
[0009] In an exemplary aspect of the present disclosure, the valid MAC ID
status associated with the MAC ID is determined by the processing unit at the PCF in an event a successful match associated with the MAC ID is determined by the processing unit, based on a comparison of the MAC ID and a set of provisioned network data at the PCF.
[0010] In an exemplary aspect of the present disclosure, positive authorisation
status associated with the DNN parameter is determined by the processing unit at the PCF in an event a successful authorisation status associated with one of the DNN parameter, and wherein the session overload parameter and set of mandatory parameters is determined by the processing unit based on a set of predefined authorisation rules.
[0011] In an exemplary aspect of the present disclosure, the method comprises
determining, by the processing unit at the PCF, the PCC rule associated with the one or more PCIDs based on a set of predefined PCIDs at the PCF and a predefined PCC determination rule.
[0012] In an exemplary aspect of the present disclosure, the MAC ID further
comprises at least one of a session overload parameter, and a set of mandatory parameters.

[0013] In an exemplary aspect of the present disclosure, the step of
determining, by the processing unit at the PCF, the valid DNN parameter status comprises: (a) determining a successful DNN match status associated with the DNN parameter based on comparing the DNN parameter and a set of predefined session range parameter associated with a Charging Function (CHF); and (b) determining a negative status associated with a current CHF session based on the successful DNN match.
[0014] Another aspect of the present disclosure may relate to a system for
managing data traffic. The system comprises a transceiver unit configured to receive from a Session Management Function (SMF) at a Policy Control Function (PCF), a create session request comprising a MAC Identifier (MAC ID) and a Data Network name (DNN) parameter. Further, the system comprises a processing unit configured to determine, at the PCF, a valid MAC ID status associated with the MAC ID, based on the create session request. Further, the processing unit is configured to determine, at the PCF, a positive authorisation status associated with the DNN parameter based on the valid MAC ID status. Further, the processing unit is configured to determine, at the PCF, a valid DNN parameter status associated with the DNN parameter based on the positive authorisation status. Further, the transceiver unit is configured to transmit, from the PCF to a charging function (CHF), a spending limit create request comprising the MAC ID, based on the valid DNN parameter. Further, the transceiver unit is configured to receive, at the PCF from the CHF, one or more Policy counter Identifiers (PCIDs) associated with the MAC ID, based on the spending limit create request. Further, the transceiver unit is configured to transmit, at the PCF to the SMF, a Policy and Charging Control (PCC) rule associated with one or more PCIDs. Further, the processing unit is configured to manage, a data traffic associated with the create session request based on the MAC ID and the PCC rule.

[0015] Yet another aspect of the present disclosure may relate to a non-
transitory computer readable storage medium storing instructions for managing data traffic. The instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit of the system to receive from a Session Management Function (SMF) at a Policy Control Function (PCF), a create session request comprising a MAC Identifier (MAC ID) and a Data Network name (DNN) parameter. Further, the executable code, when executed, causes a processing unit of the system to determine, at the PCF, a valid MAC ID status associated with the MAC ID, based on the create session request. Further, the executable code, when executed, causes the processing unit of the system to determine, at the PCF, a positive authorisation status associated with the DNN parameter based on the valid MAC ID status. Further, the executable code, when executed, causes the processing unit of the system to determine, at the PCF, a valid DNN parameter status associated with the DNN parameter based on the positive authorisation status. Further, the executable code, when executed, causes the transceiver unit of the system to transmit, from the PCF to a charging function (CHF), a spending limit create request comprising the MAC ID, based on the valid DNN parameter. Further, the executable code, when executed, causes the transceiver unit of the system to receive, at the PCF from the CHF, one or more Policy counter Identifiers (PCIDs) associated with the MAC ID, based on the spending limit create request. Further, the executable code, when executed, causes the transceiver unit of the system to transmit, at the PCF to the SMF, a Policy and Charging Control (PCC) rule associated with one or more PCIDs. Further, the executable code, when executed, causes the processing unit of the system to manage, a data traffic associated with the create session request based on the MAC ID and the PCC rule.
OBJECTS OF THE INVENTION
[0016] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.

[0017] It is an object of the present disclosure to provide a system and a method
for managing data traffic.
[0018] It is another object of the present disclosure to provide a solution that
to provide unique MAC Id to home gateway to identify each user with their corresponding MAC address/identifier (ID).
[0019] It is yet another object of the present disclosure to provide a solution
for managing data traffic cycle of Home Gateways based on HGW-MAC ID.
DESCRIPTION OF THE DRAWINGS
[0020] 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. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0021] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture.

[0022] FIG. 2 illustrates an exemplary block diagram of a computing device
upon which the features of the present disclosure may be implemented, in accordance with exemplary implementations of the present disclosure.
5 [0023] FIG. 3 illustrates an exemplary block diagram of a system for managing
data traffic, in accordance with exemplary implementations of the present disclosure.
[0024] FIG. 4 illustrates a method flow diagram for managing data traffic, in
10 accordance with exemplary implementations of the present disclosure.
[0025] FIG. 5 illustrates an exemplary scenario flow diagram for managing
data traffic, in accordance with exemplary implementations of the present disclosure. 15
[0026] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
20
[0027] 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
25 details. Several features described hereafter may 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.
9

[0028] 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
5 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.
[0029] Specific details are given in the following description to provide a
10 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, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. 15
[0030] 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 may be performed in
20 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.
[0031] The word “exemplary” and/or “demonstrative” is used herein to mean
25 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
30 known to those of ordinary skill in the art. Furthermore, to the extent that the terms
10

“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. 5
[0032] As used herein, a “processing unit” or “processor” or “operating
processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal
10 processor, a plurality of microprocessors, one or more microprocessors in
association with a (Digital Signal Processing) 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
15 functionality that enables the working of the system according to the present
disclosure. More specifically, the processor or processing unit is a hardware processor.
[0033] As used herein, “a user equipment”, “a user device”, “a smart-user-
20 device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld
device”, “a wireless communication device”, “a mobile communication device”, “a
communication device” may be any electrical, electronic and/or computing device
or equipment, capable of implementing the features of the present disclosure. The
user equipment/device may include, but is not limited to, a mobile phone, smart
25 phone, laptop, a general-purpose computer, desktop, personal digital assistant,
tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from unit(s) which are required to implement the features of the present disclosure. 30
11

[0034] As used herein, “storage unit” or “memory unit” refers to a machine or
computer-readable medium including any mechanism for storing information in a
form readable by a computer or similar machine. For example, a computer-readable
medium includes read-only memory (“ROM”), random access memory (“RAM”),
5 magnetic disk storage media, optical storage media, flash memory devices or other
types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
10 [0035] As used herein “interface” or “user interface refers to a shared boundary
across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be
15 called.
[0036] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a
general-purpose processor, a special purpose processor, a conventional processor,
20 a digital signal processor (DSP), a plurality of microprocessors, one or more
microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
25 [0037] As used herein the transceiver unit include at least one receiver and at
least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
12

[0038] As used herein, outdoor customer premise equipment (ODCPE) refers
to a hardware or device installed outside a customer's premises for establishing and
maintaining a network connection. The ODCPE includes antennas, satellite dishes,
or other communication devices mounted externally to receive and transmit signals
5 between the service provider's network and the customer's indoor equipment (i.e.
home gateways). The ODCPE facilitates in providing a stable and efficient link for services such as broadband internet, cable television, and telephone systems, especially in environments where direct line-of-sight or external signal capture is required for optimal performance.
10
[0039] Further, in accordance with the present disclosure, it is to be
acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various
15 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
20 of the present disclosure.
[0040] As discussed in the background section, the current known solutions
have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing
25 method and system of managing data traffic. As discussed above, when a
subscriber's device initiates a session or transaction that could incur charges (such as premium content access or data usage), the policy control function (PCF) or another relevant network element queries the charging function (CHF) to retrieve the subscriber's current spending limit (data limit). The CHF provides the spending
30 limit information to the PCF. This information is provided on the basis of
Subscription Permanent Identifier (SUPI). In a scenario, a single building may have
13

a single outdoor customer premise equipment (ODCPE). Now, that single ODCPE
may be assigned a single subscription permanent identifier (SUPI) such that
multiple home gateways (HGW) of multiple devices are connected to it utilizing
the same SUPI. The HGW may initiate session management (SM) policy control
5 by sending request to the policy control function (PCF) with same SUPI of ODCPE.
Since same SUPI may be assigned to multiple users having single ODCPE device,
the SLR, according to the embodiments of the present disclosure, is queried on
Media Access Control Identifier (MAC ID), which is unique for each user. This
process involves the identification of devices based on their MAC addresses (i.e.,
10 MAC IDs), the retrieval of policy control identifiers (PCIs), and the subsequent
application of policy rules by PCF to manage and control network resources or other aspects of the system.
[0041] Hereinafter, exemplary embodiments of the present disclosure will be
15 described with reference to the accompanying drawings.
[0042] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network
20 architecture [100] includes a user equipment (UE) [102], a radio access network
(RAN) [104], 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
25 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
30 the person skilled in the art for implementing features of the present disclosure.
14

[0043] 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).
5 It consists of radio base stations and the radio access technologies that enable
wireless communication.
[0044] Access and Mobility Management Function (AMF) [106] is a 5G core
network function responsible for managing access and mobility aspects, such as UE
10 registration, connection, and reachability. It also handles mobility management
procedures like handovers and paging.
[0045] Session Management Function (SMF) [108] is a 5G core network
function responsible for managing session-related aspects, such as establishing,
15 modifying, and releasing sessions. It coordinates with the User Plane Function
(UPF) for data forwarding and handles IP address allocation and QoS enforcement.
[0046] Service Communication Proxy (SCP) [110] is a network function in the
5G core network that facilitates communication between other network functions
20 by providing a secure and efficient messaging service. It acts as a mediator for
service-based interfaces.
[0047] Authentication Server Function (AUSF) [112] is a network function in
the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
25
[0048] 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 can access only the slices for which they are authorized.
30
15

[0049] Network Slice Selection Function (NSSF) [116] is a network function
responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
5 [0050] 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.
[0051] Network Repository Function (NRF) [120] is a network function that
10 acts as a central repository for information about available network functions and
services. It facilitates the discovery and dynamic registration of network functions.
[0052] Policy Control Function (PCF) [122] is a network function responsible
for policy control decisions, such as QoS, charging, and access control, based on
15 subscriber information and network policies.
[0053] Unified Data Management (UDM) [124] is a network function that
centralizes the management of subscriber data, including authentication, authorization, and subscription information. 20
[0054] Application Function (AF) [126] is a network function that represents
external applications interfacing with the 5G core network to access network capabilities and services.
25 [0055] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS enforcement.
16

[0056] Data Network (DN) [130] refers to a network that provides data services
to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.
5 [0057] Charging Function [132] refers to a network function which is
responsible for accurately calculating and allocating charges for various services and resources used by subscribers.
[0058] FIG. 2 illustrates an exemplary block diagram of a computing device
10 [200] (also referred to herein as computer system [200]) upon which the features of
the present disclosure may be implemented in accordance with exemplary
implementation of the present disclosure. In an implementation, the computing
device [200] may also implement a method for managing data traffic utilising the
system. In another implementation, the computing device [200] itself implements
15 the method for managing data traffic using one or more units configured within the
computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
[0059] The computing device [200] may include a bus [202] or other
20 communication mechanism for communicating information, and a hardware
processor [204] coupled with bus [202] for processing information. The hardware
processor [204] may be, for example, a general purpose microprocessor. The
computing device [200] may also include a main memory [206], such as a random
access memory (RAM), or other dynamic storage device, coupled to the bus [202]
25 for storing information and instructions to be executed by the processor [204]. The
main memory [206] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
processor [204]. Such instructions, when stored in non-transitory storage media
accessible to the processor [204], render the computing device [200] into a special-
30 purpose machine that is customized to perform the operations specified in the
instructions. The computing device [200] further includes a read only memory
17

(ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204].
[0060] A storage device [210], such as a magnetic disk, optical disk, or solid-
5 state drive is provided and coupled to the bus [202] for storing information and
instructions. The computing device [200] may be coupled via the bus [202] to a display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [214], including
10 alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [202] for communicating information and command selections to the processor [204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling
15 cursor movement on the display [212]. This 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.
[0061] The computing device [200] may implement the techniques described
20 herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
and/or program logic which in combination with the computing device [200] causes
or programs the computing device [200] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the
computing device [200] in response to the processor [204] executing one or more
25 sequences of one or more instructions contained in the main memory [206]. Such
instructions may be read into the main memory [206] from another storage medium,
such as the storage device [210]. Execution of the sequences of instructions
contained in the main memory [206] causes the processor [204] to perform the
process steps described herein. In alternative implementations of the present
30 disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
18

[0062] The computing device [200] also may include a communication
interface [218] coupled to the bus [202]. The communication interface [218]
provides a two-way data communication coupling to a network link [220] that is
5 connected to a local network [222]. For example, the communication interface
[218] 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 [218] may be a local area network (LAN) card to provide a data
10 communication connection to a compatible LAN. Wireless links may also be
implemented. In any such implementation, the communication interface [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
15 [0063] The computing device [200] can send messages and receive data,
including program code, through the network(s), the network link [220] and the communication interface [218]. In the Internet example, a server [230] might transmit a requested code for an application program through the Internet [228], the ISP [226], the local network [222], the host [224], and the communication interface
20 [218]. The received code may be executed by the processor [204] as it is received,
and/or stored in the storage device [210], or other non-volatile storage for later execution.
[0064] The computing device [200] encompasses a wide range of electronic
25 devices capable of processing data and performing computations. Examples of
computing device [200] include, but are not limited only to, personal computers,
laptops, tablets, smartphones, servers, and embedded systems. The devices may
operate independently or as part of a network and can perform a variety of tasks
such as data storage, retrieval, and analysis. Additionally, computing device [200]
30 may include peripheral devices, such as monitors, keyboards, and printers, as well
19

as integrated components within larger electronic systems, showcasing their versatility in various technological applications.
[0065] Referring to FIG. 3, an exemplary block diagram of a system [300] for
5 managing data traffic, is shown, in accordance with the exemplary implementations
of the present disclosure. The system [300] comprises at least one policy control function (PCF) [122], at least one transceiver unit [302], at least one processing unit [304], and at least one storage unit [306]. Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated
10 below. As shown in FIG. 3, all units shown within the system should also be
assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [300] may be
15 in communication with the user device (may also referred herein as a UE). In
another implementation, the system [300] may reside in a server or a network entity.
[0066] The system [300] is configured for managing data traffic, with the help
of the interconnection between the components/units of the system [300].
20
[0067] The transceiver unit [302] is configured to receive from a Session
Management Function (SMF) [108] at a Policy Control Function (PCF) [122], a create session request comprising a media access control (MAC) Identifier (MAC ID) (alternatively referred to as HGW MAC ID herein) and a data network name
25 (DNN) parameter. This create session request is a request for creating or
establishing a call or data session between user devices (or user equipment), which may be in the form of session initiation protocol (SIP) message used to initiate a communication session, such as a voice or video call (such as, INVITE request). For example, a first user in possession of a user device UE A wants to connect with
30 a second user in possession of user device UE B, then the user may call using the
20

UE A to the second person at UE B. Thus, when the UE A initiates the call, the
SMF [108] sends a create session request to the PCF [122]. At the PCF [122], MAC
- ID of the user of the device UE A is identified. Similarly, PCF [122] identifies the
MAC – ID of the user of the device UE B. After identifying MAC – IDs of both
5 UE A and UE B, the PCF determines whether the users allowed to use that specific
service or not. It must be noted that the MAC – IDs of multiple devices are unique even if same SUPI is assigned to them in a scenario where are multiple devices are connected to single ODCPE having single SUPI.
10 [0068] Further, the processing unit [304] is configured to determine, at the PCF
[122], a valid MAC ID status associated with the MAC ID, based on the create session request. In an implementation, the valid MAC ID status associated with the MAC ID is determined by the processing unit [304] at the PCF [122] in an event a successful match associated with the MAC ID is determined by the processing unit
15 [304] based on a comparison of the MAC ID and a set of provisioned network data
at the PCF [122]. That is, a set of data comprising valid MAC IDs is already provisioned at the PCF [122] node/server. The processing unit [304] compares the received MAC ID, that is received with the create session request, with the already provisioned data comprising the valid MAC IDs. In case the received MAC ID is
20 one of the valid MAC IDs of the provisioned data at the PCF [122] server, then the
valid MAC ID status is determined by the processing unit [304]. Otherwise, in case the received MAC ID is not found among the valid MAC IDs of the provisioned data at the PCF [122] server, then the invalid MAC ID status may be determined by the processing unit [304].
25
[0069] Further, the processing unit [304] is configured to determine, at the PCF
[122], a positive authorisation status associated with the DNN parameter based on the valid MAC ID status. In an implementation, the positive authorisation status associated with the DNN parameter is determined by the processing unit [304] at
30 the PCF [122] in an event of a successful authorisation status associated with one
of the DNN parameter. Also, the session overload parameter and set of mandatory
21

parameters is determined by the processing unit based on a set of predefined
authorisation rules. The set of predefined authorization rules comprises at least one
of service subscription validation, data usage limits, device type restrictions,
roaming restrictions, time-based access control, location-based access control,
5 network congestion management, and security and compliance checks.
[0070] Further, the processing unit [304] is configured to determine, at the PCF
[122], a valid DNN parameter status associated with the DNN parameter based on the positive authorisation status. For this purpose of determining, at the PCF [122],
10 the valid DNN parameter status, in an implementation, the processing unit [304] is
configured to determine a successful DNN match status associated with the DNN parameter based on comparing the DNN parameter and a set of predefined session range parameter associated with a Charging Function (CHF) [132]. This means that the processing unit [304] analyses the DNN parameters to check whether it falls in
15 a range as reflected by a session range parameter. This session range parameter may
be provided by the CHF [132]. The session range parameter generally defines the scope or boundary of sessions that the CHF [132] can handle. This can involve Time-Based Range (specifying the duration of sessions that fall within certain time limits), Volume-Based Ranges (defining the range of data volume or usage that is
20 applicable for charging), Session Types (different types of sessions (e.g., voice,
video, data) may have different ranges or rules applied). In case the DNN parameter falls in this range as provided by the CHF [132], the DNN is a valid DNN, otherwise the DNN is an invalid DNN. Further, in this implementation, the processing unit [304] may determine a negative status associated with a current CHF [132] session
25 based on the successful DNN match. This negative status associated with a current
CHF [132] session means that there is no CHF [132] session already established. Also, in case a CHF [132] session is already established, then a new session cannot be created.
30 [0071] Further, in case the DNN is a valid DNN, and there is no CHF [132]
session already created, then the transceiver unit [302] is configured to transmit,
22

from the PCF [122] to the CHF [132], a spending limit create request comprising
the MAC ID. This spending limit create request is sent by a network function (NF)
service consumer to the CHF [132] to retrieve the status of policy counters available
at the CHF [132]. The message body of the spending limit create request message
5 may comprise information about a plurality of parameters such as, but not limited
to, MAC ID, Subscription Permanent Identifier (SUPI), notification correlation target address, General Public Subscription Identifier (GPSI) (optional), and event filter information (optional) including a list of policy counter identifiers. The NF service consumer may send an HTTP POST request representing the "Spending
10 Limit Retrieval Subscriptions", for retrieval of the policy counter status and
spending limit reporting. As known in the art, if the CHF [132] cannot successfully fulfil the received HTTP POST request due to an internal CHF [132] error or due to the error in the HTTP POST request, the CHF [132] may send the HTTP error response. Further, if the subscriber specified in the request is unknown to the CHF
15 [132], the CHF [132] may indicate in an HTTP "400 Bad Request" response the
cause for the rejection with the "cause" attribute set to "USER_UNKNOWN". If
the CHF [132] has no available policy counters specified for the subscriber, the
CHF [132] may indicate in an HTTP "400 Bad Request" response the cause for the
rejection with the "cause" attribute set to
20 "NO_AVAILABLE_POLICY_COUNTERS ". If one or more policy counters
specified in the request in the "policyCounterIds" attribute are unknown to the CHF [132[, and the CHF [132] may reject request with an HTTP "400 Bad Request" response the cause for the rejection with the "cause" attribute set to "UNKNOWN_POLICY_COUNTERS" and the unknown policy counter identifiers
25 within the "invalidParams" attribute. Otherwise, upon the reception of an HTTP
POST request the CHF [132] shall: (a) create a new subscription resource, which contains the list of the policy counters included in the "policyCounterIds" attribute, or if the "policyCounterIds" attribute is omitted, all the policy counters of the subscriber; (b) assign a subscriptionId; and (c) store the subscription resource.
30
23

[0072] Further, the transceiver unit [302] is configured to receive, at the PCF
[122] from the CHF [132], one or more policy counter identifiers (PCIDs)
associated with the MAC ID, based on the spending limit create request. A PCID is
a unique identifier assigned to a specific policy counter, which is a mechanism used
5 to track and manage resource usage or service consumption based on predefined
policies. The PCID defines the name, optional description, and default online charging server (OCS) value for which status can be received from the OCS server. After a PCID is defined, the PCID can be used in policies, i.e., charging and related policies. Here, for a subscriber, a set of policy counter IDs is requested from the
10 OCS. In an implementation, the processing unit [304] is configured to determine,
at the PCF [122], the PCC rule associated with the one or more PCIDs based on a set of predefined PCIDs at the PCF [122] and a predefined PCC determination rule. For example, the PCID 123A is associated with a subscriber. This PCID 123A is associated with certain rules. That is, PCC rules such as 100min. of VoIP call. Thus,
15 based on this PCID 123A, it is checked whether the subscriber has some minutes
balance left that the subscriber can use, or not. If the subscriber has balance minutes of VoIP call that can be used, the subscriber should be allowed to use the balance minutes of call. In another example, say, a user's subscription plan is "Premium" and is currently accessing data services. Thus, the action of the PCC rule associated
20 with the user's subscription plan may be allocation of high-speed data bandwidth
(e.g., up to 1 Gbps) for the duration of the data session. Further, the premium data rate charges may be applied as per the user's subscription plan, and the data usage of the user is tracked to ensure that the user does not exceed the agreed quota.
25 [0073] Further, the transceiver unit [302] is configured to transmit, at the PCF
[122] to the SMF [108], a Policy and Charging Control (PCC) rule associated with one or more PCIDs. In the above example of PCID 123A, the PCC rule is the 100 min. of VoIP call to be used by the subscriber. This PCC rule is transmitted by the PCF [122] to the SMF [108].
30
24

[0074] Further, the processing unit [304] is configured to manage, a data traffic
associated with the create session request based on the MAC ID and the PCC rule.
Thus, based on the above PCC rule, that is associated with the PCID, which is
further associated with the MAC ID, the data traffic is managed for the user. In an
5 example, a user’s subscription plan has an allocated internet data of 100MB be used,
and the user has already consumed the 100MB of internet data. Now, when the user
tries to establish a data session with another user, the create session request is sent
from SMF [108] to PCF [122]. Since the PCF [122] tracks/monitors the data usage
by the user, the PCF [122] is also aware about the limit and the usage of the internet
10 data. Thus, since the user has already consumed the allocated quota of internet data,
i.e., 100MB internet data, the PCF [122] based on the MAC ID, associated PCID and PCC rule for the user, does not allow the user to establish the data session, in accordance with the PCC rule, to manage the data traffic.
15 [0075] Referring to FIG. 4, an exemplary method flow diagram [400] for
managing data traffic, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [400] is performed by the system [300]. Also, as shown in FIG. 4, the method [400] starts at step [402].
20 [0076] At step 404, the method of the present disclosure comprises receiving,
by a transceiver unit [302], from a Session Management Function (SMF) [108] at a Policy Control Function (PCF) [122], a create session request comprising a MAC Identifier (MAC ID) and a Data Network name (DNN) parameter. This create session request is a request for creating or establishing a call or data session between
25 user devices (or user equipment), which may be in the form of session initiation
protocol (SIP) message used to initiate a communication session, such as a voice or video call (such as, INVITE request). For example, a first user in possession of a user device UE A wants to connect with a second user in possession of user device UE B, then the user may call using the UE A to the second person at UE B. Thus,
30 when the UE A initiates the call, the SMF [108] sends a create session request to
PCF [122]. At the PCF [122], MAC - ID of the user of the device UE A is identified.
25

Similarly, PCF [122] identifies the MAC – ID of the user of the device UE B. After
identifying MAC – IDs of both UE A and UE B, the PCF determines whether the
users allowed to use that specific service or not. It must be noted that the MAC –
IDs of multiple devices are unique even if same SUPI is assigned to them in a
5 scenario where are multiple devices are connected to single ODCPE having single
SUPI. Also, the terms MAC ID and HGW MAC ID are used interchangeably in the present disclosure.
[0077] At step 406, the method of the present disclosure comprises
10 determining, by a processing unit at the PCF [122], a valid MAC ID status
associated with the MAC ID, based on the create session request. In an implementation, the valid MAC ID status associated with the MAC ID is determined by the processing unit [304] at the PCF [122] in an event a successful match associated with the MAC ID is determined by the processing unit [304] based
15 on a comparison of the MAC ID and a set of provisioned network data at the PCF
[122]. That is, a set of data comprising valid MAC IDs is already provisioned at the PCF [122] node/server. The processing unit [304] compares the received MAC ID, that is received with the create session request, with the already provisioned data comprising the valid MAC IDs. In case the received MAC ID is one of the valid
20 MAC IDs of the provisioned data at the PCF [122] server, then the valid MAC ID
status is determined by the processing unit [304]. Otherwise, in case the received MAC ID is not found among the valid MAC IDs of the provisioned data at the PCF [122] server, then the invalid MAC ID status may be determined by the processing unit [304].
25
[0078] At step 408, the method of the present disclosure comprises
determining, by the processing unit at the PCF [122], a positive authorisation status associated with the DNN parameter based on the valid MAC ID status. In an implementation, the positive authorisation status associated with the DNN
30 parameter is determined by the processing unit [304] at the PCF [122] in an event
of a successful authorisation status associated with one of the DNN parameter.
26

Also, the session overload parameter and set of mandatory parameters is determined by the processing unit based on a set of predefined authorisation rules.
[0079] At step 410, the method of the present disclosure comprises
5 determining, by the processing unit at the PCF [122], a valid DNN parameter status
associated with the DNN parameter based on the positive authorisation status. For this purpose of determining, at the PCF [122], the valid DNN parameter status, in an implementation, the processing unit [304] is configured to determine a successful DNN match status associated with the DNN parameter based on
10 comparing the DNN parameter and a set of predefined session range parameter
associated with a Charging Function (CHF) [132]. This means that the processing unit [304] analyses the DNN parameters to check whether it falls in a range as reflected by a session range parameter. This session range parameter may be provided by the CHF [132]. The session range generally defines the scope or
15 boundary of sessions that the CHF [132] can handle. This can involve Time-Based
Range (specifying the duration of sessions that fall within certain time limits), Volume-Based Ranges (defining the range of data volume or usage that is applicable for charging), Session Types (different types of sessions (e.g., voice, video, data) may have different ranges or rules applied). In case the DNN parameter
20 falls in this range as provided by the CHF [132], the DNN is a valid DNN, otherwise
the DNN is an invalid DNN. Further, in this implementation, the processing unit [304] may determine a negative status associated with a current CHF [132] session based on the successful DNN match. This negative status associated with a current CHF [132] session means that there is no CHF [132] session already established.
25 Also, in case a CHF [132] session is already established, then a new session cannot
be created.
[0080] Further, in case the DNN is a valid DNN, and there is no CHF [132]
session already created, then at step 412, the method of the present disclosure
30 comprises transmitting, by the transceiver unit [302] from the PCF [122] to a
charging function (CHF) [132], a spending limit create request comprising the
27

MAC ID, based on the valid DNN parameter. This spending limit create request is
sent by a network function (NF) service consumer to the CHF [132] to retrieve the
status of policy counters available at the CHF [132]. The message body of the
spending limit create request message may comprise information about a plurality
5 of parameters such as, but not limited to, MAC ID, Subscription Permanent
Identifier (SUPI), notification correlation target address, General Public Subscription Identifier (GPSI) (optional), and event filter information (optional) including a list of policy counter identifiers. The NF service consumer may send an HTTP POST request representing the "Spending Limit Retrieval Subscriptions",
10 for retrieval of the policy counter status and spending limit reporting. As known in
the art, if the CHF [132] cannot successfully fulfil the received HTTP POST request due to an internal CHF [132] error or due to the error in the HTTP POST request, the CHF [132] may send the HTTP error response. Further, if the subscriber specified in the request is unknown to the CHF [132], the CHF [132] may indicate
15 in an HTTP "400 Bad Request" response the cause for the rejection with the "cause"
attribute set to "USER_UNKNOWN". If the CHF [132] has no available policy counters specified for the subscriber, the CHF [132] may indicate in an HTTP "400 Bad Request" response the cause for the rejection with the "cause" attribute set to "NO_AVAILABLE_POLICY_COUNTERS ". If one or more policy counters
20 specified in the request in the "policyCounterIds" attribute are unknown to the CHF
[132], and the CHF [132] may reject request with an HTTP "400 Bad Request" response the cause for the rejection with the "cause" attribute set to "UNKNOWN_POLICY_COUNTERS" and the unknown policy counter identifiers within the "invalidParams" attribute. Otherwise, upon the reception of an HTTP
25 POST request the CHF [132] shall: (a) create a new subscription resource, which
contains the list of the policy counters included in the "policyCounterIds" attribute, or if the "policyCounterIds" attribute is omitted, all the policy counters of the subscriber; (b) assign a subscriptionId; and (c) store the subscription resource.
30 [0081] At step 414, the method of the present disclosure comprises receiving,
by the transceiver unit [302] at the PCF [122] from the CHF [132], one or more
28

Policy counter Identifiers (PCIDs) associated with the MAC ID, based on the spending limit create request. A PCID is a unique identifier assigned to a specific policy counter, which is a mechanism used to track and manage resource usage or service consumption based on predefined policies. The PCID defines the name, optional description, and default online charging server (OCS) value for which status can be received from the OCS server. After a PCID is defined, the PCID can be used in policies, i.e., charging and related policies. Here, for a subscriber, a set of policy counter IDs is requested from the OCS. In an implementation, the processing unit [304] is configured to determine, at the PCF, the PCC rule associated with the one or more PCIDs based on a set of predefined PCIDs at the PCF [122] and a predefined PCC determination rule. For example, the PCID 123A is associated with a subscriber. This PCID 123A is associated with certain rules. That is, PCC rules such as 100min. of VoIP call. Thus, based on this PCID 123A, it is checked whether the subscriber has some minutes balance left that the subscriber can use, or not. If the subscriber has balance minutes of VoIP call that can be used, the subscriber should be allowed to use the balance minutes of call. In another example, say, a user's subscription plan is "Premium" and is currently accessing data services. Thus, the action of the PCC rule associated with the user's subscription plan may be allocation of high-speed data bandwidth (e.g., up to 1 Gbps) for the duration of the data session. Further, the premium data rate charges may be applied as per the user's subscription plan, and the data usage of the user is tracked to ensure that the user does not exceed the agreed quota.
[0082] At step 416, the method of the present disclosure comprises
transmitting, by the transceiver unit [302] at the PCF [122] to the SMF [108], a Policy and Charging Control (PCC) rule associated with one or more PCIDs. In the above example of PCID 123A, the PCC rule is the 100 min. of VoIP call to be used by the subscriber. This PCC rule is transmitted by the PCF [122] to the SMF [108].
[0083] At step 418, the method of the present disclosure comprises managing,
by the processing unit [304], a data traffic associated with the create session request

based on the MAC ID and the PCC rule. Thus, based on the above PCC rule, that is associated with the PCID, which is further associated with the MAC ID, the data traffic is managed for the user. In an example, a user’s subscription plan has an allocated internet data of 100MB be used, and the user has already consumed the 100MB of internet data. Now, when the user tries to establish a data session with another user, the create session request is sent from SMF [108] to PCF [122]. Since the PCF [122] tracks/monitors the data usage by the user, the PCF [122] is also aware about the limit and the usage of the internet data. Thus, since the user has already consumed the allocated quota of internet data, i.e., 100MB internet data, the PCF [122] based on the MAC ID, associated PCID and PCC rule for the user, does not allow the user to establish the data session, in accordance with the PCC rule, to manage the data traffic. The method terminates at step 420.
[0084] Referring to FIG. 5 which illustrates an exemplary scenario flow
diagram for managing data traffic, in accordance with exemplary implementations of the present disclosure. As shown in FIG. 5, at 502, the SMF [108] sends session create request to PCF [122]. This session create request comprises the MAC ID, that is, the HGW MAC ID (or MAC ID of the home gateway of the user. Further, the PCF [122] sends the corresponding PCC rule to SMF [108] at 504. Further, at 506, two conditions are checked: (1) CHF [132] Query Condition, which checks whether the DNN, for which CHF [132] Session is established, falls in the session range of the CHF [132]; and (2) Sy Race Condition, which checks whether a CHF [132] Session is already in progress (in which case, a new session is not initiated), or not. In case the DNN falls within the session range of CHF [132], and no CHF [132] session is already existing, then the CHF [132] creates the session and sends create response with PCIDs associated with the MAC ID, to PCF [122], at 508.
[0085] The present disclosure further discloses a non-transitory computer
readable storage medium storing instructions for managing data traffic. The instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit [302] of the system to receive, from a Session

Management Function (SMF) [108] at a Policy Control Function (PCF) [122], a create session request comprising a MAC Identifier (MAC ID) and a Data Network name (DNN) parameter. Further, the executable code, when executed, causes a processing unit [304] of the system to determine, at the PCF [122], a valid MAC ID status associated with the MAC ID, based on the create session request. Further, the executable code, when executed, causes the processing unit [304] of the system to determine, at the PCF [122], a positive authorisation status associated with the DNN parameter based on the valid MAC ID status. Further, the executable code, when executed, causes the processing unit [304] of the system to determine, at the PCF [122], a valid DNN parameter status associated with the DNN parameter based on the positive authorisation status. Further, the executable code, when executed, causes the transceiver unit [302] of the system to transmit, from the PCF [122] to a charging function (CHF) [132], a spending limit create request comprising the MAC ID, based on the valid DNN parameter. Further, the executable code, when executed, causes the transceiver unit [302] of the system to receive, at the PCF [122] from the CHF [132], one or more Policy counter Identifiers (PCIDs) associated with the MAC ID, based on the spending limit create request. Further, the executable code, when executed, causes the transceiver unit [302] of the system to transmit, at the PCF [122] to the SMF [108], a Policy and Charging Control (PCC) rule associated with one or more PCIDs. Further, the executable code, when executed, causes the processing unit [304] of the system to manage, a data traffic associated with the create session request based on the MAC ID and the PCC rule.
[0086] As is evident from the above, the present disclosure provides a
technically advanced solution for managing data traffic. The present solution provides unique MAC ID to home gateway to identify each user with their corresponding MAC address/identifier (ID). Further, the present solution provides for managing data traffic cycle of Home Gateways based on HGW-MAC ID.
[0087] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and

that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations 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.

We Claim:
1. A method for managing data traffic, the method comprising:
- receiving, by a transceiver unit [302], from a Session Management Function (SMF) [108] at a Policy Control Function (PCF) [122], a create session request comprising a MAC Identifier (MAC ID) and a Data Network name (DNN) parameter;
- determining, by a processing unit [304] at the PCF [122], a valid MAC ID status associated with the MAC ID, based on the create session request;
- determining, by the processing unit [304] at the PCF [122], a positive authorisation status associated with the DNN parameter based on the valid MAC ID status;
- determining, by the processing unit [304] at the PCF [122], a valid DNN parameter status associated with the DNN parameter based on the positive authorisation status;
- transmitting, by the transceiver unit [302] from the PCF [122] to a charging function (CHF) [132], a spending limit create request comprising the MAC ID, based on the valid DNN parameter;
- receiving, by the transceiver unit [302] at the PCF [122] from the CHF [132], one or more Policy counter Identifiers (PCIDs) associated with the MAC ID, based on the spending limit create request;
- transmitting, by the transceiver unit [302] at the PCF [122] to the SMF [108], a Policy and Charging Control (PCC) rule associated with one or more PCIDs; and
- managing, by the processing unit [304], a data traffic associated with the create session request based on the MAC ID and the PCC rule.
2. The method as claimed in claim 1, wherein the valid MAC ID status
associated with the MAC ID is determined by the processing unit [304] at the

PCF [122] in an event a successful match associated with the MAC ID is determined by the processing unit [304], based on a comparison of the MAC ID and a set of provisioned network data at the PCF [122].
3. The method as claimed in claim 1, wherein the positive authorisation status associated with the DNN parameter is determined by the processing unit [304] at the PCF [122] in an event a successful authorisation status associated with one of the DNN parameter, and wherein a session overload parameter and a set of mandatory parameters is determined by the processing unit based on a set of predefined authorisation rules.
4. The method as claimed in claim 1, wherein the method comprises determining, by the processing unit [304] at the PCF [122], the PCC rule associated with the one or more PCIDs based on a set of predefined PCIDs at the PCF [122] and a predefined PCC determination rule.
5. The method as claimed in claim 1, wherein the MAC ID further comprises at least one of a session overload parameter, and a set of mandatory parameters.
6. The method as claimed in claim 1, wherein the step of determining, by the processing unit [304] at the PCF [122], the valid DNN parameter status comprises:

- determining a successful DNN match status associated with the DNN parameter based on comparing the DNN parameter and a set of predefined session range parameter associated with a Charging Function (CHF) [132]; and
- determining a negative status associated with a current CHF [132] session based on the successful DNN match.
7. A system for managing data traffic, the system comprising:

- a transceiver unit [302] configured to:
• receive, from a Session Management Function (SMF) [108] at a
Policy Control Function (PCF) [122], a create session request
comprising a MAC Identifier (MAC ID) and a Data Network name
(DNN) parameter;
- a processing unit [304] configured to:
• determine, at the PCF [122], a valid MAC ID status associated with the MAC ID, based on the create session request;
• determine, at the PCF [122], a positive authorisation status associated with the DNN parameter based on the valid MAC ID status;
• determine, at the PCF [122], a valid DNN parameter status associated with the DNN parameter based on the positive authorisation status;
- the transceiver unit [302] configured to:
• transmit, from the PCF [122] to a charging function (CHF) [132], a spending limit create request comprising the MAC ID, based on the valid DNN parameter;
• receive, at the PCF [122] from the CHF [132], one or more Policy counter Identifiers (PCIDs) associated with the MAC ID, based on the spending limit create request;
• transmit, at the PCF [122] to the SMF [108] , a Policy and Charging Control (PCC) rule associated with one or more PCIDs; and
- the processing unit [304] configured to:
• manage, a data traffic associated with the create session request
based on the MAC ID and the PCC rule.
8. The system as claimed in claim 7, wherein the valid MAC ID status associated with the MAC ID is determined by the processing unit [304] at the PCF [122]

in an event a successful match associated with the MAC ID is determined by the processing unit [304] based on a comparison of the MAC ID and a set of provisioned network data at the PCF [122].
9. The system as claimed in claim 7, wherein the positive authorisation status
associated with the DNN parameter is determined by the processing unit
[304] at the PCF [122] in an event of a successful authorisation status
associated with one of the DNN parameters, and wherein a session overload
parameter and a set of mandatory parameters are determined by the
processing unit [304] based on a set of predefined authorisation rules.
10. The system as claimed in claim 7, wherein the processing unit [304] is configured to determine, at the PCF [122], the PCC rule associated with the one or more PCIDs based on a set of predefined PCIDs at the PCF [122] and a predefined PCC determination rule.
11. The system as claimed in claim 7, wherein the MAC ID further comprises at least one of a session overload parameter, and a set of mandatory parameters.
12. The system as claimed in claim 7, wherein to determine, at the PCF [122], the valid DNN parameter status, the processing unit [304] is configured to:

- determine a successful DNN match status associated with the DNN parameter based on comparing the DNN parameter and a set of predefined session range parameter associated with a Charging Function (CHF) [132]; and
- determine a negative status associated with a current CHF [132] session based on the successful DNN match.