DESC:FORM 2
THE PATENTS ACT, 1970 (39 OF 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)

SYSTEM AND METHOD FOR MANAGING SUBSCRIBER DISTRIBUTION IN COMMUNICATION NETWORK

Jio Platforms Limited, an Indian company, having registered address at Office -101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India

The following complete specification particularly describes the disclosure and the manner in which it is performed.

TECHNICAL FIELD

[0001] The embodiments of the present disclosure generally relate to the field of communication networks and systems. More particularly, the present disclosure relates to a system and a method for managing subscriber distribution in a communication network.

BACKGROUND OF THE INVENTION

[0002] The subject matter disclosed in the background section should not be assumed or construed to be prior art merely due to its mention in the background section. Similarly, any problem statement mentioned in the background section or its association with the subject matter of the background section should not be assumed or construed to have been previously recognized in the prior art.

[0003] With recent developments in Fifth Generation (5G) telecommunication networks, multiple instances of Network Functions (NF) are required to be initiated in the network. Each NF instance serves a specific set of subscribers identified by a subscriber identity range. However, with lapse of time, new subscribers may enter the network and existing subscribers may move out of the network. This creates a hole in the subscriber identity range resulting in a load imbalance in the network. For example, a subscriber identity range 1-100 may be served by an NF instance 1 and a subscriber identity range 101-200 may be served by an NF instance 2. As time lapses, some of the existing subscribers present in the subscriber identity range 1-100 move out of the network, whereas all the existing subscribers present in the subscriber identity range 101-200 remain in the network. This leads to load imbalance in the network since signaling load in the NF instance 1 is lesser than that of the NF instance 2. A resolution to the load imbalance may be provided by balancing distribution of the subscribers across the multiple NF instances using a Subscriber Location Function (SLF) in a Unified Data Repository (UDR).

[0004] In the context of the 5G telecommunications networks, a network node that provides a service is referred to as a producer NF and a network node that consumes services is referred to as a consumer NF. Producer NFs register with a Network Function (NF) Repository Function (NRF). The NRF maintains an NF profile of available NF instances and the services supported by the NF instances. Consumer NFs can subscribe to receive information about producer NF instances that have registered with the NRF. A Service Communication Proxy (SCP) subscribes to the NRF and obtains reachability and service profile information regarding registered producer NF service instances.

[0005] Heretofore, in conventional methods, when the NF instance of the producer NF is not clear, the consumer NF sends a discovery request to the NRF/SCP along with specific subscriber information. The NRF/SCP uses a “Nudr_GroupIDmap” service to fetch a Group Identity (ID) associated with the subscriber. Typically, the “Nudr_GroupIDmap” is a 3GPP query service operation used by NF service consumers to retrieve the Group ID for a given NF type and a subscriber identifier. Based on the Group ID provided for the subscriber, the NRF/SCP may select a producer NF instance profile. The NRF/SCP may retrieve the Group ID corresponding to a specific subscriber identifier from the UDR using a Nudr_GroupIDmap_Query service. This leads to additional signaling from the NRF/SCP towards the UDR and increase latency in signaling. Further, in a case where the UDR is distributed across the network, the NRF/SCP faces difficulty in locating the UDR to complete a Group ID mapping for all the subscribers.

[0006] Therefore, in view of the challenges associated with the conventional methods for discovering the NF instance, there lies a need for a solution for managing subscriber distribution in the network.

SUMMARY

[0007] The following embodiments present a simplified summary in order to provide a basic understanding of some aspects of the disclosed invention. This summary is not an extensive overview, and it is not intended to identify key/critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

[0008] According to an embodiment of the present disclosure, a method for managing subscriber distribution in a communication network is disclosed. The method includes receiving, by a data exchange engine of a network management server, an identity discovery request for a first end user device in the communication network from a second end user device in the communication network. The identity discovery request comprises at least one of, identification data for the first end user device, one or more query parameters, and a type of network function (NF) associated with the first end user device. The method further includes generating, by a trigger generation engine of the network management server, a first data-fetch trigger for a database based on the identity discovery request. The first data-fetch trigger enables the database to search for a group identifier (groupID) of the first end user device. Furthermore, the method includes determining, by a data processing engine of the network management server, whether the groupID of the first end user device is received from the database. Furthermore, the method includes retrieving by an identity determination engine of the network management server, the groupID of the first user device. The groupID of the first user device is retrieved from the database when the groupID of the first user device is present in the database. Else, the groupID of the first user device is retrieved from a user defined repository (UDR) in the communication network when the groupID of the first user device is absent in the database. Furthermore, the method includes generating, by the identity determination engine, an identifier of the first end user device from a plurality of identifiers associated with the one or more query parameters based on the groupID and the type of NF associated with the first end user device.

[0009] In some aspects of the present disclosure, the method further includes transmitting, by the data exchange engine, the identifier of the first end user device to the second end user device. The identifier of the first end user device enables establishment of a communication instance between the first end user device and the second end user device.

[0010] In some aspects of the present disclosure, prior to generating the first data-fetch trigger, the method includes identifying, by a pre-processing engine of the network management server, one or more data fields in the identity discovery request. Moreover, the method includes associating, by the pre-processing engine, one or more delegated headers with the one or more data fields.

[0011] In some aspects of the present disclosure, the method further includes identifying, by the pre-processing engine, an endpoint associated with the first end user device based on the identifier of the first end user device. Moreover, the method includes transmitting, by the pre-processing engine, the identity discovery request to the first end user device using the identified endpoint.

[0012] In some aspects of the present disclosure, the database is either a local database or a central database dedicatedly associated with the network management server.

[0013] In some aspects of the present disclosure, the one or more query parameters correspond to at least one of, a public land mobile network (PLMN) associated with the first end user device, a locality of the first end user device, and one or more communication services associated with first end user device.

[0014] In some aspects of the present disclosure, the network management server is a network repository function (NRF) server or a service communication proxy (SCP) server.

[0015] According to another embodiment, a system for managing subscriber distribution in a communication network is presented. The system includes a data exchange engine of a network management system, configured to receive an identity discovery request for a first end user device associated with a subscriber account in the communication network from a second end user device associated with a customer account in the communication network. The identity discovery request comprises at least one of, an identifier associated with the first end user device, one or more query parameters, and a type of network function (NF) associated with the first end user device. The system further includes a trigger generation engine of the network management system, configured to generate a first data-fetch trigger for a database in the communication network based on the identity discovery request. The first data-fetch trigger enables the database to search for a group identifier (groupID) of the first end user device. Furthermore, the system includes a data processing engine of the network management system, configured to determine whether the groupID of the first end user device is received from the database. Furthermore, the system includes an identity determination engine of the network management system configured to retrieve the groupID of the first user device from the database when the groupID of the first user device is present in the database. Else, the identity determination engine retrieves the groupID from a user defined repository (UDR) in the communication network when the groupID of the first user device is absent in the database. Moreover, the identity determination engine is configured to determine an identifier of the first end user device from a plurality of identifiers associated with the one or more query parameters based on the groupID and the type of NF associated with the first end user device.

