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 REGISTERING A REQUEST AT A GATEWAY MOBILE LOCATION CENTRE (GMLC)”
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 REGISTERING A REQUEST AT A GATEWAY MOBILE LOCATION CENTRE (GMLC)
FIELD OF INVENTION
[0001] Embodiments of the present disclosure relate, generally, to the field of wireless communication systems. More particularly, embodiments of the present disclosure relate to a method and system for registering a request at a Gateway Mobile Location Centre (GMLC).
BACKGROUND
[0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication

technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] There are several limitations associated with Gateway Mobile Location Centre (GMLC) profile registration request in case of failure from Network Repository Function (NRF) or Service Communication Proxy (SCP). The network’s capacity to handle registration requests plays a crucial role. If the network is already under heavy load, it may not accept additional retry attempts until congestion eases.
[0005] Thus, there exists an imperative need in the art to overcome the above-stated disadvantages.
SUMMARY
[0006] 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.
[0007] An aspect of the present disclosure may relate to a method for registering a request at a Gateway Mobile Location Centre (GMLC). The method comprises sending, by a transceiver unit, a profile registration request to a network repository function (NRF) node. The method further comprises receiving, by the transceiver unit from the NRF node, one of a request serving success indication and a request serving failure indication. The method further comprises performing, by a processing unit, a repeat procedure in an event the request serving failure indication is received from the NRF node. The repeat procedure comprises sending, by the transceiver unit, the profile registration request to the NRF node.

[0008] In an exemplary aspect of the present disclosure, the method further comprises performing, by the processing unit, the repeat procedure periodically at a pre-defined interval of time until the request serving success indication is received from the NRF node.
[0009] In an exemplary aspect of the present disclosure, the pre-defined interval of time is configurable based on user inputs.
[0010] In an exemplary aspect of the present disclosure, the method further comprises performing, by the processing unit, the repeat procedure for a pre-defined number of times until the request serving success indication is received from the NRF node.
[0011] In an exemplary aspect of the present disclosure, the method further comprises sending, by the transceiver unit, the profile registration request to a service communication proxy (SCP) node, wherein the SCP node is in communication with the NRF node, and wherein the SCP node is to send the profile registration request to the NRF node.
[0012] Another aspect of the present disclosure may relate to a system for registering a request at a Gateway Mobile Location Centre (GMLC). The system may include a transceiver unit. The transceiver unit may be configured to send a profile registration request to a network repository function (NRF) node. The transceiver unit may be further configured to receive, from the NRF node, one of a request serving success indication and a request serving failure indication. The system may further include a processing unit connected to at least the transceiver unit. The processing unit may be configured to perform a repeat procedure in an event the request serving failure indication is received from the NRF node. The repeat procedure may include sending, by the transceiver unit, the profile registration request to the NRF node.

[0013] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for registering a request at a Gateway Mobile Location Centre (GMLC). The instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit of the system to send a profile registration request to a network repository function (NRF) node. Further, the instructions include executable code which, when executed, causes the transceiver unit to receive, from the NRF node, one of a request serving success indication and a request serving failure indication. Further, the instructions include executable code which, when executed, causes a processing unit to perform a repeat procedure in an event the request serving failure indication is received from the NRF node. The repeat procedure includes causing the transceiver unit to send the profile registration request to the NRF node.
OBJECTS OF THE DISCLOSURE
[0014] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0015] It is an object of the present disclosure to provide a system and a method for registering a request at a Gateway Mobile Location Centre (GMLC).
[0016] It is another object of the present disclosure to retry registration request at a configuration frequency that overcomes communication failure with other NFs.
DESCRIPTION OF THE DRAWINGS
[0017] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present

disclosure. Also, the embodiments shown in the figures are not to be construed as
limiting the disclosure, but the possible variants of the method and system
according to the disclosure are illustrated herein to highlight the advantages of the
disclosure. It will be appreciated by those skilled in the art that disclosure of such
5 drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
[0018] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture; 10
[0019] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure;
15 [0020] FIG. 3 illustrates an exemplary block diagram of a system for registering a
request at a Gateway Mobile Location Centre (GMLC), in accordance with exemplary implementations of the present disclosure;
[0021] FIG. 4 illustrates a flow diagram for registering a request at a Gateway
20 Mobile Location Centre (GMLC), in accordance with the exemplary embodiments
of the present invention; and
[0022] FIG. 5 illustrates a method flow diagram for registering a request at a
Gateway Mobile Location Centre (GMLC), in accordance with exemplary
25 implementations of the present disclosure.
[0023] The foregoing shall be more apparent from the following more detailed description of the disclosure. 30
DETAILED DESCRIPTION
6

