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 THE REGISTRATION REQUEST IN A WIRELESS 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.

METHOD AND SYSTEM FOR ROUTING THE REGISTRATION REQUEST IN A WIRELESS NETWORK
FIELD OF THE DISCLOSURE
[0001] The present disclosure relates generally to the field of wireless
communication systems. More particularly, the present disclosure relates to methods and systems for routing the registration request in a wireless communication network.
BACKGROUND
[0002] The following description of related art is intended to provide
background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] Wireless communication technology has rapidly evolved over the past
few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.

[0004] In the field of mobile communications, particularly within a Public
Land Mobile Network (PLMN) that hosts multiple dedicated isolated networks, a significant challenge arises in efficiently rerouting registration requests from User Equipment (UE) to the appropriate Access Mobility Function (AMF). These dedicated isolated networks, such as CIoT (Cellular Internet of Things) networks and Mobility networks, operate independently, each with its own set of user data, authentication functions, and mobility management functions. The traditional method of rerouting a UE to another AMF is based on network slicing, a concept that allows the creation of multiple virtual networks on top of a shared physical infrastructure. Each slice caters to a specific set of service requirements and has its own resources and network functions. However, in the case of completely isolated networks within the same PLMN, one network does not have access to the UE data of another network. This lack of shared UE data presents a problem because the authentication process fails for a UE who is wrongly routed to a network that does not possess their user data. Consequently, the UE cannot be authenticated and connected to the correct AMF, leading to service denial or delays.
[0005] Moreover, existing methods for redirecting the UE to the correct
network involve multiple message transactions between different network
functions, such as the Authentication Server Function (AUSF) and the Unified Data
Management (UDM). These interactions are necessary for authenticating the UE
and determining the correct AMF based on the user's subscription data. However,
this process introduces additional delays in redirecting the user, impacting the
overall efficiency and performance of the network. The latency in the redirection
process can be particularly detrimental in scenarios requiring low-latency
communication, such as in real-time applications or emergency services.
[0006] Thus, there exists an imperative need in the art to provide a system and
method for the efficient rerouting of registration requests to the correct AMF without the need for extensive interactions with other network functions and without the delays associated with the traditional authentication and redirection processes, which the present disclosure aims to address.

OBJECTS OF THE INVENTION
[0007] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
[0008] It is an object of the present disclosure to provide a method and system
for routing the registration request in a wireless network.
[0009] It is another object of the present disclosure to provide a method and
system for routing the registration request in a wireless network that enables the rerouting of User Equipment (UE) to the correct Access Mobility Function (AMF) within a Public Land Mobile Network (PLMN) hosting multiple dedicated isolated networks, without the need for extensive interactions with other network functions such as the Authentication Server Function (AUSF) and Unified Data Management (UDM).
[0010] It is another object of the present disclosure to provide a method and
system for routing the registration request in a wireless network that reduces the delay in redirecting the user to the appropriate AMF by eliminating the need for authentication and other message transactions typically required in traditional methods.
[0011] It is another object of the present disclosure to provide a method and
system for routing the registration request in a wireless network that enhances the efficiency and performance of the network, particularly in scenarios requiring low-latency communication, by ensuring quick and accurate connection of UEs to the appropriate network.
[0012] It is another object of the present disclosure to provide a method and
system for routing the registration request in a wireless network that utilizes a dedicated Routing Indicator (RI) value embedded in the Subscriber Concealed Identifier (SUCI) of the user to enable direct rerouting of users to the correct AMF based on the RI value, without the need for additional message exchanges or authentication processes.

