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 REGISTRATION OF A
NETWORK FUNCTION (NF) IN A WIRELESS
COMMUNICATION NETWORK”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR REGISTRATION OF A NETWORK FUNCTION (NF) IN A WIRELESS COMMUNICATION NETWORK
FIELD OF INVENTION
[0001] The present disclosure generally relates to the field of wireless communication systems. More particularly, embodiments of the present disclosure relate to method and system for registration of a network function (NF) in a wireless communication network.
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. The third generation (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] The 5G communication deploys a Service-Based Architecture (hereinafter called SBA). A Network Repository Function (NRF) of the SBA provides a Network Function (NF) service registration and discovery, enabling NFs to identify appropriate services in one another. Moreover, the NF starts and attempts to register its supported services including but not limited to configuration, IP address(es) details, NF instance id, etc. to an NRF.
[0005] Further, over the period, various solutions have been developed to improve the performance of communication devices and to deploy an effective process of registration of the NF to the NRF. Since the NF and the NRF are separate entities, both the NF and the NRF can start in any sequence of the support services. If the NRF is not yet live or in the active status, the registration of the NF becomes problematic. Certain efforts were made to address the above problem. In a scenario where the NF sends the registration request to the NRF which is not yet live/ active, the NF is unable to complete the registration process. Instead, the NF must either be restarted, or manual intervention is required to register the NF at the NRF. The manual intervention to re-register the NF to the NRF may be performed using some command line interface (hereinafter called as the CLI). Further, CLIs often require expertise on the personnel that are to be trained for customizing the set of instructions for operating the registration of the NF. These personnel will first manually detect and solve the problem of registration. This only makes the registration of the NF completely dependent upon some external factors that will require manual efforts of registering the NF.
[0006] Thus, there exists an imperative need in the art to handle registration of NF in a wireless communication network without having to resort to manual interventions which the present disclosure aims to address.

SUMMARY
[0007] 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.
[0008] An aspect of the present disclosure may relate to a method for registration of a network function (NF) in a wireless communication network. The method includes transmitting, by a transceiver unit, a registration request to a network repository function (NRF). The method further includes receiving, by the transceiver unit, a response associated with the registration request from the NRF, wherein the response received from the NRF is one of a positive response and a negative response. The method further includes, on receiving the negative response, initiating, by a processing unit, a timer, wherein the timer comprises a pre-defined time interval. The method further includes retransmitting, by the transceiver unit to the NRF, the registration request when the pre-defined time interval associated with the timer has elapsed.
[0009] In an exemplary aspect of the present disclosure, the method further comprises receiving, by the transceiver unit, a registration confirmation message from the NRF, wherein the registration confirmation message is associated with one of the registration request and the retransmitted registration request.
[0010] In an exemplary aspect of the present disclosure, the registration confirmation message from the NRF is received by the transceiver unit in an event of a successful registration of the network function (NF) based on one of the registration request and the retransmitted registration request.
[0011] In an exemplary aspect of the present disclosure, the method further comprises retransmitting, by the transceiver unit, the registration request to the NRF

periodically at a user-configurable time interval when the pre-defined time interval associated with the timer has elapsed until the positive response is received from the NRF.
[0012] In an exemplary aspect of the present disclosure, the positive response corresponds to a successful registration of the NF in the wireless communication network.
[0013] In an exemplary aspect of the present disclosure, the negative response corresponds to an unsuccessful registration of the NF in the wireless communication network.
[0014] Another aspect of the present disclosure may relate to a system for registration of a network function (NF) in a wireless communication network. The system comprises the network function (NF). The NF comprises a transceiver unit. The transceiver unit is configured to transmit a registration request to a network repository function (NRF). The transceiver unit is further configured to receive a response associated with the registration request from the NRF, wherein the response received from the NRF is one of a positive response and a negative response. The NF further comprises a processing unit connected to at least the transceiver unit. The processing unit is configured to, on receiving the negative response, initiate a timer, wherein the timer comprises a pre-defined time interval. The transceiver unit is further configured to retransmit, to the NRF, the registration request when the pre-defined time interval associated with the timer has elapsed.
[0015] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for registration of a network function (NF) in a wireless communication network. The instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit of the system to transmit a registration request to a network repository function (NRF). Further, the instructions include executable code which,