[0024] 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
5 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 above.
10
[0025] 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.
15 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.
[0026] Specific details are given in the following description to provide a thorough
20 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. 25
[0027] 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
30 concurrently. In addition, the order of the operations may be re-arranged. A process
7

is terminated when its operations are completed but could have additional steps not included in a figure.
[0028] The word “exemplary” and/or “demonstrative” is used herein to mean
5 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
10 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.
15
[0029] 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
20 of microprocessors, one or more microprocessors in association with a Digital
Signal Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of
25 the system according to the present disclosure. More specifically, the processor or
processing unit is a hardware processor.
[0030] 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”,
30 “a wireless communication device”, “a mobile communication device”, “a
communication device” may be any electrical, electronic and/or computing device
8

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
5 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.
[0031] As used herein, “storage unit” or “memory unit” refers to a machine or
10 computer-readable medium including any mechanism for storing information in a
form readable by a computer or similar machine. For example, a computer-readable
medium includes read-only memory (“ROM”), random access memory (“RAM”),
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
15 that may be required by one or more units of the system to perform their respective
functions.
[0032] As used herein “interface” or “user interface refers to a shared boundary
across which two or more separate components of a system exchange information
20 or data. The interface may also be referred to a set of rules or protocols that define
communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
25 [0033] All modules, units, components used herein, unless explicitly excluded
herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller,
30 Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
circuits (FPGA), any other type of integrated circuits, etc.
9

[0034] The Gateway Mobile Location Centre (GMLC) unit is a central unit in the system responsible for processing location related data. It acts as midway between the clients requesting location data and the components that provide such data. 5
[0035] NRF (Network Repository Function): A 5G network function responsible for service discovery, maintaining a registry of available network services, and their profiles, ensuring that service instances can be discovered by other network functions.
10
[0036] Service Communication Proxy (SCP): The SCP is a node within a 5G network architecture that acts as an intermediary, facilitating communication between network elements. It helps manage and optimize the traffic between various network functions, such as the GMLC and NRF.
15
[0037] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
20
[0038] 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 registering a request at a Gateway Mobile Location Centre
25 (GMLC).
[0039] The approaches of the present subject provides a solution, when 5G-
Gateway Mobile Location Centre (GMLC) fails to register profile in Network
Repository Function (NRF) due to failure from NRF or Service Communication
30 Proxy (SCP), it will retry registration request at a configuration frequency that will
overcome communication failure with other NFs.
10

[0040] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
[0041] FIG. 1 illustrates an exemplary block diagram representation of 5th
5 generation core (5GC) network architecture, in accordance with exemplary
implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110],
10 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
15 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.
[0042] Radio Access Network (RAN) [104] is the part of a mobile
20 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.
25 [0043] 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.
30 [0044] Session Management Function (SMF) [108] is a 5G core network function
responsible for managing session-related aspects, such as establishing, modifying,
11

and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
[0045] Service Communication Proxy (SCP) [110] is a network function in the
5 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.
[0046] Authentication Server Function (AUSF) [112] is a network function in
10 the 5G core responsible for authenticating UEs during registration and providing
security services. It generates and verifies authentication vectors and tokens.
[0047] Network Slice Specific Authentication and Authorization Function
(NSSAAF) [114] is a network function that provides authentication and
15 authorization services specific to network slices. It ensures that UEs can access only
the slices for which they are authorized.
[0048] 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.
[0049] 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. 25
[0050] 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.
12

[0051] 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.
5 [0052] Unified Data Management (UDM) [124] is a network function that
centralizes the management of subscriber data, including authentication, authorization, and subscription information.
[0053] Application Function (AF) [126] is a network function that represents
10 external applications interfacing with the 5G core network to access network
capabilities and services.
[0054] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS
15 enforcement.
[0055] 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.
20
[0056] The 5GC network architecture also comprises a plurality of interfaces for connecting the network functions with a network entity for performing the network functions. The NSSF [116] is connected with the network entity via the interface denoted as (Nnssf) interface in FIG. 1. The NEF [118] is connected with the network
25 entity via the interface denoted as (Nnef) interface in FIG. 1. The NRF [120] is
connected with the network entity via the interface denoted as (Nnrf) interface in FIG. 1. The PCF [122] is connected with the network entity via the interface denoted as (Npcf) interface in FIG. 1. The UDM [124] is connected with the network entity via the interface denoted as (Nudm) interface in FIG. 1. The AF
30 [126] is connected with the network entity via the interface denoted as (Naf)
interface in FIG. 1. The NSSAAF [114] is connected with the network entity via
13