BRIEF DESCRIPTION OF DRAWINGS

[0016] Various embodiments disclosed herein will become better understood from the following detailed description when read with the accompanying drawings. The accompanying drawings constitute a part of the present disclosure and illustrate certain non-limiting embodiments of inventive concepts. Further, components and elements shown in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. For the purpose of consistency and ease of understanding, similar components and elements are annotated by reference numerals in the exemplary drawings.

FIG. 1 illustrates an operational environment of a communication network, in accordance with an exemplary aspect of the present disclosure.

FIG. 2 illustrates a block diagram depicting exemplary components of a system for managing subscriber distribution in a communication network, in accordance with an exemplary embodiment of the present disclosure.

FIG. 3 illustrates a block diagram depicting exemplary components of a system for discovering network function instances in the communication network, in accordance with an embodiment of the present disclosure.

FIG. 4 illustrates a block diagram of a network management server, in accordance with an exemplary embodiment of the present disclosure.

FIG. 5 illustrates an architecture depicting core network entities, in accordance with an embodiment of the present disclosure.

FIG. 6 illustrates a timing diagram depicting a process for determining a network function instance in the communication network, in accordance with an embodiment of the present disclosure.

FIG. 7 illustrates a timing diagram depicting another process for determining the network function instance in the communication network, in accordance with an embodiment of the present disclosure.

FIG. 8 illustrates a flow chart depicting a method for managing the subscriber distribution in the communication network, in accordance with an embodiment of the present disclosure.

LIST OF REFERENCE NUMERALS

102 – Central Connection Points
104 – End User Devices
105 – Coverage Regions
106 – Network
208 – Network Management Server (NMS)
210 – Core Network Entities
212 – Data Processing Circuitry
214 – Server Memory
216 – Communication Interface
302 – Provisioning Gateway
304 – Central Database
306 – Local Databases
310 – User Defined Repository
402 – Console Host
403 – First Communication Bus
404 – Data Exchange Engine
406 – Trigger Generation Engine
408 – Data Processing Engine
410 – Identity Determination Engine
412 – Pre-Processing Engine
414 – Second Communication Bus
416 – Instructions Repository
418 – Request Data Repository
420 – GroupID Data Repository
422 – Identifier Repository
424 – Network Entity Data Repository
426 – User Device Data Repository
506 – User Plane Function (UPF)
508 – Data Network (DN)
510 – Authentication Server Function (AUSF)
512 – Access and Mobility management Function (AMF)
514 – Session Management Function (SMF)
516 – Service Communication Proxy (SCP)
518 – Network Slice Selection Function (NSSF)
520 – Network Exposure Function (NEF)
522 – Network Repository Function (NRF)
524 – Policy Control Function (PCF)
526 – Unified Data Management (UDM)
528 – Application Function (AF)
602 – Network Function (NF)
604 - Database

DETAILED DESCRIPTION OF THE INVENTION

[0017] Inventive concepts of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of one or more embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Further, the one or more embodiments disclosed herein are provided to describe the inventive concept thoroughly and completely, and to fully convey the scope of each of the present inventive concepts to those skilled in the art. Furthermore, it should be noted that the embodiments disclosed herein are not mutually exclusive concepts. Accordingly, one or more components from one embodiment may be tacitly assumed to be present or used in any other embodiment.

[0018] The following description presents various embodiments of the present disclosure. The embodiments disclosed herein are presented as teaching examples and are not to be construed as limiting the scope of the present disclosure. The present disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified, omitted, or expanded upon without departing from the scope of the present disclosure.

[0019] The following description contains specific information pertaining to embodiments in the present disclosure. The detailed description uses the phrases “in some embodiments” which may each refer to one or more or all of the same or different embodiments. The term “some” as used herein is defined as “one, or more than one, or all.” Accordingly, the terms “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” In view of the same, the terms, for example, “in an embodiment” refers to one embodiment and the term, for example, “in one or more embodiments” refers to “at least one embodiment, or more than one embodiment, or all embodiments.”

[0020] The term “comprising,” when utilized, means “including, but not necessarily limited to;” it specifically indicates open-ended inclusion in the so-described one or more listed features, elements in a combination, unless otherwise stated with limiting language. Furthermore, to the extent that the terms “includes,” “has,” “have,” “contains,” and other similar words are used in either the detailed description, such terms are intended to be inclusive in a manner similar to the term “comprising.”

[0021] In the following description, for the purposes of explanation, various specific details are set forth to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features.

[0022] The description provided herein discloses exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the foregoing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing any of the exemplary embodiments. Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it may be understood by one of the ordinary skilled in the art that the embodiments disclosed herein may be practiced without these specific details.

[0023] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein the description, the singular forms "a", "an", and "the" include plural forms unless the context of the invention indicates otherwise.

[0024] The terminology and structure employed herein are for describing, teaching, and illuminating some embodiments and their specific features and elements and do not limit, restrict, or reduce the scope of the present disclosure. Accordingly, unless otherwise defined, all terms, and especially any technical and/or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skill in the art.

[0025] In the present disclosure, various embodiments are described using terms such as extensible radio access network (xRAN), and open-radio access network (O-RAN)) that are commonly used in communication standards (e.g., 3rd generation partnership project (3GPP), but these are merely examples for description. Various embodiments of the disclosure may also be easily modified and applied to other communication systems.

[0026] The present invention relates to a system and a method for discovering a Network Function (NF) instance in a wireless communication network. The present invention provides mechanisms for discovering the NF instance using a Service Communication Proxy (SCP) and/or Network Repository Function (NRF) in a centralized or a distributed database. The NF may transmit a discovery request to the SCP and/or the NRF for a subscriber identity. The SCP and/or the NRF may determine whether the request needs to be served locally. A provisional gateway may create a Group Identity (ID) mapping database in the centralized database (also referred to as a central database) or the distributed database (also referred to as a local database) at the SCP and/or the NRF. When a distributed database architecture is used, the centralized database may synchronize a copy of Group ID mapping database or a Subscriber Location Function (SLF) data towards the distributed database. The SCP and/or the NRF select an associated producer NF based on a Group ID mapping for an individual subscriber identity and associated NF Type. The SCP and/or the NRF use stored NF Profiles in conjunction with the Group ID mapping retrieved from the local database to make an associated discovery of the NF instance or routing decisions.

[0027] The following description provides specific details of certain aspects of the disclosure illustrated in the drawings to provide a thorough understanding of those aspects. It should be recognized, however, that the present disclosure can be reflected in additional aspects and the disclosure may be practiced without some of the details in the following description.

[0028] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings. FIG. 1 through FIG. 8, discussed below, and the embodiments used to describe the principles of the present disclosure are by way of illustration only and should not be construed in any way to limit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0029] Various aspects including the example aspects are now described more fully with reference to the accompanying drawings, in which the various aspects of the disclosure are shown. The disclosure may, however, be embodied in different forms and should not be construed as limited to the aspects set forth herein. Rather, these aspects are provided so that this disclosure is thorough and complete, and fully conveys the scope of the disclosure to those skilled in the art. In the drawings, the sizes of components may be exaggerated for clarity.