[0013] It is yet another object of the present disclosure to provide a method and
system for routing the registration request in a wireless network that improves the overall user experience by ensuring that users are seamlessly connected to the correct network, even in environments with multiple isolated networks operating within the same PLMN.
SUMMARY OF THE DISCLOSURE
[0014] This section is provided to introduce certain aspects of the present
disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0015] An aspect of the present disclosure provides a method for rerouting a
registration request. The method comprises receiving, at a first network node from a User Equipment (UE), the registration request for establishing a connection between the UE and a Core Network (CN), wherein the registration request comprises an identifier associated with the UE. The method further includes analysing, by the first network node, the identifier to extract a Routing Indicator (RI), wherein the RI indicates whether the registration request is to be processed by the first network node. The method further includes processing, by the first network node, the registration request based on the RI.
[0016] In an aspect, processing the registration request comprises rerouting, by
the first network node, the registration request to a second network node of the CN when the RI indicates that the registration request is not to be processed by the first network node.
[0017] In an aspect, the second network node is identified based on the RI.
[0018] In an aspect, the identifier is Subscriber Concealed Identifier (SUCI).
[0019] In an aspect, the first network node is a first Access Mobility Function
(AMF) and the second network node is a target AMF.

[0020] In an aspect, rerouting the registration request to the target AMF is
performed based on a comparison of a dedicated RI of the target AMF with the extracted RI of the identifier, wherein comparison of the dedicated RI of the target AMF with the extracted RI of the identifier eliminates the step of independent communication with at least one authentication node, to decrease time for rerouting the registration request.
[0021] Another aspect of the present disclosure provides a system to reroute a
registration request. The system includes a first network node. The first network
node includes a receiving unit configured to receive from a User Equipment (UE),
the registration request for establishing a connection between the UE and a CN,
wherein the registration request comprises an identifier associated with the UE. The
system further includes an analysing unit configured to analyse the identifier to
extract a Routing Indicator (RI), wherein the RI indicates whether the registration
request is to be processed by the first network node. The system further includes a
processing unit configured to process the registration request based on the RI.
[0022] Yet another aspect of the present disclosure provides a non-transitory
computer-readable storage medium storing instruction to reroute a registration request, the storage medium comprising executable code which, when executed by one or more units of a system, causes: a receiving unit to receive from a User Equipment (UE), the registration request for establishing a connection between the UE and a CN, wherein the registration request comprises an identifier associated with the UE; an analysing unit to analyse the identifier to extract a Routing Indicator (RI), wherein the RI indicates whether the registration request is to be processed by the first network node; and a processing unit to process the registration request based on the RI.
BRIEF DESCRIPTION OF DRAWINGS
[0023] The accompanying drawings, which are incorporated herein, and
constitute a part of this disclosure, illustrate exemplary embodiments of the

disclosed methods and systems in which like reference numerals refer to the same
parts throughout the different drawings. Components in the drawings are not
necessarily to scale, emphasis instead being placed upon clearly illustrating the
principles of the present disclosure. Some drawings may indicate the components
using block diagrams and may not represent the internal circuitry of each
component. It will be appreciated by those skilled in the art that disclosure of such
drawings includes disclosure of electrical components, electronic components or
circuitry commonly used to implement such components.
[0024] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture, in accordance with exemplary
embodiment of the present disclosure.
[0025] FIG. 2 is an exemplary block diagram of system illustrating network
node with various functional units or modules, in accordance with an embodiment
of the present disclosure.
[0026] FIGs. 3A-3B illustrate an exemplary block diagram illustrating process
for routing the registration request to a correct AMF based on RI value, in
accordance with exemplary embodiments of the present disclosure.
[0027] FIGs. 4A-4B illustrate another exemplary block diagram illustrating
process for routing the registration request to a correct AMF based on RI value, in
accordance with exemplary embodiments of the present disclosure.
[0028] FIG. 5 illustrates an exemplary method flow diagram indicating the
process for routing the registration request to a correct AMF based on RI value, in
accordance with exemplary embodiments of the present disclosure.
[0029] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
[0030] In the following description, for the purposes of explanation, various
specific details are set forth in order to provide a thorough understanding of

embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
[0031] The ensuing description provides exemplary embodiments only, and is
not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0032] It should be noted that the terms "mobile device", "user equipment",
"user device", “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.
[0033] Specific details are given in the following description to provide a
thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other

components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[0034] Also, it is noted that individual embodiments may be described as a
process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
[0035] The word “exemplary” and/or “demonstrative” is used herein to mean
serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0036] As used herein, an “electronic device”, or “portable electronic device”,
or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including