the interface denoted as (Nnssaaf) interface in FIG. 1. The AUSF [112] is connected
with the network entity via the interface denoted as (Nausf) interface in FIG. 1. The
AMF [106] is connected with the network entity via the interface denoted as (Namf)
interface in FIG. 1. The SMF [108] is connected with the network entity via the
5 interface denoted as (Nsmf) interface in FIG. 1. The SMF [108] is connected with
the UPF [128] via the interface denoted as (N4) interface in FIG. 1. The UPF [128] is connected with the RAN [104] via the interface denoted as (N3) interface in FIG. 1. The UPF [128] is connected with the DN [130] via the interface denoted as (N6) interface in FIG. 1. The RAN [104] is connected with the AMF [106] via the
10 interface denoted as (N2). The AMF [106] is connected with the RAN [104] via the
interface denoted as (N1). The UPF [128] is connected with other UPF [128] via the interface denoted as (N9). The interfaces such as Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nnssaaf, Nausf, Namf, Nsmf, N9, N6, N4, N3, N2, and N1 can be referred to as a communication channel between one or more functions or modules
15 for enabling exchange of data or information between such functions or modules,
and network entities.
[0057] FIG. 2 illustrates an exemplary block diagram of a computing device [200] upon which the features of the present disclosure may be implemented in
20 accordance with exemplary implementation of the present disclosure. In an
implementation, the computing device [200] may also implement a method for registering a request at a Gateway Mobile Location Centre (GMLC) utilising the system. In another implementation, the computing device [200] itself implements the method for registering a request at a Gateway Mobile Location Centre (GMLC)
25 using one or more units configured within the computing device [200], wherein said
one or more units are capable of implementing the features as disclosed in the present disclosure.
[0058] The computing device [200] may include a bus [202] or other
30 communication mechanism for communicating information, and a hardware
processor [204] coupled with bus [202] for processing information. The hardware
14

processor [204] may be, for example, a general-purpose microprocessor. The
computing device [200] may also include a main memory [206], such as a random-
access memory (RAM), or other dynamic storage device, coupled to the bus [202]
for storing information and instructions to be executed by the processor [204]. The
5 main memory [206] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
processor [204]. Such instructions, when stored in non-transitory storage media
accessible to the processor [204], render the computing device [200] into a special-
purpose machine that is customized to perform the operations specified in the
10 instructions. The computing device [200] further includes a read only memory
(ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204].
[0059] A storage device [210], such as a magnetic disk, optical disk, or solid-state
15 drive is provided and coupled to the bus [202] for storing information and
instructions. The computing device [200] may be coupled via the bus [202] to a
display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
displaying information to a computer user. An input device [214], including
20 alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [202] for communicating information and command selections to the processor
[204]. Another type of user input device may be a cursor controller [216], such as a
mouse, a trackball, or cursor direction keys, for communicating direction
information and command selections to the processor [204], and for controlling
25 cursor movement on the display [212]. The input device typically has two degrees
of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
the device to specify positions in a plane.
[0060] The computing device [200] may implement the techniques described
30 herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
and/or program logic which in combination with the computing device [200] causes
15

or programs the computing device [200] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the
computing device [200] in response to the processor [204] executing one or more
sequences of one or more instructions contained in the main memory [206]. Such
5 instructions may be read into the main memory [206] from another storage medium,
such as the storage device [210]. Execution of the sequences of instructions
contained in the main memory [206] causes the processor [204] to perform the
process steps described herein. In alternative implementations of the present
disclosure, hard-wired circuitry may be used in place of or in combination with
10 software instructions.
[0061] The computing device [200] also may include a communication interface [218] coupled to the bus [202]. The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a
15 local network [222]. For example, the communication interface [218] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [218] may be a local area network (LAN) card to provide a data communication connection to a
20 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.
25 [0062] The computing device [200] can send messages and receive data, including
program code, through the network(s), the network link [220] and the communication interface [218]. In the Internet example, a server [230] might transmit a requested code for an application program through the Internet [228], the ISP [226], the local network [222], a host [224] and the communication interface
30 [218]. The received code may be executed by the processor [204] as it is received,
16

