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 A CONFIGURATION-BASED
MANAGEMENT OF A PROCEDURE REQUEST”
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 A CONFIGURATION-BASED MANAGEMENT OF
A PROCEDURE REQUEST
TECHNICAL FIELD
5
[0001] Embodiments of the present disclosure generally relate to network performance
management systems. More particularly, embodiments of the present disclosure relate to a
configuration-based management of a procedure request at a network function (NF).
10 BACKGROUND
[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
15 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
20 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
25 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.
30
[0004] Moreover, the 5G core networks are based on service-based architecture (SBA) that is
centered around network function (NF) services. 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)
3
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.
Also, certain NF related details are captured at the NRF whenever an NF comes up with a
5 planned event or first-time commissioning.
[0005] Also, in 5G network or in fact in any network, any network node handles multiple
procedures. For instance, for the AMF node, there are procedures like UE Initiated
Registration, UE initiated PDU Establishment, UE Initiated Deregistration, RAN initiated
10 Handover, AN Release, UDM Initiated Deregistration, SMF initiated PDU Session release,
PCF initiated policy update request, NWDAF initiated Subscription request, GMLC initiated
Location Service request and many more. These procedures are not only initiated by one
network node, but these can be initiated by many network nodes. E.g., at AMF, many network
nodes can initiate procedures like UDM, NG-RAN, MME, SMF, PCF, UE, NWDAF, GMLC,
15 Peer AMF, etc. Moreover, due to some error condition or due to some failure, these procedures
can be initiated in sequential order or parallel order, or in many permutations and combinations.
In production environment there is no fix order in which procedures can land at any node, there
is no fix number of parallelism means how many procedures can be initiated in parallel, there
is no fix wait time for any procedure to get finished means a procedure can take seconds also
20 to get completed. Practically there are so many variables in the network so it cannot be
predicted what kind of permutation or combination will happen in network for procedures at
any node. So, the limitation is any node can initiate a solution to handle some permutations and
combinations, but it is not possible to cover everything in said solution. And some
combinations are not possible now, but they can be realistic in future. That is a very problematic
25 thing to handle in the network. Further, when these type of issues or anomalies arise, then there
is a requirement to handle those cases and provide a solution for them. Also, some of these
kinds of anomalies are not explained in the standard.
[0006] Moreover, if these types of issues come at any network node, and if network node is
30 not aware about the new kind of collision and/or precedence resolution then some procedures
may fail and due to these failures end-users of the network have a bad experience. E.g., in
AMF, due to these failures, may be a user is not able to register on the network again, or the
user might not be able to establish a new PDU session or user voice call can get disconnected,
etc. Also, most importantly may be network node is busy in handling some less important
4
procedure, but the network has initiated some more important procedure, this new procedure
might be waiting for the old less important procedure to finish first. Therefore, these
precedence related problems could also occur in the network. Practical example at AMF, when
5G to 4G handover procedure is ongoing and it is in last stage, then in parallel RAN is sending
5 AN release request (procedure) to AMF. Theoretically, this case shall never happen. However,
it has been observed to happen in production due to some issue in any network node.
[0007] To solve these kinds of problems no solution exists currently and there is a requirement
in the art to provide a configuration-based solution where all the known permutation and
10 combinations of all procedures for any network node can be mentioned with its known solution
to handle collision or precedence problem. And there is a requirement in the art to provide the
solution for the collision and precedence related problems which are not known currently but
will be learnt in future. The present disclosure aims to address the above stated and the other
such limitations of the existing arts.
15
SUMMARY
[0008] 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
20 not intended to identify the key features or the scope of the claimed subject matter.
[0009] An aspect of the present disclosure may relate to a method for a configuration-based
management of a procedure request at a network function (NF). The method includes reading,
by a processing unit, a configuration file associated with the NF. The method further includes
25 receiving, by a transceiver unit, the procedure request at the NF, wherein the procedure request
is associated with a user equipment (UE). Furthermore, the method encompasses fetching, by
a retrieval unit, a set of data associated with the NF, wherein the set of data is fetched from a
database associated with the NF. The method further includes determining, by the processing
unit, one of a presence and an absence of one or more procedures running for the UE based on
30 the fetched set of data. Further, the method includes processing, by the processing unit, the
procedure request upon determining the absence of the one or more procedures running for the
UE.
5
[0010] In an exemplary aspect of the present disclosure, the procedure request comprises at
least one of a UE Initiated Registration, a Protocol Data Unit (PDU) Establishment, a
Deregistration, a Radio Access Network (RAN) initiated Handover, a Unified Data
Management (UDM) Initiated Deregistration, a Session Management Function (SMF) initiated
5 PDU Session release, a Policy Control Function (PCF) initiated policy update request.
[0011] In an exemplary aspect of the present disclosure, the reading of the configuration file
associated with the NF, is initiated by the processing unit during initialisation of the NF. In an
exemplary aspect of the present disclosure, after reading of the configuration file, by the
10 processing unit, the configuration file is stored in an in-memory associated with the NF.
[0012] In an exemplary aspect of the present disclosure, the configuration file stored in the inmemory associated with the NF, comprises one or more key-value pair, wherein each keyvalue pair from the one or more key-value pair comprises a key, and a corresponding value,
15 wherein the corresponding value further comprises a data value and an action.
[0013] In an exemplary aspect of the present disclosure, the set of data comprises at least one
of name of one or more running procedures for the UE, one or more procedures present in a
pending queue for the UE, Connection Management (CM) state of the UE, one or more flags
20 set for the UE, and name of an active timer running for the UE.
[0014] In an exemplary aspect of the present disclosure, upon determining the presence of one
or more procedures running for the UE, the method further comprises determining, by the
processing unit, one of a presence and an absence of at least one procedure in the pending
25 queue for the NF.
[0015] In an exemplary aspect of the present disclosure, upon determining the absence of the
at least one procedure in the pending queue for the NF, the method further comprises,
searching, by the processing unit, for one of a presence and an absence of a first matching key
30 in the configuration file, for a set of first key-value pair associated with the set of data fetched
from the database.
[0016] In an exemplary aspect of the present disclosure, upon determining the presence of the
first matching key in the configuration file, for the set of first key-value pair, the method further
6
includes fetching, by the processing unit, a corresponding data value and a corresponding
action of the first matching key from the configuration file. The method further encompasses
determining, by the processing unit, whether the corresponding data value of the first key-value
pair matches with the corresponding data value of the first matching key present in the
5 configuration file. Furthermore, the method encompasses performing, by the processing unit,
the corresponding action of the first matching key present in the configuration file, upon
determining that the corresponding data value of the first key-value pair matches with the
corresponding data value of the first matching key. Further, the method includes processing,
by the processing unit, the procedure request based on at least a default handling mechanism
10 associated with the NF, upon determining that the corresponding data value of the first keyvalue pair does not match with the corresponding data value of the first matching key.
[0017] In an exemplary aspect of the present disclosure, upon determining the absence of the
first matching key in the configuration file, for the set of first key-value pair, the method
15 comprises, processing, by the processing unit, the procedure request based on at least the
default handling mechanism associated with the NF.
[0018] In an exemplary aspect of the present disclosure, upon determining the presence of the
at least one procedure in the pending queue for the NF, the method comprises, searching, by
20 the processing unit, one of a presence and an absence of a second matching key in the
configuration file, for a set of second key-value pair associated with the set of data fetched
from the database.
[0019] In an exemplary aspect of the present disclosure, upon determining the presence of the
25 second matching key in the configuration file, for the set of second key-value pair, the method
includes fetching, by the processing unit, a corresponding data and a corresponding action of
the second matching key present in the configuration file. The method further includes
determining, by the processing unit, whether the data value of the second key-value pair
matches with the corresponding data of the second matching key present in the configuration
30 file. Furthermore, the method encompasses performing, by the processing unit, the
corresponding action of the second matching key present in the configuration file, upon
determining that the data value of the second key-value pair matches with the corresponding
data value of the second matching key.
7
[0020] In an exemplary aspect of the present disclosure, upon determining the absence of the
matching key in the configuration file, for the set of second key-value pair, the method, further
comprises, searching, by the processing unit, one of a presence and an absence of a third
matching key in the configuration file, for a set of third key-value pair associated with the set
5 of data fetched from the database.
[0021] In an exemplary aspect of the present disclosure, upon determining the presence of the
third matching key in the configuration file, for the set of third key-value pair, the method
includes fetching, by the processing unit, a corresponding data value and a corresponding
10 action of the third matching key present in the configuration file. The method further includes
determining, by the processing unit, whether the data value of the third key-value pair matches
with the corresponding data value of the third matching key present in the configuration file.
Furthermore, the method includes performing, by the processing unit, the corresponding action
of the third matching key present in the configuration file, upon determining that the data value
15 of the third key-value pair matches with the corresponding data value of the third matching
key. Furthermore, the method encompasses processing, by the processing unit, the procedure
request, based on at least the default handling mechanism associated with the NF, upon
determining that the data value of the third key-value pair does not match with the
corresponding data value of the third matching key.
20
[0022] In an exemplary aspect of the present disclosure, upon determining the absence of the
third matching key in the configuration file, for the set of third key-value pair, the method
comprises, processing, by the processing unit, the procedure request based on at least the
default handling mechanism associated with the NF.
25
[0023] In an exemplary aspect of the present disclosure, the configuration file associated with
the NF, is updated, by the processing unit, based on a change in the one or more key-value pair
stored in the configuration file.
30 [0024] In an exemplary aspect of the present disclosure, the change in the one or more keyvalue pair stored in the configuration file, is performed through a command line interface (CLI)
at the NF.
8
[0025] Another aspect of the present disclosure may relate to a system for a configurationbased management of a procedure request at a network function (NF). The system includes a
processing unit, configured to read, a configuration file associated with the NF. The system
further includes a transceiver unit, configured to receive, the procedure request at the NF,
5 wherein the procedure request is associated with a user equipment (UE). Furthermore, the
system includes a retrieval unit, configured to fetch, a set of data associated with the NF,
wherein the set of data is fetched from a database associated with the NF. The system further
includes the processing unit, configured to determine, one of a presence and an absence of one
or more procedures running for the UE, based on the fetched set of data. Further, the system
10 includes the processing unit, configured to process the procedure request upon determination
the absence of the one or more procedures running for the UE.
[0026] Yet another aspect of the present disclosure may relate to a non-transitory computer
readable storage medium storing instructions for a configuration-based management of a
15 procedure request at a network function (NF), the instructions include executable code which,
when executed by one or more units of a system, causes a processing unit of the system to read,
a configuration file associated with the NF. The instructions further include executable code
which, when executed causes a transceiver unit of the system to receive, the procedure request
at the NF, wherein the procedure request is associated with a user equipment (UE). The
20 instructions further include executable code which, when executed causes a retrieval unit of
the system to fetch, a set of data associated with the NF, wherein the set of data is fetched from
a database associated with the NF. The instructions further include executable code which,
when executed causes the processing unit of the system to: determine, one of a presence and
an absence of one or more procedures running for the UE, based on the fetched set of data; and
25 to process the procedure request upon determination the absence of the one or more procedures
running for the UE.
OBJECTS OF THE INVENTION
30 [0027] Some of the objects of the present disclosure, which at least one embodiment disclosed
herein satisfies are listed herein below.
9
[0028] It is an object of the present disclosure to provide a system and a method for collision
and precedence handling framework for NFs.
[0029] It is another object of the present disclosure to provide a configurable framework to
5 help in resolving all the known collisions of procedures currently happening in network on any
network node.
[0030] It is also an object of the present disclosure to provide a solution that can help in
resolving the precedence of the procedures in any network node.
10
[0031] It is another object of the present disclosure to provide a solution that can resolve
permutations and combinations of all the procedure, which are still unknown, that might
happen in network node in future, by just changing the configuration of that network node,
without doing any changes such as code changes etc. in program or software.
15
[0032] It is yet another object of the present disclosure to provide a solution can help in
changing the current behavior of the network node to resolve any type of procedure collisions
and precedence, with just change in configuration.
20 DESCRIPTION OF THE DRAWINGS
[0033] 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.
25 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
30 includes disclosure of electrical components or circuitry commonly used to implement such
components.
10
[0034] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core
(5GC) network architecture.
5 [0035] 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
implementation of the present disclosure.
[0036] FIG. 3 illustrates an exemplary block diagram of a system for a configuration-based
10 management of a procedure request at a network function (NF), in accordance with exemplary
implementations of the present disclosure.
[0037] FIG. 4 illustrates a method flow diagram for a configuration-based management of a
procedure request at a network function (NF) in accordance with exemplary implementations
15 of the present disclosure.
[0038] FIG. 5 illustrates an exemplary implementation of the method for a configuration-based
management of a procedure request at a network function (NF) in accordance with exemplary
implementations of the present disclosure.
20
[0039] The foregoing shall be more apparent from the following more detailed description of
the disclosure.
DETAILED DESCRIPTION
25
[0040] 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 may each be used
30 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.
11
[0041] 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
5 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.
[0042] Specific details are given in the following description to provide a thorough
10 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 [0043] 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 parallel or concurrently. In addition, the order of the
operations may be re-arranged. A process is terminated when its operations are completed but
20 could have additional steps not included in a figure.
[0044] 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
25 “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
30 to the term “comprising” as an open transition word—without precluding any additional or
other elements.
[0045] 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
12
instructions. A 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 (Digital Signal Processing) DSP core, a controller, a
microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array
5 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 or
processing unit is a hardware processor.
10 [0046] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smartdevice”, “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
15 to, a mobile phone, smart 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 at least one of a transceiver unit, a
processing unit, a storage unit, a detection unit and any other such unit(s) which are required
20 to implement the features of the present disclosure.
[0047] As used herein, “storage unit” or “memory unit” refers to a machine or computerreadable 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
25 memory (“ROM”), random access memory (“RAM”), 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.
30 [0048] 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
13
or more modules or one or more units with each other, which also includes the methods,
functions, or procedures that may be called.
[0049] All modules, units, components used herein, unless explicitly excluded herein, may be
5 software modules or hardware processors, the processors being a general-purpose processor, a
special purpose processor, a conventional processor, 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.
10
[0050] 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.
15
[0051] As discussed in the background section, the current known solutions of collision and
precedence handling for NFs have several shortcomings. The present disclosure aims to
overcome the above-mentioned and other existing problems in this field of technology by
providing a collision and precedence handling framework for NFs. Mainly that, the present
20 disclosure discloses a solution that implements a configuration-based process/technique where
all the known permutation and combinations of all procedures for any network node can be
mentioned, and a solution can be configured to that combination. The present solution proposes
that when some new anomaly happens means some new permutation or combination gets
generated in network for any network node, then there is only the requirement to mention that
25 case in the configuration, and that node will get an update about that new configuration change,
and that network node will start handling the new anomaly as defined in configuration. In this
way, there is no need for changes such as code changes in any node’s process/technique, this
new handling can be configured in that node’s configuration, and it will start working. The
solution as disclosed in the present disclosure is generic in nature and can be used in any
30 network node.
14
[0052] 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 architecture [100] includes a user equipment
(UE) [102], a radio access network (RAN) [104], a Session Management Function (SMF)
5 [106], an access and mobility management function (AMF) [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
10 (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.
15 [0053] The 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.
20 [0054] The Session Management Function (SMF) [106] 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) for data forwarding and
handles IP address allocation and QoS enforcement.
25 [0055] The Access and Mobility Management Function (AMF) [108] is a 5G core network
function responsible for managing access and mobility aspects, such as UE registration,
connection, and reachability. It also handles mobility management procedures like handovers
and paging.
30 [0056] The 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.
15
[0057] The 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.
5
[0058] The 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.
10 [0059] The 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.
[0060] The Network Exposure Function (NEF) [118] is a network function that exposes
15 capabilities and services of the 5G network to external applications, enabling integration with
third-party services and applications.
[0061] The 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
20 the discovery and dynamic registration of network functions.
[0062] The 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.
25
[0063] The Unified Data Management (UDM) [124] is a network function that centralizes the
management of subscriber data, including authentication, authorization, and subscription
information.
30 [0064] The Application Function (AF) [126] is a network function that represents external
applications interfacing with the 5G core network to access network capabilities and services.
16
[0065] The User Plane Function (UPF) [128] is a network function responsible for handling
user data traffic, including packet routing, forwarding, and QoS enforcement.
[0066] The Data Network (DN) [130] refers to a network that provides data services to user
5 equipment (UE) in a telecommunications system. The data services may include but are not
limited to Internet services, private data network related services.
[0067] FIG. 2 illustrates an exemplary block diagram of a computing device [200] upon which
the features of the present disclosure may be implemented in accordance with exemplary
10 implementation of the present disclosure. In an implementation, the computing device [200]
may also implement a method for a configuration-based management of a procedure request at
a network function (NF) utilising the system. In another implementation, the computing device
[200] itself implements the method for a configuration-based management of a procedure
request at a network function (NF) using one or more units configured within the computing
15 device [200], wherein said one or more units are capable of implementing the features as
disclosed in the present disclosure.
[0068] The computing device [200] may include a bus [202] or other communication
mechanism for communicating information, and a hardware processor [204] coupled with bus
20 [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] 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
25 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-purpose machine that is customized to
perform the operations specified in the instructions. The computing device [200] further
includes a read only memory (ROM) [208] or other static storage device coupled to the bus
30 [202] for storing static information and instructions for the processor [204].
17
[0069] A storage device [210], such as a magnetic disk, optical disk, or solid-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
5 (OLED) display, etc. for displaying information to a computer user. An input device [214],
including 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
10 the processor [204], and for controlling cursor movement on the display [212]. 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.
[0070] The computing device [200] may implement the techniques described herein using
15 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 sequences of one or more instructions contained in the main memory
20 [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 disclosure, hard-wired circuitry may be
used in place of or in combination with software instructions.
25
[0071] 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 connected to a local network [222]. For example, the
communication interface [218] may be an integrated services digital network (ISDN) card,
30 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 communication connection to a
compatible LAN. Wireless links may also be implemented. In any such implementation, the
18
communication interface [218] sends and receives electrical, electromagnetic or optical signals
that carry digital data streams representing various types of information.
[0072] The computing device [200] can send messages and receive data, including program
5 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 [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
10 execution.
[0073] The computing device [200] may reside in a system as explained in FIG. 3. In one
implementation, the computing device [200] may be associated with the system of FIG. 3.
15 [0074] Referring to FIG. 3, an exemplary block diagram of a system [300] for a configurationbased management of a procedure request at a network function (NF), is shown, in accordance
with the exemplary implementations of the present disclosure. The system [300] comprises at
least one processing unit [302], at least one transceiver unit [304], at least one retrieval unit
[306], and at least one database [308]. The system [300] is in communication with at least one
20 user equipment [310]. Also, all of the components/ units of the system [300] are assumed to be
connected to each other unless otherwise indicated below. As shown in the figures 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
25 features of the present disclosure. Further, in an implementation, the system [300] may be
present in a user device to implement the features of the present disclosure. The system [300]
may be a part of the user device / or may be independent of but 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. In yet another implementation, the system [300] may
30 reside partly in the server/ network entity and partly in the user device.
19
[0075] 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
5 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.
10
[0076] In an implementation of the present disclosure, in the 5th generation core network a
single network node handles multiple processes. For instance, on the AMF node, the multiple
processes include but may not be limited to a UE [310] initiated registration, a PDU
Establishment, a deregistration, a RAN initiated handover, AN Release, a UDM initiated
15 deregistration, an SMF initiated PDU session release, a PCF initiated policy update request,
and the like. The PDU establishment refers to a communication link between the UE [310] and
the 5th generation core network. The AN release refers to release of logical NG-AP signalling
connection for the UE [310] between the RAN [104] and the AMF [108] and associated User
Plane connections and RAN signalling connection between the UE [310] and the RAN [104]
20 and the associated RAN resources. The AN release may be performed by either the AMF [108]
or the RAN [104]. The UDM [124] initiated deregistration refers to initiation of the
deregistration procedure by the UDM [124], for instance, when the UE [310] is registered to
the AMF [108] which does not support Closed Access Group (CAG) feature and CAG
subscription of the UE [310] changes and it is allowed to access the 5GS via CAG cell(s) only.
25 The UDM [124] may also initiate deregistration when the UE [310] moves to different AMF
within a peer AMF. The SMF initiated PDU session release refers to initiation of the PDU
session release by the SMF based on a request from the UDM, based on a notification from the
AMF [108] that the UE [310] is out of network area, based on a notification by the RAN [104]
that the PDU session resource establishment has failed, and the like. The PCF initiated policy
30 update request refers to updating of the policies associated with the PDU session. Any of the
network nodes may initiate the multiple processes including but may not be limited to UDM,
NG-RAN, Mobile Management Entity (MME), SMF, PCF, UE, Peer AMF, at the AMF. The
Unified Data Management (UDM) [124] is a network function that centralizes the management
20
of subscriber data, including authentication, authorization, and subscription information. The
NG-RAN comprises of a set of gNBs connected to the 5th generation core network through an
NG interface. The NG-RAN may transmit and receive data between the UE [310] and the core
network. The MME is a 4G network function responsible for user registration, session
5 management, and the like. The Session Management Function (SMF) [106] 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) for data
forwarding and handles IP address allocation and QoS enforcement. The Policy Control
Function (PCF) [122] is a network function responsible for policy control decisions, such as
10 QoS, charging, and access control, based on subscriber information and network policies. Any
network node may write/use a code to handle some permutations and combinations, but it is
not possible to cover everything in code and may be missed. Some procedures may fail, and
end user of the network will have bad experience. For instance, in AMF, due to these failures,
a user is not able to register on the network, or user might not be able to establish a PDU session
15 or user voice call can get disconnected. To solve such problems, the system [300] for a
configuration-based management is introduced.
[0077] The system [300] is configured for a configuration-based management of a procedure
request at a network function (NF), with the help of the interconnection between the
20 components/units of the system [300].
[0078] The system [300] includes a processing unit [302]. The processing unit [302] is
configured to read a configuration file associated with the NF. The reading of the configuration
file associated with the NF, is initiated by the processing unit [302] during initialisation of the
25 NF. After reading of the configuration file, by the processing unit [302], the configuration file
is stored in an in-memory associated with the NF. The in-memory associated with the NF refers
to the storage of the NF on which the procedure request is taking place. For instance, in one
implementation, if the network function is the AMF [108], the configuration file will be stored
at the AMF [108]. If the procedure request is for the SMF [106], the configuration file may be
30 stored at the SMF [106].
[0079] The configuration file stored in the in-memory associated with the NF, comprises one
or more key-value pair. Each key-value pair from the one or more key-value pair comprises a
key, and a corresponding value. The corresponding value further comprises a data value and
21
an action. The configuration file associated with the NF, is updated, by the processing unit
[302], based on a change in the one or more key-value pair stored in the configuration file. The
change in the one or more key-value pair stored in the configuration file, is performed through
a command line interface (CLI) at the NF.
5
[0080] In an implementation of the present disclosure, the processing unit [302] may require
the configuration file when a communication is initiated in a network. The configuration file
plays an important part in the 5
th generation core network for deployment and management of
network functions. The configuration file includes but may not be limited to a network
10 parameter, a security parameter, and other operational details.
[0081] The network parameters include an IP address, a network interface, and the like. The
security parameter includes encryption keys, and the like to secure the network. The processing
unit [302] may store the in-memory in the form of one or more key-value pair. The one or more
15 key-value pair refers to a type of data representation used in the configuration file. The one or
more key-value pair is a unique identifier where the corresponding value is the data associated
with the key. The corresponding value further includes the data value and the action associated
with the data value. The processing unit [302] may change the one or more key-value pair
through the CLI. The processing unit [302] may update the configuration file based on the
20 change in the one or more key-value pair. For instance, the processing unit [302] is configured
to enable the functionality of the system [300] with respect to the AMF [108].
[0082] The transceiver unit [304] is configured to receive a procedure request at the NF. The
procedure request is associated with a user equipment (UE) [310]. The procedure request
25 comprises at least one of a UE initiated registration, a Protocol Data Unit (PDU) establishment,
a deregistration, a Radio Access Network (RAN) initiated handover, a Unified Data
Management (UDM) initiated deregistration, a Session Management Function (SMF) initiated
PDU Session release, a Policy Control Function (PCF) initiated policy update request. In an
implementation of the present disclosure, the transceiver unit [304] receives a procedure
30 request. The procedure request may be sent by a user. The user may be a network node operator.
22
[0083] The transceiver unit [304] may be associated with the retrieval unit [306]. Further, the
retrieval unit [306] is configured to fetch, a set of data associated with the NF, wherein the set
of data is fetched from a database [308] associated with the NF. The set of data comprises at
least one of name of one or more running procedures for the UE, one or more procedures
5 present in a pending queue for the UE, Connection Management (CM) state of the UE, one or
more flags set for the UE, and name of an active timer running for the UE.
[0084] In an implementation of the present disclosure, the retrieval unit [306] of the network
node, in this case the AMF [108], may fetch the details from the database [308]. The details
10 may include-
• Name of the procedure, if already running on the AMF [108] for the UE [310] for which
incoming new procedure request has been received.
• Fetch the details of all the procedures present in a pending queue for the UE [310]. The
pending queue means that if some procedures came in parallel at the AMF [108] node
15 but they needed to be executed in a given sequence, then the AMF [108] may put them
in the pending queue and process them one by one in a sequence.
• CM (Connection Management) State of the UE [310] may contain the values i.e., CMIDLE or CM-CONNECTED. The CM state of the UE [310] refers to a status of UE’s
[310] connection with the AMF [108]. The UE [310] may be connected with the AMF
20 [108], which may reflect the CM state as ‘CM-connected’, or the UE [310] may not be
connected to the AMF [108], which may reflect the CM state of the UE [310] as ‘CMidle’.
• All the flags set for the UE [310]. The flags may be internal flags of the AMF [108]
node. The flags are parameters for configuration that may be set or updated by a
25 network node operator to tailor the performance of the AMF [108].
• Name of a timer which is running for the UE [310]. In the AMF [108], for the UE [310],
the timer may always be initiated based on the UE [310] state in the AMF [108]. The
timer may be for a mobility reachability timer, an implicit deregistration timer, a purge
timer, and the like. The mobility reachability timer is to see the duration for which the
30 network may be reachable to the UE [310] while it is in an idle mode. The implicit
deregistration timer is to see how much time the UE [310] may take to automatically
deregister from the network, where the UE [310] is inactive for a certain period. The
23
purge timer may be to check the duration in which the network may release resources
allocated for the UE [310], where the UE [310] may be inactive.
[0085] The processing unit [302] is further configured to determine, one of a presence and an
5 absence of one or more procedures running for the UE [310], based on the set of data which is
fetched from the user. Furthermore, the processing unit [302] is configured to process the
procedure request upon determination of the absence of the one or more procedures running
for the UE [310]. Upon determining the presence of one or more procedures running for the
UE, the processing unit [302], is configured to determine one of a presence and an absence of
10 at least one procedure in the pending queue for the NF. Upon determining the absence of the
at least one procedure in the pending queue for the NF, the processing unit [302] is configured
to search, for one of a presence and an absence of a first matching key in the configuration file,
for a set of first key-value pair associated with the set of data from the in-memory of the AMF
[108]. Upon determining the presence of the first matching key in the configuration file, for
15 the set of first key-value pair, the processing unit [302] is further configured to fetch, a
corresponding data value and a corresponding action of the first matching key from the
configuration file. The set of first key-value pair may be searched in a scenario where the one
or more procedures are not in the pending queue of the AMF [108] to be executed. The
processing unit [302] is further configured to determine, whether the corresponding data value
20 of the first key-value pair matches with the corresponding data value of the first matching key
present in the configuration file. Further, the processing unit [302] is configured to perform,
the corresponding action of the first matching key present in the configuration file, upon
determining that the corresponding data value of the first key-value pair matches with the
corresponding data value of the first matching key. The processing unit [302] is further
25 configured to process, the procedure request based on at least the default handling mechanism
associated with the NF, upon determining that the corresponding data value of the first keyvalue pair does not match with the corresponding data value of the first matching key.
[0086] In an implementation of the present disclosure, the default handling mechanism may be
30 performed for the presence of the at least one procedure in the pending queue and the presence
of the at least one procedure in the running queue. For the presence of the at least one procedure
in the pending queue, the default handling mechanism includes but may not be limited to ‘no
action’ to be taken on the pending queue, drop the pending queue, a response to be sent for the
pending queue, and change the sequence of the procedure. For the presence of the at least one
24
procedure in the running queue, the default handling mechanism includes but may not be
limited to no action to be taken for the running queue, the running procedure may be ended
gracefully, and the running procedure may be ended forcefully. The default handling
mechanism may be selected based on the data value of the key. Further, upon determining the
5 absence of the first matching key in the configuration file, for the set of first key-value pair,
the processing unit [302] is configured to process the procedure request based on at least the
default handling mechanism associated with the NF.
[0087] In an implementation of the present disclosure, the processing unit [302] may determine
10 the presence or the absence of the one or more procedures for the UE [310] based on the set of
data fetched from the retrieval unit [306].
[0088] For instance, in Case A1: The processing unit [302] determines the absence of the one
or more procedures running for the UE [310], the procedure request will be processed
15 immediately without looking at the in-memory data of AMF [108].
[0089] Whereas in, Case A2: The processing unit [302] determines the presence of the one or
more procedures running in the AMF [108] for the UE [310]. The processing unit [302] may
check the AMF [108] to confirm whether the one or more procedures are in a pending queue.
20
[0090] In Case 1: If the processing unit [302] finds that the one or more procedures are not in
the pending queue of the AMF [108] to be executed, then the processing unit [302] may search
the first key-value pair in the in-memory data of the AMF [108]. The key may include:
FIRST KEY-VALUE PAIR:
25 {Incoming Procedure: Name of Incoming procedure,
Running Procedure: Name of Already running procedure,
PendingProcedureListType: NOTHING }
a) In Case C1: If any key stored in the in-memory data of the AMF [108] matches
30 with the procedure request, the data and the corresponding action are fetched from
the in-memory of the AMF [108].
1) Case D1: If the data fetched from the in-memory of the AMF [108] matches
with the first key-value pair, then the corresponding action with the data is
25
read by the user, and the user may act accordingly. The corresponding action
includes but may not be limited to starting the processing of the procedure
request immediately, putting the procedure request in the pending queue at
top, putting the procedure request in the pending queue at bottom, dropping
5 the procedure request, sending a response for the procedure request, putting
the procedure request in the pending queue with timer at top or bottom,
dropping the procedure request and initiating a new procedure request,
sending response and initiating a new procedure request.
2) Case D2: In case where the data fetched from the in-memory of the AMF
10 [108] does not match, the procedure request is processed as per the default
handling procedure of the procedure request in the AMF [108] may be
followed. The Default Handling refers to a circumstance where, if no
condition matches or that case is not yet defined in configuration, then the
AMF [108] may print a log in its Call data record and will proceed as per
15 default collision or precedence resolution handling mentioned in
configuration. The default collision or the precedence resolution handling
refers to a default procedure where the data fetched from the in-memory of
the AMF [108] does not match, only the key matches. The default collision
or the precedence resolution handling may be implemented for the procedure
20 request, for the at least one procedure in the pending queue, or for the one or
more running procedures. The default collision or the precedence resolution
handling may be determined based on the key match. The default collision
or the precedence resolution handling for the procedure request includes but
may not be limited to starting the processing of the procedure request
25 immediately, putting the procedure request in the pending queue at top,
putting the procedure request in the pending queue at bottom, dropping the
procedure request, sending a response for the procedure request, putting the
procedure request in the pending queue with timer at top or bottom, dropping
the procedure request and initiating a new procedure request, sending
30 response and initiating a new procedure request. For the presence of the at
least one procedure in the pending queue, the default handling mechanism
includes but may not be limited to ‘no action’ to be taken on the pending
queue, drop the pending queue, a response to be sent for the pending queue,
and change the sequence of the procedure. For the presence of the at least
26
one procedure in the running queue, the default handling mechanism includes
but may not be limited to no action to be taken for the running queue, the
running procedure may be ended gracefully, and the running procedure may
be ended forcefully.
5
b) Case C2: If no key matches, then process this new incoming procedure as per
default handling of the AMF [108].
[0091] Upon determining the presence of the at least one procedure in the pending queue for
10 the NF, the processing unit [302] is configured to search one of a presence and an absence of a
second matching key in the configuration file, for a set of second key-value pair associated
with the set of data fetched from the database [308]. The set of second key-value pair may be
searched if the processing unit [302] finds that the one or more procedures are not in the
pending queue of the AMF [108] to be executed. Upon determining the presence of the second
15 matching key in the configuration file, for the set of second key-value pair, the processing unit
[302] is further configured to fetch, a corresponding data and a corresponding action of the
second matching key present in the configuration file. The processing unit [302] is further
configured to determine, whether the data value of the second key-value pair matches with the
corresponding data of the second matching key present in the configuration file.
20
[0092] Furthermore, the processing unit [302] is configured to perform, the corresponding
action of the second matching key present in the configuration file, upon determining that the
data value of the second key-value pair matches with the corresponding data value of the
second matching key. Upon determining the absence of the second matching key in the
25 configuration file, for the set of second key-value pair, the processing unit [302] is further
configured to search one of a presence and an absence of a third matching key in the
configuration file, for a set of third key-value pair associated with the set of data fetched from
the database.
30 [0093] In an implementation of the present disclosure, if the processing unit [302] finds that
the one or more procedures are not in the pending queue of the AMF [108] to be executed. The
processing unit [302] may search the second key-value pair in the in-memory data of the AMF
[108]. The key may include:
27
SECOND KEY-VALUE PAIR:
{Incoming Procedure: Name of Incoming procedure,
Running Procedure: Name of Already running procedure,
PendingProcedureListType: SPECIFIC}
5
[0094] For instance, in Case C1: The processing unit [302] determines the second key-value
pair matches with the procedure request, and further the data and the corresponding action are
fetched from the in-memory of the AMF [108]. If the data fetched from the in-memory of the
AMF [108] matches with the second key-pair, then the corresponding action with the data is
10 read by the user, and the user may act accordingly.
[0095] In Case C2: If the procedure request does not match with the second key-value pair, in
case where the data fetched from the in-memory of the AMF [108] does not match, the third
key-value pair is searched by the processing unit [302] in the in-memory of the AMF [108].
15
[0096] Upon determining the presence of the third matching key in the configuration file, for
the set of third key-value pair, the processing unit [302] is further configured to fetch, a
corresponding data value and a corresponding action of the third matching key present in the
configuration file. The processing unit [302] is further configured to determine, whether the
20 data value of the third key-value pair matches with the corresponding data value of the third
matching key present in the configuration file. Furthermore, the processing unit [302] is
configured to perform, the corresponding action of the third matching key present in the
configuration file, upon determining that the data value of the third key-value pair matches
with the corresponding data value of the third matching key. The processing unit [302] is
25 further configured to process, the procedure request, based on at least the default handling
mechanism associated with the NF, upon determining that the data value of the third key-value
pair does not match with the corresponding data value of the third matching key. Upon
determining the absence of the third matching key in the configuration file, for the set of third
key-value pair, the the processing unit [302] is configured to process the procedure request
30 based on at least the default handling mechanism associated with the NF. In an implementation
of the present disclosure, the default handling mechanism may be performed for the presence
of the at least one procedure in the pending queue and the presence of the at least one procedure
28
in the running queue. For the presence of the at least one procedure in the pending queue, the
default handling mechanism includes but may not be limited to ‘no action’ to be taken on the
pending queue, drop the pending queue, a response to be sent for the pending queue, and change
the sequence of the procedure. For the presence of the at least one procedure in the running
5 queue, the default handling mechanism includes but may not be limited to no action to be taken
for the running queue, the running procedure may be ended gracefully, and the running
procedure may be ended forcefully. The default handling mechanism may be selected based on
the data value of the key.
10 [0097] In an implementation of the present disclosure, where the data fetched from the inmemory of the AMF [108] does not match, the third key-value pair is searched by the
processing unit [302] in the in-memory of the AMF [108].
[0098] The third key-value pair includes:
15 THIRD KEY-VALUE PAIR:
{Incoming Procedure: Name of Incoming procedure,
Running Procedure: Name of Already running procedure,
PendingProcedureListType: ANY}
20 [0099] In case, the processing unit [302] determines the third key-value pair any key matches
with the procedure request, the data and the corresponding action of the third key-value pair is
fetched from the in-memory of the AMF [108]. If the data matches, then the corresponding
action may be read by the user and the user may act accordingly.
25 [0100] If the data does not match, the procedure request will be processed as per the default
handling of the AMF [108]. In case the third key-value pair does not match with any key of the
AMF [108], the procedure request may be processed as per the default handling of the AMF
[108].
30 [0101] It is pertinent to note that the functionalities as disclosed in the present disclosure are
exemplary and not limited to AMF. The scope of the present disclosure may extend to the
29
solution for the other network nodes as well in light of the exemplary implementations as
provided in the present disclosure.
[0102] Also, an exemplary method flow of the configuration-based management as
5 implemented by the system [300], is shown in FIG. 4. Referring to FIG. 4, an exemplary
method flow diagram [400] for a configuration-based management of a procedure request at a
network function (NF), in accordance with exemplary implementations of the present
disclosure is shown. In an implementation the method [400] is performed by the system [300].
Further, in an implementation, the system [300] may be present in a server device to implement
10 the features of the present disclosure. Also, as shown in Figure 4, the method [400] starts at
step [402].
[0103] At step [404], the method comprises reading, by the processing unit [302], a
configuration file associated with the NF. The reading of the configuration file associated with
15 the NF, is initiated by the processing unit [302] during initialisation of the NF. After reading
of the configuration file, by the processing unit [302], the configuration file is stored in an inmemory associated with the NF. The configuration file stored in the in-memory associated with
the NF, comprises one or more key-value pair. Each key-value pair from the one or more keyvalue pair comprises a key, and a corresponding value. The corresponding value further
20 comprises a data value and an action. The configuration file associated with the NF, is updated,
by the processing unit [302], based on a change in the one or more key-value pair stored in the
configuration file. The change in the one or more key-value pair stored in the configuration
file, is performed through a command line interface (CLI) at the NF.
25 [0104] In an implementation of the present disclosure, the configuration file may be required
by the processing unit [302] file when a communication is initiated in a network. The
configuration file plays an important part in the 5th generation core network for deployment
and management of network functions. The configuration file includes but may not be limited
to a network parameter, a security parameter, and other operational details. The network
30 parameters include an IP address, a network interface, and the like. The security parameter
includes encryption keys, and the like to secure the network. The one or more key-value pair
in the in-memory may be stored by the processing unit [302]. The one or more key-value pair
refers to a type of data representation used in the configuration file. The one or more key-value
pair is a unique identifier where the corresponding value is the data associated with the key.
35 The corresponding value further includes the data value and the action associated with the data
30
value. The one or more key-value pair may be changed by processing unit [302] through the
CLI. The processing unit [302] may update the configuration file based on the change in the
one or more key-value pair. For instance, the processing unit [302] is configured to enable the
functionality of the method [400] with respect to the AMF [108].
5
[0105] Next, at step [406], the method comprises receiving, by the transceiver unit [304], the
procedure request at the NF. The procedure request is associated with a user equipment (UE)
[310]. The procedure request comprises at least one of a UE Initiated Registration, a protocol
data unit (PDU) Establishment, a Deregistration, a radio access network (RAN) initiated
10 Handover, a unified data management (UDM) Initiated Deregistration, a session management
function (SMF) initiated PDU Session release, a policy control function (PCF) initiated policy
update request.
[0106] In an implementation of the present disclosure, the transceiver unit [304] receives a
15 procedure request. The procedure request may be sent by a user. The user may be a network
node operator.
[0107] Further at step [408], the method comprises fetching, by the retrieval unit [306], a set
of data associated with the NF, wherein the set of data is fetched from a database [308]
20 associated with the NF. The set of data comprises at least one of name of one or more running
procedures for the UE, one or more procedures present in a pending queue for the UE,
connection management (CM) state of the UE, one or more flags set for the UE, and name of
an active timer running for the UE.
25 [0108] In an implementation of the present disclosure, the details may be fetched by the
retrieval unit [306] of the network node, in this case the AMF [108], from the database [308].
The details may include-
• Name of the procedure, if already running on the AMF [108] for the UE [310] for which
incoming new procedure request has been received.
30 • Fetch the details of all the procedures present in a pending queue for the UE [310]. The
pending queue means that if some procedures came in parallel at the AMF [108] node
but they needed to be executed in a given sequence, then the AMF [108] may put them
in the pending queue and process them one by one in a sequence.
31
• CM (Connection Management) State of the UE [310] may contain the values i.e., CMIDLE or CM-CONNECTED
• All the flags set for the UE [310]. The flags may be internal flags of the AMF [108]
node. The flags are parameters for configuration that may be set or updated by a
5 network node operator to tailor the performance of the AMF [108].
• Name of a timer which is running for the UE [310]. In the AMF [108], for the UE [310],
the timer may always be initiated based on the UE [310] state in the AMF [108]. The
timer may be for a mobility reachability timer, an implicit deregistration timer, a purge
timer, and the like. The mobility reachability timer is to see the duration for which the
10 network may be reachable to the UE [310] while it is in an idle mode. The implicit
deregistration timer is to see how much time the UE [310] may take to automatically
deregister from the network, where the UE [310] is inactive for a certain period. The
purge timer may be to check the duration in which the network may release resources
allocated for the UE [310], where the UE [310] may be inactive.
15
[0109] Next, at step [410], the method comprises determining, by the processing unit [302],
one of the presence and the absence of the one or more procedures running for the UE based
on the fetched set of data.
20 [0110] In an implementation of the present disclosure, the processing unit [302] may determine
the presence or the absence of the one or more procedures for the UE [310] based on the set of
data fetched from the retrieval unit [306].
[0111] At step [412], the method comprises processing, by the processing unit [302], the
25 procedure request upon determining the absence of the one or more procedures running for the
UE [310].
[0112] Upon determining the presence of one or more procedures running for the UE, the
method further comprises determining, by the processing unit [302], one of a presence and an
30 absence of at least one procedure in the pending queue for the NF. Upon determining the
absence of the at least one procedure in the pending queue for the NF, the method further
comprises, searching, by the processing unit [302], for one of a presence and an absence of a
32
first matching key in the configuration file, for a set of first key-value pair associated with the
set of data fetched from the database [308]. Upon determining the presence of the first matching
key in the configuration file, for the set of first key-value pair, the method further comprises
fetching, by the processing unit [302], a corresponding data value and a corresponding action
5 of the first matching key from the configuration file. Further, the method comprises
determining, by the processing unit [302], whether the corresponding data value of the first
key-value pair matches with the corresponding data value of the first matching key present in
the configuration file. The method further comprises performing, by the processing unit [302],
the corresponding action of the first matching key present in the configuration file, upon
10 determining that the corresponding data value of the first key-value pair matches with the
corresponding data value of the first matching key. Furthermore, the method comprises
processing, by the processing unit [302], the procedure request based on at least a default
handling mechanism associated with the NF, upon determining that the corresponding data
value of the first key-value pair does not match with the corresponding data value of the first
15 matching key. Upon determining the absence of the first matching key in the configuration file,
for the set of first key-value pair, the method comprises, processing, by the processing unit
[302], the procedure request based on at least the default handling mechanism associated with
the NF.
20 [0113] In an implementation of the present disclosure, the default handling mechanism may be
performed for the presence of the at least one procedure in the pending queue and the presence
of the at least one procedure in the running queue. For the presence of the at least one procedure
in the pending queue, the default handling mechanism includes but may not be limited to ‘no
action’ to be taken on the pending queue, drop the pending queue, a response to be sent for the
25 pending queue, and change the sequence of the procedure. For the presence of the at least one
procedure in the running queue, the default handling mechanism includes but may not be
limited to no action to be taken for the running queue, the running procedure may be ended
gracefully, and the running procedure may be ended forcefully. The default handling
mechanism may be selected based on the data value of the key.
30
[0114] In an implementation of the present disclosure, for instance, in Case A1: The
processing unit [302] determines the absence of the one or more procedures running for the UE
33
[310], the procedure request will be processed immediately without looking at the in-memory
data of AMF [108].
[0115] Whereas in, Case A2: The processing unit [302] determines the presence of the one or
5 more procedures running in the AMF [108] for the UE [310]. The following steps may be
followed in that case- the processing unit [302] may check the AMF [108] to confirm whether
the one or more procedures are in a pending queue.
[0116] In Case 1: If the processing unit [302] finds that the one or more procedures are not in
10 the pending queue of the AMF [108] to be executed. The processing unit [302] may search the
first key-value pair in the in-memory data of the AMF [108].
[0117] The key may include:
FIRST KEY-VALUE PAIR:
15 {Incoming Procedure: Name of Incoming procedure,
Running Procedure: Name of Already running procedure,
PendingProcedureListType: NOTHING }
c) In Case C1: If any key stored in the in-memory data of the AMF [108] matches
20 with the first key-value pair, the data and the corresponding action are fetched from
the in-memory of the AMF [108].
1. Case D1: If the data fetched from the in-memory of the AMF [108] matches
with the procedure request, then the corresponding action with the data is
read by the user, and the user may act accordingly.
25 2. Case D2: In case where the data fetched from the in-memory of the AMF
[108] does not match, the procedure request is processed as per the default
handling procedure of the procedure request in the AMF [108] may be
followed. The Default Handling refers to a circumstance where, if no
condition matches or that case is not yet defined in configuration, then the
30 AMF [108] may print a log in the AMF’s [108] Call data record and may
proceed as per default collision or precedence resolution handling mentioned
in configuration. The default collision or the precedence resolution handling
refers to a default procedure where the data fetched from the in-memory of
the AMF [108] does not match, only the key matches. The default collision
34
or the precedence resolution handling may be implemented for the procedure
request, for the at least one procedure in the pending queue, or for the one or
more running procedures. The default collision or the precedence resolution
handling may be determined based on the key match. The default collision
5 or the precedence resolution handling for the procedure request includes but
may not be limited to starting the processing of the procedure request
immediately, putting the procedure request in the pending queue at top,
putting the procedure request in the pending queue at bottom, dropping the
procedure request, sending a response for the procedure request, putting the
10 procedure request in the pending queue with timer at top or bottom, dropping
the procedure request and initiating a new procedure request, sending
response and initiating a new procedure request. For the presence of the at
least one procedure in the pending queue, the default handling mechanism
includes but may not be limited to ‘no action’ to be taken on the pending
15 queue, drop the pending queue, a response to be sent for the pending queue,
and change the sequence of the procedure. For the presence of the at least
one procedure in the running queue, the default handling mechanism includes
but may not be limited to no action to be taken for the running queue, the
running procedure may be ended gracefully, and the running procedure may
20 be ended forcefully.
d) Case C2: If no key matches, then process this new incoming procedure as per the
default handling of the AMF [108].
[0118] Upon determining the presence of the at least one procedure in the pending queue for
25 the NF, the method comprises, searching, by the processing unit [302], one of a presence and
an absence of a second matching key in the configuration file, for a set of second key-value
pair associated with the set of data fetched from the database [308]. Upon determining the
presence of the second matching key in the configuration file, for the set of second key-value
pair, the method comprises fetching, by the processing unit [302], a corresponding data and a
30 corresponding action of the second matching key present in the configuration file. The method
further includes determining, by the processing unit [302], whether the data value of the second
key-value pair matches with the corresponding data of the second matching key present in the
configuration file. Furthermore, the method includes performing, by the processing unit [302],
the corresponding action of the second matching key present in the configuration file, upon
35
determining that the data value of the second key-value pair matches with the corresponding
data value of the second matching key.
[0119] Upon determining the absence of the matching key in the configuration file, for the set
5 of second key-value pair, the method, further comprises, searching, by the processing unit
[302], one of a presence and an absence of a third matching key in the configuration file, for a
set of third key-value pair associated with the set of data fetched from the database.
[0120] In an implementation of the present disclosure, If the processing unit [302] finds that
10 the one or more procedures are not in the pending queue of the AMF [108] to be executed. The
processing unit [302] may search the second key-value pair in the in-memory data of the AMF
[108].
[0121] The key may include:
15 SECOND KEY-VALUE PAIR:
{Incoming Procedure: Name of Incoming procedure,
Running Procedure: Name of Already running procedure,
PendingProcedureListType: SPECIFIC}
20 [0122] For instance, in Case C1: The processing unit determines the second key-value pair
matches with the procedure request, and further the data and the corresponding action are
fetched from the database [308] of the AMF [108]. If the data fetched from the database [308]
of the AMF [108] matches with the second key-value pair, then the corresponding action with
the data is read by the user, and the user may act accordingly.
25
[0123] In Case C2: If the procedure request does not match with the second key-value pair, in
case where the data fetched from the in-memory of the AMF [108] does not match, the third
key-value pair is searched by the processing unit [302] in the in-memory of the AMF [108].
30 [0124] Upon determining the presence of the third matching key in the configuration file, for
the set of third key-value pair, the method comprises fetching, by the processing unit [302], a
corresponding data value and a corresponding action of the third matching key present in the
configuration file. The method further includes determining, by the processing unit [302],
whether the data value of the third key-value pair matches with the corresponding data value
36
of the third matching key present in the configuration file. Furthermore, the method includes
performing, by the processing unit [302], the corresponding action of the third matching key
present in the configuration file, upon determining that the data value of the third key-value
pair matches with the corresponding data value of the third matching key. The method further
5 includes processing, by the processing unit [302], the procedure request, based on at least the
default handling mechanism associated with the NF, upon determining that the data value of
the third key-value pair does not match with the corresponding data value of the third matching
key. Upon determining the absence of the third matching key in the configuration file, for the
set of third key-value pair, the method comprises, processing, by the processing unit [302], the
10 procedure request based on at least the default handling mechanism associated with the NF.
[0125] The method terminates at step [414].
[0126] The method [400] as shown in FIG. 4 will be explained through an exemplary
15 implementation of the method in FIG. 5. Referring to FIG. 5, it illustrates an exemplary
implementation of the method for a configuration-based management of a procedure request at
a network function (NF) in accordance with exemplary implementations of the present
disclosure.
20 [0127] The method starts at step 1.
[0128] At step 2, the processing unit [302] may determine the presence or the absence of the
one or more procedures for the UE [310]. If the absence of the one or more procedures for the
UE [310] is determined, the method may proceed to step 3 (A1).
25
[0129] At step 3, in Case A1: The processing unit [302] determines the absence of the one or
more procedures running for the UE [310], the procedure request will be processed
immediately without looking at the in-memory data of AMF [108].
30 [0130] If the presence of the one or more procedure for the UE [310] is determined, the method
may proceed to step 4 (A2). At step 4, in Case A2: The processing unit [302] determines the
presence of the one or more procedures running in the AMF [108] for the UE [310]. The
following steps may be followed in that case- the processing unit [302] may check the AMF
[108] to confirm whether the one or more procedures are in a pending queue. If the processing
37
unit [302] finds that the one or more procedures are not in the pending queue of the AMF [108]
to be executed, the processing unit [302] may search the key-value pair in the in-memory data
of the AMF [108].
5 [0131] At step 5, the method includes checking if the procedure request matches with any key
of the key-pair value in the in-memory data of the AMF [108].
[0132] At step 6, in Case C1: If any key stored in the in-memory data of the AMF [108]
matches with the key-value pair, the data and the corresponding action are fetched from the in10 memory of the AMF [108]. The step may further proceed to step 8 directly.
[0133] At step 7, in Case C2: If no key matches, then process the new incoming procedure as
per the default handling of the AMF [108], and the method may terminate.
15 [0134] At step 8, the data is fetched from the in-memory of the AMF [108].
[0135] Further at step 9, in Case D1: If the data fetched from the in-memory of the AMF [108]
matches with the procedure request, then the corresponding action with the data is read by the
user, and the user may act accordingly.
20
[0136] At step 10, in Case D2: In case where the data fetched from the in-memory of the AMF
[108] does not match, the procedure request is processed as per the default handling procedure
of the procedure request in the AMF [108] may be followed. The Default Handling refers to
a circumstance where, if no condition matches or that case is not yet defined in configuration,
25 then the AMF [108] may print a log in the AMF’s [108] Call data record and may proceed as
per default collision or precedence resolution handling mentioned in configuration. The default
collision or the precedence resolution handling refers to a default procedure where the data
fetched from the in-memory of the AMF [108] does not match, only the key matches. The
default collision or the precedence resolution handling may be implemented for the procedure
30 request, for the at least one procedure in the pending queue, or for the one or more running
procedures. The default collision or the precedence resolution handling may be determined
based on the key match. The default collision or the precedence resolution handling for the
procedure request includes but may not be limited to starting the processing of the procedure
request immediately, putting the procedure request in the pending queue at top, putting the
35 procedure request in the pending queue at bottom, dropping the procedure request, sending a
response for the procedure request, putting the procedure request in the pending queue with
38
timer at top or bottom, dropping the procedure request and initiating a new procedure request,
sending response and initiating a new procedure request. For the presence of the at least one
procedure in the pending queue, the default handling mechanism includes but may not be
limited to ‘no action’ to be taken on the pending queue, drop the pending queue, a response to
5 be sent for the pending queue, and change the sequence of the procedure. For the presence of
the at least one procedure in the running queue, the default handling mechanism includes but
may not be limited to no action to be taken for the running queue, the running procedure may
be ended gracefully, and the running procedure may be ended forcefully. The method may
terminate afterwards.
10
[0137] The present disclosure further discloses a non-transitory computer readable storage
medium storing instructions for a configuration-based management of a procedure request at a
network function (NF), the instructions include executable code which, when executed by one
or more units of a system, causes: a processing unit [302] of the system to read a configuration
15 file associated with the NF; a transceiver unit [304] of the system to receive, the procedure
request at the NF, wherein the procedure request is associated with a user equipment (UE)
[310]; a retrieval unit [306] of the system to fetch, a set of data associated with the NF, wherein
the set of data is fetched from a database [308] associated with the NF; the processing unit
[302], of the system to determine, one of a presence and an absence of one or more procedures
20 running for the UE, based on the fetched set of data; and the processing unit [302] of the system
to process the procedure request upon determination the absence of the one or more procedures
running for the UE [310].
[0138] As is evident from the above, the present disclosure provides a technically advanced
25 solution for providing collision and precedence handling framework for NFs. Also, the present
disclosure provides a solution that is an improvement in the standard as there is no such design
using configuration available in the standards. Also, the present disclosure provides a
configurable framework to help in resolving all the known collisions of procedures currently
happening in network on any network node. The present disclosure also provides a solution
30 that can help in resolving the precedence of the procedures in any network node. Moreover,
the present disclosure provides a solution that can resolve permutations and combinations of
all the procedure, which are still unknown, that might happen in network node in future, by just
changing the configuration of that network node, without doing any changes such as code
39
changes etc. in program or software. The solution also helps in changing the current behavior
of the network node to resolve any type of procedure collisions and precedence, with just
change in configuration.
5 [0139] 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
10 be implemented is illustrative and non-limiting.
40
We Claim:
1. A method for a configuration-based management of a procedure request at a network
5 function (NF), the method comprising:
reading, by a processing unit [302], a configuration file associated with the NF;
receiving, by a transceiver unit [304], the procedure request at the NF, wherein
the procedure request is associated with a user equipment (UE) [310];
10
fetching, by a retrieval unit [306], a set of data associated with the NF, wherein
the set of data is fetched from a database [308] associated with the NF;
determining, by the processing unit [302], one of a presence and an absence of
15 one or more procedures running for the UE [310] based on the fetched set of
data; and
processing, by the processing unit [302], the procedure request upon
determining the absence of the one or more procedures running for the UE
20 [310].
2. The method as claimed in claim 1, wherein the procedure request comprises at least one
of a UE Initiated Registration, a protocol data unit (PDU) Establishment, a
Deregistration, a radio access network (RAN) initiated Handover, a unified data
25 management (UDM) Initiated Deregistration, a session management function (SMF)
initiated PDU Session release, a policy control function (PCF) initiated policy update
request.
3. The method as claimed in claim 1, wherein the reading of the configuration file
30 associated with the NF, is initiated by the processing unit [302] during initialisation of
the NF.
41
4. The method as claimed in claim 1, wherein, after reading of the configuration file, by
the processing unit [302], the configuration file is stored in an in-memory associated
with the NF.
5 5. The method as claimed in claim 4, wherein the configuration file stored in the inmemory associated with the NF, comprises one or more key-value pair, wherein each
key-value pair from the one or more key-value pair comprises a key, and a
corresponding value, wherein the corresponding value further comprises a data value
and an action.
10
6. The method as claimed in claim 1, wherein the set of data comprises at least one of
name of one or more running procedures for the UE, one or more procedures present in
a pending queue for the UE, connection management (CM) state of the UE, one or more
flags set for the UE, and name of an active timer running for the UE.
15
7. The method as claimed in claim 6, wherein, upon determining the presence of one or
more procedures running for the UE, the method further comprises determining, by the
processing unit [302], one of a presence and an absence of the at least one procedure in
the pending queue for the NF.
20
8. The method as claimed in claim 7, wherein, upon determining the absence of the at
least one procedure in the pending queue for the NF, the method further comprises,
searching, by the processing unit [302], for one of a presence and an absence of a first
matching key in the configuration file, for a set of first key-value pair associated with
25 the set of data fetched from the database.
9. The method as claimed in claim 8, wherein upon determining the presence of the first
matching key in the configuration file, for the set of first key-value pair, the method
further comprises:
30 fetching, by the processing unit [302], a corresponding data value and a
corresponding action of the first matching key from the configuration file;
determining, by the processing unit [302], whether the corresponding data value
of the first key-value pair matches with the corresponding data value of the first
matching key present in the configuration file;
42
performing, by the processing unit [302], the corresponding action of the first
matching key present in the configuration file, upon determining that the
corresponding data value of the first key-value pair matches with the
5 corresponding data value of the first matching key; and
processing, by the processing unit [302], the procedure request based on at least
a default handling mechanism associated with the NF, upon determining that
the corresponding data value of the first key-value pair does not match with the
10 corresponding data value of the first matching key.
10. The method as claimed in claim 8, wherein upon determining the absence of the first
matching key in the configuration file, for the set of first key-value pair, the method
comprises, processing, by the processing unit [302], the procedure request based on at
15 least a default handling mechanism associated with the NF.
11. The method as claimed in claim 7, wherein upon determining the presence of the at
least one procedure in the pending queue for the NF, the method comprises, searching,
by the processing unit [302], one of a presence and an absence of a second matching
20 key in the configuration file, for a set of second key-value pair associated with the set
of data fetched from the database.
12. The method as claimed in claim 11, wherein upon determining the presence of the
second matching key in the configuration file, for the set of second key-value pair, the
25 method comprises:
fetching, by the processing unit [302], a corresponding data and a corresponding
action of the second matching key present in the configuration file;
determining, by the processing unit [302], whether a data value of the second
30 key-value pair matches with the corresponding data of the second matching key
present in the configuration file; and
43
performing, by the processing unit [302], the corresponding action of the second
matching key present in the configuration file, upon determining that the data
value of the second key-value pair matches with the corresponding data value
of the second matching key.
5
13. The method as claimed in claim 11, wherein upon determining the absence of the
second matching key in the configuration file, for the set of second key-value pair, the
method, further comprises, searching, by the processing unit [302], one of a presence
and an absence of a third matching key in the configuration file, for a set of third key10 value pair associated with the set of data fetched from the database.
14. The method as claimed in claim 13, wherein upon determining the presence of the third
matching key in the configuration file, for the set of third key-value pair, the method
comprises:
15 fetching, by the processing unit [302], a corresponding data value and a
corresponding action of the third matching key present in the configuration file;
determining, by the processing unit [302], whether a data value of the third keyvalue pair matches with the corresponding data value of the third matching key
present in the configuration file;
20
performing, by the processing unit [302], the corresponding action of the third
matching key present in the configuration file, upon determining that the data
value of the third key-value pair matches with the corresponding data value of
the third matching key; and
25
processing, by the processing unit [302], the procedure request, based on at least
a default handling mechanism associated with the NF, upon determining that
the data value of the third key-value pair does not match with the corresponding
data value of the third matching key.
30
15. The method as claimed in claim 13, wherein upon determining the absence of the third
matching key in the configuration file, for the set of third key-value pair, the method
44
comprises, processing, by the processing unit [302], the procedure request based on at
least a default handling mechanism associated with the NF.
16. The method as claimed in claim 5, wherein the configuration file associated with the
5 NF, is updated, by the processing unit [302], based on a change in the one or more keyvalue pair stored in the configuration file.
17. The method as claimed in claim 16, wherein the change in the one or more key-value
pair stored in the configuration file, is performed through a command line interface
10 (CLI) at the NF.
18. A system for a configuration-based management of a procedure request at a network
function (NF), the system comprising:
a processing unit [302], configured to read, a configuration file associated with
15 the NF;
a transceiver unit [304], configured to receive, the procedure request at the NF,
wherein the procedure request is associated with a user equipment (UE) [310];
20 a retrieval unit [306], configured to fetch, a set of data associated with the NF,
wherein the set of data is fetched from a database [308] associated with the NF;
the processing unit [302], configured to determine, one of a presence and an
absence of one or more procedures running for the UE, based on the fetched set
25 of data; and
the processing unit [302], configured to, process the procedure request upon
determination the absence of the one or more procedures running for the UE
[310].
30
19. The system as claimed in claim 18, wherein the procedure request comprises at least
one of a UE Initiated Registration, a protocol data unit (PDU) Establishment, a
Deregistration, a radio access network (RAN) initiated Handover, a unified data
management (UDM) Initiated Deregistration, a session management function (SMF)
45
initiated PDU Session release, a policy control function (PCF) initiated policy update
request.
20. The system as claimed in claim 18, wherein the reading of the configuration file
5 associated with the NF, is initiated by the processing unit [302] during initialisation of
the NF.
21. The system as claimed in claim 18, wherein, after reading of the configuration file, by
the processing unit [302], the configuration file is stored in an in-memory associated
10 with the NF.
22. The system as claimed in claim 21, wherein the configuration file stored in the inmemory associated with the NF, comprises one or more key-value pair, wherein each
key-value pair from the one or more key-value pair comprises a key, and a
15 corresponding value, wherein the corresponding value further comprises a data value
and an action.
23. The system as claimed in claim 18, wherein the set of data comprises at least one of
name of one or more running procedures for the UE, one or more procedures present in
20 a pending queue for the UE, connection management (CM) state of the UE, one or more
flags set for the UE, and name of an active timer running for the UE.
24. The system as claimed in claim 23, wherein upon determining the presence of one or
more procedures running for the UE, the processing unit [302], is configured to
25 determine one of a presence and an absence of at least one procedure in the pending
queue for the NF.
25. The system as claimed in claim 24, wherein upon determining the absence of the at
least one procedure in the pending queue for the NF, the processing unit [302] is
30 configured to search, for one of a presence and an absence of a first matching key in
the configuration file, for a set of first key-value pair associated with the set of data
fetched from the database.
46
26. The system as claimed in claim 25, wherein upon determining the presence of the first
matching key in the configuration file, for the set of first key-value pair, , the processing
unit [302] [102] is further configured to:
fetch, a corresponding data value and a corresponding action of the first
5 matching key from the configuration file;
determine, whether the corresponding data value of the first key-value pair
matches with the corresponding data value of the first matching key present in
the configuration file;
10
perform, the corresponding action of the first matching key present in the
configuration file, upon determining that the corresponding data value of the
first key-value pair matches with the corresponding data value of the first
matching key; and
15
process, the procedure request based on at least a default handling mechanism
associated with the NF, upon determining that the corresponding data value of
the first key-value pair does not match with the corresponding data value of the
first matching key.
20
27. The system as claimed in claim 25, upon determining the absence of the first matching
key in the configuration file, for the set of first key-value pair, the processing unit [302]
[102] is configured to process the procedure request based on at least a default handling
mechanism associated with the NF.
25
28. The system as claimed in claim 24, wherein upon determining the presence of the at
least one procedure in the pending queue for the NF, the processing unit [302] is
configured to search one of a presence and an absence of a second matching key in the
configuration file, for a set of second key-value pair associated with the set of data
30 fetched from the database.
47
29. The system as claimed in claim 28, wherein upon determining the presence of the
second matching key in the configuration file, for the set of second key-value pair, the
processing unit [302] is further configured to:
fetch, a corresponding data and a corresponding action of the second matching
5 key present in the configuration file;
determine, whether a data value of the second key-value pair matches with the
corresponding data of the second matching key present in the configuration file;
and
10
perform, the corresponding action of the second matching key present in the
configuration file, upon determining that the data value of the second key-value
pair matches with the corresponding data value of the second matching key.
15 30. The system as claimed in claim 28, wherein upon determining the absence of the second
matching key in the configuration file, for the set of second key-value pair, the
processing unit [302] is further configured to search one of a presence and an absence
of a third matching key in the configuration file, for a set of third key-value pair
associated with the set of data fetched from the database.
20
31. The system as claimed in claim 30, wherein upon determining the presence of the third
matching key in the configuration file, for the set of third key-value pair, the processing
unit [302] is further configured to:
fetch, a corresponding data value and a corresponding action of the third
25 matching key present in the configuration file;
determine, whether a data value of the third key-value pair matches with the
corresponding data value of the third matching key present in the configuration
file;
30
perform, the corresponding action of the third matching key present in the
configuration file, upon determining that the data value of the third key-value
pair matches with the corresponding data value of the third matching key; and
48
process, the procedure request, based on at least a default handling mechanism
associated with the NF, upon determining that the data value of the third keyvalue pair does not match with the corresponding data value of the third
5 matching key.
32. The system as claimed in claim 30, wherein upon determining the absence of the third
matching key in the configuration file, for the set of third key-value pair, the processing
unit [302] is configured to process the procedure request based on at least a default
10 handling mechanism associated with the NF.
33. The system as claimed in claim 22, wherein the configuration file associated with the
NF, is updated, by the processing unit [302], based on a change in the one or more keyvalue pair stored in the configuration file.
15
34. The system as claimed in claim 33, wherein the change in the one or more key-value
pair stored in the configuration file, is performed through a command line interface
(CLI) at the NF.