Sign In to Follow Application
View All Documents & Correspondence

Method And System For Routing A Registration Request In A Communication Network

Abstract: The present disclosure relates to a method [400] and a system [300] for routing a registration request in a communication network. The present disclosure encompasses a network node [302]. The network node [302] incorporates a receiving unit [304], configured to receive, from a User Equipment (UE), a registration request for establishment of a connection between the UE and a target network node [302] from a plurality of target network nodes, where the registration request comprises an identifier associated with the UE. The network node [302] further incorporates a processing unit [306], configured to, analyze the identifier to determine a category of the identifier, and determine the target network node [302] from the plurality of target network nodes based on the category of the identifier. Further, the network node [302] incorporates a network routing unit [308], configured to route the registration request to the target network node [302]. Figure 3

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
03 July 2023
Publication Number
2/2025
Publication Type
INA
Invention Field
COMMUNICATION
Status
Email
Parent Application
Patent Number
Legal Status
Grant Date
2025-11-21
Renewal Date

Applicants

Jio Platforms Limited
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India

Inventors

1. Mukesh Singh
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
2. Aayush Bhatnagar
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
3. Fenil Natali
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
4. Koushik Mukherjee
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
5. Jim Edakkara
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
6. Arpita Jaywant Ghag
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
7. Dipanjan Bhattacharya
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
8. Sandeep Kumar
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
9. Harbinder Pal Singh
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
10. Birendra Singh Bisht
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
11. Durgesh Rajesh
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
12. Venkatakrishna Banka
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
13. Sunny Deval
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
14. Dilip Behera
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
15. Neha Raju
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
16. Santosh Gourh
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
17. Pradeep Kumar
Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India