but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
[0037] Further, the user device may also comprise a “processor”
or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.
[0038] As portable electronic devices and wireless technologies continue to
improve and grow in popularity, the advancing wireless technologies for data
transfer are also expected to evolve and replace the older generations of
technologies. In the field of wireless data communications, the dynamic
advancement of various generations of cellular technology are also seen. The
development, in this respect, has been incremental in the order of second generation
(2G), third generation (3G), fourth generation (4G), and now fifth generation (5G),
and more such generations are expected to continue in the forthcoming time.
[0039] Radio Access Technology (RAT) refers to the technology used by
mobile devices/ user equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base stations, which are responsible for providing the wireless connection. Further,

each RAT has its own set of protocols and standards for communication, which define the frequency bands, modulation techniques, and other parameters used for transmitting and receiving data. Examples of RATs include GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System), LTE (Long-Term Evolution), and 5G. The choice of RAT depends on a variety of factors, including the network infrastructure, the available spectrum, and the mobile device's/device's capabilities. Mobile devices often support multiple RATs, allowing them to connect to different types of networks and provide optimal performance based on the available network resources.
[0040] As used herein, the Access and Mobility Management Function (AMF)
is a part of the 3GPP 5G Architecture. The primary tasks of AMF include but not limited to Registration Management, Connection Management, Reachability Management, Mobility Management and various function relating to security and access management and authorization.
[0041] As used herein, 'routing indicator (RI)' refers to a set of 1–4 decimal
digits assigned by the home network operator and stored in the USIM. The RI is included in the Subscriber Concealed Identifier (SUCI) to facilitate the routing of registration requests within a mobile network. The RI helps determine the appropriate Access and Mobility Management Function (AMF) that should handle the registration request, enabling efficient re-routing without requiring interaction with other network functions such as the Authentication Server Function (AUSF) or the Unified Data Management (UDM).
[0042] As discussed in the background section, particularly within a Public
Land Mobile Network (PLMN) that hosts multiple dedicated isolated networks, a significant challenge arises in efficiently rerouting registration requests from User Equipment (UE) to the appropriate Access Mobility Function (AMF). These dedicated isolated networks, such as CIoT (Cellular Internet of Things) networks and Mobility networks, operate independently, each with its own set of user data, authentication functions, and mobility management functions. The traditional

method of rerouting a UE to another AMF is based on network slicing, a concept
that allows the creation of multiple virtual networks on top of a shared physical
infrastructure. Each slice caters to a specific set of service requirements and has its
own resources and network functions. However, in the case of completely isolated
networks within the same PLMN, one network does not have access to the UE data
of another network. This lack of shared user data (alternatively also refer as UE
data) presents a problem because the authentication process fails for a UE who is
wrongly routed to a network that does not possess their user data. Consequently,
the UE cannot be authenticated and connected to the correct AMF, leading to
service denial or delays. Moreover, existing methods for redirecting a user to the
correct network involve multiple message transactions between different network
functions, such as the Authentication Server Function (AUSF) and the Unified Data
Management (UDM). These interactions are necessary for authenticating the UE
and determining the correct AMF based on the user's subscription data. However,
this process introduces additional delays in redirecting the UE , impacting the
overall efficiency and performance of the network. The latency in the redirection
process can be particularly detrimental in scenarios requiring low-latency
communication, such as in real-time applications or emergency services.
[0043] The present disclosure aims to overcome the above-mentioned and
other existing problems in this field of technology by introducing a method and system for efficiently rerouting registration requests in a wireless network, particularly in environments where multiple dedicated isolated networks coexist within a Public Land Mobile Network (PLMN). The proposed solution is designed to address the challenges associated with traditional methods of rerouting, which are based on network slicing and often result in delays due to the need for multiple message transactions between network functions for authentication and determination of the correct Access Mobility Function (AMF). The present invention provides a novel approach for routing by utilizing a Routing Indicator (RI) embedded in the Subscriber Concealed Identifier (SUCI) of the User Equipment (UE). This RI is used to determine the appropriate AMF for processing