[0030] Various aspects of the present disclosure provide a system and a method for determining network function instances in the communication network. Specifically, the present disclosure relates to discovering the NF instance locally within a centralized or distributed database of the NRF/SCP to reduce additional signaling and latency in signaling. In some aspects of the present disclosure, the system and the method relate to efficiently discovering the NF instance using a Service Communication Proxy (SCP) and/or Network Repository Function (NRF) in a centralized or distributed database to reduce additional signaling and latency in signaling.

[0031] FIG. 1 illustrates an operational environment of a communication network 100, in accordance with an exemplary aspect of the present disclosure. The communication network 100 may include central connection point(s) 102 communicatively coupled to end user device(s) 104 in coverage region(s) 105.

[0032] In some aspects of the present disclosure, the central connection point(s) 102 may be configured as base station(s) to provide wired/wireless communication services to the user device(s) 104. The central connection point(s) 102 may further enable the user device(s) 104 to communicate with the network 106. Typically, the central connection point(s) 102 may include a network infrastructure that provides wireless access to one or more terminals. The central connection point(s) 102 have coverage defined predetermined geographic area(s) based on distance(s) over which a communication signal can be transmitted. Examples of the central connection point(s) 102 may include, but are not limited to base stations, access point (AP), “evolved NodeB (eNodeB) (eNB)”, “5th Generation (5G) nodes, next generation NodeB (gNB), wireless points, transmission/reception points (TRP), Radio Access Networks (RAN), and the like. Aspects of the present disclosure are intended to include or otherwise cover any type of central connection point(s) 102 without deviating from the scope of the present disclosure.

[0033] The central connection point(s) 102 may further be capable of communicatively coupling multiple user devices 104 together. Examples of the user devices 104 may include but are not limited to mobile stations, subscriber stations, remote terminals, wireless terminals, receive points, end user devices and the like. The wireless communication system 100 may be divided into coverage regions 105 (presented through 105-1 to 105-N). Each coverage region may comprise central connection point(s) 102 and user device(s) 104.

[0034] Each user device 104 may be served by central connection point(s) 102 in coverage region(s) 105. The wireless communication system 100 may be a part of a wireless communication network where the central connection point(s) 102 and the user device(s) 104 communicate with the network 106.

[0035] In an exemplary embodiment, the network 106 may be configured as an application server and may be communicably operational or may be integrated with the user devices 104 via a network of wired and/or wireless communication devices coupled with a server. In another exemplary embodiment, the user devices 104 may be a wireless device. The wireless device may be a mobile device that may include, for example, cellular telephone, such as a feature phone or smartphone and other devices. The user devices 104 may not be limited to the above-mentioned devices but may include any type of device capable of providing wireless communication, such as a cellular phone, a tablet computer, a Personal Digital Assistant (PDA), a Personal Computer (PC), a laptop computer, a media center, a workstation, and other such devices.

[0036] The network 106 may pertain to 5G service-based architecture and may be configured to interconnect distinct networks associated with the architecture. Therefore, the network 106 may provide a path for the exchange of information between one or more of the networks, and corresponding subnetworks. Further, as the backbone, the core network may tie together diverse networks, say Local Area Network (LAN), Wide Area Network (WAN), Metropolitan Area Network (MAN), etc. which may be there within the same building, in different buildings, in a campus environment, or remotely located over wide areas. The system may also boost the network performance by continuously coordinating with other network functions.

[0037] In an example embodiment, the network 106 may pertain to at least one of a wireless network, a wired network, or a combination thereof. The network may be implemented as one of the different types of networks, such as Intranet, LAN, WAN, Internet, and the like. Further, the network may either be a dedicated network or a shared network. The shared network may represent an association of the different types of networks that may use variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), Automatic Repeat Request (ARQ), and the like. In an embodiment, the network may pertain to, for example a 5G network that may be facilitated through, for example, Global System for Mobile communication (GSM) network; a Universal Terrestrial Radio Access Network (UTRAN), an Enhanced Data rates for GSM Evolution (EDGE) Radio Access Network (GERAN), an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a Wi-Fi or other LAN access network, or a satellite or terrestrial wide-area access network such as a Worldwide Interoperability for Microwave Access (WiMAX) network. Various other types of communication network or service may be possible.

[0038] In an example, the network 106 may utilize different sort of air interface, such as a Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), or Frequency Division Multiple Access (FDMA), air interface and other implementation. In an example embodiment, the wire-line user device may use wired access networks, exclusively or in combination with wireless access networks, for example, including Plain Old Telephone Service (POTS), Public Switched Telephone Network (PSTN), Asynchronous Transfer Mode (ATM), and other network technologies configured to transport Internet Protocol (IP) packets.

[0039] FIG. 2 illustrates a block diagram depicting exemplary components of a system 200 for managing subscriber distribution in the communication network 100, in accordance with an exemplary embodiment of the present disclosure. The embodiments of the system 200 shown in FIG. 2 are for illustration only. Other embodiments of the system 200 may be used without departing from the scope of this disclosure.

[0040] The system 200 may include the end user devices 104 (hereinafter interchangeably referred to and designated as ‘user devices 104’) connected to the network 106 via a radio access network (RAN) 102 (i.e., a network of central connection points 102). The network 106 may further include core network entities 210 comprising hardware circuitry, logic, instructions, and/or codes to perform a number of network function operations of the network 106. Particularly, the core network entities 210 may comprise hardware component(s), code(s), protocol(s), and/or logical unit(s) that provide a network architecture for a flexible, scalable, and efficient framework to support the diverse requirements and use cases of 3GPP networks. Examples of the core network entities may include, but are not limited to, a User Plane Function (UPF), a Data Network (DN), an Authentication Server Function (AUSF), an Access and Mobility management Function (AMF), a Session Management Function (SMF), the Service Communication Proxy (SCP), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), the Network Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), and an Application Function (AF), as presented later in FIG. 5. The system 200 further includes a network management server (NMS) 208 coupled to the network 106. The NMS 208 may be configured to perform data processing and/or data storage operations for determining network function instances in the communication network 106.