Specification

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 ROUTING A REGISTRATION REQUEST IN A COMMUNICATION NETWORK”
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.
2
METHOD AND SYSTEM FOR ROUTING A REGISTRATION REQUEST IN A COMMUNICATION NETWORK
TECHNICAL FIELD
5
Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to methods and systems for routing a registration request in a communication network.
10
BACKGROUND
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 15 disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
Wireless communication technology has rapidly evolved over the past few decades, 20 with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the 25 introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple 30 devices simultaneously. With each generation, wireless communication technology
3
has become more advanced, sophisticated, and capable of delivering more services to its users.
In the 5G network, to fulfill the demand of increasing users to access 5G services, various nodes are deployed so that experience of the users with the 5G network can 5 be maintained. Conventionally, in production many a times SMF release upgrades and deployments are planned, live traffic is directly sent on such SMF nodes which leads to a high probability of service outage and affect network performance. Thus, in addition to other existing limitations, efficient upgrading or deployment of additional nodes such as SMF node at the network is a technical problem. 10
Thus, in order to improve the 3GPP radio access network capacity and performance, there exists an imperative need in the art to efficiently deploy or upgrade the SMF node in a wireless communication network, which the present disclosure aims to address. 15
SUMMARY
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 20 summary is not intended to identify the key features or the scope of the claimed subject matter.
An aspect of the present disclosure may relate to a method for routing a registration request in a communication network. The method comprise steps of receiving, at 25 the network node, from a user equipment (UE), the registration request for establishment of a connection between the UE and a target network node from a plurality of target network nodes, where the registration request comprises an identifier associated with the UE. Further, the method comprise steps of analysing, by the network node, the identifier to determine a category of the identifier. Further, 30 the method comprise steps of determining, by the network node, the target network
4
node from the plurality of target network nodes based on the category of the identifier. Furthermore, the method comprises steps of routing, by the network node, the registration request to the target network node.
In an exemplary aspect of the present disclosure, the the network node is an Access 5 and Mobility Management Function (AMF).
In an exemplary aspect of the present disclosure, the plurality of target network nodes comprises a test Session Management Function (SMF) and a non-test SMF.
10
In an exemplary aspect of the present disclosure, the identifier is Subscriber Permanent Identifier (SUPI), and wherein the category of the identifier comprises a test SUPI and a non-test SUPI
In an exemplary aspect of the present disclosure, the method further comprises 15 routing the registration request to the test SMF when the category of the identifier is the test SUPI.
In an exemplary aspect of the present disclosure, the test SMF is one of a newly deployed SMF and an upgraded SMF, wherein the test SMF is deployed in a 5G 20 core network to handle live user traffic after passing through at least one network testing procedure.
In an exemplary aspect of the present disclosure, the method further comprises transmitting, via the network node, a connection acknowledgement to the UE, in an 25 event of successful registration of the UE with the target network node.
Another aspect of the present disclosure may relate to a network node for routing a registration request in a communication network. The present disclosure encompasses a network node. The network node further incorporates a receiving 30 unit, configured to receive, from a user equipment (UE), a registration request for
5
establishment of a connection between the UE and a target network node from a plurality of target network nodes, where the registration request comprises, an identifier associated with the UE. The network node further incorporates a processing unit at least connected to the receiving unit, configured to, analyze the identifier to determine a category of the identifier, and determine the target network 5 node from the plurality of target network nodes based on the category of the identifier. Further, the network node incorporates a network routing unit at least connected to the processing unit, configured to route the registration request to the target network node.
10
Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for routing a registration request in a communication network, the instructions include executable code which, when executed by one or more units of a network node, causes: a receiving unit to receive, from a user equipment (UE), a registration request for establishment of a connection 15 between the UE and a target network node from a plurality of target network nodes, where the registration request comprises an identifier associated with the UE; a processing unit, configured to analyse the identifier to determine a category of the identifier, and determine the target network node from the plurality of target network nodes based on the category of the identifier; and the a network routing 20 unit, configured to route the registration request to the target network node.
Yet another aspect of the present disclosure may relate to a user equipment (UE) for routing a registration request in a communication network comprising a memory, and a processor coupled to the memory, the processor configured to: 25 transmit, to a network node, a request for establishing a connection between the UE and a target network node, and receive, from the network node, a connection establishment acknowledgement associated with the request, wherein the connection establishment acknowledgement is received based on: analysing, by the network node, the identifier to determine a category of the identifier, based on the 30 category of the identifier, determining, by the network node, the target network
6
node from the plurality of target network nodes, and routing, by the network node, the registration request to the target network node.
OBJECTS OF THE DISCLOSURE 5
Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
It is an object of the present disclosure to provide a system and a method for routing 10 a registration request in a communication network.
It is another object of the present disclosure to sanitize all possible 5G call flows with test user before making 5G SMF live in production.
15
It is yet another object of the present disclosure to allow smooth and risk-free deployment/upgrade of 5G SMF node in production environment without affecting end user’s 4G/5G services.
DESCRIPTION OF THE DRAWINGS 20
The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, 25 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 30
7
drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
Figure 1 illustrates an exemplary block diagram representation of 5th Generation Core (5GC) network architecture; 5
Figure 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;
10
Figure 3 illustrates an exemplary block diagram of a network node for routing a registration request in a communication network, in accordance with exemplary implementations of the present disclosure; and
Figure 4 illustrates a method flow diagram for routing a registration request in a 15 communication network in accordance with exemplary implementations of the present disclosure.
The foregoing shall be more apparent from the following more detailed description of the disclosure. 20
DETAILED DESCRIPTION
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 25 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 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 30 above.
8
The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It 5 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.
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
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 20 concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
The word “exemplary” and/or “demonstrative” is used herein to mean serving as an 25 example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of 30 ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,”
9
“contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
5
As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a Digital 10 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 15 processing unit is a hardware processor.
As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a 20 communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable 25 of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from unit(s) which are required to implement the features of the present disclosure.
As used herein, “storage unit” or “memory unit” refers to a machine or computer-30 readable medium including any mechanism for storing information in a form
10
readable by a computer or similar machine. For example, 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 5 functions.
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 10 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 15 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 20 circuits (FPGA), any other type of integrated circuits, etc.
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 25 and/or connected with the system.
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 30 functionality of these units for clarity, it is recognized that various configurations
11
and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure. 5
As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system of routing a registration request in a communication network. The present 10 disclosure involves a User Equipment (UE) sending a registration request to a network node, specifically an Access and Mobility Management Function (AMF). The request includes a unique identifier, known as the Subscriber Permanent Identifier (SUPI), which is further categorized as a test SUPI or a non-test SUPI.
15
The network node analyzes the SUPI to determine the category of SUPI and based on the category of SUPI, determines the target network node from a plurality of nodes, which include a test Session Management Function (SMF) and a non-test SMF. The registration request is then routed to the appropriate SMF. If the SUPI is a test SUPI, the request is routed to a test SMF, which may conclude a newly 20 deployed or upgraded SMF in a 5G core network. If the SUPI is a non-test SUPI, the request is routed to a non-test SMF.
The system and method disclosed ensures that the UE is connected to the most suitable network node, for facilitating efficient network operation and enhancing 25 user experience.
Figure 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 figure 1, the 5GC network architecture [100] 30 includes a user equipment (UE) [102], a radio access network (RAN) [104], an
12
access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a 5 Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data network (DN) [130], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure. 10
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. 15
Access and Mobility Management Function (AMF) [106] 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. 20
Session Management Function (SMF) [108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement. 25
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. 30
13
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.
Network Slice Specific Authentication and Authorization Function (NSSAAF) 5 [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.
Network Slice Selection Function (NSSF) [116] is a network function responsible 10 for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
Network Exposure Function (NEF) [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling 15 integration with third-party services and applications.
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. 20
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
Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
14
Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.
User Plane Function (UPF) [128] is a network function responsible for handling 5 user data traffic, including packet routing, forwarding, and QoS enforcement.
Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services. 10
Figure 2 illustrates an exemplary block diagram of a computing device [200] (or referred herein as computer system [200]) upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [200] may also 15 implement a method for routing a registration request in a communication network utilising the system. In another implementation, the computing device [200] itself implements the method for routing a registration request in a communication network using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as 20 disclosed in the present disclosure.
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] 25 may be, for example, a general-purpose microprocessor. The computer system [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 30 intermediate information during execution of the instructions to be executed by the
15
processor [204]. Such instructions, when stored in non-transitory storage media accessible to the processor [204], render the computer system [200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computer system [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static 5 information and instructions for the processor [204].
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 computer system [200] may be coupled via the bus [202] to a display [212], such 10 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. may be coupled to the bus [202] for communicating information and command selections to the processor [204]. Another type of user 15 input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane. 20
The computer system [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 computer system [200] causes or programs the computer system [200] to be a special-purpose machine. According 25 to one implementation, the techniques herein are performed by the computer system [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 30 memory [206] causes the processor [204] to perform the process steps described
16
herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
The computer system [200] also may include a communication interface [218] coupled to the bus [202]. The communication interface [218] provides a two-way 5 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, 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 10 local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information. 15
The computer system [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the communication interface [218]. In the Internet example, a server [230] might transmit a requested code for an application program through the Internet [228], the ISP [226], the local 20 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.
Referring to Figure 3, an exemplary block diagram of a system [300] for routing a 25 registration request in a communication network, is shown, in accordance with the exemplary implementations of the present disclosure. In one example, the system [300] may be implemented as a network node [302]. In another example, the system [300] may be implemented as or within the computer system [200] explained in conjunction with Figure 2. 30
17
As depicted in Figure 3, the system [300] may be in communication with a User Equipment, also referred to as UE. Examples of such User Equipment (UE) may include, but are not limited to, a personal computer (PC), a mobile device, a tablet, or similar devices known in the state of the art. It may further be noted that, the system [300] may be in communication with additional network entities other than 5 those depicted in Figure 3. Such network entities have been not depicted and explained for the sake of brevity, and would be well understood by a person skilled in the art.
Continuing with the present example, the system [300] comprises at least one 10 receiving unit [304], at least one processing unit [306], at least one network routing unit [308], at least one test Session Management Function (SMF) [310] and, at least one non-test Session Management Function (SMF) [310a]. 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 figure 3, all units shown within 15 the system [300] should also be assumed to be connected to each other. Also, in Figure 3, only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure.
20
Further, in an implementation, the system [300] may reside in a server or a network. In another implementation, the system [300] may reside partly in the server or network and partly in the user device.
The system [300] is configured for routing a registration request in a 25 communication network, with the help of the interconnection between the components/units of the system [300]. The network node [302] incorporates a a receiving unit [304], configured to receive, from a user equipment (UE), a registration request for establishment of a connection between the UE and a target network node [302] from a plurality of target network nodes, where the registration 30
18
request comprises, an identifier associated with the UE. Further, the network node [302] is an Access and Mobility Management Function (AMF).
The system [300] mentioned here facilitates a connection between the UE and the network node [302], via the receiving unit [304] at the network node [302]. Further, 5 for establishing a connection in between the UE and network node [302], a registration request is sent to the network node [302]. The registration request as mentioned includes an identifier that is linked with the UE and is transferred to the receiving unit [304] in a plurality of data packets. The identifier mentioned here may include a special identity for separating one UE from multiple UE that may 10 present around, in a network.
The receiving unit [304] at the network node [302] receives this registration request and further transmits the information within the registration request to one or more units present at the network node [302]. It is to be noted that the receiving unit [304] 15 mentioned here, is a processor or a combination of processors that are tasked for transmitting/ receiving one or more set of instructions as per requirement.
Further, the network node [302] mentioned here is an Access and Mobility Management Function (AMF), where the AMF is one of a target network node from 20 the plurality of network nodes. Also, the network node [302] includes any other necessary node that may be obvious to the person skilled in the art for implementing the solution as disclosed herein.
It is to be noted that the AMF in the network node [302] is responsible for managing 25 the access of the UE with the network, primarily during a case of mobility of UE from one location to another. The AMF manages the access of UE in a manner that any case of loss of connection or disruption is eliminated at the UE during the mobility.
30
19
For example, in case a UE is required to connect with a network node [302], the UE then sends a registration request to the receiving unit [304] at the network node [302], here an AMF. Further, the receiving unit [304] subsequent to receiving the registration request, further sends the registration request to one or more units, linked with the receiving unit [304] for further processing. 5
The network node [302] further incorporates a processing unit [306] connected at least with the receiving unit [304], configured to analyze the identifier to determine a category of the identifier. Further, the identifier is Subscriber Permanent Identifier (SUPI), and wherein the category of the identifier comprises a test SUPI and a non-10 test SUPI.
The receiving unit [304] as mentioned transfers the received registration request to the processing unit [306]. The processing unit [306] posts receiving the registration request, extracts the information (here ‘identifier’) from the registration request. 15 The identifier received at the processing unit [306] is the Subscriber Permanent Identifier (SUPI). The SUPI mentioned here may include an International Mobile Equipment Identity (IMEI) for identification of the UE from other UE’s in the network cluster. It is to be noted that the SUPI may include further information other than the IMEI, for the identification and managing of the UE. 20
Here the processing unit [306] is referred to a processor or a combination of processors that are configured to process/ execute one or more set of instructions/ commands, as per requirements.
25
Further, the processing unit [306] further processes the SUPI to determine the category of the SUPI. Here the category of the SUPI is referred to a test SUPI and a non-test SUPI. Firstly, the test SUPI refers to an identifier of a UE that is being used for testing the functionality and performance of the UE in the network. Conversely, the non-test SUPI is referred to the identifier of the UE that are used 30 by a user in live network, by the users.
20
For example, the processing unit [306] works differently based on the category of the identifier, such as in case the processing unit [306] recognizes the identifier as a test SUPI, then the processing unit [306] will work accordingly, and further if the processing unit [306] recognizes the identifier as a non-test SUPI, then the 5 processing unit [306] will work differently.
The processing unit [306] is further configured to determine the target network node [302] from the plurality of target network nodes based on the category of the identifier. The plurality of target network nodes may include a test Session 10 Management Function (SMF) [310] and a non-test SMF [310a].
The processing unit [306] as mentioned determines the target network node based on the identifier (or specifically based on the SUPI). The plurality of target network nodes disclosed here may include one of a test Session Management Function 15 (SMF) [310] and a non-test Session Management Function (SMF) [310a].
It is to be noted that the Session Management Function (SMF) [108] is primarily used for managing sessions in the network, which may further include a continuous exchange of data in between the UE and the network. 20
In one example, in case the identifier is a test SUPI, the processing unit [306] may categorize the target network node as a test SMF [310]. Here the test SMF [310] concludes a network node [302], primary created for testing purposes of a newly launched UE or any upgradation in the UE. The test SMF [310] as mentioned 25 functions separate from the normal SMF [108] (or say non-test SMF), thereby reducing any additional traffic on the live network.
In another example, in case the identifier is a non-test SUPI, the processing unit [306] may categorize the target network node as a non-test SMF [310a]. Here, the 30
21
non-test SMF [310a] concludes a network node [302], designed for the live network and works differently in accordance with the test SMF [310].
The network node [302] further incorporates a network routing unit [308] connected at least with the processing unit [306], configured to route the registration request 5 to the target network node [302], where the network routing unit [308] is configured to route the registration request to the test SMF [310] when the category of the identifier is the test SUPI. Further, the test SMF [310] is one of a newly deployed SMF [108] and an upgraded SMF [108], wherein the test SMF [310] is deployed in a 5G core network to handle live user traffic after passing through at least one 10 testing procedure.
Here the network routing unit [308] is merely a processor or a combination of processors, designed primarily to route one or more registration request. Post determination of the target network node, the network routing unit [308] further 15 routes the registration request to the target network node [302]. In case the target network node [302] is the test SMF [310]. The network routing unit [308] accordingly routes the registration request to the test SMF [310]. Here, the test SMF [310] is one of a newly developed SMF [108] or an upgraded SMF [108] with an inclusion of one or more features within the existing SMF [108], recently deployed 20 in a fifth generation (5G) core network. The test SMF [310] is further to be deployed for handling live user traffic in the network, only after passing through at least one testing procedure.
Here, the at least one testing procedure involves one or more necessary changes, 25 that are required to handle the live user traffic without causing any disruption in the performance standards of the live user traffic.
For example, in case a specific entity desires to launch a new model or upgrade a version of an existing UE in the market. In such case, the new model of UE is 30 required to be tested within a Research and Development (R&D) center of the
22
specific entity before the market release. In such events, the testing is performed within the test SMF [310] and similarly the registration request for the UE is routed to the test SMF [310], and the test SMF [310] functions accordingly.
Conversely, in case the target network node [302] is the non-test SMF [310a], the 5 network routing unit [308] accordingly routes the registration request to the test SMF [310]. Here the non-test SMF [310a] is either a test SMF [310] that is being deployed in the live data traffic, after passing the at least one testing procedures or a pre-existing SMF [108] that is already present in the live data traffic.
10
For example, by using the previous example, post completing the testing of the new model or upgraded version of the existing UE model, the UE model is launched in the market, and further when the user desires to connect with the network, the registration request of the UE will be sent to the non-test SMF [310a], allowing the UE is now to be operated within live data traffic. 15
Further, upon successful registration of UE with the target network node [302], the receiving unit [304] is configured to transmit a connection establishment acknowledgement to the UE.
20 Further, post successful registration of the UE with the target network node [302] be it either, the test SMF [310] or the non-test SMF [310a], the receiving unit [304] further transmits an acknowledgement to the UE. Here, the acknowledgement may be in form of a text message, voice input or similar known in the art. Further, the acknowledgement also provides a means to double check the target network node 25 that is connected with the UE.
Referring to Figure 4, an exemplary method flow diagram [400] for routing a registration request in a communication network, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the 30 method [400] is performed by the system [300]. Further, in an implementation, the
23
system [300] may be present in a server or a network, to implement the features of the present disclosure. Also, as shown in Figure 4, the method [400] starts at step [402].
At step 404, the method [400] comprises - receiving, at the network node [302], 5 from a user equipment (UE), the registration request for establishment of a connection between the UE and a target network node [302] from a plurality of target network nodes, where the registration request comprises an identifier associated with the UE. Further the network node [302] is an Access and Mobility Management Function (AMF). 10
The method [400] states that a registration request is sent at a network node [302] from a User Equipment (UE). The registration request as mentioned includes an identifier that is linked with the UE and is transferred to the network node [302] in a plurality of data packets. Further, the identifier may include a special identity for 15 separating one UE from multiple UE that may present around, in a network.
Further, the network node [302] mentioned here is an Access and Mobility Management Function (AMF), where the AMF is one of a target network node from the plurality of network nodes, responsible for managing the access of the UE with 20 the network.
At step 406, the method [400] comprises – analyzing, by the network node [302], the identifier to determine a category of the identifier. Further, the identifier is Subscriber Permanent Identifier (SUPI), and wherein the category of the identifier 25 comprises a test SUPI and a non-test SUPI.
The method [400] further states that, post receiving the registration request, the network node [302] extracts the information (here ‘identifier’) from the registration request. The identifier is the Subscriber Permanent Identifier (SUPI), mainly used 30 for identification of the UE from other UE’s in the network.
24
Further, the network node [302] further processes the SUPI to determine the category of the SUPI such as a test SUPI and a non-test SUPI. The test SUPI refers to an identifier of a UE that is being used for testing the functionality and performance of the UE in the network. Conversely, the non-test SUPI is referred to 5 the identifier of the UE that are used by a user in live network, by the users.
At step 408, the method [400] comprises – determining, by the network node [302], the target network node [302] from the plurality of target network nodes based on the category of the identifier. wherein the plurality of target network nodes 10 comprises a test Session Management Function (SMF) [310] and a non-test SMF [310a].
The method [400] further states that the network node [302] further determines the target network node based on the identifier (or specifically based on the SUPI). The 15 plurality of target network nodes disclosed here may include one of a test Session Management Function (SMF) [310] and a non-test Session Management Function (SMF) [310a].
Further, in case the identifier is a test SUPI, the network node [302] categorizes the 20 target network node as a test SMF [310]. Here the test SMF [310] concludes a network node [302], primarily created for testing purposes of a newly launched UE or any upgradation in the UE. The test SMF [310] as mentioned functions separate from the normal SMF [108] (or say non-test SMF [310a]), thereby reducing any additional live data traffic on the network. 25
Meanwhile, in case the identifier is a non-test SUPI, the network node [302] may categorize the target network node as a non-test SMF [310a]. Here, the non-test SMF [310a] concludes a network node [302], designed for the live data traffic, and works differently in accordance with the test SMF [310]. 30
25
At step 410, the method [400] comprises – routing, by the network node [302], the registration request to the target network node [302]. The method [400] further comprises routing the registration request to the test SMF [310] when the category of the identifier is the test SUPI, where the test SMF [310] is one of a newly deployed SMF [108] and an upgraded SMF [108], wherein the test SMF [310] is 5 deployed in a 5G core network to handle live user traffic after passing through at least one network testing procedure.
The method [400] further states that, post determination of the target network node, the network routing unit [308] further routes the registration request to the target 10 network node [302]. In case the target network node [302] is the test SMF [310]. The network routing unit [308] accordingly routes the registration request to the test SMF [310]. Here, the test SMF [310] is one of a newly developed SMF [108] or an upgraded SMF [108] with an inclusion of one or more features within the existing SMF [108], recently deployed in a fifth generation (5G) core network. The 15 test SMF [310] is further to be deployed for handling live user traffic in the network, only after passing through at least one testing procedure. Here, the at least one testing procedure involves one or more necessary changes, that are required to handle the live user traffic without causing any disruption in the performance standards of the live user traffic. 20
For example, in case a specific entity desires to launch a new model or upgrade a version of an existing UE in the market. Then, the new model of UE is required to be tested within a Research and Development (R&D) center of the specific entity before the market release. In such events, when the UE desires to connect to a 25 particular network node [302], the UE sends a registration request to the network node [302], for example an AMF. The registration request incorporates an identifier (i.e. SUPI) of the UE. The AMF analyzes the SUPI as test SUPI, and accordingly determines the target network node as a Test SMF [310] and the registration request is then routed to a test SMF [310]. 30
26
Conversely, in case the target network node [302] is the non-test SMF [310a]. The network routing unit [308] accordingly routes the registration request to the non-test SMF [310a]. Here the non-test SMF [310a] is either a test SMF [310] that is being deployed in the live data traffic, after passing the at least one testing procedures or a pre-existing SMF that is already present in the live data traffic. 5
For example, by using the previous example, the UE is launched within the market, and when the user further desires to connect to the target network node. Here the AMF analyzes the SUPI as test SUPI, and accordingly determines the target network node as a non-test SMF [310a] and the registration request is then routed 10 to a non-test SMF [310a], implying the UE is now to be operated in live data traffic.
Further, the method [400] further comprises transmitting, via the network node [302], a connection acknowledgement to the UE, in an event of successful registration of the UE with the target network node. 15
Post successful registration of the UE with the target network node [302] be it either, the test SMF [310] or the non-test SMF [310a], the network node [302] further transmits an acknowledgement to the UE. Here, the acknowledgement may be in form of a text message, voice input or similar known in the art. Further, the 20 acknowledgement also provides a means to double check the target network node that is connected with the UE.
The method [400] terminates at step 412.
25
The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for routing a registration request in a communication network, the instructions include executable code which, when executed by one or more units of a network node [302], causes: a receiving unit [304] of the network node [302] to receive from a UE, a registration request for establishment of a 30 connection between the UE and a target network node [302] from a plurality of
27
target network nodes; a processing unit [306] of the network node [302] to analyze the identifier to determine a category of the identifier, and determine the target network node [302] from the plurality of target network nodes based on the category of the identifier; and a network routing unit [308] to route the registration request to the target network node [302]. 5
The present disclosure further discloses a user equipment (UE) for routing a registration request in a communication network comprising a memory, and a processor coupled to the memory, the processor configured to: transmit, to a network node [302], a request for establishing a connection between the UE and a 10 target network node [302], and receive, from the network node [302], a connection establishment acknowledgement associated with the request, wherein the connection establishment acknowledgement is received based on: analysing, by the network node [302], the identifier to determine a category of the identifier, based on the category of the identifier, determining, by the network node [302], the target 15 network node [302] from the plurality of target network nodes, and routing, by the network node [302], the registration request to the target network node [302].
As is evident from the above, the present disclosure provides a technically advanced solution for routing a registration request in a communication network. The present 20 solution solves the problem of service outage in production network in case of any issue with the upgrade or deployment of SMF. The present disclosure allows smooth and risk-free deployment/upgrade of 5G SMF node in production environment without affecting end user’s 4G/5G services. The present disclosure solves the problem of service outage in production network in case of any issue 25 with the upgrade or deployment of SMF.
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 30 principles of the present disclosure. These and other changes in the implementations
28
of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
We Claim:
1. A method [400] for routing a registration request in a communication
network, the method [400] comprising:
receiving, at a network node [302], from a User Equipment (UE), a registration request for establishing a connection between the UE and a target network node [302] from a plurality of target network nodes, wherein the registration request comprises an identifier associated with the UE;
analysing, by the network node [302], the identifier to determine a category of the identifier;
based on the category of the identifier, determining, by the network node [302], the target network node [302] from the plurality of target network nodes; and
routing, by the network node [302], the registration request to the target network node [302].
2. The method [400] as claimed in claim 1, wherein the network node [302] is an Access and Mobility Management Function (AMF).
3. The method [400] as claimed in claim 1, wherein the plurality of target network nodes comprises a test Session Management Function (SMF) [310] and a non-test SMF [310a].
4. The method [400] as claimed in claim 3, wherein the identifier is Subscriber Permanent Identifier (SUPI), and wherein the category of the identifier comprises a test SUPI and a non-test SUPI.
5. The method [400] as claimed in claim 4, further comprising: routing the registration request to the test SMF [310] when the category of the identifier is the test SUPI.

6. The method [400] as claimed in claim 5, wherein the test SMF [310] is one of a newly deployed SMF [108] and an upgraded SMF [108], and wherein the test SMF [310] is deployed in a 5G core network to handle live user traffic after passing through at least one network testing procedure.
7. The method [400] as claimed in claim 1, further comprises transmitting, via the network node [302], a connection acknowledgement to the UE, in an event of successful registration of the UE with the target network node.
8. A network node [302] for routing a registration request in a communication network, the network node [302] comprising:
a receiving unit [304], configured to receive, from a User Equipment (UE), a registration request for establishing a connection between the UE and a target network node [302] from a plurality of target network nodes, wherein the registration request comprises an identifier associated with the UE;
a processing unit [306] connected at least with the receiving unit [304], configured to:
analyze the identifier to determine a category of the identifier; and determine the target network node [302] from the plurality of target
network nodes based on the category of the identifier; and
a network routing unit [308] connected at least with the processing unit [306], configured to route the registration request to the target network node [302].
9. The network node [302] as claimed in claim 8, wherein the network node [302] is an Access and Mobility Management Function (AMF).
10. The network node [302] as claimed in claim 8, wherein the plurality of target network nodes comprises a test Session Management Function (SMF) [310] and a non-test SMF [310a].

11. The network node [302] as claimed in claim 10, wherein the identifier is Subscriber Permanent Identifier (SUPI), and wherein the category of the identifier comprises a test SUPI and a non-test SUPI.
12. The network node [302] as claimed in claim 11, wherein the network routing unit [308] is configured to route the registration request to the test SMF [310] when the category of the identifier is the test SUPI.
13. The network node [302] as claimed in claim 12, wherein the test SMF [310] is one of a newly deployed SMF [108] and an upgraded SMF [108], and wherein the test SMF [310] is deployed in a 5G core network to handle live user traffic after passing through at least one testing procedure.
14. The network node [302] as claimed in claim 8, wherein upon successful registration of UE with the target network node [302], the receiving unit [304] is configured to transmit a connection establishment acknowledgement to the UE.
15. A user equipment (UE) for routing a registration request in a communication
network comprising:
- a memory, and
- a processor coupled to the memory, the processor configured to:
o transmit, to a network node [302], a request for establishing a connection between the UE and a target network node [302], and
o receive, from the network node [302], a connection establishment acknowledgement associated with the request,
wherein the connection establishment acknowledgement is received based on:
analysing, by the network node [302], the identifier to determine a category of the identifier,

based on the category of the identifier, determining, by the network node [302], the target network node [302] from the plurality of target network nodes, and
routing, by the network node [302], the registration request to the target network node [302].

Documents

Application Documents

# Name Date
1 202321044616-STATEMENT OF UNDERTAKING (FORM 3) [03-07-2023(online)].pdf 2023-07-03
2 202321044616-PROVISIONAL SPECIFICATION [03-07-2023(online)].pdf 2023-07-03
3 202321044616-FORM 1 [03-07-2023(online)].pdf 2023-07-03
4 202321044616-FIGURE OF ABSTRACT [03-07-2023(online)].pdf 2023-07-03
5 202321044616-DRAWINGS [03-07-2023(online)].pdf 2023-07-03
6 202321044616-FORM-26 [08-09-2023(online)].pdf 2023-09-08
7 202321044616-Proof of Right [03-10-2023(online)].pdf 2023-10-03
8 202321044616-ORIGINAL UR 6(1A) FORM 1 & 26)-261023.pdf 2023-11-04
9 202321044616-ENDORSEMENT BY INVENTORS [27-05-2024(online)].pdf 2024-05-27
10 202321044616-DRAWING [27-05-2024(online)].pdf 2024-05-27
11 202321044616-CORRESPONDENCE-OTHERS [27-05-2024(online)].pdf 2024-05-27
12 202321044616-COMPLETE SPECIFICATION [27-05-2024(online)].pdf 2024-05-27
13 Abstract1.jpg 2024-06-25
14 202321044616-FORM 3 [31-07-2024(online)].pdf 2024-07-31
15 202321044616-Request Letter-Correspondence [09-08-2024(online)].pdf 2024-08-09
16 202321044616-Power of Attorney [09-08-2024(online)].pdf 2024-08-09
17 202321044616-Form 1 (Submitted on date of filing) [09-08-2024(online)].pdf 2024-08-09
18 202321044616-Covering Letter [09-08-2024(online)].pdf 2024-08-09
19 202321044616-CERTIFIED COPIES TRANSMISSION TO IB [09-08-2024(online)].pdf 2024-08-09
20 202321044616-FORM 18A [12-02-2025(online)].pdf 2025-02-12
21 202321044616-FER.pdf 2025-03-25
22 202321044616-FORM 3 [23-05-2025(online)].pdf 2025-05-23
23 202321044616-FER_SER_REPLY [29-05-2025(online)].pdf 2025-05-29
24 202321044616-US(14)-HearingNotice-(HearingDate-22-07-2025).pdf 2025-06-26
25 202321044616-FORM-26 [14-07-2025(online)].pdf 2025-07-14
26 202321044616-Correspondence to notify the Controller [14-07-2025(online)].pdf 2025-07-14
27 202321044616-Written submissions and relevant documents [04-08-2025(online)].pdf 2025-08-04
28 202321044616-ORIGINAL UR 6(1A) FORM 5-250825.pdf 2025-09-01
29 202321044616-RELEVANT DOCUMENTS [08-10-2025(online)].pdf 2025-10-08
30 202321044616-FORM 13 [08-10-2025(online)].pdf 2025-10-08
31 202321044616-ORIGINAL UR 6(1A) AFFIDAVIT-031125.pdf 2025-11-04
32 202321044616-PatentCertificate21-11-2025.pdf 2025-11-21
33 202321044616-IntimationOfGrant21-11-2025.pdf 2025-11-21

Search Strategy

1 202321044616_SearchStrategyNew_E_SearchHistory-2263E_07-03-2025.pdf

ERegister / Renewals