the registration request, allowing for direct rerouting of the UE to the correct AMF
without the need for communication with the Authentication Server Function
(AUSF) or Unified Data Management (UDM). This significantly reduces the delay
in redirecting the UE, as the redirection occurs before the authentication process,
5 eliminating several message transactions that are typically required in other
methods of redirection. By addressing the issue of isolated networks not having access to each other's UE data, the invention ensures that the authentication process does not fail due to the UE being wrongly routed to a network that does not possess their data. Instead, the registration request is rerouted towards a dedicated AMF
10 based on the RI value used in the SUCI, allowing for the assignment of International
Mobile Subscriber Identities (IMSIs) with dedicated RIs to specific AMFs without any signalling with other network functions.
[0044] It would be appreciated by the person skilled in the art that the present
disclosure provides an efficient and streamlined method for routing registration
15 requests in complex network environments, improving the overall performance and
user experience in wireless networks.
[0045] Hereinafter, exemplary embodiments of the present disclosure will be
described with reference to the accompanying drawings.
[0046] FIG. 1 illustrates an exemplary block diagram representation of 5th
20 generation core (5GC) network architecture, in accordance with exemplary
embodiment of the present disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110],
25 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
30 User Plane Function (UPF) [128], a data network (DN) [130], wherein all the
13

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.
[0047] The User Equipment (UE) [102] interfaces with the network via the
Radio Access Network (RAN) [104]; the Access and Mobility Management
5 Function (AMF) [106] manages connectivity and mobility, while the Session
Management Function (SMF) [108] administers session control; the service communication proxy (SCP) [110] routes and manages communication between network services, enhancing efficiency and security, and the Authentication Server Function (AUSF) [112] handles user authentication; the NSSAAF for integrating
10 the 5G core network with existing 4G LTE networks i.e., to enable Non-Standalone
(NSA) 5G deployments, the Network Slice Selection Function (NSSF) [116], Network Exposure Function (NEF) [118], and Network Repository Function (NRF) [120] enable network customization, secure interfacing with external applications, and maintain network function registries respectively; the Policy Control Function
15 (PCF) [122] develops operational policies, and the Unified Data Management
(UDM) [124] manages subscriber data; the Application Function (AF) [126] enables application interaction, the User Plane Function (UPF) [128] processes and forwards user data, and the Data Network (DN) [130] connects to external internet resources; collectively, these components are designed to enhance mobile
20 broadband, ensure low-latency communication, and support massive machine-type
communication, solidifying the 5GC as the infrastructure for next-generation mobile networks.
[0048] Radio Access Network (RAN) [104] is the part of a mobile
telecommunications system that connects user equipment (UE) [102] to the core
25 network (CN) and provides access to different types of networks (e.g., 5G, LTE).
It consists of radio base stations and the radio access technologies that enable wireless communication.
[0049] Access and Mobility Management Function (AMF) [106] is a 5G core
network function responsible for managing access and mobility aspects, such as UE
14

registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
[0050] Session Management Function (SMF) [108] is a 5G core network
function responsible for managing session-related aspects, such as establishing,
5 modifying, and releasing sessions. It coordinates with the User Plane Function
(UPF) for data forwarding and handles IP address allocation and QoS enforcement.
[0051] Service Communication Proxy (SCP) [110] is a network function in the
5G core that facilitates communication between other network functions by
providing a secure and efficient messaging service. It acts as a mediator for service-
10 based interfaces.
[0052] 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.
[0053] Network Slice Specific Authentication and Authorization Function
15 (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.
[0054] Network Slice Selection Function (NSSF) [116] is a network function
responsible for selecting the appropriate network slice for a UE based on factors
20 such as subscription, requested services, and network policies.
[0055] 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.
[0056] Network Repository Function (NRF) [120] is a network function that
25 acts as a central repository for information about available network functions and
services. It facilitates the discovery and dynamic registration of network functions.
[0057] 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.
15

[0058] Unified Data Management (UDM) [124] is a network function that
centralizes the management of subscriber data, including authentication, authorization, and subscription information.
[0059] Application Function (AF) [126] is a network function that represents
5 external applications interfacing with the 5G core network to access network
capabilities and services.
[0060] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS enforcement.
10 [0061] 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.
[0062] Referring to FIG. 2, an exemplary block diagram of a system [200]
illustrating network node (such as AMF [106]) with various functional units or
15 modules, in accordance with an embodiment of the present disclosure is shown.
The AMF [106] comprises a receiving unit [202], an analyzing unit [204], and processing unit [206]. Also, all of the components/ units of the system [200] are assumed to be connected to each other unless otherwise indicated below. Also, in FIG. 2 only a few units are shown, however, the system [200] may comprise
20 multiple such units or the system [200] may comprise any such numbers of said
units, as required to implement the features of the present disclosure. Further, in an implementation, the system [200] may be present at a network level to implement the features of the present invention. In an implementation, the system [200] may reside in a server or a network entity.
25 [0063] The system [200] is configured for routing the registration request to a
correct AMF, with the help of the interconnection between the components/units of
the system [200]. In order to re-route the registration request, the AMF [106] of the
system [200] is configured to receive the registration request from the UE.
[0064] The AMF [106] includes a receiving unit [202]. The receiving unit
30 [202] is configured to receive a registration request from the User Equipment (UE)
16

[102]. The registration request comprises an identifier associated with the UE [102].
Examples of identifiers include but not limited only to international mobile
equipment identity (IMSI), subscriber concealed identifier (SUCI), subscriber
permanent identifier (SUPI), international mobile equipment identity (IMEI), and
5 globally unique temporary identifier (GUTI). The identifier may contain
information that is used by the AMF [106] to determine how to process the registration request, including whether it needs to be rerouted to a different AMF within the network. The reroute refers to the process of redirecting a registration request from the UE to the appropriate AMF [106] within a mobile network. The
10 receiving unit [202] acts as the initial point of contact for the UE [102] within the
AMF [106], receiving incoming registration requests and forwarding them for further processing based on the contained identifier.
[0065] The AMF [106] includes an analysing unit [204] operatively coupled
with the receiving unit [202]. The analysing unit [204] is configured to analyse the
15 identifier received in the registration request from the User Equipment (UE) [102].
The analysing unit [204] extracts a Routing Indicator (RI) from the identifier that indicates whether the registration request is to be processed by the current AMF [106A] or if it needs to be rerouted to a different AMF [106B] within the Core Network (CN). The RI may assist in directing signalling messages to the correct
20 network entity or network function. The ability to extract and interpret the RI from
the identifier enables the AMF [106A or 106B] to handle the registration request, ensuring that it is directed to the appropriate network node for processing. This feature is particularly important in scenarios where multiple dedicated isolated networks exist within a Public Land Mobile Network (PLMN), as it allows for
25 efficient routing of registration requests without the need for extensive
communication with other network functions.
[0066] The AMF [106] includes a processing unit [206] operatively coupled
with the analysing unit [204] and the receiving unit [202]. The processing unit [206] is configured to process the registration request based on the RI extracted by the
30 analysing unit [204]. Once the RI is determined, the processing unit [206] assesses
17

whether the current AMF [106A] is the correct destination to process the
registration request. If the RI indicates that the registration request should be
processed by the current AMF, the processing unit [206] proceeds with the
necessary steps to establish a connection between the User Equipment (UE) [102]
5 and the Core Network (CN). On the other hand, if the RI suggests that the
registration request is intended for a different AMF, the processing unit [206] is responsible for rerouting the registration request to the appropriate target AMF [106B]. The target AMF identified based on the RI enables the efficient redirection of registration requests to the correct network node, ensuring that the UE [102] is
10 connected to the right part of the network without unnecessary delays or
communication with other network functions like the Authentication Server Function (AUSF) or Unified Data Management (UDM). This streamlined approach significantly reduces the time required for rerouting registration requests, enhancing the overall performance of the network.
15 [0067] Referring to FIGs. 3A-3B, an exemplary block diagram for processing
of registration request to a correct AMF based on RI value is shown, in accordance with exemplary embodiments of the present disclosure. As shown in FIGs. 3A-3B, a user equipment (UE) [302] may attach with AMF1 [106A] or AMF2 [106B] based on processing the registration request with RI value.
20 [0068] In FIG. 3A, the UE [302] sends a registration request to the first network
node, AMF1 [106A]. The receiving unit [202] of the AMF1 receives the registration request. The registration request includes an identifier such as a RI. The analysing unit [204] of the AMF1 [106A] analyses the identifier to determine the RI for indicating whether AMF1 [106A] should process the registration request or reroute
25 it to another AMF, which could be AMF2 [106B] (as shown in FIG. 3B). If the RI
matches the dedicated RI of AMF1 [106A], then the processing unit [206] within AMF1 [106A] proceeds to process the registration request, allowing the User Equipment [302] to establish a connection with the Core Network (CN). If the RI does not match, implying that another AMF is to handle the registration, AMF1
30 [106A] reroutes the registration request to AMF2 [106B], which is identified as the
18

correct network node to process the request based on the RI value (as shown in FIG.
3B). For example, the UE having SUPI with RI-X (test SUPIs) may be processed
by the first AMF i.e., AMF1 while UE having SUPI with non RI-X (non-test SUPIs)
may be processed by the second AMF i.e., AMF2.
5 [0069] Referring to FIGs. 4A-4B, an exemplary block diagram for processing
of registration request to a correct AMF based on RI value is shown, in accordance with exemplary embodiments of the present disclosure. As shown in FIGs. 4A-4B, a user equipment (UE) [402] may attach with AMF1 [106A] or AMF2 [106B] based on processing the registration request with RI value.
10 [0070] In FIG. 4A, the UE [402] sends a registration request to the second
network node, AMF2 [106B]. The receiving unit [202] of the AMF2 receives the registration request. The registration request includes an identifier such as a Routing Indicator (RI). The analysing unit [204] of the AMF2 [106B] analyses the identifier to determine the RI for indicating whether AMF2 [106B] should process the
15 registration request or reroute it to another AMF, which could be AMF1 [106A] (as
shown in FIG. 4B). If the RI matches the dedicated RI of AMF2 [106B], then the processing unit [206] of the AMF2 [106B] proceeds to process the registration request, allowing the User Equipment [402] to establish a connection with the Core Network (CN). If the RI does not match, implying that another AMF is to handle
20 the registration request, AMF2 [106B] reroutes the registration request to AMF1
[106A], which is identified as the correct network node to process the request based on the RI value (as shown in FIG. 4B).
[0071] It would be appreciated by the person skilled in the art that the present
disclosure facilitates the correct routing of the User Equipment's [102] registration
25 request to the intended Access Mobility Function based on the RI value without
necessitating independent communication with other network functions like the Authentication Server Function (AUSF) or Unified Data Management (UDM). This efficient routing is beneficial in environments with multiple dedicated isolated networks within a Public Land Mobile Network (PLMN) and results in a decrease
19

in the time required to redirect the User Equipment [102] to the correct network node.
[0072] Referring to FIG. 5 an exemplary method flow diagram [500], for
processing and re-routing the registration request at correct AMF based on RI value
5 is shown, in accordance with exemplary embodiments of the present invention is
shown. In an implementation the method [500] is performed by the system [100]. As shown in FIG. 5, the method [500] starts at step [502].
[0073] Next, at step [504], the method [500] as disclosed by the present
disclosure comprises receiving, at a first network node [106A] from a User
10 Equipment (UE) [102], the registration request for establishing a connection
between the UE and a Core Network (CN), wherein the registration request comprises an identifier associated with the UE [102]. The network node such as Access Mobility Function (AMF) (e.g., AMF1 [106A] or AMF2 [106B]) receives registration request with identifier Subscriber Concealed Identifier (SUCI) from the
15 UE [102]. In an exemplary aspect, the network node(s) AMFs (such as
AMF1[106A] or AMF2 [106B]) may be part of isolated networks within a PLMN. The registration request comprises an identifier associated with the UE [102]. The identifier may contain information that is used by the AMF (such as AMF1[106A] or AMF2 [106B]) to determine how to process the registration request, including
20 whether it needs to be rerouted to a different AMF (such as AMF1[106A] or AMF2
[106B]) within the network. The AMF (such as AMF1[106A] or AMF2 [106B]) acts as the initial point of contact for the UE [102], receiving incoming registration requests and forwarding them for further processing based on the contained identifier.
25 [0074] Next, at step [506], the method [500] as disclosed by the present
disclosure comprises analysing the identifier to extract a routing indicator (RI), wherein the RI indicates whether the registration request is to be processed by the network node [106A, 106B]. The network node such as AMFs (such as AMF1[106A] or AMF2 [106B]) analyses the SUCI identifier to extract a PLMN
30 and routing indicator (RI) value, for determining whether the registration request is
20

to be processed by the network node such as AMF1 [106A] or second network node AMF2 [106B]. In an aspect, the AMF1[106A] is configured to process registration request with RI value X and AMF2 [106A] is configured to other than this value. The ability to extract and interpret the RI from the identifier enables the AMF (such as AMF1[106A] of AMF2 [106B])to handle the registration request, ensuring that it is directed to the appropriate network node for processing. This feature is particularly important in scenarios where multiple dedicated isolated networks exist within a Public Land Mobile Network (PLMN), as it allows for efficient routing of registration requests without the need for extensive communication with other network functions.
[0075] Next, at step [508], the method [500] as disclosed by the present
disclosure comprises processing the registration request based on the RI. After
analysing the RI value, such as R1 value X, the AMF (such as AMF1[106A])
process the registration request, otherwise AMF (such as AMF1[106A]) reroute the
registration request to AMF2 [106A] or similarly AMF2 [106A] processes the
registration request based on the RI value. If the RI indicates that the registration
request should be processed by the current AMF (such as AMF1[106A]), the
processing unit [206] proceeds with the necessary steps to establish a connection
between the User Equipment (UE) [102] and the Core Network (CN). On the other
hand, if the RI suggests that the registration request is intended for a different AMF
(such as AMF1[106A]), the processing unit of AMF1 is responsible for rerouting
the request to the appropriate target AMF [106B] identified based on the RI enables
the efficient redirection of registration requests to the correct network node,
ensuring that the UE [102] is connected to the right part of the network without
unnecessary delays or communication with other network functions like the
Authentication Server Function (AUSF) or Unified Data Management (UDM). This
streamlined approach significantly reduces the time required for rerouting
registration requests, enhancing the overall performance of the network.
[0076] Thereafter, the method [500] terminates at step 510.

[0077] In an example, a user with a 5G smartphone, which acts as the user
equipment, might be moving in an area where a Consumer IoT (CIoT) network and a standard mobility network operate independently. The smartphone sends a registration request to connect to the core network. This request includes a Subscriber Concealed Identifier (SUCI), which contains a Routing Indicator (RI) among other details. The first network node, an Access Mobility Function (AMF), receives this registration request. The AMF analyzes the SUCI to extract the RI to determine if it's the correct AMF to handle this request. If the extracted RI matches the AMF’s assigned RI, indicating that this is the correct AMF, the registration request is processed, and the user is connected to the core network. If the RI does not match, it implies that the registration request should be handled by another AMF within the network. The invention streamlines the process by rerouting the registration request to the correct or target AMF based on the RI without needing to communicate with the Authentication Server Function (AUSF) or Unified Data Management (UDM). This avoids the usual delays in the redirection process, which involves multiple message transactions and authentication steps.
[0078] For example, if the user's SUCI indicates they are a subscriber to a CIoT
service, which uses a different network slice, the first AMF will reroute the registration request to the CIoT-dedicated AMF. This dedicated AMF will then process the registration request without querying the AUSF or UDM, expediting the user's connection to the correct network slice tailored for IoT devices. This method eliminates the need for additional signaling between network functions, thus reducing the time taken for rerouting and increasing the overall efficiency of the network.
[0079] An aspect of the present disclosure provides a non-transitory computer-
readable storage medium storing instruction to reroute a registration request, the storage medium comprising executable code which, when executed by one or more units of a system, causes: a receiving unit [202] to receive from a User Equipment (UE) [102], the registration request for establishing a connection between the UE and a CN, wherein the registration request comprises an identifier associated with

the UE [102]; an analysing unit [204] to analyse the identifier to extract a Routing Indicator (RI), wherein the RI indicates whether the registration request is to be processed by the first network node; and a processing unit [206] to process the registration request based on the RI.
[0080] As is evident from the above, the present disclosure provides a
technically advanced solution for routing the registration request based on the value of the RI configured in the SUCI. Thus, the present disclosure overall efficiently enhances the capability of the network by preventing any delay during the registration process. Thus, the proposed invention allows UE to be re-routed to correct AMF without communication with AUSF/UDM. This reduces the delay in redirecting the user as the redirection takes place before authentication itself. This allows to avoid several message transactions which are required for other methods of redirection.
[0081] Further, in accordance with the present disclosure, it is to be
acknowledged that the functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
[0082] While considerable emphasis has been placed herein on the disclosed
embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

We Claim:
1. A method for rerouting a registration request, the method comprising:
receiving, at a first network node [106A] from a User Equipment (UE) [102], the registration request for establishing a connection between the UE and a Core Network (CN), wherein the registration request comprises an identifier associated with the UE [102];
analyzing, by the first network node [106A], the identifier to extract a Routing Indicator (RI), wherein the RI indicates whether the registration request is to be processed by the first network node [106A]; and
processing, by the first network node [106A], the registration request based on the RI.
2. The method as claimed in claim 1, wherein processing the registration request comprises rerouting, by the first network node [106A], the registration request to a second network node [106B] of the CN when the RI indicates that the registration request is to be processed by the second network node [106B].
3. The method as claimed in claim 2, wherein the second network node [106B] is identified based on the RI.
4. The method as claimed in claim 1, wherein the identifier is Subscriber Concealed Identifier (SUCI).
5. The method as claimed in claim 2 wherein the first network node [106A] is a first Access Mobility Function (AMF) and the second network node [106B] is a target AMF.

6. The method as claimed in claim 5, wherein rerouting the registration request to the target AMF is performed based on a comparison of a dedicated RI of the target AMF with the extracted RI of the identifier.
7. The method as claimed in claim 6, wherein comparison of the dedicated RI of the target AMF with the extracted RI of the identifier eliminates the step of independent communication with at least one authentication node, to decrease time for rerouting the registration request.
8. A system to reroute a registration request, the system comprising:
a first network node [106A] comprising:
a receiving unit [202] configured to receive from a User Equipment (UE) [102], the registration request for establishing a connection between the UE and a CN, wherein the registration request comprises an identifier associated with the UE [102];
an analysing unit [204] configured to analyse the identifier to extract a Routing Indicator (RI), wherein the RI indicates whether the registration request is to be processed by the first network node; and
a processing unit [206] configured to process the registration request based on the RI.
9. The system as claimed in claim 8, wherein the processing unit is configured
to reroute the registration request to a second network node [106B] of the CN when
the RI indicates that the registration request is not to be processed.

10. The system as claimed in claim 9, wherein the second network node [106B] is identified based on the RI.
11. The system as claimed in claim 8, wherein the identifier is Subscriber Concealed Identifier (SUCI).
12. The system as claimed in claim 9, wherein the first network node [106A] is a first Access Mobility Function (AMF) and the second network node [106B] is a target AMF.
13. The system as claimed in claim 12, wherein the processing unit is configured to reroute the registration request to the target AMF based on a comparison of a dedicated RI of the target AMF with the extracted RI of the identifier.
14. The system as claimed in claim 13, wherein comparison of the dedicated RI of the target AMF with the extracted RI of the identifier eliminates the step of independent communication with at least one authentication node, to decrease time for rerouting the registration request.