[0041] Examples of the user devices 104 may include, but not limited to portable handheld electronic devices such as a mobile phone, a tablet, a laptop, a smart watch etc., or fixed electronic devices such as a desktop computer, computing device, etc. In some aspects of the present disclosure, each of the user devices 104 may be a service consumer and/or a service provider.

[0042] Preferably, a user device 104 may be configured to transmit request(s) to access details associated with another user device 104. The user device 104 may further be configured to receive the desired details of the other device 104 based on the request(s), based on which the user device 104 may establish communication instance(s) with the other user device 104. The term “communication instance(s)” as used herein may be referred to as data object(s) and/or instruction object(s) for initiation of communication between the core network entities 210 (presented later in FIG. 2) and other components in the communication network or within the core network entities 210. The other user device 104 may further be configured to receive the request(s) from the user device 104. The user devices 104 may further include an application console (not shown) that enables the user devices 104 to communicate with the NMS 208 via the network 106. Preferably, the application console may be hosted by the NMS 208.

[0043] The NMS 208 may be a network of computers, a software framework, or a combination thereof, that may provide a generalized approach to create a server implementation. Examples of the NMS 208 may include, but are not limited to, personal computers, laptops, mini-computers, mainframe computers, any non-transient and tangible machine that can execute a machine-readable code, cloud-based servers, distributed server networks, or a network of computer systems. The NMS 208 may be realized through various web-based technologies such as, but not limited to, a Java web-framework, a .NET framework, a personal home page (PHP) framework, or any web-application framework.

[0044] In some aspects of the present disclosure, the NMS 208 may be capable of performing registration management, connection management, reachability management, mobility management, lawful intercepts, SMS transport and session management messages transport between the user device 104 and other network functions, access authentication and authorization, location services management, functionality to support 3GPP access networks and/or non-3GPP access networks, and/or other types of management processes. In some aspects of the present disclosure, the NMS 208 may be configured to receive data and/or instructions (in the form of access requests) from the user device 104 via core network entities 210 to determine identification details of the other user device 104 to establish communication instances between them.

[0045] The NMS 208 may include data processing circuitry 212, server memory 214, and a network interface 216. The data processing circuitry 212 may include processor(s) (such as data processing engines) suitable logic, instructions, circuitry, interfaces, and/or codes for executing one or more operations of various operations performed by the NMS 208 for determination of network instances in the network 106. Examples of the NMS 108 may include, but are not limited to, an ASIC processor, a RISC processor, a CISC processor, a FPGA, and the like.

[0046] The server memory 214 may be configured to store the logic, instructions, circuitry, interfaces, and/or codes of the NMS 208 for executing various operations. The server memory 214 may further be configured to store data associated with the network function instances in the network 106. Aspects of the present disclosure are intended to include and/or otherwise cover any type of the data associated with the network function instances, without deviating from the scope of the present disclosure. Examples of the server memory 214 may include but are not limited to, a ROM, a RAM, a flash memory, a removable storage drive, a HDD, a solid-state memory, a magnetic storage drive, a PROM, an EPROM, and/or an EEPROM.

[0047] Although FIG. 2 illustrates one example of the system 200, various changes may be made to FIG. 2. Further, the system 200 may include any number of components in addition to the components shown in FIG. 2. Further, various components in FIG. 2 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0048] FIG. 3 illustrates a block diagram illustrating exemplary components of a system 300 for discovering the network function instances in the communication network 100, in accordance with an embodiment of the present disclosure. The embodiment presents a representation of operational components deployed in one of the coverage regions 105 for determining network function instances between user devices 104 associated with the coverage region 105. The system 300 may include multiple NMS 208 (as presented in FIG. 3 by way of first through nth NMS 208-1 to 208-N) coupled to the end user devices 104 via the core network entities 210. Each NMS 208 may be coupled with a dedicated local database 306 (presented by first through nth local databases 306-1 to 306-N). Each local database 306 may further be coupled to a central database 304. Moreover, the central database is connected to a provisioning gateway 302. Furthermore, the central database 304 may also be connected to a user-defined repository (UDR) 310 configured to store data of the network 106 in a distributed manner.

[0049] The UDR 310 may correspond to a centralized data repository for subscription data, subscriber policy data, sessions, contexts, and application states. The UDR 310 may provide standard-based Application Programming Interface (API) integrations with other network functions to retrieve subscriber subscription and policy data.

[0050] The provisioning gateway 302 may transfer Group Identity (ID) mapping information corresponding to each subscriber (i.e., end-user device 104) to the central database 304 and may manage Group ID mapping for each subscriber based on the Group ID mapping information stored in the central database 404. The provisioning gateway 302 may further be configured to create, edit, read, or delete mapping records in the central database 304. For example, the Group Identity of each subscriber may be mapped with an information (such as a device identifier, an account identifier, etc.) of a subscriber and may be stored in a look-up table in the database 304. The provisioning gateway 302 may retrieve the information from the look-up table based on the mapping of the information of the subscriber with the Group Identity of the subscriber.

[0051] The central database 304 may be configured to receive a provisioning request from the provisioning gateway 302. The central database 304 may store a central copy of the Group ID mapping or Subscriber Location Function (SLF) data. The SLF data comprises information about the home subscriber server (HSS) associated with a particular profile/account associated with a user device. The central database 304 may further be configured to replicate the SLF data to the NMS 208 through the local database 306 depending upon architecture requirements. The central database 304 may also act as the local database 306 when required. Preferably, the NMS 208 may be one of, a Service Communication Proxy (SCP) (as shown later in FIG. 5 as SCP 516) or a Network Repository Function (NRF) (as shown later in FIG. 5 as NRF 522). The SCP is a crucial component in the 5G network architecture that functions as an intermediary to enhance communication between different Network Functions (NFs). The Network Repository Function (NRF) is a central repository for Network Functions (NFs) on the network that provides NF service registration and discovery, enabling NFs to identify appropriate services in one another. The NMS 208 may also be configured to perform an audit on the central database 304 and the local database 306 to update the Group ID mapping or the SLF data locally.

[0052] The local database 306 may be shared by each NMS 208. The local database 306 may receive provisioning data copy from the central database 304. The local database 306 may also receive the provisioning data copy after the audit. The local database 306 may be accessed by the NMS 208 for fetching the Group ID mapping or the SLF data according to the requirement of processing discovery request(s) for an end user device 104. The local database 306 may be a common/existing database used by the NMS 208.

[0053] The NMS 208 may be configured to receive the discovery request from the core network entities 210. The NMS 208 may consume/fetch the Group ID mapping or the SLF data from the central database 304 or the local database 306 to determine an associated Group IDs for the subscriber identity. The NMS 208 may use Group ID mapping or the SLF data in combination with the one or more query parameters and stored NF profiles to make an associated decision either to forward the request to a target producer NF or to respond to the discovery request with associated NF profiles.