when executed, causes the transceiver unit to receive a response associated with the registration request from the NRF, wherein the response received from the NRF is one of a positive response and a negative response. Further, the instructions include executable code which, when executed, causes a processing unit to initiate a timer on receiving the negative response, wherein the timer comprises a pre-defined time interval. Further, the instructions include executable code which, when executed, causes the transceiver unit to retransmit, to the NRF, the registration request when the pre-defined time interval associated with the timer has elapsed.
OBJECTS OF THE INVENTION
[0016] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0017] It is an object of the present disclosure to provide a system and method for handing registration of NF in a 5G communication network.
[0018] It is another object of the present disclosure to provide a solution that enables NF to register to the NRF without relying on the CLIs.
[0019] It is yet another object of the present disclosure to provide a solution that enables NF to register to the NRF without relying on the manual setting/ resetting the NF.
DESCRIPTION OF THE DRAWINGS
[0020] 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.
[0021] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture. 10
[0022] 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 [0023] FIG. 3 illustrates an exemplary block diagram of a system for registration of a network function (NF) in a wireless communication network, in accordance with exemplary implementations of the present disclosure.
[0024] FIG. 4 illustrates a process flow diagram for registration of a network 20 function (NF) in a wireless communication network, in accordance with exemplary implementations of the present disclosure.
[0025] FIG. 5 illustrates a method flow diagram for registration of a network function (NF) in a wireless communication network, in accordance with exemplary 25 implementations of the present disclosure.
[0026] The foregoing shall be more apparent from the following more detailed description of the disclosure.
30 DETAILED DESCRIPTION
7

[0027] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific 5 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 [0028] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and
15 arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0029] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of 20 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 [0030] 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 concurrently. In addition, the order of the operations may be re-arranged. A process
30 is terminated when its operations are completed but could have additional steps not included in a figure.
8

[0031] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any 5 aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed 10 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.
[0032] As used herein, a “processing unit” or “processor” or “operating processor”
15 includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific
20 Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
25
[0033] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device
30 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
9

phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of 5 a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
[0034] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a
10 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 that may be required by one or more units of the system to perform their respective
15 functions.
[0035] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define 20 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.
[0036] All modules, units, components used herein, unless explicitly excluded 25 herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array 30 circuits (FPGA), any other type of integrated circuits, etc.
10

[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. 5
[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 for registration of a network function (NF) in a wireless 10 communication network.
[0039] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network
15 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], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice
20 Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data network (DN) [130], wherein all the components are assumed to be connected to each other in a manner as obvious to
25 the person skilled in the art for implementing features of the present disclosure.
[0040] Radio Access Network (RAN) [104] is the part of a mobile
telecommunications system that connects user equipment (UE) [102] to the core
network (CN) and provides access to different types of networks (e.g., 5G network).
30 It consists of radio base stations and the radio access technologies that enable
wireless communication. In an exemplary aspect, the N2 interface connects
11

different AMFs [106] with RAN [104] to facilitate handover management, load balancing, and resource allocation within the core network, ensuring seamless connectivity and mobility.
5 [0041] 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. AMF [106] uses an Namf interface. Namf is a service-based interface exhibited by Access and Mobility Management Function 10 (AMF) [106]. In an exemplary aspect, N1 interface is used by UE [102] for transmitting non radio signalling between UE [102] and AMF [106] which includes information related to connection, mobility and session related messages to the AMF [106] which handles cases related to connection, mobility messages.
15 [0042] Session Management Function (SMF) [108] is a 5G core network function
responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement. Nsmf is a service-based interface exhibited by Session Management Function (SMF) [108]. 20 In an exemplary aspect, N4 interface in the 5G network is responsible for the interaction between the Session Management Function (SMF) 108], and the User Plane Function (UPF) [128]. And it uses the PFCP protocol. The SMF [108] uses the N4 interface to select the appropriate UPF [128] for a specific user session.
25 [0043] Service Communication Proxy (SCP) [110] is a network function in the
5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.
30 [0044] Authentication Server Function (AUSF) [112] is a network function in
the 5G core responsible for authenticating UEs during registration and providing
12

security services. It generates and verifies authentication vectors and tokens. Nausf is a service-based interface exhibited by AUSF [112].
[0045] Network Slice Specific Authentication and Authorization Function
5 (NSSAAF) [114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized. Nnssaaf interface is a service-based interface exhibited by NSSAAF [114].
10 [0046] Network Slice Selection Function (NSSF) [116] is a network function
responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies. Nnssf interface is a service-based interface exhibited by NSSF [116].
15 [0047] 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. Nnef is a service-based interface exhibited by NEF [118].
20 [0048] 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. Nnrf is a service-based interface exhibited by NRF [120].
25 [0049] 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. Npcf is a service-based interface exhibited by PCF [122].
30 [0050] Unified Data Management (UDM) [124] is a network function that
centralizes the management of subscriber data, including authentication,
13

authorization, and subscription information. Nudm is a service-based interface exhibited by UDM [124].
[0051] Application Function (AF) [126] is a network function that represents
5 external applications interfacing with the 5G core network to access network capabilities and services. Naf is service-based interface exhibited by AF [126].
[0052] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS 10 enforcement. The N3 interface is an interface defined within the 3GPP specifications for communication between the RAN [102] and the UPF [128]. The UPF [128] is a key component of the 5G core network responsible for handling user plane traffic. N3 interface is primarily used for the exchange of user plane traffic between the RAN [102] and the UPF [128]. This includes the forwarding of data 15 packets between the radio access network and the core network.
[0053] 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 In an exemplary aspect, the N6 interface in 5G architecture is a crucial component that connects the User Plane Function (UPF) to the Data Network (DN), such as the internet or private networks. The key functionalities of N6 interface are traffic demarcation, data transport, quality of service (QoS), and security.
25 [0054] FIG. 2 illustrates an exemplary block diagram of a computing device [200] (also referred to herein as computer system [200]) upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [200] may also implement a method for registration of a network function
30 (NF) in a wireless communication network utilising a system. In another implementation, the computing device [200] itself implements the method for
14

registration of a network function (NF) in a wireless communication network using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure. 5
[0055] The computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The
10 computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the
15 processor [204]. Such instructions, when stored in non-transitory storage media accessible to the processor [204], render the computing device [200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static
20 information and instructions for the processor [204].
[0056] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a
25 display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor
30 [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
15

information and command selections to the processor [204], and for controlling cursor movement on the display [212]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane. 5
[0057] The computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [200] causes or programs the computing device [200] to be a special-purpose machine.
10 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 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
15 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 software instructions.
20 [0058] The computing device [200] also may include a communication interface [218] coupled to the bus [202]. The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or
25 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 compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [218] sends and receives electrical,
30 electromagnetic or optical signals that carry digital data streams representing various types of information.
16

[0059] 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 5 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 [218]. The received code may be executed by the processor [204] as it is received, and/or stored in the storage device [210], or other non-volatile storage for later execution.
10
[0060] The computing device [200] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of computing device [200] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The devices may
15 operate independently or as part of a network and can perform a variety of tasks such as data storage, retrieval, and analysis. Additionally, computing device [200] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications.
20
[0061] Referring to FIG. 3, an exemplary block diagram of a system [300] for registration of a network function (NF) in a wireless communication network, in accordance with the exemplary implementations of the present disclosure, is shown. In one example, the system [300] may be implemented as or within a Network
25 Function (NF). This has been depicted in FIG. 4.
[0062] FIG. 4 illustrates a process flow diagram for registration of a network function (NF) in a wireless communication network, in accordance with exemplary implementations of the present disclosure. 30
17

[0063] It may be noted that FIG. 3 and FIG. 4 have been explained simultaneously and may be read in conjunction with each other.
[0064] As depicted in FIG. 3, the system [300] may be in communication with a 5 Network Repository Function (NRF) [120]. It may be noted that the system [300], along with NRF [120], may be in communication with other network components/entities as well, known to a person skilled in the art. Such network components/entities have not been depicted in FIGs. 3-4 and explained here for the sake of brevity.
10
[0065] As depicted in FIG. 3, the system [300] may include at least one transceiver unit [302] and at least one processing unit [304]. In cases where the system [300] is implemented as or within a Network Function (NF), as depicted in FIG. 4, the different units may be a part of the NF.
15
[0066] Continuing further, also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the FIG. 3, all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however,
20 the system [300] may comprise multiple such units or the system [300] may comprise any such numbers of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [300] may be present in a user device to implement the features of the present disclosure. The system [300] may be a part of the user device / or may be independent of but in
25 communication with the user device (may also 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.
18

[0067] The system [300] is configured for registration of a network function (NF) in a wireless communication network, with the help of the interconnection between the components/units of the system [300].
5 [0068] In operation, the transceiver unit [302] may transmit a registration request to the network repository function (NRF) [120]. This has been depicted by Step 402 in FIG. 4.
[0069] The transceiver unit [302] transmits a registration request to the network 10 repository function (NRF) [120] which manages the registration and discovery of the Network Function (NF). In an exemplary aspect, the transceiver unit [302], upon start-up of NF, transmits the registration request to the NRF [120]. The registration request may include a NF profile of the requesting NF.
15 [0070] In an exemplary aspect, among other functionalities, the transceiver unit [302] may also describe optional procedures that may be supported by the NF to detect the failure or restart of the NF or a NF service using the NRF [120].
[0071] In an exemplary aspect, for registering the NF in the NRF [120] the 20 transceiver unit [302] provides the NF profile of the requesting NF to the NRF [120], and the NRF [120] marks the requesting NF as available to be discovered by other NFs.
[0072] In an exemplary aspect, the transceiver unit [302] transmits the registration 25 request to register services associated to an existing NF Instance.
[0073] In an exemplary aspect, the transceiver unit [302] transmits the registration request to register NRF [120] information in another NRF [120], and this information is used for forwarding or redirecting service discovery request. 30
19

[0074] The transmitting of registration request from transceiver unit [302] to the Network Repository Function (NRF) [120] supports the functionality of maintaining the NF profile of available NF instances and their supported services; allowing other NF instances to subscribe to, and get notified about, the registration 5 in NRF of new NF instances of a given type; supporting service discovery function. It receives NF Discovery Requests from NF instances and provides the information of the available NF instances fulfilling certain criteria (e.g., supporting a given service).
10 [0075] Continuing further, the transceiver unit [302] may then receive a response associated with the registration request from the NRF [120], wherein the response received from the NRF [120] is one of a positive response and a negative response.
[0076] The NRF [120] asses the registration request and sends back the response 15 which could be the positive response or the negative response. In one example, upon receiving the registration request, the NRF [120] may also mark the requesting NF as available or unable to be discovered by the other NFs by sending back to the transceiver unit [302] the positive response and the negative response respectively.
20 [0077] In an exemplary aspect, the positive response corresponds to a successful registration of the NF in the wireless communication network. The positive response means that the registration request from the NF is successful, and the NF is registered with the NRF [120] and may be used or discovered by other network functions. In such cases, the transceiver unit [302] may then receive a registration
25 confirmation message from the NRF [120]. The registration confirmation message may indicate a successful registration of the NF, based on the transmission of registration request and receiving the positive response.
[0078] In another exemplary aspect, the NRF [120] may transmit a negative 30 response to the NF. This has been depicted by Step 404 in FIG. 4.
20

[0079] The negative response corresponds to an unsuccessful registration of the NF in the wireless communication network. The negative response means that the registration request has failed due to invalid details or other network issues.
5 [0080] Continuing further, on receiving the negative response, the processing unit [304] may initiate a timer. This has been depicted by Step 406 in FIG. 4.
[0081] As would be noted, the timer may be initiated by the processing unit [304] to delay the next attempt to register the NF with the NRF [120]. The timer further 10 includes the pre-defined time interval. This pre-defined time interval is a specific duration specifies how long the NF should wait before retrying the registration.
[0082] Continuing further, the transceiver unit [302] may be configured to retransmit, to the NRF [120], the registration request when the pre-defined time 15 interval associated with the timer has elapsed. This has been depicted by Step 408 in FIG. 4.
[0083] For example, once the pre-defined time interval has elapsed, the timer indicates that the waiting period is over and the transceiver unit [302] retransmits
20 the registration request to the NRF [120] again. The retransmission of the registration request allows the NF to make multiple attempts to register with the NRF [120] in case of initial failures. It may be noted that, as depicted in FIG. 4, the transceiver unit [302] may keep transmitting the registration to the NRF [120] for every time a negative response is received, until the positive response is received
25 from the NRF [120].
[0084] In one example, the transceiver unit [302] is configured to retransmit the registration request to the NRF [120] periodically at a user-configurable time interval when the pre-defined time interval associated with the timer has elapsed 30 until the positive response is received from the NRF [120].
21

[0085] The transceiver unit [302] retransmits the registration request to the NRF [120] the periodical user-configurable time interval which is a time period set by a user or network administrator that indicates how frequently certain actions need to be performed. In an exemplary aspect, the retransmitting of the registration request 5 to the NRF [120], the user configurable time interval specifies how often the transceiver unit [302] should attempt to resend the request until the positive response is received from the NRF [120].
[0086] Continuing further, once the positive response is received, i.e., the NF is 10 successfully registered in the wireless communication network, the transceiver unit [302] may receive a registration confirmation message from the NRF [120]. This has been depicted by Step 410 in FIG. 4.
[0087] It may be the case that the NF may receive the registration confirmation 15 message in its first attempt itself, i.e., pursuant to transmission of the registration request and successful registration of the NF.
[0088] It may also be the case that the NF may get successfully registered after multiple attempts, i.e., pursuant to retransmission of the registration request. In such 20 cases, the registration confirmation message may be received after the retransmission of the registration request.
[0089] Referring to FIG. 5, an exemplary method flow diagram [500] for registration of a network function (NF) in a wireless communication network, in 25 accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [500] is performed by the system [300]. Further, in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure.
30 [0090] It may be noted that the particular description related to one or more steps of the method [500], as would be described in foregoing description, are disclosed
22

in and may be understood in conjunction with the description of FIGS. 3-4. Also, as shown in FIG. 5, the method [500] starts at step [502].
[0091] At step [504], the method [500] comprises transmitting, by a transceiver unit 5 [302], a registration request to a network repository function (NRF).
[0092] The transceiver unit [302] transmits a registration request to the network repository function (NRF) [120] which manages the registration and discovery of the Network Function (NF). In an exemplary aspect, the transceiver unit [302], upon 10 start-up of the NF, transmits the registration request to the NRF [120]. The registration request may include a NF profile of the requesting NF.
[0093] In an exemplary aspect, among other functionalities, the transceiver unit [302] may also describe optional procedures that may be supported by NF to detect 15 the failure or restart of the NF or a NF service using the NRF [120].
[0094] In an exemplary aspect, the transceiver unit [302] transmits the registration request to register services associated to an existing NF Instance.
20 [0095] In an exemplary aspect, the transceiver unit [302] transmits the registration request to register NRF [120] information in another NRF [120], and this information is used for forwarding or redirecting service discovery request.
[0096] The transmitting of registration request from the transceiver unit [302] to 25 the Network Repository Function (NRF) [120] supports the functionality of maintaining the NF profile of available NF instances and their supported services; allowing other NF instances to subscribe to, and get notified about, the registration in NRF [120] of new NF instances of a given type; supporting service discovery function. It receives NF Discovery Requests from NF instances and provides the 30 information of the available NF instances fulfilling certain criteria (e.g., supporting a given service).
23

[0097] At step [506], the method [500] comprises receiving, by the transceiver unit [302], a response associated with the registration request from the NRF, wherein the response received from the NRF [120] is one of a positive response and a 5 negative response.
[0098] Continuing further, the transceiver unit [302] may then receive a response associated with the registration request from the NRF [120], wherein the response received from the NRF [120] is one of a positive response and a negative response.
10
[0099] The NRF [120] asses the registration request and sends back the response which could be positive response or negative response. In one example, upon receiving the registration request, the NRF [120] may also mark the requesting NF as available or unable to be discovered by other NFs by sending back to the
15 transceiver unit [302] the positive response and the negative response respectively.
[0100] In an exemplary aspect, the positive response corresponds to a successful registration of the NF in the wireless communication network. The positive response means that the registration request from the NF is successful, and the NF
20 is registered with the NRF [120] and may be used or discovered by other network functions. In such cases, the transceiver unit [302] may then receive a registration confirmation message from the NRF [120]. The registration confirmation message may indicate a successful registration of the NF, based on the transmission of registration request and receiving the positive response.
25
[0101] In another exemplary aspect, the NRF [120] may transmit a negative response to the NF. The negative response corresponds to the unsuccessful registration of the NF in the wireless communication network. The negative response means that the registration request has failed due to invalid details or other
30 network issues.
24

[0102] At step [508], the method [500] comprises on receiving the negative response, initiating, by a processing unit [304], a timer, wherein the timer comprises a pre-defined time interval.
[0103] Continuing further, on receiving the negative response, the processing unit [304] may initiate a timer. As would be noted, the timer may be initiated by the processing unit [304] to delay the next attempt to register the NF with the NRF [120]. The timer further includes the pre-defined time interval. This pre-defined time interval is a specific duration specifies how long the NF should wait before retrying the registration.
[0104] At step [510], the method [500] comprises retransmitting, by the transceiver unit [302] to the NRF [120], the registration request when the pre-defined time interval associated with the timer has elapsed.
[0105] Continuing further, the transceiver unit [302] may be configured to retransmit, to the NRF [120], the registration request when the pre-defined time interval associated with the timer has elapsed.
[0106] For example, once the pre-defined time interval has elapsed, the timer indicates that the waiting period is over and transceiver unit [302] retransmits the registration request to the NRF [120] again. The retransmission of the registration request allows the NF to make multiple attempts to register with the NRF [120] in case of initial failures. It may be noted that, as depicted in FIG. 4, the transceiver unit [302] may keep transmitting the registration to the NRF [120] for every time a negative response is received, until a positive response is received from the NRF [120].
[0107] In one example, the transceiver unit [302] is configured to retransmit the registration request to the NRF [120] periodically at a user-configurable time

interval when the pre-defined time interval associated with the timer has elapsed until the positive response is received from the NRF [120].
[0108] In one example, predefined time interval associated with a timer may be a value set between 10 seconds – 60 seconds. For example, the transceiver unit [302] sends a registration request to the NRF [120]. The NRF [120] responds with a negative response indicating that the registration request was not successful. Then upon receiving the negative response, if the pre-defined time interval associated with a timer is set at the value of 30 seconds, the processing unit [304] start a timer set to 30 seconds. Once the 30 seconds have passed, the transceiver unit [302] retransmits the registration request to the NRF [120].
[0109] The transceiver unit [302] retransmits the registration request to the NRF [12] the periodical user-configurable time interval which is a time period set by a user or network administrator that indicates how frequently certain actions need to be performed. In an exemplary aspect, the retransmitting of the registration request to the NRF [120], the user configurable time interval specifies how often the transceiver unit [302] should attempt to resend the request until the positive response is received from the NRF [120].
[0110] Continuing further, once the positive response is received, i.e., the NF is successfully registered in the wireless communication network, the transceiver unit [302] may receive a registration confirmation message from the NRF [120].
[0111] It may be the case that the NF may receive the registration confirmation message in its first attempt itself, i.e., pursuant to transmission of the registration request and successful registration of the NF.
[0112] It may also be the case that the NF may get successfully registered after multiple attempts, i.e., pursuant to retransmission of the registration request. In such

cases, the registration confirmation message may be received after the retransmission of the registration request.
[0113] At step [512], the method [500] terminates.
[0114] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for registration of a network function (NF) in a wireless communication network. 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 transmit a registration request to a network repository function (NRF) [120]. Further, the instructions include executable code which, when executed, causes the transceiver unit [302] to receive a response associated with the registration request from the NRF [120], wherein the response received from the NRF [120] is one of a positive response and a negative response. Further, the instructions include executable code which, when executed, causes a processing unit [304] to initiate a timer on receiving the negative response, wherein the timer comprises a pre-defined time interval. Further, the instructions include executable code which, when executed, causes the transceiver unit [302] to retransmit, to the NRF [120], the registration request when the pre-defined time interval associated with the timer has elapsed.
[0115] As is evident from the above, the present disclosure provides a technically advanced solution for registration of a network function (NF) in a wireless communication network. The present solution can be applied to any type of the support services of the NF whose registration is required to be done to the NRF. Thus, the manual intervention carried on in performing the registration in case of registration failure is automated thereby saving time and effort on part of the personnel employed in the services of the wireless communication network. Further, the lags and inordinate delays caused in the reporting and correction of the other associated problems in the wireless communication network is also overcome as the overall process of registration of NF to the NRF is completely automated.

[0116] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
[0117] 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.

We Claim:
1. A method [500] for registration of a network function (NF) in a wireless
communication network, the method [500] comprising:
- transmitting [504], by a transceiver unit [302], a registration request to a network repository function (NRF) [120];
- receiving [506], by the transceiver unit [302], a response associated with the registration request from the NRF [120], wherein the response received from the NRF [120] is one of a positive response and a negative response;
- on receiving the negative response, initiating [508], by a processing unit [304], a timer, wherein the timer comprises a pre-defined time interval; and
- retransmitting [510], by the transceiver unit [302] to the NRF [120], the registration request when the pre-defined time interval associated with the timer has elapsed.

2. The method [500] as claimed in claim 1 further comprising: receiving, by the transceiver unit [302], a registration confirmation message from the NRF [120], wherein the registration confirmation message is associated with one of the registration request and the retransmitted registration request.
3. The method [500] as claimed in claim 2, wherein the registration confirmation message from the NRF [120] is received by the transceiver unit in an event of a successful registration of the network function (NF) based on one of the registration request and the retransmitted registration request.
4. The method [500] as claimed in claim 1, further comprising: retransmitting, by the transceiver unit, the registration request to the NRF [120] periodically at a user-configurable time interval when the pre-defined time interval associated with the timer has elapsed until the positive response is received from the NRF [120].

5. The method [500] as claimed in claim 1, wherein the positive response corresponds to a successful registration of the NF in the wireless communication network.
6. The method [500] as claimed in claim 1, wherein the negative response corresponds to an unsuccessful registration of the NF in the wireless communication network.
7. A system [300] for registration of a network function (NF) in a wireless
communication network, the system [300] comprising:
- a transceiver unit [302] configured to:
o transmit a registration request to a network repository function (NRF) [120];
o receive a response associated with the registration request from the NRF [120], wherein the response received from the NRF [120] is one of a positive response and a negative response;
- a processing unit [304] connected to at least the transceiver unit [302], the processing unit [304] configured, to on receiving the negative response, initiate a timer, wherein the timer comprises a pre-defined time interval; and
- the transceiver unit [302] further configured to retransmit, to the NRF [120], the registration request when the pre-defined time interval associated with the timer has elapsed.

8. The system [300] as claimed in claim 7, wherein the transceiver unit [302] is further configured to receive a registration confirmation message from the NRF [120], wherein the registration confirmation message is associated with one of the registration request and the retransmitted registration request.
9. The system [300] as claimed in claim 8, wherein the registration confirmation message from the NRF [120] is received by the transceiver unit [302]

in an event of a successful registration of the network function (NF) based on one of the registration request and the retransmitted registration request.
10. The system [300] as claimed in claim 7, wherein the transceiver unit [302] is further configured to retransmit the registration request to the NRF [120] periodically at a user-configurable time interval when the pre-defined time interval associated with the timer has elapsed until the positive response is received from the NRF [120].
11. The system [300] as claimed in claim 7, wherein the positive response corresponds to a successful registration of the NF in the wireless communication network.
12. The system [300] as claimed in claim 7, wherein the negative response corresponds to an unsuccessful registration of the NF in the wireless communication network.