and/or stored in the storage device [210], or other non-volatile storage for later execution.
[0063] Referring to FIG. 3, an exemplary block diagram of a system [300] for
5 registering a request at a Gateway Mobile Location Centre (GMLC), in accordance
with the exemplary implementations of the present disclosure, is shown. Further, FIG. 4 illustrates a flow diagram for registering a request at a Gateway Mobile Location Centre (GMLC), in accordance with the exemplary embodiments of the present invention. 10
[0064] FIG. 3 and FIG. 4 have been explained simultaneously and may be read in conjunction with each other.
[0065] As depicted in FIG. 3, the system [300] may include at least one transceiver
15 unit [302] and at least one processing unit [304]. 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 FIG. 3, all units shown within the system [300] should
also be assumed to be connected to each other. Also, in FIG. 3 only a few units are
shown, however, the system [300] may comprise multiple such units or the system
20 [300] may comprise any such numbers of said units, as required to implement the
features of the present disclosure. Further, in an implementation, the system [300]
may be present in a user device/ user equipment [102] to implement the features of
the present disclosure. The system [300] may be a part of the user device [102]/ or
may be independent of but in communication with the user device [102] (may also
25 referred herein as a UE). In another implementation, the system [300] may reside
in a server or a network entity. In yet another implementation, the system [300] may
reside partly in the server/ network entity and partly in the user device.
[0066] The system [300] is configured for registering a request at a Gateway
30 Mobile Location Centre (GMLC), with the help of the interconnection between the
components/units of the system [300].
17

[0067] In one example, the system [300] may be implemented as or within a Gateway Mobile Location Centre (GMLC) [300A] (as depicted in FIG. 4). In such case, the different units, as depicted in FIG. 3, may be a part of the GMLC. 5
[0068] As would be understood, Gateway Mobile Location Centre (GMLC) [300A]
is a central unit in the network responsible for processing location related data. It
acts as midway between the clients requesting location data and the components
that provide such data. The Gateway Mobile Location Centre (GMLC) [300A]
10 includes functionality required to support Location Services (LCS). In one Public
Land Mobile Network (PLMN), there may be more than one GMLC [300A]. A GMLC is the first node an external LCS client accesses in a PLMN. AFs and NFs may access the GMLC [300A] directly or via NEF.
15 [0069] As would be further understood, among other functions, the GMLC [300A]
may request routing information and/or target UE privacy information from the UDM via the Nudm interface. After performing authorization of an external LCS Client or AF and verifying target UE privacy, a GMLC forwards a location request to either a serving AMF using Namf interface or to a GMLC in another PLMN using
20 the Ngmlc interface in the case of a roaming UE.
[0070] Returning to the present example, the present description has been explained with respect to the system [300] implemented as the Gateway Mobile Location Centre (GMLC) [300A]. 25
[0071] In order to perform the registration of a request at the Gateway Mobile Location Centre (GMLC) [300A], the transceiver unit [302] may send a profile registration request to a network repository function (NRF) node [306].
18

[0072] In an implementation of the present disclosure, this request is an initiation step where the GMLC [300A] communicates with the NRF node [306] to register or confirm the availability of services related to the location-based request.
5 [0073] In an example, the transceiver unit [302] is configured to send the profile
registration request to a service communication proxy (SCP) node [308]. This has
been depicted by Step 402 in FIG. 4. The SCP node [308] node may be in
communication with the NRF node [306]. The SCP node [308] acts as a relay
between the GMLC [300A] and the NRF node [306], to manage traffic, load
10 balancing, and other network optimizations.
[0074] On receiving the profile registration request from the system [300], the SCP
node [308] node may then send the profile registration request to the NRF node
[306]. This has been depicted by Step 404 in FIG. 4. The NRF node [306] receives
15 the profile registration request from the SCP node [308].
[0075] In another example, the transceiver unit [302] may directly send the profile
registration request to the NRF node [306]. On receiving the profile registration
request, the NRF node [306] checks whether the requested service is available and
20 whether it may be provided.
[0076] Thereafter, the transceiver unit [302] may receive, from the NRF node [306], one of a request serving success indication and a request serving failure indication. This has been depicted by Step 406 in FIG. 4.
25
[0077] In an implementation of the present disclosure, after the profile registration request is sent, the transceiver unit [302] is configured to wait for a response from the NRF node [306]. This response could either be a "request serving success indication," meaning the registration was successful, or a "request serving failure
30 indication," meaning the registration has failed. The transceiver unit [302] handles
19

