WO2025012979A1 - Procédé et système aux fins d'une gestion basée sur la configuration d'une demande de procédure - Google Patents

Procédé et système aux fins d'une gestion basée sur la configuration d'une demande de procédure Download PDF

Info

Publication number
WO2025012979A1
WO2025012979A1 PCT/IN2024/050997 IN2024050997W WO2025012979A1 WO 2025012979 A1 WO2025012979 A1 WO 2025012979A1 IN 2024050997 W IN2024050997 W IN 2024050997W WO 2025012979 A1 WO2025012979 A1 WO 2025012979A1
Authority
WO
WIPO (PCT)
Prior art keywords
key
configuration file
processing unit
value pair
determining
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/IN2024/050997
Other languages
English (en)
Inventor
Birendra Bisht
Aayush Bhatnagar
Harbinder Pal Singh
Gaurav Luthra
Sumit Singh
Rakesh Kumar JAISWAL
Saniya JAT
Rahul Kumar
Anshul Gupta
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Jio Platforms Ltd
Original Assignee
Jio Platforms Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Jio Platforms Ltd filed Critical Jio Platforms Ltd
Publication of WO2025012979A1 publication Critical patent/WO2025012979A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/024—Standardisation; Integration using relational databases for representation of network management data, e.g. managing via structured query language [SQL]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements

Definitions

  • 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).
  • NF network function
  • Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements.
  • the first generation of wireless communication technology was based on analog technology and offered only voice services.
  • 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.
  • 4G technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security.
  • 5G fifth generation
  • wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
  • the 5G core networks are based on service-based architecture (SBA) that is centered around network function (NF) services.
  • SBA service-based architecture
  • NF network function
  • Each NF can register itself and its supported services to a Network Repository Function (NRF), which is used by other NFs for the discovery of NF instances and their services.
  • the NRF therefore supports functions related to 1) maintaining the profiles of the available network function (NF) instances and their supported services in the 5G core network, 2) allowing NF instances to discover other NF instances in the 5G core network, and 3) allowing the NF instances to track the status of other NF instances.
  • certain NF related details are captured at the NRF whenever an NF comes up with a planned event or first-time commissioning.
  • 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 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.
  • many network nodes can initiate procedures like UDM, NG-RAN, MME, SMF, PCF, UE, NWDAF, GMLC, Peer AMF, etc.
  • 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 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.
  • 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 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.
  • 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 receiving, by a transceiver unit, the procedure request at the NF, wherein the procedure request is associated with a user equipment (UE).
  • 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 the fetched set of data.
  • 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.
  • 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 PDU Session release, a Policy Control Function (PCF) initiated policy update request.
  • PDU Protocol Data Unit
  • RAN Radio Access Network
  • UDM Unified Data Management
  • SMF Session Management Function
  • PCF Policy Control Function
  • the reading of the configuration file associated with the NF is initiated by the processing unit during initialisation of the NF.
  • the configuration file is stored in an in-memory associated with the NF.
  • 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.
  • 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.
  • CM Connection Management
  • the method 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 queue for the NF.
  • the method 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 in the configuration file, for a set of first key-value pair associated with the set of data fetched from the database.
  • the method upon determining the presence of the first matching key in the configuration file, for the set of first key-value pair, the method further 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 configuration file.
  • 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.
  • the method includes processing, by the processing unit, 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.
  • the method 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, the procedure request based on at least the default handling mechanism associated with the NF.
  • the method 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, 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.
  • the method upon determining the presence of the 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 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.
  • the method 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 of data fetched from the database.
  • the method 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 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.
  • 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 of the third key-value pair matches with the corresponding data value of the third matching key.
  • 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 keyvalue pair does not match with the corresponding data value of the third matching key.
  • the method 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.
  • 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.
  • 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.
  • CLI command line interface
  • Another aspect of the present disclosure may relate to a system for a configuration-based 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, wherein the procedure request is associated with a user equipment (UE).
  • UE user equipment
  • 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.
  • the system includes the processing unit, configured to process the procedure request upon determination the absence of the one or more procedures running for the UE.
  • 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).
  • UE user equipment
  • the 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 to process the procedure request upon determination the absence of the one or more procedures running for the UE.
  • FIG. 1 illustrates an exemplary block diagram representation of 5th generation core
  • 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.
  • FIG. 3 illustrates an exemplary block diagram of a system for a configuration-based management of a procedure request at a network function (NF), in accordance with exemplary implementations of the present disclosure.
  • NF network function
  • 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 of the present disclosure.
  • 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.
  • 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.
  • any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art.
  • a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions.
  • a processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc.
  • the processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
  • a user equipment may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure.
  • the user equipment/device may include, but is not limited to, a mobile phone, smart 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.
  • 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 to implement the features of the present disclosure.
  • “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine.
  • a computer-readable medium includes read-only 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.
  • interface refers to a shared boundary across which two or more separate components of a system exchange information or data.
  • the interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
  • All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, 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.
  • DSP digital signal processor
  • ASIC Application Specific Integrated Circuits
  • FPGA Field Programmable Gate Array circuits
  • 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.
  • 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.
  • the present 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 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 network node.
  • FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure.
  • the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], a Session Management Function (SMF) [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 (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
  • UE user equipment
  • 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.
  • 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.
  • UPF User Plane Function
  • 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.
  • 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.
  • 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.
  • 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.
  • NSSAAF Network Slice Specific Authentication and Authorization Function
  • 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.
  • the Network Exposure Function (NEF) [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
  • 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 the discovery and dynamic registration of network functions.
  • the Policy Control Function (PCF) is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.
  • the Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
  • 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.
  • the User Plane Function [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
  • the Data Network (DN) refers to a network that provides data services to user equipment (UE) in a telecommunications system.
  • the data services may include but are not limited to Internet services, private data network related services.
  • 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 implementation of the present disclosure.
  • 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.
  • 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 device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
  • NF network function
  • the computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information.
  • the hardware processor [204] may be, for example, a general-purpose microprocessor.
  • the computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204],
  • the main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [204], Such instructions, when stored in non-transitory storage media accessible to the processor [204], render the computing device [200] into a special-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 [202] for storing static information and instructions for the processor [204],
  • ROM read only memory
  • 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 (OLED) display, etc. for displaying information to a computer user.
  • An input device [214] including alphanumeric and other keys, touch screen input means, etc.
  • a cursor controller [216] such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling 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.
  • the computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [200] causes or programs the computing device [200] to be a special-purpose machine.
  • 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 [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.
  • hard-wired circuitry may be used in place of or in combination with software instructions.
  • 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],
  • the communication interface [218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line.
  • the communication interface [218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN.
  • LAN local area network
  • Wireless links may also be implemented.
  • the communication interface [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
  • the computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the communication interface [218],
  • 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 execution.
  • 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.
  • 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 user equipment [310],
  • 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.
  • system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure.
  • 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).
  • the system [300] may reside in a server or a network entity.
  • the system [300] may reside partly in the server/ network entity and partly in the user device.
  • a single network node handles multiple processes.
  • 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 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 5 th 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] 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.
  • CAG Closed Access Group
  • 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 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.
  • MME Mobile Management Entity
  • the Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
  • the NG-RAN comprises of a set of gNBs connected to the 5 th 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 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.
  • UPF User Plane Function
  • the Policy Control Function (PCF) is a network function responsible for policy control decisions, such as 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 or user voice call can get disconnected. To solve such problems, the system [300] for a configuration-based management is introduced.
  • 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 components/units of the system [300],
  • 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 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 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 stored at the SMF [106],
  • 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 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.
  • 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 parameter, a security parameter, and other operational details.
  • 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 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 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],
  • 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 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.
  • the transceiver unit [304] receives a procedure request.
  • the procedure request may be sent by a user.
  • the user may be a network node operator.
  • 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 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.
  • CM Connection Management
  • the retrieval unit [306] of the network node in this case the AMF [108]
  • the details may include-
  • 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.
  • CM (Connection Management) State of the UE [310] may contain the values i.e., CM- IDLE 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 [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 ‘CM-idle’.
  • 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 network node operator to tailor the performance of the AMF [108],
  • 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 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.
  • the processing unit [302] is further configured to determine, one of a presence and an 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 at least one procedure in the pending queue for the NF.
  • the processing unit [302] 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 the set of first keyvalue 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 keyvalue 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 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 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 key -value pair does not match with the corresponding data value of the first matching key.
  • 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.
  • 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.
  • 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 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.
  • 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], [0088] For instance, in Case Al: 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],
  • 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.
  • 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:
  • Running Procedure Name of Already running procedure, PendingProcedureListType: NOTHING ⁇ a)
  • PendingProcedureListType NOTHING ⁇ a)
  • Case Cl If any key stored in the in-memory data of the AMF [108] matches with the procedure request, the data and the corresponding action are fetched from the inmemory of the AMF [108],
  • Case DI 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 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 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.
  • 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 AMF [108] may print a log in its Call data record and will 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 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 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 response and initiating a new procedure request.
  • 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.
  • 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 processing unit [302] 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 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 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.
  • 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.
  • 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 keyvalue pair associated with the set of data fetched from the database.
  • the processing unit [302] may search the second key -value pair in the in-memory data of the AMF [108],
  • the key may include:
  • Running Procedure Name of Already running procedure, PendingProcedureLi stType : SPECIFIC ⁇
  • Case Cl 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 read by the user, and the user may act accordingly.
  • 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 keyvalue pair is searched by the processing unit [302] in the in-memory of the AMF [108],
  • the processing unit [302] 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 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 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.
  • the processing unit [302] is configured to process the procedure request based on at least the default handling mechanism associated with the NF.
  • 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.
  • 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.
  • 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.
  • the third key-value pair is searched by the processing unit [302] in the in-memory of the AMF [108],
  • the third key -value pair includes:
  • Running Procedure Name of Already running procedure, PendingProcedureListType: ANY ⁇ [0099]
  • 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.
  • the procedure request will be processed as per the default handling of the AMF [108]
  • the procedure request may be processed as per the default handling of the AMF [108]
  • FIG. 4 an exemplary method flow of the configuration-based management as implemented by the system [300], is shown in FIG. 4.
  • 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.
  • the method [400] is performed by the system [300]
  • the system [300] may be present in a server device to implement the features of the present disclosure.
  • the method [400] starts at step [402],
  • the method comprises reading, by the processing unit [302], 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 NF.
  • the configuration file is stored in an in-memory 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 key-value pair comprises a key, and a corresponding value. The corresponding value further 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.
  • CLI command line interface
  • 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 5 th 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 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.
  • the corresponding value further includes the data value and the action associated with the data 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.
  • the processing unit [302] is configured to enable the functionality of the method [400] with respect to the AMF [108],
  • 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 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.
  • PDU protocol data unit
  • RAN radio access network
  • UDM unified data management
  • SMF session management function
  • PCF policy control function
  • the transceiver unit [304] receives a procedure request.
  • the procedure request may be sent by a user.
  • the user may be a network node operator.
  • 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] 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.
  • CM connection management
  • 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.
  • 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.
  • CM (Connection Management) State of the UE [310] may contain the values i.e., CM- IDLE or CM-CONNECTED
  • 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 network node operator to tailor the performance of the AMF [108],
  • 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 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 deregi ster from the network, where the UE [310] is inactive for a certain period.
  • the purge tinier 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.
  • 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.
  • 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],
  • the method comprises processing, by the processing unit [302], the procedure request upon determining the absence of the one or more procedures running for the UE [310], [0112]
  • the method further comprises determining, by the processing unit [302], one of a presence and an absence of 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 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 of the first matching key from the configuration file.
  • 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 determining that the corresponding data value of the first key -value pair matches with the corresponding data value of the first matching key.
  • 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 matching key.
  • the method 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the key may include:
  • Running Procedure Name of Already running procedure, PendingProcedureListType: NOTHING ⁇ c)
  • Case Cl If any key stored in the in-memory data of the AMF [108] matches with the first key -value pair, the data and the corresponding action are fetched from the inmemory of the AMF [108],
  • Case DI 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.
  • 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 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 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 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 response and initiating a new procedure request.
  • 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.
  • 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. d) Case C2: If no key matches, then process this new incoming procedure as per the default handling of the AMF [108],
  • 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 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 determining that the data value of the second key-value pair matches with the corresponding data value of the second matching key.
  • 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.
  • 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:
  • Running Procedure Name of Already running procedure, PendingProcedureLi stType : SPECIFIC ⁇
  • Case Cl 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.
  • 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 of the third matching key present in the configuration file.
  • 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 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.
  • the method comprises, processing, by the processing unit [302], the procedure request based on at least the default handling mechanism associated with the NF.
  • 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.
  • 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 (Al).
  • 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 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],
  • 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],
  • step 6 in Case Cl: 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 in-memory of the AMF [108], The step may further proceed to step 8 directly.
  • 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.
  • step 8 the data is fetched from the in-memory of the AMF [108],
  • 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 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 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 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 response and initiating a new procedure request.
  • 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.
  • 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.
  • 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 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 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
  • the present disclosure provides a technically advanced 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 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 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente divulgation concerne un procédé et un système aux fins d'une gestion basée sur la configuration d'une demande de procédure. Le procédé consiste à lire, par une unité de traitement [302], un fichier de configuration associé à la NF. Le procédé consiste en outre à recevoir, par une unité d'émetteur-récepteur [304], la demande de procédure au niveau de la NF. En outre, le procédé consiste à extraire, par une unité de récupération [306], un jeu de données associées à la NF. Le procédé consiste en outre à déterminer, par l'unité de traitement [302], une présence ou une absence d'une ou de plusieurs procédures s'exécutant pour un UE [310] sur la base du jeu de données extrait. Le procédé consiste en outre à traiter, par l'unité de traitement [302], la demande de procédure lors de la détermination de l'absence de la ou des procédures s'exécutant pour l'UE [310].
