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 CONFIGURING AND MANAGING PROXY REGISTRATIONS IN A 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 CONFIGURING AND MANAGING PROXY REGISTRATIONS IN A NETWORK
FIELD OF THE DISCLOSURE
[0001] The present disclosure relates generally to the field of wireless
communication systems, more particularly, the present disclosure relates to methods and systems for configuring and managing proxy registrations in a network, and may also relate to methods and systems for registering custom service for Service Communication Proxy (SCP).
BACKGROUND
[0002] The following description of related art is intended to provide
background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] Wireless communication technology has rapidly evolved over the past
few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 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] 5G core networks are based on service-based architecture (SBA), which
is centered around network function (NF) services, where each NF registers itself and its supported services to a Network Repository Function (NRF), which is used by other NFs for the discovery of NF instances and their services. The Service communication Proxy (SCP) architecture contains different microservice components such as Egress SCP, Ingress SCP, and SCP Controller, where each egress SCP and Ingress SCP are associated with single or multiple NF and with single or Multiple Public Land Mobile Networks (PLMN) for better management. For Registering to NRF, all Egress SCP as well as Ingress SCP need to register separately to NRF which increases overhead at each SCP Proxy to support N27 Interface with NRF which increases compute resource requirement and thus overall cost of SCP Proxy. Also, as there can be multiple proxies, number of registration and their associated Heart Beat will increase load at NRF which ultimately increases cost of compute resources, power requirements etc.
[0005] To attempt to solve the above problem, the SCP controller performs
OAM (Operations Administration & Management) tasks for SCP Proxies to send a single registration to NRF containing details of all proxies. One way to achieve is to have multiple service instances corresponding to multiple SCP Proxies, however the existing solutions have not allowed any service for the SCP as it is just a Proxy, making single registration from the controller impossible.
[0006] Thus, there exists an imperative need in the art to register custom
service for service communication proxy, which the present disclosure aims to address.

OBJECTS OF THE DISCLOSURE
[0007] Some of the objects of the present disclosure, which at least one
implementation disclosed herein satisfies are listed herein below.
[0008] It is an object of the present disclosure to provide a system and a method
for configuring and managing proxy registrations in a network.
[0009] It is another object of the present disclosure to provide a solution that
the SCP controller which performs OAM (Operations Administration & Management) tasks for SCP Proxies sends a single registration to NRF containing details of all proxies.
SUMMARY OF THE DISCLOSURE
[0010] 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.
[0011] A first aspect of the present disclosure is related to a method for
configuring and managing proxy registrations in a network. The method comprising receiving, by a transceiver unit, one or more proxy registration requests for registration of one or more proxy services to a service communication proxy (SCP) controller, wherein the one or more proxy registration requests are transmitted in one of a startup event and during an update event. The method further comprises defining, by an identification unit, a service instance identifier with each of the one or more proxy services during the registration. The method further comprises updating, by an updating unit. one or more service attributes associated with one or

more proxy services, at the SCP controller, based at least on the one or more proxy registration requests of the one or more proxy services. The method further comprises sending, by the transceiver unit, an update registration request to a Network Repository Function (NRF) comprising information of a set of network instances.
[0012] As per another aspect of the present disclosure, the one or more proxy
registration requests comprises the one or more service attributes, wherein the one or more service attributes comprises at least one of a supported network function (NF) type, a proxy type, a supported Public Land Mobile Network (PLMN), a load, a network slice, and a locality.
[0013] As per another aspect of the present disclosure, the proxy type is at least
one of an ingress proxy type and an egress proxy type.
[0014] As per another aspect of the present disclosure, upon determining that
the proxy type of the one or more proxy service is the ingress proxy type, transmitting, by the transceiver unit, an ingress profile information to one or more egress proxies associated with the one or more proxy services.
[0015] As per another aspect of the present disclosure, the method further
comprises receiving, by the transceiver unit, a notification of NF profile update from the NRF, and forwarding, by the transceiver unit upon receiving the notification of NF profile update, a configuration information to the ingress proxy type associated with a specific NF.
[0016] Another aspect of the present disclosure further discloses a system for
configuring and managing proxy registrations in a network. The system comprises a transceiver unit, an identification unit, and an updating unit connected to each other. The transceiver unit is configured to receive one or more proxy registration