these responses appropriately, which may involve triggering further actions, such as a repeat procedure if a failure indication is received.
[0078] Continuing further, then, the processing unit [304] may perform a repeat
5 procedure in an event the request serving failure indication is received from the
NRF node [306]. The repeat procedure comprises sending, by the transceiver unit
[302], the profile registration request to the NRF node [306]. The transceiver unit
[302] is responsible for communicating with the NRF node [306], ensuring that the
registration request is transmitted each time the repeat procedure is triggered by the
10 processing unit [304].
[0079] In an implementation of the present disclosure, the processing unit [304]
manages what happens if the network repository function (NRF) node [306] sends
back a failure indication. Specifically, if the request serving failure indication is
15 received, the processing unit [304] is configured to initiate a repeat procedure. This
means the processing unit [304] takes action to resend the profile registration request in an attempt to achieve a successful outcome.
[0080] In an example, the processing unit [304] is configured to perform the repeat
20 procedure periodically at a pre-defined interval of time until the request serving
success indication is received from the NRF node [306].
[0081] The processing unit [304] is further configured to automatically repeat the
profile registration request at regular time intervals until a successful response
25 (request serving success indication) is received from the NRF node [306]. This
periodic repeat mechanism ensures that the system continues to try and register the request without requiring manual intervention.
[0082] In another example, the pre-defined interval of time is configurable based
30 on user inputs.
20

[0083] The processing unit [304] is described as having the capability to adjust the interval at which it repeats the profile registration request based on user input. For example, in some network environments, it may be preferable to retry every 5 seconds, while in others, a longer interval might be more efficient. 5
[0084] In another example, the processing unit [304] is configured to perform the repeat procedure for a pre-defined number of times until the request serving success indication is received from the NRF node [306].
10 [0085] The processing unit [304] is programmed to repeat the profile registration
request a specific number of times. If a request serving success indication is not received from the NRF node [306] after these attempts, the procedure will stop. This feature is important for controlling the resource usage and preventing the system from endlessly repeating the process.
15
[0086] As depicted in FIG. 4, the repeat procedure may keep happening until the request serving success indication is received at the transceiver unit [302] from the NRF node [306].
20 [0087] Referring to FIG. 5, an exemplary method flow diagram [500] for
registering a request at a Gateway Mobile Location Centre (GMLC), in accordance with exemplary implementations of the present disclosure, is shown. In an implementation, the method [500] may be performed by the system [300]. Further, in an implementation, the system [300] may be present in a server device to
25 implement the features of the present disclosure. Also, as shown in FIG. 5, the
method [500] starts at step [502].
[0088] At step [504], the method comprises sending, by a transceiver unit [302], a profile registration request to a network repository function (NRF) node [306]. 30
21

[0089] In an implementation of the present disclosure, this request is an initiation step where the GMLC [300A] communicates with the NRF node [306] to register or confirm the availability of services related to the location-based request.
[0090] In an example, the transceiver unit [302] is configured to send the profile registration request to a service communication proxy (SCP) node [308]. The SCP node [308] may be in communication with the NRF node [306]. The SCP node [308] acts as a relay between the GMLC [300A] and NRF node [306], to manage traffic, load balancing, and other network optimizations.
[0091] On receiving the profile registration request from the system [300], the SCP node [308] may then send the profile registration request to the NRF node [306]. The NRF node [306] receives the profile registration request from the SCP node [308].
[0092] In another example, the transceiver unit [302] may directly send the profile registration request to the NRF node [306]. On receiving the profile registration request, the NRF node [306] checks whether the requested service is available and whether it may be provided.
[0093] At step [506], the method comprises, receiving, by the transceiver unit [302] from the NRF node [306], one of: a request serving success indication and a request serving failure indication.
[0094] In an implementation of the present disclosure, after the profile registration request is sent, the transceiver unit [302] is configured to wait for a response from the NRF node [306]. This response could either be a "request serving success indication," meaning the registration was successful, or a "request serving failure indication," meaning the registration has failed. The transceiver unit [302] handles these responses appropriately, which may involve triggering further actions.