PCT/IN2024/050997 2023-07-08 2024-06-28 Procédé et système aux fins d'une gestion basée sur la configuration d'une demande de procédure Ceased WO2025012979A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202321046042 2023-07-08
IN202321046042 2023-07-08

Publications (1)

Publication Number Publication Date
WO2025012979A1 true WO2025012979A1 (fr) 2025-01-16

Family

ID=94215032

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IN2024/050997 Ceased WO2025012979A1 (fr) 2023-07-08 2024-06-28 Procédé et système aux fins d'une gestion basée sur la configuration d'une demande de procédure

Country Status (1)

Country Link
WO (1) WO2025012979A1 (fr)

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3 (Release 17)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 29.510, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG4, no. V17.1.0, 30 March 2021 (2021-03-30), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , pages 1 - 243, XP052000210 *
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Principles and Guidelines for Services Definition; Stage 3 (Release 18)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 29.501, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG4, no. V18.2.0, 26 June 2023 (2023-06-26), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, pages 1 - 84, XP052409267 *

Similar Documents

Publication Publication Date Title
WO2025012936A1 (fr) Procédé et système de rapport d'informations de charge spécifiques à une tranche
WO2025008895A1 (fr) Procédé et système pour effectuer un transfert intercellulaire d'un wlan à une nouvelle radio (nr) dans un réseau sans fil
WO2025008879A1 (fr) Procédé et système d'optimisation de procédure de déclenchement de dispositif pour dispositifs iot
WO2025008875A1 (fr) Procédé et système de configuration et de gestion d'enregistrements mandataires dans un réseau
WO2025012979A1 (fr) Procédé et système aux fins d'une gestion basée sur la configuration d'une demande de procédure
WO2025013070A1 (fr) Procédé et système de pointage de contrôle d'un appel dans un sous-système multimédia de protocole internet
WO2025017730A1 (fr) Procédé et système de gestion de données de configuration de distribution de données non ip (nidd)
WO2025012956A2 (fr) Procédé et système permettant de fournir un service de priorité multimédia dans un réseau de communication
WO2025052436A1 (fr) Procédé et système de découverte d'une ou de plusieurs fonctions de réseau homologues
WO2025052420A1 (fr) Procédé et système d'établissement d'une session de réseau au niveau d'une fonction de support de liaison (bsf)
WO2025008876A1 (fr) Procédé et système de mise sur liste d'autorisation de dispositifs compatibles avec vowifi
WO2025012980A1 (fr) Procédé et système pour la réalisation d'une procédure d'interdiction dans une zone de rapport de présence prédéfinie (pra)
WO2025069062A1 (fr) Procédé et système de continuité de service dans un réseau de communication
WO2025062413A1 (fr) Procédé et système de maintien de session pour des demandes d'autorisation d'authentification (aar)
WO2025017686A1 (fr) Procédé et système de fourniture d'informations de tranche dans un réseau de communication
WO2025057183A1 (fr) Procédé et système pour établir une connexion entre un équipement utilisateur et un réseau
WO2025008888A1 (fr) Procédé mis en œuvre par un nœud de réseau pour gérer un transfert dans un réseau de communication
WO2025008977A1 (fr) Procédé et système de gestion de message d'échec d'établissement de contexte initial
WO2025062454A1 (fr) Procédé et système pour augmenter le débit de transactions de données par mise en œuvre d'un système de stockage
WO2025008915A1 (fr) Procédé et système de fourniture d'informations d'instance de tranche de réseau
WO2025052421A1 (fr) Procédé et système de traitement des demandes de localisation dans un réseau de communication sans fil
WO2025012991A1 (fr) Procédé et système de commande d'un ou de plusieurs serveurs d'application dans un réseau
WO2025052433A1 (fr) Procédé et système d'extraction automatique de données d'autorisation de tranche au niveau d'une amf d'un réseau
WO2025012964A1 (fr) Procédé et système de gestion de routage de messages
WO2025008871A1 (fr) Procédé et système de routage d'une demande d'enregistrement dans réseau de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24839092

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2024839092

Country of ref document: EP

Effective date: 20260209

WWE Wipo information: entry into national phase

Ref document number: 2024839092

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE