FORM 2
THE PATENTS ACT, 1970
THE PATENTS RULE 0) 003
COMPLETE SPECIFICATION
APPLICANT
JIO PLATFORMS LIMITED
of Office-101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India; Nationality: India
The following specification particularly describes
the invention and the manner in which
it is to be performed

RESERVATION OF RIGHTS
[001] A portion of the disclosure of this patent document contains
material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, integrated circuit (IC) layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (herein after referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.
TECHNICAL FIELD
[002] The present disclosure relates to a field of Network Repository
Function (NRF) in a wireless network, and specifically to a system and a method for providing NRF support for cross Public Land Mobile Network (PLMN) Network Function (NF) in a wireless network.
BACKGROUND
[003] 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.
[004] Wireless communication technology has rapidly evolved over the
past few decades. The first generation of wireless communication technology was analog technology that offered only voice services. Further, when the second-generation (2G) technology was introduced, text messaging and data services became possible. The 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, the fifth

generation (5G) technology is being deployed, with even faster data speeds, low
latency, and the ability to connect multiple devices simultaneously.
[005] As wireless technologies are advancing, there is a need to cope with
the 5G requirements and deliver a high level of service to the users. In 5G network functions (NFs) are the fundamental building blocks of a telecommunications network. They are software-based entities responsible for specific tasks or services within the network architecture. Each NF performs a specific function or set of functions to enable communication services, manage network resources, ensure security, and facilitate data transmission. Generally, as a part of 5G core network deployment strategy, some of the NFs such as Location management function (LMF), Gateway Mobile Location Centre (GMLC), Network Exposure Function (NEF), Network Data Analytics Function (NWDAF) and Security Edge Protection Proxy (SEPP) may be deployed in limited super cores (e.g., central business districts or downtown areas within cities that serve as the primary hubs for economic, commercial, and cultural activities). However, the NFs may be required to support across Public Land Mobile Network (PLMN) traffic. For example, LMF, GMLC and NEF may be deployed in four super cores (e.g., city 1, city 2, city 3, and city 4 ) but these NFs (LMF, GMLC, NEF) deployed at the city 1 location may also need to cater to traffic from a different city such as a city 5 location and similar case for other super core locations as well. This poses unique challenge as these NFs may not be registering in cross PLMN Network Repository Function (NRFs) that are responsible for managing and distributing network data such as slice information, service profiles, and policies. For example, city 1 LMF may only register in city 1 NRF but not in city 5 NRF although it may also serve traffic for NF in city 5 PLMNs.
[006] There is, therefore, a need in the art to improve the state of providing
NRF support for cross-PLMN NFs in the wireless network by overcoming the deficiencies of the prior arts.

OBJECTS OF THE PRESENT DISCLOSURE
[007] It is an object of the present disclosure to provide a system to provide
Network Repository Function (NRF) support for cross-Public Land Mobile
Network (PLMN) Network Function (NF) in a wireless network.
[008] It is an object of the present disclosure to support NF registration
with PLMN list in addition to PLMN currently served by NRF.
[009] It is an object of the present disclosure to support static routing based
on a combination of NFType and PLMN (individual or list entries) for various
services.
DEFINITION
[0010] As used in the present disclosure, the following terms are generally
intended to have the meaning as set forth below, except to the extent that the context
in which they are used to indicate otherwise.
[0011] The term LMF as used herein, refers to location management
function. The LMF is responsible for keeping track of the current location of mobile
devices (such as smartphones) within the network. This function is vital for
ensuring that incoming calls, messages, and data can be routed to the correct
location when a mobile device moves from one area to another.
[0012] The term GMLC, as used herein, refers to a gateway mobile location
center. The GMLC serves as an interface between location-based service
applications and the mobile network’s location infrastructure. Its primary function
is to request and obtain the location information of mobile devices from the
network’s positioning systems.
[0013] The term NEF as used herein, refers to network exposure function.
The NEF enables authorized third-party applications and services to access specific
network functions and data securely.
[0014] The term NWDAF as used herein, refers to network data analytics
function. The NWDAF is responsible for providing data analytics and insights to
support various network functions and services, enabling operators to optimize
network performance, enhance user experience, and enable new use cases.

[0015] The term PLMN, as used herein, refers to the public land mobile
network, which is the geographical area a mobile network operator covers for voice and data services to a mobile subscriber using a SIM card. For example, an operator may have one PLMN in the whole city. Based on the location, it can be a home PLMN (HPLMN) or a visitor PLMN (VPLMN).
[0016] The term SEPP as used herein, refers to security edge protection
proxy. The SEPP plays a critical role in ensuring the security and integrity of data
transmitted between the user equipment (UE) and the core network.
[0017] The term NRF, as used herein, refers to the network repository
function. The NRF is a key architectural component specified by the 3rd Generation Partnership Project (3GPP). Its primary role is to manage and distribute network data and configuration information across the network.
SUMMARY
[0018] In an exemplary embodiment, the present invention discloses a
method for providing network repository function (NRF) support for cross public
land mobile network (PLMN) network function (NF). The method discloses
receiving, at a serving NRF, a request from a NF. The method discloses extracting
one or more parameters from the received request. The method discloses identifying
the one or more parameters in a database. The method discloses responsive to the
identifying, determining if the received request belongs to the serving NRF or a
home NRF. The method discloses responsive to the determining, registering the NF
to the serving NRF or to the home NRF. The method discloses communicating a
response message to the NF after the registration.
[0019] In some embodiments, the one or more parameters include at least
one of a type of NF (NFType) and a PLMN identifier (ID).
[0020] In some embodiments, the method further comprises determining an
address of the home NRF based on one or more extracted parameters from the
received request.
[0021] In some embodiments, the method further comprises routing the
received request to the home NRF based on the determined address.

[0022] In some embodiments, the method further comprises rejecting the
received request when one or more extracted parameters are not identified in the
database.
[0023] In some embodiments, the method further comprises communicating
an error message to the NF responsive to the rejection of the received request.
[0024] In some embodiments, the serving NRF and the home NRF are
served by a different geographical location.
[0025] In an exemplary embodiment, the present invention discloses a
system for providing network repository function (NRF) support for cross public
land mobile network (PLMN) network function (NF) in a network. The system
comprises a receiving unit configured for receiving, at a serving NRF, a request
from an NF, a database configured to store the request, and a processing unit
coupled to the receiving unit and the database and configured for receiving the
request from the database. The processing unit is further configured for extracting
one or more parameters from the received request and identifying one or more
parameters in the database. The processing unit is further configured for responsive
to the identifying and determining if the received request belongs to the serving
NRF or a home NRF. The processing unit is further configured for responsive to
the determining, registering the NF to the serving NRF or to the home NRF and
communicating a response message to the NF after the registration.
[0026] In some embodiments, the one or more parameters include at least
one of a type of NF (NFType) and a PLMN identifier (ID).
[0027] In some embodiments, the system is further configured for
determining an address of the home NRF based on the one or more extracted
parameters from the received request.
[0028] In some embodiments, the system is further configured for routing
the received request to the home NRF based on the determined address.
[0029] In some embodiments, the system is further configured to reject the
received request when one or more extracted parameters are not identified in the
database.

[0030] In some embodiments, the system is further configured for
communicating an error message to the NF responsive to the rejection of the received request.
[0031] In some embodiments, the serving NRF and the home NRF are
served by a different geographical location.
[0032] In an exemplary embodiment, the present invention discloses a user
equipment (UE) communicatively coupled with a network, the coupling comprises steps of receiving, by the network, a connection request from the UE, sending, by the network, an acknowledgment of the connection request to the UE and transmitting a plurality of signals in response to the connection request. The network is configured for performing a method for providing network repository function (NRF) support for cross public land mobile network (PLMN) network function (NF). The method discloses receiving, at a serving NRF, a request from a NF. The method discloses extracting one or more parameters from the received request. The method discloses identifying the one or more parameters in a database. The method discloses responsive to the identifying, determining if the received request belongs to the serving NRF or a home NRF. The method discloses responsive to the determining, registering the NF to the serving NRF or to the home NRF. The method discloses communicating a response message to the NF after the registration.
BRIEF DESCRIPTION OF THE DRAWINGS
[0033] In the figures, similar components and/or features may have the
same reference label. Further, various components of the same type may be
distinguished by following the reference label with a second label that distinguishes
among the similar components. If only the first reference label is used in the
specification, the description is applicable to any one of the similar components
having the same first reference label irrespective of the second reference label.
[0034] The diagrams are for illustration only, which thus is not a limitation
of the present disclosure, and wherein:

[0035] FIG. 1A illustrates an exemplary network architecture in which or
with which embodiments of the present disclosure may be implemented.
[0036] FIG. 1B illustrates another exemplary network architecture in which
or with which embodiments of the present disclosure may be implemented.
[0037] FIG. 2 illustrates an exemplary block diagram of a Network
Repository Function (NRF) support system, in accordance with an embodiment of
the present disclosure.
[0038] FIG. 3 illustrates an exemplary flow diagram of Network Function
(NF) registration, in accordance with an embodiment of the present disclosure.
[0039] FIG. 4 illustrates an exemplary flow diagram of NF discovery, in
accordance with an embodiment of the present disclosure.
[0040] FIG. 5 illustrates an exemplary computer system in which or with
which embodiments of the present disclosure may be implemented.
[0041] FIG. 6 illustrates an exemplary flow diagram for a method providing
NRF support for cross public land mobile network (PLMN) NF in a network, in
accordance with an embodiment of the disclosure.
LIST OF REFERENCE NUMERALS
100A, 100B - Network architecture
102-1, 102-2…102-N - A plurality of users
104-1, 104-2….104-N - A plurality of computing devices
106 - Network
108 – System
110 - Centralized server
112- gNodeB
200 - Block diagram
202 – Receiving unit
204 - Memory

206 – Interfacing unit
208 - Processing unit
210 – Database
212- Registration engine 5 214-Management engine
216-Other engine (s)
300 – Flow Diagram
400 – Flow Diagram
500- A computer system 10 520 – Bus
530 – Main Memory
540 – Read Only Memory
550 – Mass Storage Device
560 – Communication Port 15 570 – Processor
600- Flow Diagram
DETAILED DESCRIPTION
[0042] The following is a detailed description of embodiments of the
20 disclosure depicted in the accompanying drawings. The embodiments are in such detail as to clearly communicate the disclosure. However, the amount of detail offered is not intended to limit the anticipated variations of embodiments; on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure as defined by the
25 appended claims.
[0043] Conventionally, some of the NFs, such as LMF, GMLC, NEF,
NWDAF, and SEPP, may be deployed in limited super cores (e.g., central business districts or downtown areas within cities that serve as the primary hubs for
9

economic, commercial, and cultural activities). However, the NFs may be required
to support PLMN traffic. For example, LMF, GMLC and NEF may be deployed in
four super cores (e.g., city 1, city 2, city 3, and city 4 ) but these NFs (LMF, GMLC,
and NEF) deployed at the city 1 location may also need to cater to traffic from a
5 different city such as a city 5 location and similar case for other super core locations
as well. This poses a unique challenge as these NFs may not be registering in cross
PLMN NRFs, i.e., city 1 LMF may only register in city 1 NRF but not in a city 5
NRF, although it may also serve traffic for NF in a city 5 PLMNs.
[0044] The present invention mitigates the deficiencies of the prior arts and
10 provides an improved system and method in which the NRF supports for cross PLMN NF in a wireless network.
[0045] In an aspect, the present disclosure may provide static routing based
on a combination of NFType and PLMN (individual or list entries). There are various types of NFs, each serving a specific purpose within the network
15 architecture. The NFType corresponds to the type of NF request, for example, without limitations, a Location management function (LMF) request, a Gateway Mobile Location Centre (GMLC) request, a Network Exposure Function (NEF) request, a Network Data Analytics Function (NWDAF) request and a Security Edge Protection Proxy (SEPP) request that may be acted upon.
20 [0046] In an aspect, the NRF may refer to the routing policy for NF
discovery service (NFDiscover), AccessToken, NF status subscribe (NFStatusSubscribe), and NF status unsubscribe (NFStatusUnSubscribe) requests for forwarding it to other NRFs. The NFDiscover request fulfils the service discovery request of NF Consumer, where NRF can forward the service discovery
25 request to other NRFs based on service discovery request parameters. The NRF supports an AccessToken for a client request authorization. The NRF supports requesting an AccessToken request to the NRF and validating the AccessToken in the incoming requests. The NFStatusSubscribe allows an NF instance to subscribe to changes in the status of NF instances registered in NRF. This service operation
30 can be invoked by an NF instance in a different PLMN (via the local NRF in that PLMN). The NFStatusUnSubscribe allows an NF instance to unsubscribe to
10

changes in the status of NF instances registered in NRF. This service operation can be invoked by an NF Instance in a different PLMN (via the local NRF in that PLMN) The search order in NRF may be as follows:
a. If PLMN is not received in a request and only NF type is received, then the
5 NRF may look in static routing table based on its own PLMN list. If no entry
is found in the table, then the NRF may perform a local search in its Database (DB). If not found in the local DB, then the request may be rejected.
b. If both NFType and PLMN are received in the request and the PLMN is
10 served by NRF, then the NRF may check for an entry in the static routing
table. If the entry is found, then both NFType and PLMN may be forwarded
to the corresponding NRF. If no entry is found in the static routing table,
then the NRF may check in the local DB. If the entry is found and at least
one NF is in the "Registered” state, then a response with the NF profile
15 present in the local DB may be provided. If all the NFs found are in
"Suspended" or "Undiscoverable" state, then the request may be rejected.
c. If PLMN received in the request is not served by NRF, then the order
mentioned below may be followed:
1. If NF type is received in the request, then the NRF may check in
20 static routing table. If the entry is found, then the NF type may be
forwarded to corresponding NRF. If no entry is found in static
routing table, then the NRF may look for NR type into the NRF
address corresponding to PLMN identifier (ID) (from NRF-to-NRF
registration) to forward the request. If no match is found, then the
25 request may be rejected.
2. If NF type is not received, then the NRF may look into the NRF
address corresponding to PLMN ID either provisioned in NRF or
from NRF to NRF registration and forward the request. If no match
is found, then the request may be rejected.
30 [0047] The various embodiments of the present disclosure will be explained
in detail with reference to FIGs. 1 to 6.
11

[0048] FIG. 1A illustrates an exemplary network architecture (100A) in
which or with which embodiments of the present disclosure may be implemented.
[0049] Referring to FIG. 1A, the network architecture (100A) may include
one or more computing devices or user equipments (104-1, 104-2…104-N) 5 associated with one or more users (102-1, 102-2…102-N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2…102-N) may be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more user equipments (104-1, 104-2…104-N) may be
10 individually referred to as the user equipment (104) and collectively referred to as the user equipment (104). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although three user equipments (104) are depicted in FIG. 1A, however any number of the user equipments (104) may be
15 included without departing from the scope of the ongoing description.
[0050] In an embodiment, the user equipment (104) may include smart
devices operating in a smart environment, for example, an Internet of Things (IoT) system. In such an embodiment, the user equipment (104) may include, but is not limited to, smart phones, smart watches, smart sensors (e.g., mechanical, thermal,
20 electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users (102) and/or entities, or any combination thereof.
25 A person of ordinary skill in the art will appreciate that the user equipment (104)
may include, but is not limited to, intelligent, multi-sensing, network-connected
devices, that can integrate seamlessly with each other and/or with a central server
or a cloud-computing system or any other device that is network-connected.
[0051] In an embodiment, the user equipment (104) may include, but is not
30 limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a tablet device, and so on), a wearable computer device (e.g., a head-
12

mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of computer device with 5 wireless communication capabilities, and the like. In an embodiment, the user equipment (104) may include but is not limited to, any electrical, electronic, electro-mechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer,
10 mainframe computer, or any other computing device, wherein the user equipment (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or the entity such as touchpad, touch-enabled screen, electronic pen, and the like. A person of
15 ordinary skill in the art will appreciate that the user equipment (104) may not be
restricted to the mentioned devices and various other devices may be used.
[0052] Referring to FIG. 1A, the user equipment (104) may communicate
with a system (108), for example, an NRF support system, through a network (106). In an embodiment, the network (106) may include at least one of a Fifth Generation
20 (5G) network, 6G network, or the like. The network (106) may enable the user equipment (104) to communicate with other devices in the network architecture (100A) and/or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of
25 a variety of different communication technologies such as a wide area network
(WAN), a local area network (LAN), a wireless network, a mobile network, a
Virtual Private Network (VPN), the Internet, the Public Switched Telephone
Network (PSTN), or the like.
[0053] In another exemplary embodiment, the centralized server (110) may
30 include or comprise, by way of example but not limitation, one or more of: a stand¬alone server, a server blade, a server rack, a bank of servers, a server farm, hardware
13

supporting a part of a cloud service or system, a home server, hardware running a
virtualized server, one or more processors executing code to function as a server,
one or more machines performing server-side functionality as described herein, at
least a portion of any of the above, some combination thereof.
5 [0054] In accordance with embodiments of the present disclosure, the
system (108) may be designed and configured for supporting NF registration with PLMN list in addition to PLMN currently served by NRF. The present disclosure may support static routing based on a combination of NFType and PLMN (individual or list entries) for NFDiscover, AccessToken, NFStatusSubscribe, and
10 NFStatusUnSubscribe services.
[0055] Although FIG. 1A shows exemplary components of the network
architecture (100A), in other embodiments, the network architecture (100A) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1A. Additionally, or
15 alternatively, one or more components of the network architecture (100A) may perform functions described as being performed by one or more other components of the network architecture (100A).
[0056] FIG. 1B illustrates another exemplary network architecture in which
or with which embodiments of the present disclosure may be implemented.
20 [0057] Referring to FIG. 1B, the network architecture (100B) may include the user equipment (UE) (104), a gNodeB (112) (e.g., a network node), the network (106) and the system (108). In 5G networks, gNodeB stands for “Next Generation Node B”. The gNodeB is essentially the equivalent of the eNodeB in LTE (4G) networks. The gNodeB is the base station component in the 5G radio access network (RAN)
25 responsible for radio communication with the UE. The UE (104) may be communicatively coupled with the network (106). The communicative coupling comprises receiving, from the UE (104), a connection request by the network (106), sending an acknowledgment of the connection request, and transmitting a plurality of signals in response to the connection request.
14

[0058] FIG. 2 illustrates an exemplary block diagram (200) of a network
repository function (NRF) support system (108), in accordance with an embodiment of the present disclosure.
[0059] In an aspect, the NRF support system (108) may include a receiving
5 unit (202), a memory (204), an interfacing unit (206), a processing unit (208), and a database (210). The receiving unit (202) is configured for receiving, at a serving NRF, a request from a NF. The database (210) is configured to store the request, and the processing unit (208) is configured for receiving the request from the database (210). The processing unit (208) is further configured for extracting one
10 or more parameters from the received request and identifying/searching the one or more parameters in the database (210). The processing unit (208) is further configured for determining if the received request belongs to the serving NRF or a home NRF. The processing unit (208) is further configured for registering the NF to the serving NRF or to the home NRF and communicating a response message to
15 the NF after the registration. The processing unit (208) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the processing unit (208) may be configured to fetch and
20 execute computer-readable instructions stored in the memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may comprise any non-transitory storage
25 device including, for example, volatile memory such as Random-Access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like.
[0060] In an embodiment, the system (108) may include an interfacing unit
(206). The interfacing unit (206) may include a variety of interfaces, for example,
30 interfaces for data input and output devices, referred to as I/O devices, storage devices, and the like. The interfacing unit (206) may facilitate communication of
15

the system (108). The interfacing unit (206) may also provide a communication
pathway for one or more components of the system (108). Examples of such
components include, but are not limited to, the processing unit (208) and the
database (210).
5 [0061] The processing unit (208) may be implemented as a combination of
hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing unit (208). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the
10 processing unit (208) may be processor-executable instructions stored on a non-transitory machine-readable storage medium, and the hardware for the processing unit (208) may comprise a processing resource (for example, one or more processors) to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the
15 processing resource, implement the processing unit (208). In such examples, the system (108) may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the processing unit (208) may be
20 implemented by an electronic circuitry.
[0062] In an embodiment, the processing unit (208) may include a
registration engine (212), a management engine (214), and other engines (216). In an embodiment, the registration engine (212) may register the NF in NRF with PLMNs (part list or complete list) that are currently not served by NRF. In an
25 embodiment, the management engine (214) may handle the Discovery/ AccessToken/StatusSubscribe/StatusUnSubscribe in the following way:
a. Check A: NRF may check for the requested NFType and PLMN identifier (ID) (if provided) in its own DB. If the combination is found from the current NRF with a PLMN belonging to NRF, the NRF may send the
30 response back to the consumer NF. In case only NFType is requested and
16

no PLMN is specified, and NRF is not able to find an entry in its own DB, the request may be rejected.
b. Check B: In case PLMN ID is requested by consumer NF but is not served
by the NRF, the NRF may check the configuration table where the NRF
5 address corresponding to the PLMN list is defined based on which serving
NRF forwards the request to the home NRF. For any other PLMNs, communication may happen via SEPP procedure.
c. In the above list, post check A, check C may be performed: In check C, NRF
may check NFType and PLMN ID in the request. There may be a static table
10 configuration in NRF, which checks the combination of the above and select
target NRF (Primary and Secondary IP address and Port) for different
services, including management, discover, and AccessToken services. This
table may be able to hold multiple entries, which may contain the same
NFType multiple times, as well as the corresponding PLMN ID list
15 (comma-separated values). If check A fails, next check may be checking C
followed by check B.
[0063] In an embodiment, the database (210) may comprise data that may
be either stored or generated as a result of functionalities implemented by the
processing unit (208) or the system (108).
20 [0064] Although FIG. 2 shows an exemplary block diagram (200) of the
NRF support system (108), in other embodiments, the NRF support system (108)
may include fewer components, different components, differently arranged
components, or additional functional components than depicted in FIG. 2.
Additionally, or alternatively, one or more components of the NRF support system
25 (108) may perform functions described as being performed by one or more other
components of the NRF support system (108).
[0065] FIG. 3 illustrates an exemplary flow diagram (300) of Network
Function (NF) registration, in accordance with an embodiment of the present
disclosure.
30 [0066] With respect to FIG. 3, during NF registration to NRF, normally,
only NFs in PLMN IDs served by NRF may be allowed to register. In the present
17

disclosure, the NRF may allow NFs to register to NRF even if NRF is not serving the associated PLMN (or PLMN List). The NRF may need to create a general PLMN list for home PLMN as well as NFType and PLMN list that may be allowed to register to the NRF. Any NF that is not from the home PLMN list nor NFType 5 and PLMN list, the NF may not be registered in the NRF.
[0067] FIG. 3 discloses an NF associated with a PLMN 3 (NF (PLMN 3))
(302), a NF associated with a PLMN 2 (NF (PLMN 2)) (304), a NF associated with a PLMN 1 (NF (PLMN 1)) (306)) and a NRF associated with the PLMN 1 (NRF (PLMN 1)) (308).
10 [0068] At step 310, an NF register request is communicated from NF
(PLMN1) (306) to NRF (PLMN 1) (308). The NF (PLMN 1) (306) and the NRF (PLMN 1) (308) are associated with the same PLMN. When the NRF (PLMN 1) (308) finds the entry of the NF (PLMN 1) (306) in the home PLMN list, the NRF (PLMN 1) (308) allows the registration of the NF (PLMN 1) (306) to the NRF
15 (PLMN 1) (308).
[0069] At step 312, the NRF (PLMN 1) (308) communicates an NF register
response to the NF (PLMN 1) (306).
[0070] At step 314, an NF register request is communicated from NF
(PLMN2) (304) to NRF (PLMN 1) (308). The NF (PLMN 2) (304) and the NRF
20 (PLMN 1) (308) are associated with different PLMN. The NRF (PLMN 1) (308) extracts one or more parameters (such as an NFType and PLMN) from the received request. When the NRF (PLMN 1) (308) finds the entry of the extracted one or more parameters (NFType and PLMN) in a list containing a combination of NFType and PLMN, the NRF (PLMN 1) (308) allows registration of the NF
25 (PLMN 2) (304).
[0071] At step 316, the NRF (PLMN 1) (308) communicates an NF register
success response to the NF (PLMN 2) (304).
[0072] At step 318, a NF register request is communicated from NF (PLMN
3) (302) to NRF (PLMN 1) (308). The NRF (PLMN 1) (308) extracts one or more
30 parameters (such as a NFType and PLMN) from the received request. When the NRF (PLMN 1) (308) fails to find entry of the extracted one or more parameters
18

(NFType and PLMN) in a list containing combination of NFType and PLMN or a home PLMNs, the NRF (PLMN 1) (308) rejects the registration of the NF (PLMN 3) (302).
[0073] At step 320, the NRF (PLMN 1) (308) communicates a NF register
5 error response to the NF (PLMN 3) (302).
[0074] FIG. 4 illustrates an exemplary flow diagram (400) of NF discovery,
in accordance with an embodiment of the present disclosure.
[0075] With respect to FIG. 4, the 3rd Generation Partnership Project
(3GPP) provides an option of preconfigured NRF for fulfilling service discovery
10 requests of NF consumers where NRF may forward the service discovery request
to other NRF based on service discovery request parameters. The present disclosure
may enhance NFType and PLMN combination by building a table of lists including
NFType, PLMN list, and home NRF information available in the 3GPP standard.
[0076] The NFType value may be anyone as defined in 3GPP standards for
15 enumeration type “NFType”. PLMN list may support any combination of PLMN list in comma separated list. But NRF may make a sanity check that any combination of a single NFType and PLMN ID is not repeated while entering data into the table, and if the user tries to make such an entry, it may throw an informative error to the user and avoid duplication of entries. The table may be
20 configurable while the system is operational without any impact on the running system, and changes may be applied to the running system. The table may also provide primary Internet Protocol (IP) and secondary IP for home NRF that may be used for forwarding the discovery request. Secondary IP may be used in case the primary IP of NRF is unreachable, or the Hypertext Transfer Protocol version 2
25 (HTTP/2) connection is down. The NRF may allow other NRFs to make HTTP2 connections and may monitor the HTTP2 connections so as to make the decision to send a request from a secondary IP (in case the primary IP is no longer available). The NRF may configure a number of retries towards the primary IP of NRF before trying to the secondary IP. In case the primary IP becomes available again, NRF
30 may send a request to the primary IP automatically. Further in case, the primary IP becomes unavailable, the NRF may generate a minor alarm and when both primary
19

and secondary IP become unavailable, the NRF may generate a major alarm. Fig. 3 discloses an NF (Serving PLMN) (402), an NRF (Serving PLMN) (404), and an NRF (Home PLMN) (406).
[0077] At step 408, an NFDiscover request is received from the NF (Serving
5 PLMN) (402) to the NRF (Serving PLMN) (404). The NRF (Serving PLMN) (404) searches for the NFType and PLMN ID in its own PLMN table entries. Further, the NRF (Serving PLMN) (404) searches for the NFType and PLMN ID in the request in a configured list (containing PLMN of other NRFs) and when a Home NRF corresponding to the NFType and PLMN ID is found, the NRF (Serving PLMN)
10 (404) routes the request to the home NRF.
[0078] At step 410, an NFDiscover request is received from the NRF
(Serving PLMN) (404) to the NRF (Home PLMN) (406). The NRF (Home PLMN)
(406) searches for the NFType and PLMN ID in its own PLMN table.
[0079] At step 412, when the NRF (Home PLMN) (406) finds the NFType
15 and PLMN ID in its own PLMN table, the NRF (Home PLMN) (406)
communicates an NFDiscover success response to the NRF (Serving PLMN) (404).
[0080] At step 414, the NRF (Serving PLMN) (404) communicates the
NFDiscover success response to the NF (Serving PLMN) (402).
[0081] Upon reception of the request, if the NFType and PLMN
20 combination is served by the NRF, the NRF may cater to the service request and send a response to the serving NRF. In case NRF is not serving, then further checks, i.e., check A, check B, or check C, may be continued as defined earlier. Further, in case a request is forwarded to another NRF, the NRF may keep track of the original request and may start the timer (configurable on the fly), which checks for timeout
25 cases.
[0082] AccessToken, NFStatusSubscribe, and NFStatusUnSubscribe
services may also make use of the same table as defined for the NFDiscover service.
[0083] NFStatusNotify message may be sent directly from home NRF to
NFConsumer in serving PLMN. The NFStatusNotify allows the NRF to notify
30 subscribed NF instances of changes on the status of NF instances. This service
20

operation can be invoked directly between the NRF and an NF instance in a
different PLMN (without the involvement of the local NRF in that PLMN).
[0084] FIG. 5 illustrates an exemplary computer system (500) in which or
with which embodiments of the present disclosure may be implemented. As shown 5 in FIG. 5, the computer system (500) may include an external storage device (510), a bus (520), a main memory (530), a read only memory (540), a mass storage device (550), a communication port (560), and a processor (570). A person skilled in the art will appreciate that the computer system (500) may include more than one processor (570) and communication ports (560). Processor (570) may include
10 various modules associated with embodiments of the present disclosure.
[0085] In an embodiment, the communication port (560) may be any of an
RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port (560) may be chosen
15 depending on a network, such as a Local Area Network (LAN), Wide Area Network
(WAN), or any network to which the computer system (500) connects.
[0086] In an embodiment, the memory (530) may be Random Access
Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory (540) may be any static storage device(s) e.g., but not limited
20 to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input/Output System (BIOS) instructions for the processor (570).
[0087] In an embodiment, the mass storage (550) may be any current or
future mass storage solution, which may be used to store information and/or
25 instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g.,
30 an array of disks (e.g., SATA arrays).
21

[0088] In an embodiment, the bus (520) communicatively couples the
processor(s) (570) with the other memory, storage and communication blocks. The bus (520) may be, e.g., a Peripheral Component Interconnect (PCI)/PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB) 5 or the like, for connecting expansion cards, drives and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (570) to the computer system (500).
[0089] Optionally, operator and administrative interfaces, e.g., a display,
keyboard, joystick, and a cursor control device, may also be coupled to the bus
10 (520) to support direct operator interaction with the computer system (500). Other operator and administrative interfaces may be provided through network connections connected through the communication port (560). Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (500) limit the scope of the present
15 disclosure.
[0090] FIG. 6 illustrates an exemplary flow diagram for a method providing
NRF support for cross public land mobile network (PLMN) NF in a network, in
accordance with an embodiment of the disclosure.
[0091] At step 602, the method discloses receiving, at a serving NRF, a
20 request from an NF.
[0092] At step 604, the method discloses extracting one or more parameters
from the received request.
[0093] At step 606, the method discloses identifying the one or more
parameters in a database.
25 [0094] At step 608, the method discloses responsive to the identifying,
determining if the received request belongs to the serving NRF or a home NRF.
[0095] At step 610, the method discloses responsive to the determining,
registering the NF to the serving NRF or to the home NRF.
[0096] At step 612, the method discloses communicating a response
30 message to the NF after the registration.
22

[0097] In some embodiments, the one or more parameters include at least
one of a type of NF (NFType) and a PLMN identifier (ID).
[0098] In some embodiments, the method further comprising determining
an address of the home NRF based on the one or more extracted parameters from 5 the received request.
[0099] In some embodiments, the method further comprising routing the
received request to the home NRF based on the determined address.
[00100] In some embodiments, the method further comprising rejecting the
received request when the one or more extracted parameters are not identified in
10 the database.
[00101] In some embodiments, the method further comprising
communicating an error message to the NF responsive to the rejection of the
received request.
[00102] In some embodiments, the serving NRF and the home NRF are
15 served by a different geographical location.
[00103] In an exemplary embodiment, the present invention discloses a
system for providing network repository function (NRF) support for cross public land mobile network (PLMN) network function (NF) in a network. The system comprises a receiving unit configured for receiving, at a serving NRF, a request
20 from an NF, a database configured to store the request, and a processing unit coupled to the receiving unit and the database and configured for receiving the request from the database. The processing unit is further configured for extracting one or more parameters from the received request and identifying one or more parameters in the database. The processing unit is further configured for
25 determining if the received request belongs to the serving NRF or a home NRF.
The processing unit is further configured for registering the NF to the serving NRF
or to the home NRF and communicating a response message to the NF after the
registration.
[00104] In some embodiments, the one or more parameters include at least
30 one of a type of NF (NFType) and a PLMN identifier (ID).
23

[00105] In some embodiments, the system is further configured for
determining an address of the home NRF based on the one or more extracted
parameters from the received request.
[00106] In some embodiments, the system is further configured for routing
5 the received request to the home NRF based on the determined address.
[00107] In some embodiments, the system is further configured to reject the
received request when one or more extracted parameters are not identified in the
database.
[00108] In some embodiments, the system is further configured for
10 communicating an error message to the NF responsive to the rejection of the
received request.
[00109] In some embodiments, the serving NRF and the home NRF are
served by a different geographical location.
[00110] In an exemplary embodiment, the present invention discloses a user
15 equipment (UE) communicatively coupled with a network, the coupling comprises
steps of receiving, by the network, a connection request from the UE, sending, by
the network, an acknowledgment of the connection request to the UE and
transmitting a plurality of signals in response to the connection request. The
network is configured for performing a method for providing network repository 20 function (NRF) support for cross public land mobile network (PLMN) network
function (NF). The method discloses receiving, at a serving NRF, a request from a
NF. The method discloses extracting one or more parameters from the received
request. The method discloses identifying the one or more parameters in a database.
The method discloses responsive to the identifying, determining if the received 25 request belongs to the serving NRF or a home NRF. The method discloses
responsive to the determining, registering the NF to the serving NRF or to the home
NRF. The method discloses communicating a response message to the NF after the
registration.
[00111] While the foregoing describes various embodiments of the present
30 disclosure, other and further embodiments of the present disclosure may be devised
without departing from the basic scope thereof. The scope of the present disclosure
24

is determined by the claims that follow. The present disclosure is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the present disclosure when combined with information and knowledge available to the person having ordinary 5 skill in the art.
ADVANTAGES OF THE PRESENT DISCLOSURE
[00112] The present disclosure provides a system to provide Network
Repository Function (NRF) support for cross Public Land Mobile Network 10 (PLMN) Network Function (NF) in a wireless network.
[00113] The present disclosure supports NF registration with PLMN list in
addition to PLMN currently served by NRF.
[00114] The present disclosure supports static routing based on combination
of NFType and PLMN (individual or list entries) for NFDiscover, AccessToken, 15 NFStatusSubscribe and NFStatusUnSubscribe services.
25

We Claim:
1. A method (600) for providing network repository function (NRF) support
for cross public land mobile network (PLMN) network function (NF) in a network
(106), the method comprising:
receiving (602), at a serving NRF, a request from the NF;
extracting (604) one or more parameters from the received request;
identifying (606) the one or more parameters in a database (210);
responsive to the identifying, determining (608) if the received request belongs to the serving NRF or a home NRF;
responsive to the determining, registering (610), by a registration engine (212) the NF to the serving NRF if the received request belongs to the serving NRF or registering the NF to the home NRF if the received request belongs to the home NRF; and
communicating (612) a response message to the NF responsive to the registration.
2. The method (600) as claimed in claim 1, wherein the one or more parameters include at least one of a type of NF (NFType) and a PLMN identifier (ID).
3. The method (600) as claimed in claim 1, further comprising determining an address of the home NRF based on the one or more extracted parameters from the received request.
4. The method (600) as claimed in claim 3, further comprising routing the received request to the home NRF based on the determined address.
5. The method (600) as claimed in claim 1, further comprising rejecting the received request when the one or more extracted parameters are not identified in the database (210).

6. The method (600) as claimed in claim 5, further comprising communicating an error message to the NF responsive to the rejection of the received request.
7. The method (600) as claimed in claim 1, wherein the serving NRF and the home NRF are served by a different geographical location.
8. A system (108) for providing network repository function (NRF) support for cross public land mobile network (PLMN) network function (NF) in a network (106), the system comprising:
a receiving unit (202) configured for receiving, at a serving NRF, a request from the NF;
a database (210) configured to store the request;
a processing unit (208) coupled to the receiving unit (202) and the database (210) and configured for receiving the request from the database (210);
the processing unit (208) further configured to:
extract one or more parameters from the received request;
identify the one or more parameters in the database (210);
responsive to the identifying, determine if the received request belongs to the serving NRF or a home NRF;
responsive to the determining, register the NF to the serving NRF if the received request belongs to the serving NRF or register the NF to the home NRF if the received request belongs to the home NRF the NF to the serving NRF or to the home NRF; and
communicate a response message to the NF responsive to the registration.
9. The system (108) as claimed in claim 8, wherein the one or more parameters
include at least one of a type of NF (NFType) and a PLMN identifier (ID).

10. The system (108) as claimed in claim 8, further configured for determining an address of the home NRF based on the one or more extracted parameters from the received request.
11. The system (108) as claimed in claim 10, further configured for routing the received request to the home NRF based on the determined address.
12. The system (108) as claimed in claim 8, further configured for rejecting the received request when the one or more extracted parameters are not identified in the database (210).
13. The system (108) as claimed in claim 12, further configured for communicating an error message to the NF responsive to the rejection of the received request.
14. The system (108) as claimed in claim 8, wherein the serving NRF and the home NRF are served by a different geographical location.
15. A user equipment (UE) (104) communicatively coupled with a network (106), the coupling comprises steps of:
receiving, by the network (106), a connection request from the UE (104);
sending, by the network (106), an acknowledgment of the connection request to the UE (104); and
transmitting a plurality of signals in response to the connection request, wherein the network (106) is configured for performing a method for providing network repository function (NRF) support for cross public land mobile network (PLMN) network function (NF) as claimed in claim 1.