[0095] At step [508], the method comprises, performing, by a processing unit [304], a repeat procedure in an event the request serving failure indication is received from the NRF node [306].
[0096] Continuing further, then, the processing unit [304] may perform a repeat procedure in an event the request serving failure indication is received from the NRF node. The repeat procedure comprises sending, by the transceiver unit [302], the profile registration request to the NRF node [306]. The transceiver unit [302] is responsible for communicating with the NRF, ensuring that the registration request is transmitted each time the repeat procedure is triggered by the processing unit [304].
[0097] In an implementation of the present disclosure, the processing unit [304] manages what happens if the network repository function (NRF) sends back a failure indication. Specifically, if the request serving failure indication is received, the processing unit [304] is configured to initiate a repeat procedure. This means the processing unit [304] takes action to resend the profile registration request in an attempt to achieve a successful outcome.
[0098] In an example, the processing unit [304] is configured to perform the repeat procedure periodically at a pre-defined interval of time until the request serving success indication is received from the NRF node [306].
[0099] In another example, the pre-defined interval of time is configurable based on user inputs.
[0100] In another example, the processing unit [304] is configured to perform the repeat procedure for a pre-defined number of times until the request serving success indication is received from the NRF node [306].
[0101] Thereafter, the method terminates at step [510].

[0102] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for registering a request at a Gateway Mobile Location Centre (GMLC) [300A]. The instructions include executable code which, when executed by one or more units of a system [300], causes a transceiver unit [302] of the system [300] to send a profile registration request to a network repository function (NRF) node [306]. Further, the instructions include executable code which, when executed, causes the transceiver unit [320] to receive, from the NRF node [306], one of a request serving success indication and a request serving failure indication. Further, the instructions include executable code which, when executed, causes a processing unit [304] to perform a repeat procedure in an event the request serving failure indication is received from the NRF node [306]. The repeat procedure includes causing the transceiver unit [302] to send the profile registration request to the NRF node [306].
[0103] As is evident from the above, the present disclosure provides a technically advanced solution for registering a request at a Gateway Mobile Location Centre (GMLC). In the present disclosure, provides a solution to retry registration request at a configuration frequency that overcomes communication failure with other NFs.
[0104] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
[0105] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a

particular functionality of these units for clarity, it is recognized that various 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.

We Claim:
1. A method [500] for registering a request at a Gateway Mobile Location
Centre (GMLC), the method comprising:
- sending [504], by a transceiver unit [302], a profile registration request to a network repository function (NRF) node;
- receiving [506], by the transceiver unit [302] from the NRF node, one of: a request serving success indication and a request serving failure indication; and
- performing [508], by a processing unit [304], a repeat procedure in an event the request serving failure indication is received from the NRF node,
wherein the repeat procedure comprises:
o sending, by the transceiver unit [302], the profile registration request to the NRF node.
2. The method [500] as claimed in claim 1, further comprising performing, by the processing unit [304], the repeat procedure periodically at a pre-defined interval of time until the request serving success indication is received from the NRF node.
3. The method [500] as claimed in claim 2, wherein the pre-defined interval of time is configurable based on user inputs.
4. The method [500] as claimed in claim 1, further comprising performing, by the processing unit [304], the repeat procedure for a pre-defined number of times until the request serving success indication is received from the NRF node.
5. The method [500] as claimed in claim 1, further comprising sending, by the transceiver unit [302], the profile registration request to a service communication proxy (SCP) node, wherein the SCP node [304] is in communication with the NRF node, and wherein the SCP node is to send the profile registration request to the NRF node.

6. A system [300] for registering a request at a Gateway Mobile Location
Centre (GMLC), the system comprising:
- a transceiver unit [302] configured to:
o send a profile registration request to a network repository
function (NRF) node; o receive, from the NRF node, one of: a request serving success
indication and a request serving failure indication; and
- a processing unit [304] connected to at least the transceiver unit [302],
the processing unit [304] configured to perform a repeat procedure in an
event the request serving failure indication is received from the NRF
node,
wherein the repeat procedure comprises:
▪ sending, by the transceiver unit [302], the profile registration request to the NRF node.
7. The system [300] as claimed in claim 6, wherein the processing unit [304] is configured to perform the repeat procedure periodically at a pre-defined interval of time until the request serving success indication is received from the NRF node.
8. The system [300] as claimed in claim 7, wherein the pre-defined interval of time is configurable based on user inputs.
9. The system [300] as claimed in claim 6, wherein the processing unit [304] is configured to perform the repeat procedure is performed for a pre-defined number of times until the request serving success indication is received from the NRF node.
10. The system [300] as claimed in claim 6, wherein the transceiver unit [302] is configured to send the profile registration request to a service communication proxy (SCP) node [304], wherein the SCP node [304] is in communication with the NRF node, and wherein the SCP node is configured to send the profile registration request to the NRF node.