requests for registration of one or more proxy services to a service communication proxy (SCP) controller, wherein the one or more proxy registration requests are transmitted in one of a startup event and during an update event. The identification unit is configured to define a service instance identifier with each of the one or more proxy services during the registration. The updating unit configured to update one or more service attributes at the SCP controller based at least on the one or more proxy registration requests of the one or more proxy services. The transceiver unit is further configured to send an update registration request to a Network Resource Function (NRF) comprising information of a set of network instances.
[0017] Further, an aspect of the present disclosure relates to a non-transitory
computer readable storage medium storing instruction for configuring and managing proxy registrations in a 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 receive one or more proxy registration requests for registration of one or more proxy services to a service communication proxy (SCP) controller, wherein the one or more proxy registration requests are transmitted in one of a startup event and during an update event; an identification unit of the system to define a service instance identifier with each of the one or more proxy services during the registration; an updating unit of the system to update one or more service attributes at the SCP controller based at least on the one or more proxy registration requests of the one or more proxy services; the transceiver unit of the system to send an update registration request to a Network Resource Function (NRF) comprising information of a set of network instances.
BRIEF DESCRIPTION OF DRAWINGS
[0018] The accompanying drawings, which are incorporated herein, and
constitute a part of this disclosure, illustrate exemplary implementations of the disclosed methods and systems in which like reference numerals refer to the same

parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0019] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture.
[0020] FIG. 2 illustrates an exemplary block diagram of a system for
configuring and managing proxy registrations in a network, in accordance with exemplary implementations of the present disclosure.
[0021] FIG. 3 illustrates an exemplary diagram of a network to configuring and
managing proxy registrations in a network, in accordance with exemplary implementations of the present disclosure.
[0022] FIG. 4 illustrates an exemplary method flow diagram indicating the
process for configuring and managing proxy registrations in a network, in accordance with exemplary implementations of the present disclosure.
[0023] FIG. 5 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.
[0024] The foregoing shall be more apparent from the following more detailed
description of the disclosure.

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

equivalent terms or variations thereof may be used interchangeably without departing from the scope of the disclosure as defined herein.
[0028] Specific details are given in the following description to provide a
5 thorough understanding of the implementations. However, it will be understood by
one of ordinary skill in the art that the implementations may be practiced without
these specific details. For example, circuits, systems, networks, processes, and other
components may be shown as components in block diagram form in order not to
obscure the implementations in unnecessary detail. In other instances, well-known
10 circuits, processes, algorithms, structures, and techniques may be shown without
unnecessary detail in order to avoid obscuring the implementations.
[0029] Also, it is noted that individual implementations may be described as a
process which is depicted as a flowchart, a flow diagram, a data flow diagram, a
15 structure diagram, or a block diagram. Although a flowchart may describe the
operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
20
[0030] The word “exemplary” and/or “demonstrative” is used herein to mean
serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not
25 necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner
9

similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0031] As used herein, an “electronic device”, or “portable electronic device”,
5 or “user device” or “communication device” or “user equipment” or “device” refers
to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory,
10 a battery and an input-means such as a hard keypad and/or a soft keypad. The user
equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wireless Fidelity (Wi-Fi), Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a
15 mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR)
devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
20 [0032] Further, the user device may also comprise a “processor”
or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in
25 association with a DSP core, a controller, a microcontroller, Application Specific
Integrated Circuits (ASIC), Field Programmable Gate Array (FPGA) 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
30 processor is a hardware processor.
10

[0033] As portable electronic devices and wireless technologies continue to
improve and grow in popularity, the advancing wireless technologies for data
transfer are also expected to evolve and replace the older generations of
5 technologies. In the field of wireless data communications, the dynamic
advancement of various generations of cellular technology are also seen. The development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), and now fifth generation (5G), and more such generations are expected to continue in the forthcoming time.
10
[0034] 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
15 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
20 of the present disclosure.
[0035] Radio Access Technology (RAT) refers to the technology used by
mobile devices/ user equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with
25 base stations, which are responsible for providing the wireless connection. Further,
each RAT has its own set of protocols and standards for communication, which define the frequency bands, modulation techniques, and other parameters used for transmitting and receiving data. Examples of RATs include GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), UMTS
30 (Universal Mobile Telecommunications System), LTE (Long-Term Evolution),
11

and 5G NR (New Radio). The choice of RAT depends on a variety of factors,
including the network infrastructure, the available spectrum, and the mobile
device's/device's capabilities. Mobile devices often support multiple RATs,
allowing them to connect to different types of networks and provide optimal
5 performance based on the available network resources.
[0036] As discussed in the background section, the current known solutions for
registering to network repository function (NRF), all Egress SCP as well as Ingress
SCP need to register separately to NRF requires increased overhead at each SCP
10 Proxy to support N27 Interface with NRF and increased compute resource
requirement and thus overall cost of SCP Proxy. Also, as there can be multiple proxies, number of registration and their associated Heart Beat will increase load at NRF which ultimately increases cost of compute resources, power requirements etc.
15 [0037] The present disclosure aims to overcome the above-mentioned and
other existing problems in this field of technology by performing OAM (Operations Administration & Management) tasks for SCP Proxies to send a single registration to NRF containing details of all proxies. One way to achieve is to have multiple service instances corresponding to multiple SCP Proxies, however the existing
20 solutions have not allowed any service for SCP as it is just a Proxy, making single
registration from controller impossible. To overcome the existing problems, the present disclosure defines a custom service for SCP.
[0038] Hereinafter, exemplary implementations of the present disclosure will
25 be described with reference to the accompanying drawings.
[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
30 architecture [100] includes a user equipment (UE) [102], a radio access network
12

(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
5 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
10 the person skilled in the art for implementing features of the present disclosure.
[0040] The User Equipment (UE) [102] interfaces with the network via the
Radio Access Network (RAN) [104]; the Access and Mobility Management Function (AMF) [106] manages connectivity and mobility, while the Session
15 Management Function (SMF) [108] administers session control; the service
communication proxy (SCP) [110] routes and manages communication between network services, enhancing efficiency and security, and the Authentication Server Function (AUSF) [112] handles user authentication; the Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] for integrating the 5G
20 core network with existing 4G LTE networks i.e., to enable Non-Standalone (NSA)
5G deployments, the Network Slice Selection Function (NSSF) [116], Network Exposure Function (NEF) [118], and Network Repository Function (NRF) [120] enable network customization, secure interfacing with external applications, and maintain network function registries respectively; the Policy Control Function
25 (PCF) [122] develops operational policies, and the Unified Data Management
(UDM) [124] manages subscriber data; the Application Function (AF) [126] enables application interaction, the User Plane Function (UPF) [128] processes and forwards user data, and the Data Network (DN) [130] connects to external internet resources; collectively, these components are designed to enhance mobile
30 broadband, ensure low-latency communication, and support massive machine-type
13

communication, solidifying the 5GC as the infrastructure for next-generation mobile networks.
[0041] Radio Access Network (RAN) [104] is the part of a mobile
5 telecommunications system that connects user equipment (UE) [102] to the core
network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
10 [0042] 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.
15 [0043] 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.
20 [0044] 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.
25 [0045] Authentication Server Function (AUSF) [112] is a network function in
the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
[0046] Network Slice Specific Authentication and Authorization Function
30 (NSSAAF) [114] is a network function that provides authentication and
14

authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.
[0047] Network Slice Selection Function (NSSF) [116] is a network function
5 responsible for selecting the appropriate network slice for a UE based on factors
such as subscription, requested services, and network policies.
[0048] Network Exposure Function (NEF) [118] is a network function that
exposes capabilities and services of the 5G network to external applications,
10 enabling integration with third-party services and applications.
[0049] 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.
15 The Network Repository Function (NRF) [120] also provides service discovery of
NRF services and their endpoint addresses by the NRF bootstrapping service. The NRF [120] also supports service discovery function and receive NF Discovery Request from NF instance or SCP [110], and provides the information of the discovered NF instances (be discovered) to the NF instance or SCP [110]. The NRF
20 [120] also supports proxy call session control function (P-CSCF) discovery which
is a specialized case of application function (AF) discovery by the SMF [110]. The NRF [120] further comprises maintaining an NF profile of available NF instances and their supported services. The NRF [120] also maintains a SCP profile of available SCP instances. The NRF [120] further supports SCP discovery by SCP
25 instances.
[0050] The NRF [120] also notifies about newly registered/updated/
deregistered NF and SCP instances along with its potential NF services to the
subscribed NF service consumer or SCP [110]. The NRF [120] is also responsible
30 for maintaining the health status of NFs and SCP [110].
15

[0051] Policy Control Function (PCF) [122] is a network function responsible
for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies. 5
[0052] Unified Data Management (UDM) [124] is a network function that
centralizes the management of subscriber data, including authentication, authorization, and subscription information.
10 [0053] Application Function (AF) [126] is a network function that represents
external applications interfacing with the 5G core network to access network capabilities and services.
[0054] User Plane Function (UPF) [128] is a network function responsible for
15 handling user data traffic, including packet routing, forwarding, and QoS
enforcement.
[0055] Data Network (DN) [130] refers to a network that provides data services
to user equipment (UE) in a telecommunications system. The data services may
20 include but are not limited to Internet services, private data network related services.
[0056] Referring to FIG. 2, an exemplary block diagram of a system [200] for
configuring and managing proxy registrations in a network is shown, in accordance with the exemplary implementations of the present disclosure. The system [200]
25 may also be used for registering custom service for service communication proxy.
The system [200] comprises at least one transceiver unit [202], an identification unit [204], and an updating unit [206]. Also, all of the components/ units of the system [200] are assumed to be connected to each other unless otherwise indicated below. Also, in FIG. 2 only a few units are shown, however, the system [200] may
30 comprise multiple such units or the system [200] may comprise any such numbers
16

of said units, as required to implement the features of the present disclosure.
Further, in an implementation, the system [200] may be present in a server device
configured at the network entity to implement the features of the present disclosure.
The system [200] may be a part of the server device / or may be independent of but
5 in communication with the server device.
[0057] The system [200] is configured for configuring and managing proxy
registrations in a network, with the help of the interconnection between the components/units of the system [200]. 10
[0058] Also, the system [200] may also be configured at a network end i.e.,
system [200] may be configured at 5G network.
[0059] The present disclosure provides the system [200] for configuring and
15 managing proxy registrations in a network. The network may refer to the 5G
communication network as a whole, and may also refer to the communication
network from other RAT. the configuring and managing proxy registrations may be
registration of custom service for service communication proxy (SCP). Further, the
system [200] may also be configured to perform the function of a SCP controller
20 [302] such as performing operations administration and management (OAM) for
one or more proxy services such as health check, service discovery, NF instance discovery, etc.
[0060] The transceiver unit [202] of the system [200] is configured to receive
25 one of more proxy registration requests for registration of the one or more proxy
services to a service communication proxy (SCP) controller, wherein the one or
more proxy registration requests are transmitted in one of a startup event and during
an update event. The transceiver unit [202] may refer to a device capable of
transmission and reception of data and/or signals. The one or more proxy
30 registration requests may refer to a request to register the one or more proxy services
17

at least at one of system and a network repository function (NRF) [120]. The one
or more proxy services may refer to intercepting incoming/ outgoing messages and
decrypting/encrypting the incoming/outgoing messages and are used for providing
the routing services for the incoming and outgoing messages. The one or more
5 proxy services are to be registered with the SCP controller [302] and the NRF [120].
The SCP controller [302] is a device capable of managing and controlling the one or more proxy services and managing communication. The startup event may be an event where the one or more proxy registration requests are initiated at a startup of the associated one or more proxy services. The update event may be an event where
10 the one or more proxy services were already registered, but the one or more proxy
registration requests are re-initiated due to an update in the one or more proxy services. In an implementation of the present disclosure, the one or more proxy registration requests is received by the SCP control over an interface, which is a communication channel between the SCP controller [302] and the one or more
15 proxy services. The communication channel may use hypertext transfer protocol
(such as http/1.1) for communication between the one or more proxy services and the SCP controller [302], and may also be on a different virtual local area network.
[0061] The identification unit [204] is configured to define a service instance
20 identifier with each of the one or more proxy services during the registration. The
identification unit [204] may be a processor capable of defining a service instance identifier based on processing of data. The service instance identifier may also refer to an identifier assigned to the particular service instance and/or to each of the one or more proxy services. 25
[0062] The updating unit [206] is configured to update one or more service
attributes at the SCP controller [302] based at least on the one or more proxy
registration requests of the one or more proxy services. The one or more service
attributes may be at least one of a supported network function (NF) type, a proxy
30 type, a supported Public Land Mobile Network (PLMN), a load, a network slice,
18

and a locality. The supported NF type may refer to the type of NF which is trying
to connect with the one or more proxy service. The proxy type may be an ingress
proxy type or an egress proxy type. The ingress proxy type may be an ingress proxy
which intercepts incoming messages and decrypts the incoming messages before
5 sending them to their final destination. The egress proxy type may be an egress
proxy which intercepts the outgoing messages and encrypts the outgoing message before sending them to their destination. If the proxy type of the proxy service is the ingress proxy type, then the transceiver unit [202] may also be configured to transmit an ingress profile information to the one or more egress proxies associated
10 with the one or more proxy services, wherein the ingress profile information
comprises information associated with the one or more service attributes. The PLMN is a mobile operator's cellular network in a specific country. The load may refer to the amount of traffic or data being carried by a network, device or system at a given time. The network slice may refer to the securely isolated and tailored
15 portion of the network infrastructure configured to meet the specific performance,
reliability and security requirements of diverse network functions, services or applications. The locality may refer to the geographical area served by a specific network, service provider or telecommunications infrastructure.
20 [0063] The transceiver unit [202] is configured to send an update registration
request to a network repository function (NRF) [120] comprising information of a set of network instances. The update registration request is a request for updating the one or more service attributes at the NRF [120]. The NRF [120] may comprise information of a set of network instances. The set of network instances may refer
25 to the different instances of Network Functions.
[0064] The present disclosure further discloses that the transceiver unit [202]
may be configured to receive a notification of NF profile update from the NRF
[120], and then forward a configuration information to the ingress proxy type
30 associated with a specific NF type upon receiving the notification of NF profile
19

update. The notification of the NF profile update may refer to a notification pop-up
or notification message showing that the one or more service attributes has been
updated. The configuration information may refer to the information associated
with the one or more service attributes or the information specifically associated
5 with a particular NF.
[0065] In order to register custom service for service communication proxy,
the identification unit [204] of the system [200] may also be configured to define
custom service ‘nscp-routing’ for the SCP. The transceiver unit [202] is configured
10 to send from the SCP controller [302], a single registration request to the NRF [120]
with help of custom service.
[0066] Also, SCP Proxy sets or updates the one or more service attributes
present at the one or more proxy services or the nfservice, to communicate the one
15 or more service attributes (such as the current load, the supported NF type, the
supported slice, the supported PLMN, etc) to the SCP controller [302] which further informs to the NRF [120].
[0067] Further, the one or more service attributes are sent to Ingress Proxy
20 which is associated with the particular NF by the SCP controller [302] on receiving
Notification from the NRF [120] for NF Profile update.
[0068] Furthermore, the transceiver unit [202] is configured to transmit to
broadcast/transmit update the SCP Ingress Proxy profile to all Egress Proxy type.
25
[0069] The present disclosure describes that on startup or during update, the
Proxy Registration to the SCP controller [302] contains one or more service attributes like NF types supported, type of Proxy (Egress/Ingress), supported PLMNs, load, slice & locality to the SCP controller [302] over an interface. At the
30 SCP controller [302], for each proxy registration, defining a service instance
20

identifier or serviceInstanceID associated with each of the one or more Proxy services.
[0070] Then, the SCP controller [302] updates the one or more service
5 attributes or nfservice attributes as per Proxy registration details and sends a request
to update Registration to the NRF [120] containing multiple nfserviceInstance
details. If the Proxy registration received is identified as ingress proxy, then the
SCP controller [302] forwards ingress details to each egress proxies registered with
it. On receipt of Notification of NF Profile update, the SCP controller [302]
10 forwards the details to ingress proxy type associated with that NF type.
[0071] A storage unit [not shown] may also be provided in the system [200] to
store the data required for the implementation of the features of the present disclosure.
15
[0072] It is pertinent to note that the system [200] is capable of implementing
the features that are obvious to a person skilled in the art in light of the disclosure as disclosed above and the implementation of the system [200] is not limited to the above disclosure.
20
[0073] Referring to FIG. 3, an exemplary visualisation of an interface is
provided. The interface illustrates that the SCP controller [302] is connected to the one or more proxy services via an internal communication path (the internal communication path is illustrated as the (i) in FIG. 3). The one or more service
25 attributes are provided to a register within the SCP controller [302] or a register
within the NRF [120] for providing information associated with different kind of one or more service attributes. The user traffic [314] exists between the different one or more service communication proxy (SCP) (also used as one or more proxy services in the present disclosure) such as proxy A01, proxy A02, proxy A03, and
30 proxy A04. The proxy A01, proxy A02, proxy A03, and proxy A04 [310] are
21

connected to the network functions such as NF A POD01, NF A POD02, etc. which
are associated with respective PLMN’s. Each of the proxy A01, proxy A02, proxy
A03, and proxy A04 comprises the egress proxy type (illustrated as eP in FIG. 3)
and the ingress proxy type (illustrated as iP in FIG. 3). The egress proxy type of one
5 SCP transfers the user traffic [314] with ingress proxy type of other SCP and also
communicates with different PLMNs [312]. For performing the discovery function,
the SCP controller [302] is connected with the network repository function (NRF)
[120] and each of the network functions in the respective PLMNs via a discovery
path [304] (illustrated as D in FIG. 3). For registering the SCP proxies, the SCP
10 controller [302] is connected with the NRF [120] and each of the network functions
in the respective PLMNs via an NF registration path [306] (illustrated as R in FIG. 3).
[0074] Referring to FIG. 4, an exemplary method flow diagram [400], for
15 configuring and managing proxy registration in a network, in accordance with
exemplary implementations of the present disclosure is shown. The method [400]
may also be implemented for registering custom service for service communication
proxy. In an implementation the method [400] is performed by the system [200].
The network may refer to the 5G communication network as a whole, and may also
20 refer to the communication network from other RAT. Further, the configuring and
managing proxy registrations may also comprise registration of custom service for service communication proxy (SCP). As shown in FIG. 4, the method [400] starts at step [402].
25 [0075] At step [404], the method [400] as disclosed by the present disclosure
comprises receiving, by the transceiver unit [202], one of more proxy registration requests for registration of one or more proxy services to a service communication proxy (SCP) controller, wherein the one or more proxy registration requests are transmitted in one of a startup event and during an update event. The transceiver
30 unit [202] may refer to a device capable of transmission and reception of data and/or
22

signals. The one or more proxy registration requests may refer to a request to
register the one or more proxy services at least at one of a system and a network
repository function (NRF) [120]. The one or more proxy services may refer to
intercepting incoming/ outgoing messages and decrypting/encrypting the
5 incoming/outgoing messages and are used for providing the routing services for the
incoming and outgoing messages. The one or more proxy services are to be registered with the SCP controller [302] and the NRF [120]. The SCP controller [302] is a device capable of managing and controlling the one or more proxy services and managing communication. The startup event may be an event where
10 the one or more proxy registration requests are initiated at a startup of the associated
one or more proxy services. The update event may be an event where the one or more proxy services were already registered, but the one or more proxy registration requests are re-initiated due to an update in the one or more proxy services. In an implementation of the present disclosure, the one or more proxy registration
15 requests is received by the SCP control over an interface, which is a communication
channel between the SCP controller [302] and the one or more proxy services. The communication channel may use hypertext transfer protocol (such as http/1.1) for communication between the one or more proxy services and the SCP controller [302], and may also be on a different virtual local area network.
20
[0076] Next, at step [406], the method [400] as disclosed by the present
disclosure comprises defining, by the identification unit [204], a service instance identifier (serviceInstanceID associated with each Proxy) with each of the one or more proxy services during the registration. The identification unit [204] may be a
25 processor capable of defining a service instance identifier based on processing of
some data. The service instance identifier may also refer to an identifier assigned to the particular service instance and/or to each of the one or more proxy services.
[0077] Next, at step [408], the method [400] as disclosed by the present
30 disclosure comprises updating, by the updating unit [206], one or more service
23

attributes associated with one or more proxy services at the SCP controller [302],
based at least one the one or more proxy registration requests of the one or more
proxy services. In other words, the updating unit [206] updates the one or more
service attributes or the nfservice attributes. The updating is based on Proxy
5 registration details. The one or more service attributes may be at least one of a
supported network function type, a proxy type, a supported Public Land Mobile Network (PLMN), a load, a network slice, and a locality. The supported NF type may refer to the type of NF which is trying to connect with the one or more proxy service. The proxy type may be an ingress proxy type or an egress proxy type. The
10 ingress proxy type may be an ingress proxy which intercepts incoming messages
and decrypts the incoming messages before sending them to their final destination. The egress proxy type may be an egress proxy which intercepts the outgoing messages and encrypts the outgoing message before sending them to their destination. If the proxy type of the proxy service is the ingress proxy type, then the
15 transceiver unit [202] may also be configured to transmit an ingress profile
information to the one or more egress proxies associated with the one or more proxy services, wherein the ingress profile information comprises information associated with the one or more service attributes.
20 [0078] Next, at step [410], the method [400] as disclosed in the present
disclosure comprises sending by the transceiver unit [202] an update registration request to the network repository function (NRF) [120] comprising information of a set of network instances. The NRF [120] may also comprise multiple nfserviceInstance details, wherein if the Proxy registration received is Ingress, then
25 the SCP controller [302] forwards ingress details to each Egress proxies registered
with it. The update registration request is a request for updating the one or more service attributes at the NRF [120]. The NRF [120] may comprise information of a set of network instances. The set of network instances may refer to the different instances of Network Functions.
30
24

[0079] The method [400] as disclosed by the present disclosure further
comprises receiving, by the transceiver unit [202] a notification of NF Profile
update from the NRF [120], and then forwarding, by the transceiver unit [202], a
configuration information to the ingress proxy type associated with a specific NF.
5 The notification of NF profile update may refer to a notification pop-up or
notification message showing that the one or more service attributes has been updated. The configuration information may refer to the information associated with the one or more service attributes or the information specifically associated with a particular NF.
10
[0080] In order to register custom service for service communication proxy, in
further implementation of the present disclosure, the method [400] comprises defining, by the identification unit [204], custom service ‘nscp-routing’ for the SCP [110]. The method [400] may also comprise sending, by the transceiver unit [202],
15 from the SCP controller [302], a single registration request to the NRF [120] with
help of custom service.
[0081] Also, SCP Proxy sets or updates the one or more service attributes
present at the one or more proxy services or the nfservice, to communicate the one
20 or more service attributes (such as the current load, the supported NF type, the
supported slice, the supported PLMN, etc) to the SCP controller [302] which further informs to the NRF [120].
[0082] Further, the one or more service attributes are sent to Ingress Proxy
25 which is associated with the particular NF by the SCP controller [302] on receiving
Notification from the NRF [120] for NF Profile update.
[0083] Furthermore, the transceiver unit [202] is configured to transmit to
broadcast/transmit update the SCP Ingress Proxy profile to all Egress Proxy type. 30
25

[0084] The present disclosure describes that on startup or during update, the
Proxy Registration to the SCP controller [302] contains one or more service
attributes like NF types supported, type of Proxy (Egress/Ingress), supported
PLMNs, load, slice & locality to the SCP controller [302] over an interface. At the
5 SCP controller [302], for each proxy registration, defining a service instance
identifier or serviceInstanceID associated with each of the one or more Proxy services.
[0085] Then, the SCP controller [302] updates the one or more service
10 attributes or nfservice attributes as per Proxy registration details and sends a request
to update Registration to the NRF [120] containing multiple nfserviceInstance
details. If the Proxy registration received is identified as ingress proxy, then the
SCP controller [302] forwards ingress details to each egress proxies registered with
it. On receipt of Notification of NF Profile update, the SCP controller [302]
15 forwards the details to ingress proxy type associated with that NF type.
[0086] Thereafter, the method terminates at step [412].
[0087] FIG. 5 illustrates an exemplary block diagram of a computing device
20 [500] 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 [500] may also implement the method [400]
for configuring and managing proxy registrations in a network by utilising the
system [200]. In another implementation, the computing device [500] itself
25 implements the method [400] for configuring and managing proxy registrations in
a network using one or more units configured within the computing device [500], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
26

[0088] The computing device [500] may include a bus [502] or other
communication mechanism for communicating information, and a hardware
processor [504] coupled with bus [502] for processing information. The hardware
processor [504] may be, for example, a general-purpose microprocessor. The
5 computing device [500] may also include a main memory [506], such as a random-
access memory (RAM), or other dynamic storage device, coupled to the bus [502] for storing information and instructions to be executed by the processor [504]. The main memory [506] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the
10 processor [504]. Such instructions, when stored in non-transitory storage media
accessible to the processor [504], render the computing device [500] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [500] further includes a read only memory (ROM) [508] or other static storage device coupled to the bus [502] for storing static
15 information and instructions for the processor [504].
[0089] A storage device [510], such as a magnetic disk, optical disk, or solid-
state drive is provided and coupled to the bus [502] for storing information and instructions. The computing device [500] may be coupled via the bus [502] to a
20 display [512], 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 [514], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [502] for communicating information and command selections to the processor
25 [504]. Another type of user input device may be a cursor controller [516], such as
a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [504], and for controlling cursor movement on the display [512]. 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
30 the device to specify positions in a plane.
27

[0090] The computing device [500] 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 [500] causes
5 or programs the computing device [500] to be a special-purpose machine.
According to one implementation, the techniques herein are performed by the computing device [500] in response to the processor [504] executing one or more sequences of one or more instructions contained in the main memory [506]. Such instructions may be read into the main memory [506] from another storage medium,
10 such as the storage device [510]. Execution of the sequences of instructions
contained in the main memory [506] causes the processor [504] 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.
15
[0091] The computing device [500] also may include a communication
interface [518] coupled to the bus [502]. The communication interface [518] provides a two-way data communication coupling to a network link [520] that is connected to a local network [522]. For example, the communication interface
20 [518] may be an integrated services digital network (ISDN) card, cable modem,
satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [518] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be
25 implemented. In any such implementation, the communication interface [518]
sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
[0092] The computing device [500] can send messages and receive data,
30 including program code, through the network(s), the network link [520] and the
28

communication interface [518]. In the Internet example, a server [530] might
transmit a requested code for an application program through the Internet [528], the
ISP [526], the host [524], the local network [522] and the communication interface
[518]. The received code may be executed by the processor [504] as it is received,
5 and/or stored in the storage device [510], or other non-volatile storage for later
execution.
[0093] Further, the present disclosure discloses a non-transitory computer
readable storage medium storing instruction for configuring and managing proxy
10 registrations in a network. The instructions include executable code which, when
executed by one or more units of a system [200], causes: a transceiver unit [202] of the system [200] to receive one or more proxy registration requests for registration of one or more proxy services to a service communication proxy (SCP) controller over an interface, wherein the one or more proxy registration requests are
15 transmitted in one of a startup event and during an update event; an identification
unit [204] of the system [200] to define a service instance identifier with each of the one or more proxy services during the registration; an updating unit [206] of the system [200] to update one or more service attributes at the SCP controller [302] based at least on the one or more proxy registration requests of the one or more
20 proxy services; the transceiver unit [202] of the system [200] to send an update
registration request to a Network Resource Function (NRF) [120] comprising information of a set of network instances.
[0094] As is evident from the above, the present disclosure provides a
25 technically advanced solution by defining services to the SCP which did not happen
in the existing solutions. Also, the present disclosure has following advantages mentioned below:
1. The SCP controller [302] can send single NF registration or one or more proxy registration request for registration of one or more proxy services
29

with NF Profile containing one or more proxy services and multiple
nfservice instances each mapped to particular SCP Proxy.
2. Each SCP Proxy is associated with single or multiple NF type, single or
multiple slices, single or multiple PLMNs, and locality details. These
5 details can be incorporated in nfservice and can be used for discovery of
SCP egress by NF and of SCP ingress by SCP egress. This enables
dynamic allocation of SCP Egress & SCP Ingress Proxy for an NF in a
network which enables time efficient routing path determination and
also provides redundant path in case of SCP Proxy failure.
10 3. The SCP controller [302] sends single Heart beat containing load details
& NFstatus to NRF periodically. As health check is already performed by SCP controller [302] which has OAM capability, no extra signaling is needed for sending single Heart beat containing SCP Proxy details.
15 [0095] 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
20 be understood that the foregoing descriptive matter to be implemented is illustrative
and non-limiting.
[0096] Further, in accordance with the present disclosure, it is to be
acknowledged that the functionality described for the various components/units can
25 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
30 arrangements and substitutions of units, provided they achieve the intended
30

functionality described herein, are considered to be encompassed within the scope of the present disclosure.
31

We Claim:
1. A method for configuring and managing proxy registrations in a network,
comprising:
- receiving, by a transceiver unit [202], one or more proxy registration requests for registration of one or more proxy services to a service communication proxy (SCP) controller, wherein the one or more proxy registration requests are transmitted in one of a startup event and during an update event;
- defining, by an identification unit [204], a service instance identifier with each of the one or more proxy services during the registration;
- updating, by an updating unit [206], one or more service attributes associated with one or more proxy services, at the SCP controller [302], based at least on the one or more proxy registration requests of the one or more proxy services; and
- sending, by the transceiver unit [202], an update registration request to a Network Repository Function (NRF) [120] comprising information of a set of network instances.

2. The method as claimed in claim 1, wherein the one or more proxy registration requests comprises the one or more service attributes, wherein the one or more service attributes comprises at least one of a supported network function (NF) type, a proxy type, a supported Public Land Mobile Network (PLMN), a load, a network slice, and a locality.
3. The method as claimed in claim 2, wherein the proxy type is at least one of an ingress proxy type and an egress proxy type.
4. The method as claimed in claim 3, wherein upon determining that the proxy type of the one or more proxy service is the ingress proxy type, transmitting,

by the transceiver unit [202], an ingress profile information to one or more egress proxies associated with the one or more proxy services.
5. The method as claimed in claim 3 further comprising:
- receiving, by the transceiver unit [202], a notification of NF profile update from the NRF [120]; and
- forwarding, by the transceiver unit [202] upon receiving the notification of NF profile update, a configuration information to the ingress proxy type associated with a specific NF.
6. A system [200] for configuring and managing proxy registrations in a
network, comprising:
a transceiver unit [202], configured to receive one or more proxy registration requests for registration of one or more proxy services to a service communication proxy (SCP) controller, wherein the one or more proxy registration requests are transmitted in one of a startup event and during an update event;
an identification unit [204] connected at least to the transceiver unit [202], the identification unit [204] configured to define a service instance identifier with each of the one or more proxy services during the registration;
an updating unit [206] connected at least to the identification unit [204], the updating unit [206] configured to update one or more service attributes at the SCP controller [302] based at least on the one or more proxy registration requests of the one or more proxy services; and
the transceiver unit [202] further configured to send an update registration request to a Network Resource Function (NRF) [120] comprising information of a set of network instances.
7. The system [200] as claimed in claim 6, wherein the one or more proxy
registration request comprises a set of attributes, wherein the set of attributes

comprises at least one of a supported network function (NF) type, a proxy type, a supported Public Land Mobile Network (PLMN), a load, a slice, and a locality.
8. The system [200] as claimed in claim 7, wherein the proxy type is at least one of an ingress proxy type and an egress proxy type.
9. The system [200] as claimed in claim 8, wherein upon determining that the proxy type of the one or more proxy service is the ingress proxy type, the transceiver unit [202] is further configured to transmit an ingress profile information to one or more egress proxies associated with the one or more proxy services.
10. The system [200] as claimed in claim 8, wherein the transceiver unit [202] is configured to:
receive a notification of NF profile update from the NRF [120]; and forward a configuration information to the ingress proxy type
associated with a specific NF type upon receiving the notification of NF
profile update.