[0054] In a non-limiting embodiment, the provisioning gateway 302 may correspond to a north-bound provisioning gateway. The provisioning gateway 302 may receive a subscriber Group ID mapping request to create, modify, or delete mapping records of an individual subscriber. The subscriber identity may be at least one of a Subscription Permanent Identifier (SUPI), an International Mobile Subscriber Identity (IMSI), a Generic Public Subscription Identifier (GPSI), a Mobile Station International Subscriber Directory Number (MSISDN), Internet Protocol (IPv4/IPv6), and Media Access Control (MAC). The SUPI is a unique identifier associated with a subscriber in a 5G network. It serves as a long-term identifier for a user and is provisioned in the Subscriber Profile Repository (SPR) during the subscription process. The IMSI uniquely identifies every mobile subscriber within the network. Specifically, the IMSI is used for mobile services and/or Internet of Things (IoT) applications ensure secure and reliable communication between user devices and networks. The GPSI is typically used for addressing a 3GPP subscription in different data networks outside of the 3GPP compliant network. The MSISDN is a number uniquely identifying a subscription in a Global System for Mobile communications or a Universal Mobile Telecommunications System mobile network that maps a telephone number associated with a user device (i.e., mobile communication device) to the subscriber identity module in the user device. Internet protocol is a set of rules that allows devices to communicate with each other over the network (i.e., internet). The MAC is a layer that controls hardware component(s) responsible for interaction with the wired (electrical or optical) or wireless transmission medium in the communication network.

[0055] The Group ID mapping may be performed based on the NF type with ability to define Group IDs for the customer NF. The provisioning gateway 302 may convert the request to applicable APIs and may forward the request to the central database 304 for provisioning the Group ID mapping information or the SLF data in the central database 304.

[0056] In some aspects of the present disclosure, the local databases 306, the central database 304, the UDR 310 and the provisioning gateway 302 may be a part of the core network entities 210. The components of the system 300 may be deployed in a full redundant architecture as per customer’s requirement in both local redundancy and geo-redundancy.

[0057] FIG. 4 illustrates a block diagram of the network management server 208, in accordance with an exemplary embodiment of the present disclosure. The NMS 208 includes the data processing circuitry 212, the server memory 214, the communication interface 216, and a console host 402 connected via a first communication bus 403.

[0058] The console host 402 may include suitable logic, circuitry, interfaces, and/or codes that may be configured to enable the communication interface 216 to receive input(s) and/or present output(s). In some aspects of the present disclosure, the console host 402 may include suitable logic, instructions, and/or codes for executing various operations of computer executable applications to host the application on the user devices 104, by way of which the user can trigger the NMS 208 for determining the network function instances in the network 106. In some other aspects of the present disclosure, the console host 402 may provide a Graphical User Interface (GUI) for the NMS 208 for user interaction.

[0059] The data processing circuitry 212 may include data processor(s) (e.g., data processing engines) as presented in FIG. 4. According to an exemplary embodiment, the data processing circuitry 212 may include a data exchange engine 404, a trigger generation engine 406, a data processing engine 408, an identity determination engine 410, and a pre-processing engine 412 coupled to each other by way of a second communication bus 414.

[0060] The data exchange engine 404 may be configured to enable exchange of data and/or instruction(s) between the server memory 214, the core network entities 210, the user devices 104, and various other engines of the data processing circuitry 212. The data exchange engine 404 may be configured to enable the NMS 208 to receive user-defined data and/or instructions from the user devices 104 via the network 106.

[0061] Particularly, the data exchange engine 404 may also be configured to receive the identity discovery request for the first end user device 104-1 in the communication network from the second end user device 104-2 in the communication network 106. The identity discovery request comprises an identity data of the first end user device104-1, query parameters for the first end user device 104-1, and a type of network function (NF) associated with the first end user device 104-1. In some aspects of the present disclosure, the identity data may be associated with label(s) and/or tag(s) of identification of the first end user device (104-1) that may correspond to identity information of the first end user device (104-1) that may be useful to fetch a groupID map from the local database 304 or the central database 304. In some aspects of the present disclosure, the query parameters correspond to a public land mobile network (PLMN) associated with the first end user device, a locality of the first end user device, and one or more communication services associated with first end user device 104-1.

[0062] The trigger generation engine 406 may be configured to generate a first data-fetch trigger for a database 604 (cumulatively referring the local database 306 and the central database 304, presented as database 604 later in FIG. 6 and FIG. 7) based on the identity discovery request. The first data-fetch trigger enables the database to search for a group identifier (groupID) of the first end user device 104-1. Preferably, the groupID is an identifier assigned to a group of subscriber accounts in the communication network 100. The allocation of the groupID may be in accordance with a date of association with the communication network 100, type(s) of service(s) availed by the subscribers, and/or a geographical location (i.e., a service region) of the subscribers. Based on group ID provided for subscriber and Producer NF Profile indicating the group IDs served by them, resulting Producer NF instance profile will be selected by NMS 208.

[0063] The data processing engine 408 may be configured to determine whether the groupID of the first end user device 104-1 is received from the database 604.

[0064] In a first case, when the data processing engine 408 determines that the groupID is received from the database 604, the identity determination engine 410 may be configured to determine an identifier of the first end user device 104-1 from multiple identifiers associated with the query parameter(s), based on the groupID and the type of NF associated with the first end user device 104-1. In some aspects of the present disclosure, the identity determination engine 410 may retrieve the identifiers associated with the query parameter(s) from the database 604 and segregate the identifiers based on the type of NF associated with the first end user device 104-1. Moreover, the identity determination engine 410 may identify the identifier of the first end user device 104-1 matching with the groupID. The identifier of the first end user device 104-1 may be transmitted to the second end user device 104-2 to enable establishment of a communication instance between the first end user device 104-1 and the second end user device 104-2.

[0065] In a second case, when the data processing engine 408 determines that the groupID is not received from the database 604, the trigger generation engine 406 may be configured to generate a second data-fetch trigger for the UDR 310. The second data-fetch trigger enables the UDR 310 to search for the groupID of the first end user device 104-1. In response to the second data-fetch trigger, the identity determination engine 410 receives the groupID of the first end user device 104-1 from the UDR 310. Moreover, upon reception of the groupID from the UDR 310, the identity determination engine 410 may determine the identifier of the first end user device 104-1 as presented above for the first case and share the identifier of the first end user device 104-1 with the second end user device 104-2 to enable the establishment of the communication instance between the first end user device 104-1 and the second end user device 104-2.

[0066] According to an embodiment, the network management server 208 is a network repository function (NRF) server 522 (presented later in FIG 5). In such a scenario, the data exchange engine 404 may be configured to transmit the identifier of the first end user device 104-1 to the second end user device 104-2.

[0067] According to another embodiment, the network management server 208 is a service communication proxy (SCP) server 516 (presented later in FIG. 5). In such a scenario, prior to the generation of the first data-fetch trigger, the pre-processing engine 412 may be configured to identify data field(s) in the identity discovery request. Examples of the data field(s) may include, but are not limited to, issuer name, key material, supported scopes. Aspects of the present disclosure are intended to include or otherwise cover any type of data field that may include an identity of the endpoint(s). The pre-processing engine 412 may further be configured to associate delegated header(s) with the data field(s). The delegated header(s) may be in the form of label(s) or tag(s) rendering an information of the corresponding data field. Furthermore, the pre-processing engine 412 may be configured to identify an endpoint associated with the first end user device 104-1 based on the identifier of the first end user device 104-1. Moreover, the pre-processing engine 412 may be configured to transmit, the identity discovery request to the first end user device 104-1 using the identified endpoint. Preferably, the endpoint is a type of interactive node in the communication network 100 comprising interface(s) exposed by a communicating party or by a communication channel. Typically, the endpoint is an interface between a user of a communication facility and the medium through which information is sent and relayed to the destination. An example of the endpoint is a publish–subscribe topic or a group in group communication network capable of receiving and communicating data and/or information through the communication network.

[0068] Various engines of the data processing circuitry 212 are presented to illustrate the functionality driven by the NMS 208. It will be apparent to a person having ordinary skill in the art that various engines in the data processing circuitry 212 are for illustrative purposes and not limited to any specific combination of hardware circuitry and/or software.

[0069] In the presented embodiment, the server memory 214 may include instructions repository 416, request data repository 418, groupID data repository 420, identifier repository 422, network entity data repository 424, and user device repository 426. The instructions repository 416 may be configured to store instruction(s) for operations performed by the various engines of the data processing circuitry 212. The request data repository 418 may be configured to store the identity discovery requests from the end user devices 104. The groupID data repository 420 may be configured to temporarily store groupID(s) of the user device(s) 104 derived based on the identity discovery requests. The identifier repository 422 may be configured to store the identifiers of all user devices 104 in the communication network. The network entity data repository 424 may be configured to store data of the core network entities 210. The user device repository 226 may be configured to store data associated with the user devices 104 of the network 106.

[0070] According to an exemplary embodiment of the present disclosure, the instructions repository 416 may be configured to store computer program instructions corresponding to the operation(s) performed by various engines in the NMS 208. In an embodiment of the present disclosure, the instructions repository 416 may be configured as a non-transitory storage medium. Examples of the instructions repository 416 configured as the non-transitory storage medium includes hard drives, solid-state drives, flash drives, Compact Disk (CD), Digital Video Disk (DVD), and the like. Aspects of the present disclosure are intended to include or otherwise cover any type of non-transitory storage medium as the instructions repository 416, without deviating from the scope of the present disclosure. As will be appreciated, any such computer program instructions stored in the instructions repository 416 may be executed by one or more computer processors, including without limitation a general-purpose computer or special purpose computer, or other programmable processing apparatus to produce a machine, such that the computer program instructions which execute on the computer processor(s) or other programmable processing apparatus create means for implementing the function(s) specified.

[0071] It will be apparent to a person of ordinary skill in the art that the repositories in the server memory 214 are presented based on the functionality of NMS 208 and are not limited to those disclosed. The server memory 214 may have any configuration, combination and/or count of repositories without deviating from the scope of the present disclosure. Although FIG. 4 illustrates one example of the NMS 208, various changes may be made to FIG. 4. Further, the NMS 208 may include any number of components in addition to those shown in FIG. 4, without deviating from the scope of the present disclosure. Further, various components in FIG. 4 may be combined, further subdivided, or omitted and additional components may be added according to particular needs.

[0072] FIG. 5 illustrates an architecture 500 depicting the core network entities 210, in accordance with an embodiment of the present disclosure. The network architecture 500 may depict the connections and interfaces between the core network entities 210, an end user device (EUD) 104, and a RAN 102.

[0073] The EUD 104 and the RAN 102 may be connected with the network 106 comprising the core network entities 210. The core network entities 210 may include various network functions such as a User Plane Function (UPF) 506, a Data Network (DN) 508, an Authentication Server Function (AUSF) 510, an Access and Mobility management Function (AMF) 512, a Session Management Function (SMF) 514, the Service Communication Proxy (SCP) 516, a Network Slice Selection Function (NSSF) 518, a Network Exposure Function (NEF) 520, the Network Repository Function (NRF) 522, a Policy Control Function (PCF) 524, a Unified Data Management (UDM) 526, and an Application Function (AF) 528. The core network entities 210 may be configured to communicate with the EUD 104 and the RAN 102 using communication interfaces N1-N9. Further, the core network entities 210 may be further configured to communicate with each other.

[0074] The AMF 512 may be a network function capable of managing the mobility of the EUD 104. The SMF 514 may be a network function capable of managing a packet data network (PDN) connection provided to the EUD 104. The PCF 524 may provide a network function of applying a service policy, a charging policy, and a policy for the PDU session of a mobile communication service provider with the EUD 104. The AUSF 510 may perform authentication services for the EUD 104 seeking access to the network 106. The NSSF 518 may provide network slicing services for the EUD 104 seeking to access specific network capabilities and characteristics associated with a network slice.

[0075] The NEF 520 may access information for managing the EUD 104 in the network 106. The NEF 520 may perform subscribing the EUD 104 to a mobility management event, a session management event, requesting session-related information, configuring charging information, making a request for changing a PDU session policy, and transmitting data for the EUD 104. The UPF 506 may transmit packets that are transmitted and received by the EUD 104 to the network 106. The UPF 506 may also be connected to the DN 508 via Internet. The UDM 526 may be a network function for storing subscription data of the EUD 104.

[0076] The NRF 522 may provide a discovery response for specific producer Network Function (NF) types. For example, when a consumer NF (NF consuming services) sends a discovery request, the NRF 522 may access a list of producer NF (NF providing services) for the producer NF type requested. The producer NF may have multiple service endpoints. The service endpoint is a combination of Fully Qualified Domain Name (FQDN)/Internet protocol (IP) address and port number on a network node that hosts the producer NF. The FQDN is a domain name that specifies its exact location in the tree hierarchy of the Domain Name System (DNS). It specifies all domain levels, including the top-level domain and the root zone. The producer NF may register with the NRF 522. The NRF 522 may maintain the NF profile of available NF instances and supported services. The consumer NF may subscribe to receive information about producer NF instances registered with the NRF 522. The NF instances may include data object(s) and/or instruction object(s) in specific forms such as firewall, session border controller, etc., deployed on purpose-built physical appliances by network service providers. Examples of the NF instances may include but are not limited to a Virtual Network Function instance, an application instance, a network element instance, or the like. Aspects of the present disclosure are intended to include or otherwise cover any NF instances known or related to later developed technologies, without deviating from the scope of the present disclosure.

