System and method for managing migration of network repository functions

Abstract

A method (500) for migrating at least one public mobile network (PLMN) in a network (106) is disclosed. The method (500) includes a processing engine (208) associating a new network repository function (NRF) (346) with a network function set (NF set) that is associated with an existing NRF (316) configured to serve one or more PLMNs. The processing engine (208) synchronizes operational data between the existing NRF (316) and the at least one new NRF (346) during a specified transition period. Based on the synchronization, generating, by the processing engine (208), a migration report indicating an operational status of the existing NRF (316) and the at least one new NRF (346). Based on the generated report, executing, by the processing engine (208), a migration cutoff command and upon execution, migrating, by the processing engine (208), the at least one PLMN to the at least one new NRF (346).

Description

NETWORK REPOSITORY FUNCTIONSRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD

[0002] The present disclosure generally relates to the field of telecommunication networks. More particularly, the present disclosure relates to a method and a system for migrating at least one public mobile network (PLMN) in a network.DEFINITION

[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[0004] The term ‘Network Function (NF)’ used hereinafter in the specification refers to a specific software or hardware component within a network and is designed to perform a particular function, such as routing, switching, firewalling, load balancing, traffic optimization, and the like, to enable network operations and enhance performance.

[0005] The term ‘NRF’ used hereinafter in the specification refers to a network repository function. The NRF acts as a central service directory for NFs and allows NFs to register, subscribe, and discover other NFs within the network.

[0006] The term ‘PLMN’ used hereinafter in the specification refers to a public land mobile network. The PLMN provides services such as voice, data, and messages to users and includes a collection of infrastructure, such as base stations and network elements, designed to provide mobile communication services within a defined geographic area.

[0007] The term ‘Migration’ refers to a process of transferring services, data, and resources from one network component to another (for example, from one NRF to another NRF).

[0008] The term ‘CLI’ used hereinafter in the specification refers to a command-line interface. The CLI is a text-based interface through which users can interact within the network by entering specific commands. For example, a migration cutoff command can be entered using the CLI.

[0009] The term ‘GUI’ used hereinafter in the specification refers to a graphical user interface. The GUI is a visual-based interface that allows the users to interact within the network using graphical elements such as buttons, windows, icons, etc. For example, the migration cutoff command can be entered using the GUI.

[0010] The term ‘migration cutoff used hereinafter in the specification refers to a situation in the migration process when the responsibility of managing specific PLMNs and NFs is transferred from an existing NRF to a new NRF. During the migration cutoff, data synchronization between the existing NRF and the new NRF is stopped, the PLMNs are reassigned to appropriate NRFs, and profiles, subscriptions, and access tokens are either retained, removed, or updated based on the PLMNs distribution.

[0011] The term ‘migration cutoff command’ used hereinafter in the specification refers to an instruction executed using the CLI or GUI to initiate the migration process. The migration cutoff command collects data, pauses synchronization, and changes PLMNs from an existing NRF to a new NRF.

[0012] The term ‘rollback operation’ used hereinafter in the specification refers to a process of recovery that reverses the migration process if any issue or error is detected during the migration cutoff. The rollback operation restores the changes in network configuration to its pre-migration state using backup data. The rollback operation involves reverting the PLMNs to the original configuration, i.e., existing NRF, by restoring data such as profiles of NFs, subscriptions access to tokens, and similar.

[0013] These definitions are in addition to those expressed in the art.BACKGROUND

[0014] 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 reader's understanding with respect to the present disclosure, and not as admissions of prior art.

[0015] In telecommunications, a geographical region is divided into different circles with separate public land mobile networks (PLMN) per circle. Based on a current deployment strategy, network repository functions (NRFs) have been deployed to simultaneously serve multiple circles or PLMNs.

[0016] With the expansion of a network and the need for 5G or 6G services reach, there is a growing need for efficient handling of NFs to provide enhancedservices to users. In the network, NRFs play a central role in managing the services provided to the NFs. The NRFs often serve multiple PLMNs simultaneously, which is also referred to as super core configuration.

[0017] However, operators often need to break the above-mentioned super core. For example, the existing super core, which serves a set of PLMNs (e.g., PLMN A, PLMN B, PLMN C, and PLMN D), must be broken into two sub-super cores, namely, a first sub-super core and a second sub-super core. The first sub-super core consists of PLMN A and PLMN B, while the second sub-super core may consist of PLMN C and PLMN D.

[0018] However, the problem arises when the NRFs serving a set of PLMNs (for example, PLMN A, PLMN B, PLMN C, and PLMN D) are already active (live) and running. Thus, deploying a second NRF and migrating the NFs is challenging.

[0019] However, the existing NRF instance is live and actively serving multiple PLMNs (for example, PLMN A, PLMN B, PLMN C, and PLMN D), making it operationally complex to introduce a second NRF and migrate network functions without disrupting ongoing services. This setup limits flexibility in managing regionspecific network functions.

[0020] There is no direct method to migrate PLMNs and associated network functions from the existing NRF to a new NRF without impacting ongoing services. Any interruption during the migration process may adversely affect network function interactions and degrade service performance. Furthermore, the migration must support parallel execution, extended durations, and include comprehensive pre- and postmigration validation procedures. The current architecture lacks the flexibility to scale NRF instances dynamically across PLMNs, thereby necessitating a robust procedural framework to enable safe and efficient migration of PLMNs from an existing NRF to a new NRF instance without impacting service availability

[0021] In the existing system, splitting the PLMNs may be done manually. However, this manual process may lead to potential errors and impact on the ongoing service, thus leading to a poor user experience.

[0022] In existing systems, keeping data up-to-date without causing downtime or affecting the end-user experience presents significant challenges.

[0023] Due to a lack of synchronization between existing and new NRF instances during PLMN migration, end users may face service disruptions such as failed session establishment, authentication errors, and inability to access expected services, resulting in degraded connectivity and user experience.

[0024] There is, therefore, a need in the art to provide a method and a system that can mitigate the disadvantages of the prior art.OBJECTIVE

[0025] Some of the objectives of the present disclosure, which at least one embodiment herein satisfies, are as follows:

[0026] An objective of the present disclosure is to provide a method and a system for migrating at least one public mobile network (PLMN) in a network.

[0027] Another objective of the present disclosure is to provide a method and a system to migrate an existing running public land mobile network (PLMN) served by an existing NRF to a new NRF without impacting the services.

[0028] Another objective of the present disclosure is to provide a method and a system for maintaining real-time data synchronization during a migration process, ensuring data integrity throughout the migration process.

[0029] Another objective of the present disclosure is to provide an optimized approach to split PLMNs without disrupting any ongoing service.

[0030] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.SUMMARY

[0031] In an exemplary embodiment, a method for migrating at least one public mobile network (PLMN) in a network is disclosed. The method includes associating, by a processing engine, at least one new network repository function (NRF) with a network function set (NF set), where the NF set is associated with an existing NRF that is configured to serve one or more PLMNs. The method includes synchronizing, by the processing engine, operational data corresponding to the NF set between the existing NRF and the at least one new NRF during a predefined transition period. The method includes based on the synchronization, generating, by the processing engine, a migration report indicating an operational status of the existing NRF and the at least one new NRF. The method includes based on the generated report, executing, by the processing engine, a migration cutoff command. The method includes upon execution, migrating, by the processing engine, the at least one PLMN to the at least one new NRF.

[0032] In an embodiment, at least one PLMN is selected from the one or more PLMNs that are previously associated with the existing NRF, where the selection is performed based on a predefined configuration specified by a network operator.

[0033] In an embodiment, upon execution of the migration cutoff command, the method includes terminating, by the processing engine, the synchronization of the operational data between the existing NRF and the at least one new NRF. The method includes reallocating, by the processing engine, at least one NF from the NF set that isassociated with the migrated at least one PLMN to the at least one new NRF. The method includes enabling, by the processing engine ((208)), one or more operations of the at least one new NRF with the reallocated at least one NF.

[0034] In an embodiment, the one or more operations includes registration handling of the at least one NF, service discovery operations of the at least one NF, and subscription management of the at least one NF corresponding to the migrated at least one PLMN.

[0035] In an embodiment, the operational status is at least one of a registration status, a service availability status, and an update or modification status, corresponding to synchronization of the operational data between the existing NRF and the at least one new NRF.

[0036] In an embodiment, the operational data includes one or more parameters, the one or more parameters include at least one of: an NF instance ID, an NF profile, subscription information, an access token, an authorization policy, and service discovery information.

[0037] In an embodiment, on the generated report, the method includes determining, by the processing engine, whether a variation is present between the synchronized operational data of the at least one new NRF and the operational data of the existing NRF. The method includes based on the determination, performing, by the processing engine, one or more actions across the existing and the at least one new NRF.

[0038] In an embodiment, the one or more actions includes one of validating, by the processing engine, a successful migration of the at least one PLMN or performing, by the processing engine, a rollback operation with the existing NRF and the at least one new NRF.

[0039] In an exemplary embodiment, a system for migrating at least one public mobile network (PLMN) in a network is disclosed. The system includes a processing engine and a memory coupled to the processing engine, where the processing engine is configured to associate at least one new network repository function (NRF) with a network function set (NF set), wherein the NF set is associated with an existing NRF, that is configured to serve one or more PLMNs. Synchronize operational data corresponding to the NF set between the existing NRF and the at least one new NRF during a predefined transition period. Generate a migration report indicating an operational status of the existing NRF and the at least one new NRF based on the synchronization. Execute a migration cutoff command based on the generated report and upon execution, migrate the at least one PLMN to the at least one new NRF.

[0040] In an embodiment, at least one PLMN is selected from the one or more PLMNs that are previously associated with the existing NRF, where the selection is performed based on a predefined configuration specified by a network operator.

[0041] In an embodiment, upon execution of the migration cutoff command, the processing engine is configured to terminate the synchronization of the operational data between the existing NRF and the at least one new NRF. The processing engine reallocates at least one NF from the NF set that is associated with the migrated at least one PLMN to the at least one new NRF. The processing engine enables one or more operations of the at least one new NRF with the reallocated at least one NF.

[0042] In an embodiment , the one or more operations includes registration handling of the at least one NF, service discovery operations of the at least one NF, and subscription management of the at least one NF corresponding to the migrated at least one PLMN.

[0043] In an embodiment, the operational status is at least one of a registration status, a service availability status, and an update or modification status, correspondingto synchronization of the operational data between the existing NRF and the at least one new NRF.

[0044] In an embodiment, the operational data comprises one or more parameters, the one or more parameters include at least one of an NF instance ID, an NF profile, subscription information, an access token, an authorization policy, and service discovery information.

[0045] In an embodiment, based on the generated report, the processing engine is configured to determine whether a variation is present between the synchronized operational data of the at least one new NRF and the operational data of the existing NRF and based on the determination, perform one or more actions the existing and the at least one new NRF.

[0046] In an embodiment, the one or more actions includes one of validating, by the processing engine, a successful migration of the at least one PLMN or performing, by the processing engine, a rollback operation between the existing NRF and the at least one new NRF.

[0047] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method for migrating at least one public mobile network (PLMN) in a network. The method includes associating, by the processing engine, at least one new network repository function (NRF) with a network function set (NF set), wherein the NF set is associated with an existing NRF that is configured to serve one or more PLMNs. The method includes synchronizing, by the processing engine, operational data corresponding to the NF set between the existing NRF and the at least one new NRF during a predefined transition period. The method includes based on the synchronization, generating, by the processing engine, a migration report indicating anoperational status of the existing NRF and the at least one new NRF. The method includes based on the generated report, executing, by the processing engine, a migration cutoff command and upon execution, migrating, by the processing engine, the at least one PLMN to the at least one new NRF.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

[0048] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which, like reference numerals, refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale emphasis instead being placed upon clearly illustrating the principles of the present disclosure. 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.

[0049] FIG. 1 illustrates an exemplary network architecture for implementing a system for migrating at least one public mobile network (PLMN) in a network, in accordance with an embodiment of the present disclosure.

[0050] FIG. 2 illustrates an exemplary block diagram of the system configured for migrating the at least one PLMN in the network, in accordance with an embodiment of the present disclosure.

[0051] FIG. 3 illustrates an exemplary system architecture of the system configured for migrating the at least one PLMN in the network, in accordance with an embodiment of the present disclosure.

[0052] FIG. 4A illustrates an exemplary process flow for adding a new network repository function (NRF) to a existing NRF in accordance with an embodiment of the present disclosure.

[0053] FIG. 4B illustrates an exemplary session flow for redistribution of a network functions (NFs) towards the new NRF, in accordance with an embodiment of the present disclosure.

[0054] FIG. 4C illustrates an exemplary process flow for the NFs migration cutoff, in accordance with an embodiment of the present disclosure.

[0055] FIG. 5 illustrates an exemplary flow diagram of a method for migrating the at least one PLMN in the network, in accordance with an embodiment of the present disclosure.

[0056] FIG. 6 illustrates an exemplary computer system in which or with which the embodiments of the present disclosure may be implemented.

[0057] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102-1, 102-2... 102-N - Plurality of Users104-1, 104-2... 104-N - Plurality of User Equipments106 - Network108 - System200 - Block Diagram(202) - Processor(s)(204) - Memory(206) - Plurality of Interfaces(208) - Processing engine (210) - Database300 - System Architecture302 - Multicast Broadcast Service Function (MBSF)304 - Multicast or Broadcast Session Management Function (MB-SMF)306 -Network slice-specific Authentication and Authorization Function (NSSAAF) 308 - Network data analysis function (NWDAF)310 - Gateway Mobile Location Center (GMLC)312 - Network slice selection function (NSSF)314 - Network exposure function (NEF)316 - Existing Network repository function (NRF) 318 - Policy control function (PCF)320 - Unified data management (UDM)322 - Multicast broadcast session transfer function (MBSTF)324 - Mobile number portability function (MNPF)326 - Short message service interworking mobile switching center (SMS-IWMSC)328 - Location management function (LMF)330 - Unified data repository (UDR)332 - Authentication server function (AUSF) 334 - Access and mobility management function (AMF)336 - Session management function (SMF)338 - Service communication proxy (SCP)340 - Application function (AF)342 - Charging function (CHF) 344 - Security edge protection proxy (SEPP)346 - New NRF400A - Flow Diagram400B - Flow Diagram400C - Flow Diagram 500 - Method flow diagram600 - Computer System610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670 - ProcessorDETAILED DESCRIPTION

[0058] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific 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 embodiments 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.

[0059] The ensuing description provides exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0060] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0061] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations 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. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0062] 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 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 like the term “comprising” as an open transition word without precluding any additional or other elements.

[0063] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0064] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any combinations of one or more of the associated listed items. 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 invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention 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 invention as defined herein.

[0065] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers toany 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, 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, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a 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.

[0066] 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, a plurality of microprocessors, one or more microprocessors in association with a Digital Signal Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.

[0067] 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 technologies. In the field of wireless data communications, the dynamic advancement of variousgenerations 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.

[0068] 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 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 a GSM (Global System for Mobile Communications), a Code Division Multiple Access (CDMA), a Universal Mobile Telecommunications System (UMTS), a Long-Term Evolution (LTE), a Fifth Generation (5G) technology, and a Sixth Generation (6G) technology. 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 performance based on the available network resources.

[0069] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog, offering only voice services. Further, text messaging and data services became possible when a Second Generation (2G) technology was introduced. A Third Generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. A Fourth Generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, the 5G technology is being deployed, offering significantly faster data speeds, lower latency, and the ability to connect many devicessimultaneously. These advancements represent a significant leap forward from previous generations, enabling enhanced mobile broadband, improved Internet of Things (loT) connectivity, and more efficient use of network resources. The 6G technology promises to build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidly evolving, with the aim of revolutionizing the way of connecting and interacting with technology.

[0070] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.

[0071] Embodiments herein relate to a method for migrating at least one public mobile network (PLMN) in a network. The method and a system are disclosed for migrating PLMNs in the network to efficiently manage Super Cores serving multiple PLMNs. Currently, a single Network Repository Function (NRF) handles various PLMNs within a Super Core, creating challenges when network expansion and 5G implementation necessitate splitting the Super Core into smaller units with different PLMNs. The present disclosure addresses the problem of transitioning PLMNs from an existing NRF to a new NRF without disrupting services. The processes involve synchronizing data between the existing NRF and the new NRFs during migration, generating reports on operational status, executing migration commands, and reallocating network functions to enable seamless operations. By ensuring these transitions occur without service impact and permitting multiple concurrent migrations,the solution enhances network management and addresses the growing demands on network operators. The present disclosure of a method of procedure (MoP) at the Network Function level, enabling operators to perform migrations without service interruptions. The step-by-step process includes setting up new NRFs as part of the existing network, facilitating extended NF migration activities, and executing a well- defined cutover strategy, ensuring data integrity and continuity of services.

[0072] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0073] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1- FIG. 6.

[0074] FIG. 1 illustrates an exemplary network architecture (100) for migrating the at least one PLMN in the network (106), in accordance with an embodiment of the present disclosure. As illustrated in FIG. 1, the network architecture (100) may include one or more computing devices or User Equipments (UEs) (104-1, 104-2... 104-N) associated with one or more users (102-1, 102-2... 102-N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2... 102- N) may be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more UEs (104-1, 104-2... 104-N) may be individually referred to as the UE (104) and collectively referred to as the UEs (104). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although three UEs (104) are depicted in FIG. 1 , however, any number of the UEs (104) may be included without departing from the scope of the ongoing description.

[0075] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such anembodiment, the UE (104) may include, but is not limited to, smartphones, smart watches, smart sensors (e.g., a mechanical sensor, a thermal sensor, an electrical sensor, a magnetic sensor, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart televisions (TVs), computers, smart security systems, smart home systems, other devices for monitoring or interacting with or for the user (102) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (104) may include, but is not limited to, intelligent, multi-sensing, network-connected devices, that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0076] In an embodiment, the UE (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE (104) may include, but is not limited to, any electrical, electronic, electro-mechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. Further, the UE (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or an entity such as a touch pad, a touch enabled screen, an electronic pen,and the like. A person of ordinary skill in the art will appreciate that the UE (104) may not be restricted to the mentioned devices and various other devices may be used.

[0077] In FIG. 1, the UE (104) may communicate with the system (108) through the network (106). In particular, the UE (104) may be communicatively coupled with the network (106). The coupling includes steps of receiving, by network (106), a connection request from UE (104). Upon receiving the connection request, the coupling includes steps of sending, by the network (106), an acknowledgment of the connection request to the UE (104). Further, the coupling includes steps of transmitting a plurality of signals in response to the connection request.

[0078] In an embodiment, the network (106) may include at least one of the 4G network, the 5G network, the 6G network, or the like. The network (106) may enable the UE (104) to communicate with other devices in the network architecture (100) and / or with the system (108). The network (106) may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network (106) may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public- Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. In another embodiment, the network (106) includes, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth.

[0079] In another exemplary embodiment, the network architecture (100) may include a centralized server (not shown) may include or comprise, by way of example but not limitation, one or more of a stand-alone server, a server blade, a server rack, a bank of servers, a server farm, a hardware supporting a part of a cloud service or the system, a home server, a hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof.

[0080] The system (108) is configured for migrating the at least one PLMN in the network (106) as explained in detail in FIG. 2.

[0081] Although FIG. 1 shows exemplary components of the network architecture 100, in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture 100.

[0082] FIG. 2 illustrates an exemplary block diagram (200) of the system (108) configured migrating the at least one PLMN in the network (106), in accordance with an embodiment of the disclosure. FIG. 2 is explained in conjunction with FIG. 1. In an embodiment, the network may be, for example, the 4G network, the 5G network, the 6G network, and the like.

[0083] In an embodiment, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based onoperational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include any non-transitory storage device including, for example, volatile memory such as a Random-Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.

[0084] In an embodiment, the system (108) may include an interface(s) (206). The interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices (VO), storage devices, and the like. The interface(s) (206) may facilitate communication through the system (108). The interface(s) (206) may also provide a communication pathway for one or more components of the system (108). Examples of such components include, but are not limited to, a processing engine (208) and a database (210).

[0085] In an embodiment, the processing engine (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (208). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine (208) may be processor-executable instructions stored on a non- transitory machine-readable storage medium and the hardware for the processing engine (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine- readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine (208). In such examples, the system (108)may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the processing engine (208) may be implemented by electronic circuitry.

[0086] In an embodiment, the database (210) may include data that may be either stored or generated as a result of functionalities implemented by any of the components of the processing engine (208).

[0087] In an embodiment, the processing engine (208) is configured for migrating the at least one PLMN in the network (106). The NRF is a component within the 5G network that manages the registration and discovery of NFs. The NRF acts as a central repository for NFs profiles enabling different NFs to discover each other and interact with each other. The PLMN is a mobile network that provides mobile services to the public. The PLMN comprises an infrastructure and spectrum that allows the UEs (104) to connect to the network. The PLMN is of two types: a home PLMN (PLMN1) and a PLMN2.

[0088] A geographical area is divided (or split) into different circles, each with a separate PLMN deployed. Based on a current deployment strategy, the NRFs simultaneously serve multiple circles or PLMNs. For example, the NRF may serve a PLMN A, a PLMN B, a PLMN C, and PLMN D. When a single NRF instance serves a set of the PLMNs, it is called a super core. In this regard, the existing NRFs that may be serving the set PLMNs are divided into one or more new NRFs based on the segregation of the PLMNs. This division allows for more focused resource management, leading to improved performance and scalability of the network. The segregation process of the PLMNs involves organizing them into distinct groups. This ensures that each NRF specializes in a specific set of the PLMNs, allowing for more tailored service delivery and resource allocation. For example, one or more NRFsmight be serving the PLMN A and the PLMN B, while another NRF might be serving the PLMN C and the PLMN D. The migration is the process of transferring PLMNs from NRFs that are serving the PLMNs at this time to one or more newly established NRFs.

[0089] In an embodiment, the processing engine (208) is configured to install the new NRF and integrate it into a set of network functions (NFs) of the existing NRF, wherein both the new NRF and the existing NRF serve the PLMNs. The new NRF is deployed within the network. Integrating the new NRF with the existing NRF enables both NRFs to share operational data and necessary configurations. The new NRF may support a mirrored NF set approach where data synchronization occurs between a set of NFs in both NRFs. In the mirrored NF set approach, the state and data between multiple NRFs or NFs are synchronized, which ensures that any changes such as registrations, updates, or deletions made in one NRF are also reflected in the new NRF, allowing for consistency in the network.

[0090] In an embodiment, the processing engine (208) is configured to initiate at least one operation of the NFs associated with the PLMNs with the new NRF during a migration period. The at least one operation of the NFs may be an operation of registering NF with the new NRF, subscribing NF to the new NRF, or discovering the NRF. Upon initiating at least one operation, the new NRF begins to serve requests as previously done by the existing NRF. The at least one operation may be performed during the migration period. The migration period is a defined time frame during the migration process. In the migration period, the at least one operation is initiated until all the NFs complete specific migration towards the new NRF.

[0091] In an embodiment, the processing engine (208) is configured to monitor the status of the NFs to generate a report and to determine the state of migration of the NRF. The monitoring involves assessing the operational status of the NFs, such as checking the heartbeat of the NFs, registration status of the NFs, service availability of1 the NFs, and similar. The ongoing heartbeat ensures that the NFs are actively communicating with the NRFs, whereas monitoring the registration status indicates whether the NFs are successfully registered with the new NRF. Moreover, monitoring the service availability of the NFs indicates the ability of the NFs to provide service during the migration, ensuring the requests for services are handled appropriately. Upon monitoring the status of the NFs, the report, including an NF Instance ID, an NF Type, the PLMNs, and similar, is generated.

[0092] In an aspect, if any NF is active or has an ongoing heartbeat and is served with non-matching PLMNs, then the generated report also includes this information. For example, a mismatch occurs if an NF is intended to handle the PLMN A but subscribes to an NRF maintaining the PLMN B. Upon detecting the mismatch, a notification or alert may be generated in the report such that the user reviews the report to obtain detailed insights about the operational status of the NFs. The user can execute the generated reports for the existing or existing NRFs (316) and the new NRFs to determine if the NFs are ready for the migration cutoff. The migration cutoff is when the PLMNs transition from the existing NRF (316) to the new NRF (346).

[0093] In an embodiment, the processing engine (208) is configured to execute a migration cutoff command using a command line interface (CLI) or graphical user interface (GUI). The migration cutoff command is a directive instruction that the user 102 enters using the CLI or GUI. The CLI or GUI may be a centralized CLI or GUI or the NRF-specific CLI or GUI. The centralized CLI or GUI is an interface that can manage multiple NRFs, whereas the NRF-specific CLI or GUI is the interface explicitly dedicated to the single NRF.

[0094] In an aspect, the migration cutoff command is used to collect data to create backups and reports, stop synchronization between the existing NRFs and the new NRFs, and reassign the PLMNs associated with the NRFs. The migration cutoff command triggers data collection from existing and new NRFs. The data may includethe current configuration of the NFs, the status of active registration and associations with the PLMNs, performance, and heartbeat status of the NFs. As a part of the migration cutoff command execution, a backup of the current configuration is created, this backup serves as a restore point, allowing the PLMNs to revert to the original configuration in case any issue arises during the migration process. Moreover, the migration cutoff command halts synchronization between the existing NRF and the new NRF to prevent any inconsistencies or data conflicts that may complicate the migration process. After stopping the synchronization, the PLMNs are reassigned to reflect the new changes as needed for migration. For example, if currently both the new and the existing NRFs serve the PLMN A, the PLMN B, the PLMN C, and the PLMN D. Post the migration cutoff command, the existing NRF starts serving the PLMN A and the PLMN B while the new NRF starts serving the PLMN C and the PLMN D with consideration that the PLMN C and the PLMN D are identified for migration. The new NRF is taken out of the set of NFs and created as an independent NRF under a different set of NFs. It will be appreciated that one or more NRFs may be made a part of the new set of NFs at this time.

[0095] In an embodiment, the processing engine (208) is configured to perform at least one check to verify the successful migration of the NRFs. The at least one check may be an automatic check for NFs profiles provided to mark the profiles that will be removed from the new NRF (346) and the existing NRF (316) as per new PLMNs distribution. The user 102 may also select the exception NFs to be retained in the NFs profile. Moreover, at least one check may be related to checks for other objects, such as subscriptions and access tokens. The subscription and access tokens checks identify whether the subscription and access tokens associated with the NFs are transferred to the new NRF or whether any expired or incorrect subscriptions are still active in both NRF. and are also distributed according to the target PLMN condition. Additionally, at least one check may be an auto check for pre-migration cut-off subscription or accesstoken and other objects and comparison with post-migration cut-off carried out in both old and new NRF to create comprehensive reports.

[0096] In an embodiment, the processing engine (208) is configured to enable an independent operation of the new NRF with a new set of NFs. After performing the necessary checks, the new NRF with migrated PLMN and the existing NRF (316) with corresponding, the PLMNs start working independently.

[0097] In an embodiment, the processing engine (208) is configured to execute a rollback operation when it is determined that the migration of the NRFs has failed. The rollback operation is executed using the backup that is created at the time of entering the migration cutoff command. Upon detecting any issue during the migration process, the rollback operation is executed such that all the above methods are performed reversely. The ongoing configuration is removed while updating any delta profile additions or new objects created in both NRFs, and a single set of NFs is made with multiple joint PLMNs.

[0098] In an embodiment the system (108) for migrating the at least one PLMN in the network (106), the system (108) includes the processing engine (208) and the memory coupled to the processing engine (208). The processing engine (208) is configured to associate at least one new NRF (346) with a NF set, where the NF set is associated with the existing NRF (316), that is configured to serve one or more PLMNs. Herein, associating may refer to establishing a relationship where the new NRF (346) enhances the existing NF set's functionality. The processing engine (208) is configured to synchronize an operational data corresponding to the NF set between the existing NRF (316) and the at least one new NRF (346) during a predefined transition period. Herein, synchronize refers to matching and updating the operational data to ensure that the existing NRF (316) and any new NRF (346) remain consistent with each other during a specified transition period. The processing engine (208) is configured to generate a migration report indicating an operational status of the existing NRF (316)and at least one new NRF (346) using the operational data gathered during the synchronization. The processing engine (208) is configured to execute a migration cutoff command based on the generated report. The processing engine (208) is configured to execute a migration cutoff command. The migration command halts the migration process when the responsibility for managing specific PLMNs and NFs shifts from the existing NRF (316) to the new NRF (346). During migration cutoff, data synchronization between the NRFs ends, the PLMNs are reassigned, and profiles, subscriptions, and access tokens are adjusted accordingly. The migration cutoff is guided by a report that may determine the optimal timing to ensure data integrity and minimize disruptions. The processing engine (208) is configured to, upon execution, migrate the at least one PLMN to the at least one new NRF (346).

[0099] In an embodiment, the at least one PLMN is selected from the one or more PLMNs that are previously associated with the existing NRF (316), where the selection is performed based on a predefined configuration specified by a network operator. For instance, the network operator may select the PLMNs with the strongest signal strength or least congestion, such as choosing the PLMN with fewer active users in a densely populated area, maybe to provide optimal connectivity and service quality.

[0100] In an embodiment, the system (108), upon execution of the migration cutoff command, the processing engine (208) is configured to terminate the synchronization of the operational data between the existing NRF (316) and the at least one new NRF (346). The processing engine (208) reallocates at least one NF from the NF set that is associated with the migrated the at least one PLMN to the at least one new NRF (346). The processing engine (208) enables one or more operations of the at least one new NRF (346) with the reallocated at least one NF. For instance, the processing engine (208) terminates the operational data synchronization between the existing NRF (316) and the new NRF (346). For example, this may prevent the operational data conflicts during the handover. The processing engine (208) reallocatesat least one NF from the NF set associated with the migrating PLMN to the new NRF (346). For example, the reallocation may include redirecting operational NFs to maintain uninterrupted service. The processing engine (208) enables certain features of the new NRF (346) with the newly reassigned NF, the new NRF (346) may be fully operational.

[0101] In an embodiment, the one or more operations includes registration handling of the at least one NF, service discovery operations of the at least one NF, and subscription management of the at least one NF corresponding to the migrated at least one PLMN. For example, if the network operator migrates its services to the new PLMN (346), the system (108) handles the registration of service instances for NFs, enables seamless discovery of these services, and manages active subscriptions which may provide continuity and integrity of network communications during and after the migration process.

[0102] In an embodiment, the operational status is at least one of which include a registration status, a service availability status, and an update or modification status, corresponding to synchronization of the operational data between the existing NRF (316) and the at least one new NRF (346). For instance, a registration status may indicate whether the system (108) is registered and ready for use. The service availability status may reflect whether services are currently accessible. The update or modification status may represent whether there has been synchronization of operational data between the existing NRF (316) and at least one new NRF (346).

[0103] In an embodiment, the operational data include one or more parameters, the one or more parameters include at least one of which include an NF instance ID, an NF profile, subscription information, an access token, an authorization policy, and service discovery information. For instance, the operational data include the NF instance ID may be for identifying specific NF, the NF profile may include detailing the capabilities and configurations of the NF, and the subscription information may beused to manage a service access. The access token may be present for authenticating identity, and an authorization policy may dictate the permissions associated with different operations. The service discovery information may locate and establish connections with necessary services.

[0104] In an embodiment, based on the generated report, the processing engine (208) is configured to determine whether a variation is present between the synchronized operational data of the at least one new NRF (346) and the operational data of the existing NRF (316) and based on the determination, perform one or more actions the existing and the at least one new NRF (346). For example, if the new NRF (346) has updated software or configuration compared to the existing NRF (316), the processing engine (208) can detect this variation. Based on this determination, the processing engine (208) may update the existing NRF (316) to match the new configuration.

[0105] In an embodiment, the one or more actions includes one of which by validating, by the processing engine (208), a successful migration of the at least one PLMN or performing, by the processing engine (208), a rollback operation between the existing NRF (316) and the at least one new NRF (346). For instance, when the mobile network operator migrates from an old network configuration to a new one, the system (108) can verify the migration went smoothly. If issues arise, it may also revert to the previous configuration to maintain network stability.

[0106] FIG. 3 illustrates an exemplary system architecture (300) of the system (108) configured for migrating the at least one PLMN in the network (106), in accordance with an embodiment of the present disclosure. FIG. 3 is explained in conjunction with FIG. 2.

[0107] FIG. 3 shows the 5G network architecture (300), including two interconnected PLMN1, and PLMN2. The network architecture (300) may supportseamless service continuity and interoperability of the NF during migration of NFs or expansion of NFs.

[0108] The PLMN1 is a primary network, responsible for managing subscription profiles and delivering core services. The PLMN1 is organized into a control plane and a data plane. The control plane includes several key network functions. The Multicast Broadcast Service Function (MBSF) (302) manages and controls multicast and broadcast delivery services, handling session management, user plane function selection, and resource allocation. The Multicast or Broadcast Session Management Function (MB-SMF) (304) is responsible for managing multicast and broadcast sessions, including setup, modification, and release of PDU sessions, and works closely with the MBSF (302) to ensure efficient content delivery. The Network Slice-Specific Authentication and Authorization Function (NSSAAF) (306) performs authentication and authorization specific to individual network slices, ensuring that UE (104) is permitted to access a particular slice based on subscription information and policies. The NWDAF (308) collects, analyzes, and distributes network-related data and analytics, providing real-time and predictive insights to optimize performance and enforce policies. The GMLC (310) handles external requests for user location information, enabling secure access to location-based services. The NSSF (312) selects appropriate network slices for the UE based on subscription data and requested services. The NEF (314) securely exposes network capabilities and services to authorized external applications via standardized APIs. The existing NRF (316) maintains a registry of available network functions and supports service discovery. The PCF (318) manages policy rules to control network behavior and ensure compliance with service requirements. The UDM (320) function manages subscription data, user authentication, authorization, and mobility management.

[0109] The data plane of the PLMN 1 includes additional network functions that support service delivery and mobility. The MBSTF (322) manages the seamlesstransfer or handover of multicast and broadcast sessions between network nodes or areas. The MNPF (324) facilitates the portability of mobile subscriber numbers between network operators, ensuring correct routing and service continuity. The Short Message Service Interworking Mobile Switching Center (SMS-IWMSC) (326) enables interworking and routing of SMS messages between circuit- switched and packet- switched networks. The LMF (328) manages location-related procedures, including UE (104) positioning. The UDR (330) provides a centralized database for storing and managing subscriber-related data, supporting authentication, session management, and policy enforcement. The AUSF (332) performs authentication procedures for UEs (104) accessing the network, interacting with the UDM (320) to validate user identity. The AMF (334) manages UE (104) access, mobility, registration, and session control, acting as a gateway between the UE (104) and other core network functions. The SMF (336) handles session setup, modification, and release for UEs (104) accessing the network. The SCP (338) acts as an intermediary to route and manage service-based interface communications, providing message forwarding, load balancing, and security. The AF (340) interacts with the 5 G core network to influence service delivery, such as requesting policy control and quality of service adjustments. The CHF (342) collects and processes charging data for billing and accounting purposes. The SEPP (344) provides secure interconnection between different operator networks, enforcing security policies including authentication, authorization, and message protection for signaling and data exchanged across network boundaries. The New NRF (346) represents the updated network repository function in the PLMN2.

[0110] The PLMN2 is a secondary network. It includes similar 5G components to those in the PLMN 1 to ensure service continuity. The New NRF (346) in the PLMN2 interacts with the existing NRF (316) in the PLMN1 via the N27 interface. The N27 interface is a standardized 5G interface that enables service discovery, data synchronization, and roaming support. The N27 facilitates the exchange of the NF registration and discovery data between the NRFs of the PLMN1 and the PLMN2,allowing coordinated service delivery and migration of the NF without impacting ongoing services.

[0111] In one embodiment, the network architecture (300) facilitates migration of the NFs and services from the PLMN1 to the PLMN2. The migration process involves the synchronization of service registries between the existing NRF (316) in the PLMN1 and the new NRF (346) in the PLMN2. The N27 interface enables realtime exchange of network function data, allowing the PLMN2 to discover and register functions previously hosted in the PLMN1. This may ensure that service continuity is maintained during the migration of user sessions, policy enforcement, and authentication procedures. Functions such as the UDM (320), the AUSF (332), and the PCF (318) in the PLMN 1 remain accessible to the PLMN2 through secure signaling pathways, coordinated by the SEPP (344).

[0112] The network architecture (300) also supports network expansion by allowing the deployment of new NFs in the PLMN2. The NFs, once registered with the new NRF (346), become discoverable to the PLMN1 via the N27 interface. Enabling the PLMN1 to offload certain services or extend coverage by leveraging resources in the PLMN2. For example, multicast and broadcast services managed by the MBSF (302) and the MB-SMF (304) can be extended to the PLMN2, with session continuity ensured by the MBSTF (322). The expansion process is further supported by the NSSF (312), which dynamically assigns network slices based on service requirements and user profiles.

[0113] In another embodiment, the network architecture (300) enables a new migration mechanism between the PLMN 1 to the PLMN2 experiences uninterrupted service access. Upon entering the coverage area of the PLMN2, the UE (104) connects to the access network of PLMN2. The new NRF (346) in PLMN2 initiates communication with the existing NRF (316) in PLMN 1 via the N27 interface, allowing the PLMN2 to retrieve necessary service and function data. Core functions such as theAMF (334), the SMF (336), and the SCP (338) in the PLMN2 are configured to serve the roaming UE (104), while policy control and authentication continue to be managed by the PLMN1. The AF (340) and the CHF (342) ensure that application-level service delivery and billing are maintained across network boundaries.

[0114] The SEPP (344) enforces security policies for all inter-network signaling and data exchange, ensuring confidentiality, integrity, and compliance with operator agreements. This roaming model supports slice-aware roaming, dynamic service discovery, and real-time policy enforcement, thereby enabling differentiated services and seamless user experience across the PLMN1 and the PLMN2.

[0115] The network architecture (300) depicted in FIG. 3 thus provides a robust framework for enabling the migration, the expansion, and the roaming in 5G networks, ensuring service continuity, scalability, and secure inter-network operations.

[0116] The network architecture (300) ensures uninterrupted service delivery during roaming, with both the PLMN1 and the PLMN2 coordinating via standardized interfaces and synchronized network functions to maintain seamless connectivity and service continuity for the subscriber.

[0117] FIGS. 4A, 4B, and 4C illustrate an exemplary process flow 400 for migrating the at least PLMN in the network (106), in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIGS. 2 and 3.

[0118] With reference to FIG. 4A, the process flow for adding the new NRF (346) to the existing NRF (316) is depicted.

[0119] At step 402, the new NRF (346) is added to the existing NFs set of the existing NRF (316).

[0120] In an aspect, the addition of the new NRF (346) may ensure that all objects, such as the NFs currently associated with the existing NRF (316), are also replicated and served by the new NRF (346). Similarly, any new object created, modified, or deleted at the new NRF or the existing NRF is also replicated across these two NRFs. It should be appreciated that both the new NRF (346) and the existing NRF (316) are serving similar PLMNs at this time.

[0121] At step 404, data such as configuration data of the NFs, state information of the NFs, subscription, and access tokens associated with the NFs, and profiles of the NFs are synchronized across both the existing and the new NRF for NFs set support. By keeping data synchronized, it is ensured that both the NRFs can serve the respective PLMNs without any data loss.

[0122] At step 406, the new NRF (346) is activated (made live) and declared as part of the set of the NFs (NF set).

[0123] With reference to FIG. 4B, the process flow of redistribution of the NFs towards the new NRF (346) is depicted.

[0124] With the above steps, the NF migration activity may start. The NFs in the PLMN to be migrated may start registering, subscribing, or discovering the new NRF (346) so that it serves requests as it does by the existing NRF (316).

[0125] At step 408, the set of the NFs corresponding to the existing NRF (316) or the old NRF (316) continues to interact with it and vice versa. The NFs associated with the existing NRF (316) continue to send requests or queries for data or services, and the existing NRF (316) responds to these requests or queries as needed.

[0126] At the same time, at step 410, the set of the NFs that need to be migrated to the new NRF (346) based on serving the PLMN interacts with and connects to the new NRF (346). The new NFs associated with the new NRF (346) can register,subscribe, and send requests to the new NRF (346) to manage data and services. The newNRF (346) handles these requests as it did previously by the existing NRF (316).

[0127] At step 412, data synchronization continues between the existing NRF (316) and the new NRF (346) during migration, without impacting the NRF services and corresponding results.

[0128] With reference to FIG. 4C, the process flow of the NFs migration cutoff is depicted.

[0129] The status of the NFs is determined by a tool, such as a monitoring tool. This tool tracks which NFs are currently active and for which the NRF is handling heartbeat. The heartbeat is a signal sent from the NFs to the NRFs to indicate that they are active and functioning correctly. Moreover, the monitoring tool provides a report that includes the NF Instance ID, NF Type, the PLMNs, and similar information.

[0130] In an aspect, if the NF is sending heartbeats but is associated with nonmatching PLMNs (i.e., the NF is registered under the PLMN that the corresponding NRF is not serving), the monitoring tool flags this inconsistency and provides information on the same. The users may execute these reports for the existing and new NRF to determine if the NRF is ready for migration cutoff. Once the user determines that NRF is ready for migration, the user (102) proceeds to the next step.

[0131] At step 414, once the migration cutoff decision is taken, user (102) provides the migration command using the centralized CLI or GUI or NRF-specific CLI or GUI.

[0132] At step 416, once the migration cutoff is entered, it collects data, stops the synchronization between the existing or old and the new NRF, and changes the PLMNs associated with the NRFs as per migration need. In example, if currently both new NRF( 346) and existing NRFs (316) are serving the PLMN A, the PLMN B, thePLMN C and the PLMN D, then post the migration command, the existing NRF (316) will start serving the PLMN A and the PLMN B, while the new NRF (346) will start serving the PLMN C and the PLMN D (with consideration that the PLMN C and the PLMN D is used for migration).

[0133] At step 418, the new NRF (346) is taken out of the set of NFs and further created as independent NRF under different NFs set. In an example, in the existing NRF (316), the PLMN A and the PLMN B are updated, whereas in the new NRF (346), the PLMN C and the PLMN D are updated.

[0134] At step 420, an automatic check for profiles is provided to mark the profiles that will be removed from new and existing NRFs (316) as per the new PLMN distribution. The user (102) may also select the exception NFs that are to be retained in the profile. For example, the profiles for NFs other than the PLMN A and the PLMN B are removed from the existing NRF (316), whereas the profiles for the NFs other than the PLMN C and the PLMN D are removed from the new NRF (346).

[0135] At step 422, other objects, such as subscriptions and access tokens other than those associated with the target PLMN are also distributed. For example, the subscription and access tokens other than those associated with the target PLMN A and PLMN B are removed from the existing NRF (316). Similarly, the subscription and access tokens other than those associated with the target PLMN C and PLMN B are removed from the new NRF (346).

[0136] At step 424, an automatic check for pre-migration cut-off subscription or access tokens and other objects and a comparison with post-migration cut-off is carried out in both the old and new NRF to create a comprehensive report. Further, a result is determined, and if the results are okay, then the new NRF (or new NFs set) with the migrated PLMN and the existing NRF (316) with corresponding the PLMNs begin to work independently.

[0137] If it is determined that the results of post checks are not okay, i.e., not in accordance, then an automatic or manual rollback operation is initiated using the backup taken at the time of entering the migration cutoff command. The rollback operation reverses the configuration removals while updating any delta profile additions or new objects created in both NRFs, making a single NF set with multiple joint PLMNs.

[0138] FIG. 5 illustrates an exemplary flow diagram of the method (500) for migrating at least one PLMN in the network (106), in accordance with an embodiment of the present disclosure.

[0139] At step 502, the method 500 includes associating, by the processing engine (208), at least one new NRF (346) with the NF set, where the NF set is associated with the existing NRF (316) that is configured to serve one or more PLMNs. For example, when deploying a communication service in a newly established area, the new NRF (346) may be integrated into the NF set to support additional functionalities such as capacity expansion or enhancement of service coverage and the like. For example, the existing NRF (316) may continue to handle the core network operations, while the new NRF (346) augments these capabilities, thereby ensuring seamless service delivery across the PLMNs.

[0140] In an embodiment, the method (500) includes selecting the at least one PLMN from a list of PLMNs previously linked to the existing NRF (316), where the selection is performed based on a predefined configuration specified by the network operator. For example, if the network operator has configured a preference for specific PLMNs based on network performance or coverage criteria, the selection will prioritize these PLMNs over others. Suppose the network operator specifies a high-priority PLMN due to its superior connectivity in urban areas. The method will select it first, ensuring optimal network performance based on the network operator predefined settings.

[0141] In an embodiment, the method (500) includes the one or more operations. The one or more operations handling the registration of the at least one NF, which provides precise records of the NF's status and configuration, executing service discovery operations for at least one NF, which may allow various network services to be identified and accessed efficiently and managing subscriptions for at least one NF that corresponds to the migrated the at least one PLMN, updating subscriber information to reflect any changes from the migration.

[0142] At step 504, the method 500 includes synchronizing, by the processing engine (208), operational data corresponding to the NF set between the existing NRF (316) and the at least one new NRF (346) during a predefined transition period. For example, at step 504 may align service registry information from the existing NRF (316) and new NRFs (346) which may facilitate seamless data access and management as the new system comes online.

[0143] In an embodiment, the method (500) includes operational data that includes one or more specific parameters. The one or more parameters includes at least one of the following, the NF instance ID, the NF profile, the subscription information, the access token, the authorization policy, and the service discovery information.

[0144] At step 506 based on the synchronization, generating, by the processing engine (208), a migration report indicating an operational status of the existing NRF (316) and the at least one new NRF (346)

[0145] In an embodiment, the method (500) includes the operational status such as the registration status, the service availability status, and the update or modification status, corresponding to synchronization of the operational data between the existing NRF (316) and the at least one new NRF (346).

[0146] In step 508, the method (500) includes, based on the generated report, executing, by the processing engine (208), a migration cutoff command. For example,if the report generated indicates that data migration is complete, the migration cutoff command may stop further data transfers to provide system integrity.

[0147] In an embodiment, based on the generated report, the method (500) includes determining, by the processing engine (208), whether a variation is present between the synchronized operational data of the at least one new NRF (346) and the operational data of the existing NRF (316). Based on the determination, the method (500) performing, by the processing engine (208), one or more actions across the existing and the at least one new NRF (346). For instance, if there is a deviation in the synchronized operational data performance, it is identified. Then, the processing engine (208) may implement actions on both the existing NRF (316) and the new NRF (346), such as adjusting data parameters, initiating corrections, or updating protocols to ensure consistency.

[0148] At step 510, the method (500) includes upon execution, migrating, by the processing engine (208), the at least one PLMN to the at least one new NRF (346). For example, the network operator might migrate the cellular network listing from the existing NRF (316) to the new NRF (346), which may improve service efficiency and management capabilities.

[0149] FIG. 6 illustrates an exemplary computer system (600) in which or with which embodiments of the present disclosure may be implemented. As shown in FIG. 6, the computer system (600) may include an external storage device (610), a bus (620), a main memory (630), a read-only memory (640), a mass storage device (650), communication port(s) (660), and a processor (670). A person skilled in the art will appreciate that the computer system (600) may include more than one processor and communication ports. The processor (670) may include various modules associated with embodiments of the present disclosure. The communication port(s) (660) may be any of an RS-232 port for use with a modem- based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallelport, or other existing or future ports. The communication port(s) (660) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (600) connects.

[0150] The main memory (630) may be Random- Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (640) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (670). The mass storage device (650) may be any current or future mass storage solution, which can be used to store information and / or instructions. The mass storage device (650) includes, but is not limited to, Parallel Advanced Technology Attachment (PAT A) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, a Redundant Array of Independent Disks (RAID) storage, e.g. an array of disks.

[0151] The bus (620) communicatively couples the processor (670) with the other memory, storage, and communication blocks. The bus (620) may be, e.g. a Peripheral Component Interconnect (PCI) / PCI Extended (PCLX) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (670) to the computer system (600).

[0152] Optionally, operator and administrative interfaces, e.g. a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (620) to support direct operator interaction with the computer system (600). Other operators and administrative interfaces can be provided through network connections connected through the communication port(s) (660). The components described above are meantonly to exemplify various possibilities. In no way should the aforementioned exemplary computer system (600) limit the scope of the present disclosure.

[0153] In an exemplary embodiment, the system (108) for migrating the at least one PLMN in the network (106), the system (108) includes the processing engine (208) and the memory coupled to the processing engine (208), where the processing engine (208) is configured to associate at least one new NRF (346) with the NF set, where the NF set is associated with the existing NRF (316), that is configured to serve the one or more PLMNs. Synchronize operational data corresponding to the NF set between the existing NRF (316) and the at least one new NRF (346) during a predefined transition period. Generate a migration report indicating an operational status of the existing NRF (316) and the at least one new NRF (346) based on the synchronization. Execute a migration cutoff command based on the generated report and upon execution, migrate the at least one PLMN to the at least one new NRF (346).

[0154] In another exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute the method (500) for migrating the at least one PLMN in the network (106), the method (500) includes associating, by the processing engine (208), at least one NRF with the NF set, wherein the NF set is associated with the existing NRF (316) that is configured to serve one or more PLMNs. The method (500) includes synchronizing, by the processing engine (208), operational data corresponding to the NF set between the existing NRF (316) and the at least one new NRF (346) during a predefined transition period. The method (500) includes based on the synchronization, generating, by the processing engine (208), a migration report indicating an operational status of the existing NRF (316) and the at least one new NRF (346). The method (500) includes based on the generated report, executing, by the processing engine (208), a migration cutoff command. The method (500) includes,upon execution, migrating, by the processing engine (208), the at least one PLMN to the at least one new NRF (346).

[0155] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

[0156] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

[0157] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.

[0158] The present disclosure the method (500) and the system (108) for migrating the at least one PLMN in the network (106) represent a major technical advancement by incorporating the new NRF (346) into the existing NF set. This approach addresses the limitations of the traditional PLMN migrations by providing continuity and minimizing service interruptions. The present disclosure may achieve this through precise synchronization of operational data between the existing NRF (316) and the new NRFs (346) which may reduce downtime. The system (108) may further advance this field by generating a comprehensive migration report to monitor progress and executing the migration cutoff command to optimize network transfers. A key challenge it may overcome is preserving the network (106) performance during migration, enabling seamless transitions. Additionally, the technology may provide overall reliability and efficiency by validating successful migrations and providing the rollback capabilities if required, which may substantially improve the process of network upgrades or expansions.ADVANTAGES OF THE PRESENT DISCLOSURE

[0159] The present disclosure provides a method and a system for managing the migration of a network repository function (NRF) based on segregating public land mobile networks (PLMNs) in a network.

[0160] The present disclosure allows migrating the NRFs without impacting any existing or new service.

[0161] The present disclosure provides an ability to migrate multiple NRFs simultaneously, which ensures efficient delivery service.

[0162] The present disclosure provides an optimized approach to accommodating an extended duration of migration without impacting services, resulting in improved efficiency and accuracy in updates.

[0163] The present disclosure provides an efficient way to check the NRF to make go or no-go decisions for migration.

[0164] The present disclosure provides checks at the NRF to ensure pre and post-migration status checks for various objects and services.

Claims

We claim:

1. A method (500) for migrating at least one public mobile network (PLMN) in a network (106), the method (500) comprising: associating, by a processing engine (208), at least one new network repository function (NRF) with a network function set (NF set), wherein the NF set is associated with an existing NRF (316) that is configured to serve one or more PLMNs; synchronizing, by the processing engine (208), operational data corresponding to the NF set between the existing NRF (316) and the at least one new NRF (346) during a predefined transition period; based on the synchronization, generating, by the processing engine (208), a migration report indicating an operational status of the existing NRF (316) and the at least one new NRF (346); based on the generated report, executing, by the processing engine (208), a migration cutoff command; and upon execution, migrating, by the processing engine (208), the at least one PLMN to the at least one new NRF (346).

2. The method (500) as claimed in claim 1, wherein at least one PLMN is selected from the one or more PLMNs that are previously associated with the existing NRF (316), wherein the selection is performed based on a predefined configuration specified by a network operator.

3. The method (500) as claimed in claim 1, wherein upon execution of the migration cutoff command, the method (500) comprising: terminating, by the processing engine (208), the synchronization of the operational data between the existing NRF (316) and the at least one new NRF (346);reallocating, by the processing engine (208), at least one NF from the NF set that is associated with the migrated at least one PLMN to the at least one new NRF (346); enabling, by the processing engine (208) (208), one or more operations of the at least one new NRF (346) with the reallocated at least one NF.

4. The method (500) as claimed in claim 2, wherein the one or more operations comprise: registration handling of the at least one NF, service discovery operations of the at least one NF, and subscription management of the at least one NF corresponding to the migrated at least one PLMN.

5. The method (500) as claimed in claim 1 , wherein the operational status is at least one of: a registration status, a service availability status, and an update or modification status, corresponding to synchronization of the operational data between the existing NRF (316) and the at least one new NRF (346).

6. The method (500) as claimed in claim 1, wherein the operational data comprises one or more parameters, the one or more parameters include at least one of: an NF instance ID, an NF profile, subscription information, an access token, an authorization policy, and service discovery information.

7. The method (500) as claimed in claim 1, wherein, based on the generated report, the method (500) comprising: determining, by the processing engine (208), whether a variation is present between the synchronized operational data of the at least one new NRF (346) and the operational data of the existing NRF (316); and based on the determination, performing, by the processing engine (208), one or more actions across the existing and the at least one new NRF (346).

8. The method (500) as claimed in claim 6, wherein the one or more actions comprising one of: validating, by the processing engine (208), a successful migration of the at least one PLMN; or performing, by the processing engine (208), a rollback operation with the existing NRF (316) and the at least one new NRF (346).

9. A system (108) for migrating at least one public mobile network (PLMN) in a network, the system (108) comprising: a processing engine (208); and a memory coupled to the processing engine (208), wherein the processing engine (208) is configured to: associate at least one new network repository function (NRF) with a network function set (NF set), wherein the NF set is associated with an existing NRF (316), that is configured to serve one or more PLMNs. synchronize operational data corresponding to the NF set between the existing NRF (316) and the at least one new NRF (346) during a predefined transition period; generate a migration report indicating an operational status of the existing NRF (316) and the at least one new NRF (346) based on the synchronization; execute a migration cutoff command based on the generated report; and upon execution, migrate the at least one PLMN to the at least one new NRF (346).

10. The system (108) as claimed in claim 9, wherein at least one PLMN is selected from the one or more PLMNs that are previously associated with the existingNRF (316), wherein the selection is performed based on a predefined configuration specified by a network operator.

11. The system (108) as claimed in claim 9, wherein upon execution of the migration cutoff command, the processing engine (208) is configured to: terminate the synchronization of the operational data between the existing NRF (316) and the at least one new NRF (346); reallocate at least one NF from the NF set that is associated with the migrated at least one PLMN to the at least one new NRF (346); enable one or more operations of the at least one new NRF (346) with the reallocated at least one NF.

12. The system (108) as claimed in claim 11, wherein the one or more operations comprise: registration handling of the at least one NF, service discovery operations of the at least one NF, and subscription management of the at least one NF corresponding to the migrated at least one PLMN.

13. The system (108) as claimed in claim 9, wherein the operational status is at least one of: a registration status, a service availability status, and an update or modification status, corresponding to synchronization of the operational data between the existing NRF (316) and the at least one new NRF (346).

14. The system (108) as claimed in claim 9, wherein the operational data comprises one or more parameters, the one or more parameters include at least one of: an NF instance ID, an NF profile, subscription information, an access token, an authorization policy, and service discovery information.

15. The system (108) as claimed in claim 9, wherein, based on the generated report, the processing engine (208) is configured to:determine whether a variation is present between the synchronized operational data of the at least one new NRF (346) and the operational data of the existing NRF (316); and based on the determination, perform one or more actions the existing and the at least one new NRF (346).

16. The system (108) as claimed in claim 9, wherein the one or more actions comprise one of: validating, by the processing engine (208), a successful migration of the at least one PLMN; or performing, by the processing engine (208), a rollback operation between the existing NRF (316) and the at least one new NRF (346).

17. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (500) for migrating at least one public mobile network (PLMN) in a network, the method (500) comprising: associating, by the processing engine (208), at least one new network repository function (NRF) with a network function set (NF set), wherein the NF set is associated with an existing NRF (316) that is configured to serve one or more PLMNs. synchronizing, by the processing engine (208), operational data corresponding to the NF set between the existing NRF (316) and the at least one new NRF (346) during a predefined transition period; based on the synchronization, generating, by the processing engine (208), a migration report indicating an operational status of the existing NRF (316) and the at least one new NRF (346);based on the generated report, executing, by the processing engine (208), a migration cutoff command; and upon execution, migrating, by the processing engine (208), the at least one PLMN to the at least one new NRF (346).

Images