[0077] The SCP 516 may subscribe to the NRF 352 and obtain reachability and service profile information regarding registered producer NF instances. The consumer NF may connect to the SCP 516. The SCP 516 may provide load balances or alternate/optimal routing among the producer NF instances that provide the required service. The SCP 516 may directly route traffic to the producer NF.

[0078] FIG. 6 illustrates a timing diagram for a process 600 for determining the network function instance in the communication network 100, in accordance with an embodiment of the present disclosure. Specifically, the process 600 presents an embodiment where the NMS 208 is configured as the NRF 522.

[0079] At block 606, a Network Function (NF) 602 may send the discovery request to NRF 522. The NRF 522 may determine the NF instance from the database 604 based on the discovery request. It should be noted that the NF 602 as shown in FIG. 5 is similar to the core network entities 210 of FIG. 5. The database 604 as used herein cumulatively refers to the central database 304 and the local database 306 as shown in FIG. 3. Therefore, a detailed description of the same is omitted herein for the sake of brevity of the present disclosure.

[0080] At block 608, the NRF 522 may receive a discovery request for the subscriber identity from the NF 602. The discovery request may comprise the subscriber identifier, the NF type and the query parameters. The query parameters may be at least one of Public Land Mobile Network (PLMN), location, and service of the subscriber.

[0081] At block 610, the NRF 522 may authorize the discovery request for the subscriber identity based on a local decision. The NRF 522 may determine whether the request needs to be served locally.

[0082] At block 612, the NRF 522 may fetch a Group Identity (ID) based on the subscriber identifier and the NF type from the central database/ the local database 506. If the central database 304 and/or the local database 306 associated with the NRF 522 is not available, the NRF 522 may use any alternate databases or may fall back to query the UDR 310.

[0083] At block 614, the NRF 522 may decide a discovery response to the NF 602 based on the Group ID, the NF type and the one or more query parameters.

[0084] At block 616, the NRF 522 may transmit the discovery response to the NF 602. The discovery response may comprise matched NF profiles for the subscriber identity.

[0085] FIG. 7 illustrates a timing diagram for another process 700 for determining the network function instance in the communication network 100, in accordance with an embodiment of the present disclosure. Particularly, the process 600 presents an embodiment where the NMS 208 is configured as the SCP 516.

[0086] A consumer Network Function (NF) (i.e., associated with the second end-user device 104-2 may send the discovery request to SCP 516. The SCP 516 may determine the NF instance from the database 604 based on the discovery request and forward the request to a producer NF (i.e., associated with the first end-user device 104-1). It should be noted that the consumer NF and the producer NF as shown in FIG. 7 are similar to the core network entities 210 of FIG. Therefore, a detailed description of the same is omitted herein for the sake of brevity of the present disclosure.

[0087] At block 710, the SCP 516 may receive a delegated discovery request for a subscriber identity from the consumer NF. The discovery request may comprise a subscriber identifier, an NF type and one or more query parameters. The query parameters may be at least one of Public Land Mobile Network (PLMN), location, and service of the subscriber.

[0088] At block 712, the SCP 516 may authorize the delegated discovery request for the subscriber identity based on a local decision. The SCP 516 may determine whether the request needs to be served locally.

[0089] At block 714, the SCP 516 may fetch a Group Identity (ID) based on the subscriber identifier and the NF type from the database 604. If the central database 304 and/or the local database 306 associated with the SCP 516 is not available, the SCP 516 may use any alternate databases or fallback to query the Unified Data Repository (UDR).

[0090] At block 716, the SCP 516 may determine the producer NF (i.e., the first end user device 104-1) based on the Group ID, the NF type and query parameters.

[0091] At block 718, the SCP 516 may forward the delegated discovery request to the producer NF of the first end-user device 104-1.

[0092] FIG. 8 presents a flow chart that depicts a method 800 for managing the subscriber distribution in the communication network 100, in accordance with an embodiment of the present disclosure.

[0093] At block 802, the NMS 208 may receive the identity discovery request for the first end user device 104-1 from the network function(s) associated with the second end user device 104-2 in the communication network 106. The identity discovery request comprises the identity data of the first end user device 104-1, the query parameter(s) for the first end user device 104-1, and the type of network function (NF) associated with the first end user device 104-1.

[0094] At block 804, the NMS 208 may generate the first data-fetch trigger for the database 604 based on the identity discovery request. The first data-fetch trigger enables the database 604 to search for the group identifier (groupID) of the first end user device 104-1.

[0095] At block 806, the NMS 208 may determine whether the groupID of the first end user device 104-1 is received from the database 604. When the groupID of the first end user device 104-1 is not received from the database 604 (i.e., absent in the database 604), the method 800 proceeds to block 808. Else, when the groupID of the first end user device 104-1 is received from the database 604 (i.e., absent in the database 604), the method 800 proceeds to block 810.

[0096] At block 808, the NMS 208 may generate the second data-fetch trigger for the UDR 310 and receive the groupID of the first end user device 104-1 from the UDR 310. The second data-fetch trigger enables the UDR 310 to search for the groupID of the first end user device 104-1.

[0097] At block 810, the NMS 208 may determine the identifier of the first end user device 104-1 from multiple identifiers associated with the one or more query parameters based on the groupID and the type of NF associated with the first end user device 104-1. In some aspects of the present disclosure, the query parameter(s) correspond to the public land mobile network (PLMN) associated with the first end user device 104-1, the locality of the first end user device 104-1, and the communication service(s) associated with first end user device 104-1.

[0098] At block 812, the NMS 208 may determine its configuration. When the NMS 208 is configured as the NRF server 522, the method 800 proceeds to block 814. Else when the NMS 208 is configured as the SCP server 516, the method 800 proceeds to block 816.

[0099] At block 814, the NMS 208 may transmit the identifier of the first end user device 104-1 to the second end user device 104-2 via an associated network function.

[00100] At block 816, the NMS 208 may determine the endpoint associated with the first end user device 104-1 based on the identifier of the first end user device 104-1. The NMS 208 may further transmit the identity discovery request to the first end user device 104-1 using the identified endpoint. In some aspects of the present disclosure, prior to the generation of the first data-fetch trigger, the NMS 208 may also identify data fields in the identity discovery request and associate delegated headers with the data fields.

[00101] Referring to the technical abilities and advantageous effect of the present disclosure, operational advantages that may be provided by one or more embodiments may include enabling discovery of the producer NF by the SCP 516 and/or the NRF 522 using the central database 304 and/or the local database 306 without additional signaling and processing load to the UDR 310. This further simplifies the network implementation. A further potential advantage of the one or more embodiments disclosed herein may include decreasing the overall signaling latency and efficiently improving the scalability of the network 106. The discovery of the producer NF enables the system 200 to determine a status of engagement of the subscribers in the communication network 100, and therefore helps in efficient resource utilization of the communication network by managing the subscriber distribution in the communication network 100 based on a state of occupancy of resources at various NF instances. Specifically, the system 200 removes dependency of additional messages from the NMS 208 towards the UDR 310 which significantly decreases the signaling and processing load at the UDR 310. Moreover, the system 200 enables a possibility to change the architecture to support both distributed and/or centralized group ID mapping database depending upon the user requirements. Furthermore, the system 200 decreases an overall signaling latency in the communication network 100 and increases the ability to scale the communication network 100 more efficiently. Particularly, as primary purpose of the SLF is to assist in routing of signaling messages, moving this operation from the UDR 310 to the NMS 208 simplifies the network implementation.

[00102] Those skilled in the art will appreciate that the methodology described herein in the present disclosure may be carried out in other specific ways than those set forth herein in the above disclosed embodiments without departing from essential characteristics and features of the present invention. The above-described embodiments are therefore to be construed in all aspects as illustrative and not restrictive.

[00103] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Any combination of the above features and functionalities may be used in accordance with one or more embodiments.

[00104] In the present disclosure, each of the embodiments has been described with reference to numerous specific details which may vary from embodiment to embodiment. The foregoing description of the specific embodiments disclosed herein may reveal the general nature of the embodiments herein that others may, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and is not limited in scope.
,CLAIMS:1. A method (800) for managing subscriber distribution in a communication network (100), the method (800) comprising:
receiving, by a data exchange engine (404) of a network management server (208), an identity discovery request for a first end user device (104-1) in the communication network (100) from a second end user device (104-2) in the communication network (100), wherein the identity discovery request comprises at least one of, identification data for the first end user device (104-1), one or more query parameters, and a type of network function (NF) associated with the first end user device (104-1);
generating, by a trigger generation engine (406) of the network management server (208), a first data-fetch trigger for a database (604) in the communication network (100) based on the identity discovery request, wherein the first data-fetch trigger enables the database (604) to search for a group identifier (groupID) of the first end user device (104-1);
determining, by a data processing engine (408) of the network management server (208), whether the groupID of the first end user device (104-1) is present or absent in the database (604);
retrieving, by an identity determination engine (410) of the network management server (208), the groupID of the first user device (104-1) from
the database (608) when the groupID of the first user device (104-1) is present in the database (604), and
a user defined repository (UDR) (310) in the communication network (100) when the groupID of the first user device (104-1) is absent in the database (604); and
identifying, by the identity determination engine (410) of the network management server (208), an identifier of the first end user device (104-1) from a plurality of identifiers associated with the one or more query parameters, based on the groupID of the first user device (104-1) and the type of NF associated with the first end user device (104-1).

2. The method (800) as claimed in claim 1, further comprises transmitting, by the data exchange engine (404), the identifier of the first end device (104-1) to the second end user device (104-2), wherein the identifier of the first end device (104-1) enables establishment of a communication instance between the first end user device (104-1) and the second end user device (104-2).

3. The method (800) as claimed in claim 1, wherein, prior to generating the first data-fetch trigger, the method (800) further comprising:
identifying, by a pre-processing engine (412) of the network management server (208), one or more data fields in the identity discovery request; and
associating, by the pre-processing engine (412), one or more delegated headers with the one or more data fields.

4. The method (800) as claimed in claim 3, further comprising:
identifying, by the pre-processing engine (412), an endpoint associated with the first end user device (104-1) based on the identifier of the first end user device (104-1); and
transmitting, by the pre-processing engine (412), the identity discovery request to the first end user device (104-1) using the identified endpoint.

5. The method (800) as claimed in claim 1, wherein the database (604) is a local database (306) or a central database (304) dedicatedly associated with the network management server (208).

6. The method (800) as claimed in claim 1, wherein the one or more query parameters correspond to at least one of, a public land mobile network (PLMN) associated with the first end user device (104-1), a locality of the first end user device (104-1), and one or more communication services associated with first end user device (104-1).

7. The method (800) as claimed in claim 4, wherein the network management server (208) is a network repository function (NRF) server or a service communication proxy (SCP) server.

8. A system (200) for managing subscriber distribution in a communication network (100), the system (200) comprising:
a data exchange engine (404) of a network management system (208), configured to receive an identity discovery request for a first end user device (104-1) associated with a subscriber account in the communication network (100) from a second end user device (104-2) associated with a customer account in the communication network (100), wherein the identity discovery request comprises at least one of, identification data for the first end user device (104-1), one or more query parameters, and a type of network function (NF) associated with the first end user device (104-1);
a trigger generation engine (406) of the network management system (208), configured to generate a first data-fetch trigger for a database (604) in the communication network (100) based on the identity discovery request, wherein the first data-fetch trigger enables the database (604) to search for a group identifier (groupID) of the first end user device (104-1);
a data processing engine (408) of the network management system (208), configured to determine whether the groupID of the first end user device (104-1) is received from the database (604); and
an identity determination engine (410) of the network management system (208), configured to:
retrieve the groupID of the first user device (104-1) from
the database (608) when the groupID of the first user device (104-1) is present in the database (604), and
a user defined repository (UDR) (310) in the communication network (100) when the groupID of the first user device (104-1) is absent in the database (604); and
identify an identifier of the first end user device (104-1) from a plurality of a plurality of identifiers associated with the one or more query parameters, based on the groupID of the first user device (104-1) and the type of NF associated with the first end user device (104-1).

9. The system (200) as claimed in claim 8, wherein the data exchange engine (404) is further configured to transmit the identifier of the first end user device (104-1) to the second end user device (104-2), wherein the identifier of the first end user device (104-1) enables establishment of a communication instance between the first end user device (104-1) and the second end user device (104-2).

10. The system (200) as claimed in claim 8, wherein the network management system (208) further comprises a pre-processing engine (412), wherein, prior to the generation of the first data-fetch trigger, the pre-processing engine (412) is configured to:
identify one or more data fields in the identity discovery request; and
associate one or more delegated headers with the one or more data fields.

11. The system (200) as claimed in claim 10, wherein the pre-processing engine (412) is further configured to:
identify an endpoint associated with the first end user device (104-1) based on the identifier of the first end user device (104-1); and
transmit the identity discovery request to the first end user device (104-1) using the identified endpoint.

12. The system (200) as claimed in claim 8, wherein the database (604) is a local database (306) or a central database (304) dedicatedly associated with the network management server (208).

13. The system (200) as claimed in claim 8, wherein the one or more query parameters correspond to at least one of, a public land mobile network (PLMN) associated with the first end user device (104-1), a locality of the first end user device (104-1), and one or more communication services associated with first end user device (104-1).

14. The system (200) as claimed in claim 11, wherein the network management server (208) is a network repository function (NRF) server or a service communication proxy (SCP) server.