DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR ASSIGNING A NETWORK INSTANCE NAME
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN OFFICE-101, SAFFRON, NR. CENTRE POINT, PANCHWATI 5 RASTA, AMBAWADI, AHMEDABAD 380006, GUJARAT, INDIA
3.PREAMBLE TO THE DESCRIPTION

THE FOLLOWING SPECIFICATION PARTICULARLY DESCRIBES THE NATURE OF THIS INVENTION AND THE MANNER IN WHICH IT IS TO BE PERFORMED.

FIELD OF THE INVENTION
[0001] The present invention generally relates to wireless communication networks, and more particularly relates to a method and system for assigning a network instance name.
BACKGROUND OF THE INVENTION
[0002] Traditionally, there are a number of network elements present in a network at different locations. Each of the network elements may include a cluster host and an instance name. The instance name is particular with respect to a server on which it is running. The system takes the instance name as a random number, that is known as a Universal Unique Identifier (UU ID). The UU ID is of 30-40 digits and unable to be understood. To that understanding, a user may not be able to understand the instance name and may not be able to determine which network function the instance name belongs to.
[0003] Furthermore, during a network troubleshooting, it may become a time-consuming task without knowing about the instance name as it is tough to determine which instance name belongs to which network function. To this understanding, a machine generated network instance name is not recognized with ease and is not easily understandable and familiar to the users.
[0004] Currently the names of the network instances are generated by the system. These are machine generated network instance names having several digits/fields and not so convenient for user as disclosed above. There are several users accessing the system interfaces. Since there are thousands of network instances, it is very challenging for the end users to identify and remember the name of each network instance by these machine names.
[0005] Therefore, there is a need for an advancement of a system and method that can overcome at least one of the above shortcomings, particularly to assign the network instance name.

BRIEF SUMMARY OF THE INVENTION
[0006] One or more embodiments of the present disclosure provide a method and system for assigning a network instance name.
[0007] In one aspect of the present invention, the method for assigning a network instance name is disclosed. The method includes the step of receiving, by a processor, a request for assigning a user defined network instance name corresponding to a machine generated network instance name. The method includes the step of mapping, by the processor, the machine generated network instance name to the user defined network instance name. The method includes the step of replacing, by the processor, the machine generated network instance name with the user defined network instance name.
[0008] In one embodiment, the machine generated network instance name indicating a name of a network instance of a network slice.
[0009] In another embodiment, the step of validating, by the processor, the machine generated network instance name with the user defined network instance name.
[0010] In yet another embodiment, storing, by the processor, meta data corresponding to the replacement of the machine generated network instance name with the user defined network instance name in a database.
[0011] In yet another embodiment, the request for assigning the user defined network instance name is received corresponding to the machine generated network instance name.
[0012] In another aspect of the present invention, the system for assigning a network instance name is disclosed. The system includes a receiving unit configured to receive a request for assigning a user defined network instance name corresponding to a machine generated network instance name. The system includes a mapping unit configured to map the machine generated network instance name to the user defined network instance name. The system includes a replacing unit configured to replace the machine generated network instance name with the user defined network instance name.
[0013] In another aspect of the present invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions that, when executed by a processor is disclosed. The processor is configured to receive a request for assigning a user defined network instance name corresponding to a machine generated network instance name. The machine generated network instance name including a Universal Unique Identifier (UU ID) generated using random numbers. The machine generated network instance name indicating a name of a network instance of a network slice. The processor is configured to map the machine generated network instance name to the user defined network instance name. The processor is configured to replace the machine generated network instance name with the user defined network instance name.
[0014] Other features and aspects of this invention will be apparent from the following description and the accompanying drawings. The features and advantages described in this summary and in the following detailed description are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the relevant art, in view of the drawings, specification, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS
[0015] 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.
[0016] FIG. 1 is an exemplary block diagram of an environment for assigning a network instance name, according to one or more embodiments of the present disclosure;
[0017] FIG. 2 is an exemplary block diagram of a system for assigning the network instance name, according to one or more embodiments of the present disclosure;
[0018] FIG. 3 is a schematic representation of workflow of the system of FIG. 2, according to one or more embodiments of the present disclosure; and
[0019] FIG. 4 is a flow diagram illustrating a method for assigning the network instance name, according to one or more embodiments of the present disclosure.
[0020] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0021] Some embodiments of the present disclosure, illustrating all its features, will now be discussed in detail. It must also be noted that as used herein and in the appended claims, the singular forms "a", "an" and "the" include plural references unless the context clearly dictates otherwise.
[0022] Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure including the definitions listed here below are not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
[0023] A person of ordinary skill in the art will readily ascertain that the illustrated steps detailed in the figures and here below are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0024] Various embodiments of the invention provide a method for assigning a network instance name. The method disclosed in the present invention may be configured to support provisioning and assignment of a number of user-defined names for each network instance. The provisioning and assignment may be supported at an individual user level for each network instance. Furthermore, according to the present invention, for a same network instance, any user can be able to assign any name as per a user choice and based on which the name may be visible differently to each user at a same time.
[0025] In an embodiment, a network instance display name may be a string to be displayed for a network instance name. By default, the network instance display name is referred as the network instance name. In an embodiment, where it is determined that some other text needs to be displayed presumably more user-readable, an option to override the default value with a new value is present.
[0026] FIG. 1 illustrates an exemplary block diagram of an environment 100 for assigning a network instance name, according to one or more embodiments of the present disclosure. The environment 100 includes the network 105, a User Equipment (UE) 110, a server 115, and a system 120. The UE 110 aids a user to interact with the system 120 for assigning the network instance name. The network instance name is particular with respect to the server 115 on which it is running.
[0027] For the purpose of description and explanation, the description will be explained with respect to one or more UEs 110, or to be more specific will be explained with respect to a first UE 110a, a second UE 110b, and a third UE 110c, and should nowhere be construed as limiting the scope of the present disclosure. Each of the at least one UE 110 from the first UE 110a, the second UE 110b, and the third UE 110c is configured to connect to the server 115 via the network 105.
[0028] In an embodiment, each of the first UE 110a, the second UE 110b, and the third UE 110c is one of, but not limited to, any electrical, electronic, electro-mechanical or an equipment and a combination of one or more of the above devices such as smartphones, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.
[0029] The network 105 includes, by way of example but not limitation, one or more of a wireless network, a wired network, 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. The network 105 may include, but is not limited to, a Third Generation (3G), a Fourth Generation (4G), a Fifth Generation (5G), a Sixth Generation (6G), a New Radio (NR), a Narrow Band Internet of Things (NB-IoT), an Open Radio Access Network (O-RAN), and the like.
[0030] The network 105 may also include, 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. The network 105 may also include, by way of example but not limitation, one or more of a wireless network, a wired network, 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, a VOIP or some combination thereof.
[0031] The environment 100 includes the server 115 accessible via the network 105. The server 115 may include by way of example but not limitation, one or more of a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a part of a cloud service or system, a home server, hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof. In an embodiment, the entity may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business enterprise side, a defense facility side, or any other facility that provides service.
[0032] The environment 100 further includes the system 120 communicably coupled to the server 115 and each of the first UE 110a, the second UE 110b, and the third UE 110c via the network 105. The system 120 is adapted to be embedded within the server 115 or is embedded as the individual entity. However, for the purpose of description, the system 120 is described as an integral part of the server 115, without deviating from the scope of the present disclosure.
[0033] The system 120 is further configured to employ Transmission Control Protocol (TCP) connection to identify any connection loss in the network 105 and thereby improving overall efficiency. The TCP connection is a communication standard enabling applications and the system 120 to exchange information over the network 105.
[0034] Operational and construction features of the system 120 will be explained in detail with respect to the following figures.
[0035] FIG. 2 illustrates an exemplary block diagram of the system 120 for assigning the network instance name, according to one or more embodiments of the present disclosure. The system 120 includes one or more processors 205, a memory 210, a user interface 215, and a database 235. The one or more processors 205, hereinafter referred to as the processor 205 may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, single board computers, and/or any devices that manipulate signals based on operational instructions. As per the illustrated embodiment, the system 120 includes one processor 205. However, it is to be noted that the system 120 may include multiple processors as per the requirement and without deviating from the scope of the present disclosure.
[0036] Among other capabilities, the processor 205 is configured to fetch and execute computer-readable instructions stored in the memory 210. The memory 210 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 210 may include any non-transitory storage device including, for example, volatile memory such as RAM, or non-volatile memory such as EPROMs, FLASH memory, unalterable memory, and the like.
[0037] The user interface 215 includes a variety of interfaces, for example, interfaces for a Graphical User Interface (GUI), a web user interface, a Command Line Interface (CLI), and the like. The user interface 215 facilitates communication of the system 120. In one embodiment, the user interface 215 provides a communication pathway for one or more components of the system 120. Examples of the one or more components include, but are not limited to, the UE 110 and the database 235.
[0038] The database 235 is one of, but is not limited to, one of a centralized database, a cloud-based database, a commercial database, an open-source database, a distributed database, an end-user database, a graphical database, a No-Structured Query Language (NoSQL) database, an object-oriented database, a personal database, an in-memory database, a document-based database, a time series database, a wide column database, a key value database, a search database, a cache databases, and so forth. The foregoing examples of database types are non-limiting and may not be mutually exclusive e.g., a database can be both commercial and cloud-based, or both relational and open-source, etc.
[0039] Further, the processor 205, in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 205. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 205 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for processor 205 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 210 may store instructions that, when executed by the processing resource, implement the processor 205. In such examples, the system 120 may comprise the memory 210 storing the instructions and the processing resource to execute the instructions, or the memory 210 may be separate but accessible to the system 120 and the processing resource. In other examples, the processor 205 may be implemented by electronic circuitry.
[0040] In order for the system 120 to assign the network instance name, the processor 205 includes a receiving unit 220, a mapping unit 225, and a replacing unit 230 communicably coupled to each other for assigning the network instance name.
[0041] The receiving unit 220, the mapping unit 225, and the replacing unit 230 in an embodiment, may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processor 205. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processor 205 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processor may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the memory 210 may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system 120 may comprise the memory 210 storing the instructions and the processing resource to execute the instructions, or the memory 210 may be separate but accessible to the system 120 and the processing resource. In other examples, the processor 205 may be implemented by electronic circuitry.
[0042] The receiving unit 220 is configured to receive a request for assigning a user defined network instance name corresponding to a machine generated network instance name. In an embodiment, the machine generated network instance name including a Universal Unique Identifier (UU ID) generated using random numbers. The UU ID provides a unique and unpredictable identifier for each network instance, enhancing the security and reliability of a network management system. Let us consider for example, the machine generated network instance name (UUID) is f47ac10b-58cc-4372-a567-0e02b2c3d479, and the user defined network instance name is “production server1”.
[0043] In another embodiment, the machine generated network instance name indicates a name of a network instance of a network slice. The machine generated network instance name aids in identifying and managing different network slices effectively within a network management system.
[0044] Upon receiving the request for assigning the user defined network instance name corresponding to the machine generated network instance name, the mapping unit 225 is configured to map the machine generated network instance name to the user defined network instance name. Upon mapping, further the mapping unit 225 is configured to validate the machine generated network instance name with the user defined network instance name. The mapping unit 225 is configured to validate if the machine generated network instance name matches with the user defined network instance name by using pattern matching techniques to ensure that the names follow a specific format. Let’s consider for an example, the mapping unit 225 receives the machine generated network instance name "inst-123" and the user defined network instance name "web-server-01". The mapping unit 225 is configured to validate an exact match or a defined pattern match. The mapping unit 225 checks that the machine generated network instance name "inst-123" corresponds to the user defined network instance name "web-server-01". Upon successful validation, the mapping is confirmed, logged, and integrated into the network management system. Further, the mapping unit 225 is configured to validate that the "inst-123" can be correctly mapped to the "web-server-01" by cross-referencing with the database 235.
[0045] Further, the mapping unit 225 is configured to store metadata corresponding to the replacement of the machine generated network instance name with the user defined network instance name in the database 235. The metadata includes details about the mapping between the machine generated network instance name and the user defined network instance name. The metadata can include the original machine generated network instance name, the corresponding user defined network instance name, the timestamp of the mapping, and any other relevant information. The metadata is stored in the database 235 which allows the system 120 to track and manage the association between the machine generated network instance name and the user defined network instance name, facilitating efficient network management and retrieval.
[0046] Upon storing the metadata corresponding to the replacement of the machine generated network instance name with the user defined network instance name, the replacing unit 230 is configured to replace the machine generated network instance name with the user defined network instance name without impacting functioning of network components. The replacing unit 230 is configured to identify the network instances where the machine generated network instance name needs to be replaced with the user defined network instance name.
[0047] Using the metadata, the replacing unit 230 is configured to substitute the machine generated network instance name with the corresponding user defined network instance name in relevant areas within the network components, such as configurations, references, or data structures. The machine generated network instance name is replaced with the user defined network instance name in configurations and references. Let’s consider for an example, original configuration is "Connect to f47ac10b-58cc-4372-a567-0e02b2c3d479" and updated configuration is "Connect to ProductionServer1".
[0048] The replacing unit 230 ensures that the replacement does not impact the functioning of the network components by validating the changes made. Once validated, the replacing unit 230 is configured to confirm that the replacement has been completed successfully. Let’s consider for an example, "f47ac10b-58cc-4372-a567-0e02b2c3d479" replaced with the "ProductionServer1" without impacting the network functionality. By doing so, the system 120 ensures that network operations continue smoothly while allowing for user-friendly and easily identifiable network instance names and process the replacement function seamlessly without causing any disruptions to the network operations.
[0049] FIG. 3 is a schematic representation of workflow of the system of FIG. 2, according to one or more embodiments of the present disclosure. Referring to FIG. 3, describes the system 120 for assigning the network instance name.
[0050] At 302, the receiving unit 220 is configured to receive the request for assigning the user defined network instance name corresponding to the machine generated network instance name. In an embodiment, the machine generated network instance name including the UU ID generated using random numbers. The UU ID provides the unique and unpredictable identifier for each network instance, enhancing the security and reliability of the network management system. In another embodiment, the machine generated network instance name indicates the name of the network instance of the network slice. The machine generated network instance name aids in identifying and managing different network slices effectively within the network management system.
[0051] At 304, upon receiving the request for assigning the user defined network instance name corresponding to the machine generated network instance name, the mapping unit 225 is configured to map the machine generated network instance name to the user defined network instance name. Upon mapping, further the mapping unit 225 is configured to validate the machine generated network instance name with the user defined network instance name.
[0052] At 306, the mapping unit 225 is configured to store the metadata corresponding to the replacement of the machine generated network instance name with the user defined network instance name in the database 235. The metadata includes details about the mapping between the machine generated network instance name and the user defined network instance name. The metadata can include the original machine generated network instance name, the corresponding user defined network instance name, the timestamp of the mapping, and any other relevant information. The metadata is stored in the database 235 which allows the system 120 to track and manage the association between the machine generated network instance name and the user defined network instance name, facilitating efficient network management and retrieval.
[0053] At 308, Upon storing the metadata corresponding to the replacement of the machine generated network instance name with the user defined network instance name, the replacing unit 230 is configured to replace the machine generated network instance name with the user defined network instance name without impacting functioning of network components.
[0054] FIG. 4 is a flow diagram illustrating a method 400 for assigning the network instance name, according to one or more embodiments of the present disclosure. For the purpose of description, the method 400 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0055] At step 405, the method 400 includes the step of receiving the request for assigning the user defined network instance name corresponding to the machine generated network instance name by the receiving unit 220. In an embodiment, the machine generated network instance name including the UU ID generated using random numbers. The UU ID provides a unique and unpredictable identifier for each network instance, enhancing the security and reliability of the network management system.
[0056] At step 410, the method 400 includes the step of mapping the machine generated network instance name to the user defined network instance name by the mapping unit 225. Upon mapping, further the mapping unit 225 is configured to validate the machine generated network instance name with the user defined network instance name.
[0057] As per one embodiment, the mapping unit 225 is configured to store metadata corresponding to the replacement of the machine generated network instance name with the user defined network instance name in the database 235. The metadata includes details about the mapping between the machine generated network instance name and the user defined network instance name. The metadata can include the original machine generated network instance name, the corresponding user defined network instance name, the timestamp of the mapping, and any other relevant information. The metadata is stored in the database 235 which allows the system 120 to track and manage the association between the machine generated network instance name and the user defined network instance name, facilitating efficient network management and retrieval.
[0058] At step 415, the method 400 includes the step of replacing the machine generated network instance name with the user defined network instance name without impacting functioning of network components by the replacing unit 230. The replacing unit 230 is configured to identify the network instances where the machine generated network instance name needs to be replaced with the user defined network instance name.
[0059] Using the metadata, the replacing unit 230 is configured to substitute the machine generated network instance name with the corresponding user defined network instance name in relevant areas within the network components, such as configurations, references, or data structures. The machine generated network instance name is replaced with the user defined network instance name in configurations and references.
[0060] The replacing unit 230 ensures that the replacement does not impact the functioning of the network components by validating the changes made. Once validated, the replacing unit 230 is configured to confirm that the replacement has been completed successfully. By doing so, the method 400 ensures that network operations continue smoothly while allowing for user-friendly and easily identifiable network instance names and process the replacement function seamlessly without causing any disruptions to the network operations.
[0061] The present invention discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by a processor 205 is disclosed. The processor 205 is configured to receive a request for assigning a user defined network instance name corresponding to a machine generated network instance name, the machine generated network instance name comprising a Universal Unique Identifier (UU ID) generated using random numbers, the machine generated network instance name indicating a name of a network instance of a network slice. The processor 205 is configured to map the machine generated network instance name to the user defined network instance name. The processor 205 is configured to replace the machine generated network instance name with the user defined network instance name.
[0062] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-4) are set out to explain the exemplary embodiments shown, and it should be anticipated that ongoing technological development will change the manner in which particular functions are performed. These examples are presented herein for purposes of illustration, and not limitation. Further, the boundaries of the functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternative boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc., of those described herein) will be apparent to persons skilled in the relevant art(s) based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.
[0063] The present disclosure incorporates technical advancement of assigning the network instance name for each network instance at the individual user level. With this, for the same network instance, any user can assign any name to the network instance and hence it will be seen differently to all users at the same time. By doing so, the present disclosure ensures that network operations continue smoothly while allowing for user-friendly and easily identifiable network instance names and process the replacement function seamlessly without causing any disruptions to the network operations.
[0064] The present invention offers multiple advantages over the prior art and the above listed are a few examples to emphasize on some of the advantageous features. The listed advantages are to be read in a non-limiting manner.

REFERECE NUMERALS
[0065] Environment - 100;
[0066] Network - 105;
[0067] User Equipment - 110;
[0068] Server - 115;
[0069] System - 120;
[0070] Processor -205;
[0071] Memory – 210;
[0072] User Interface – 215;
[0073] Receiving unit - 220;
[0074] Mapping unit- 225;
[0075] Replacing unit- 230;
[0076] Database- 235.
,CLAIMS:CLAIMS
We Claim:
1. A method (400) of assigning a network instance name, the method (400) comprising the steps of:
receiving (405), by a processor (205), a request for assigning a user defined network instance name corresponding to a machine generated network instance name;
mapping (410), by the processor (205), the machine generated network instance name to the user defined network instance name; and
replacing (425), by the processor (205), the machine generated network instance name with the user defined network instance name.

2. The method (400) as claimed in claim 1, the machine generated network instance name indicating a name of a network instance of a network slice.

3. The method (400) as claimed in claim 1, comprising validating, by the processor, the machine generated network instance name with the user defined network instance name.

4. The method (400) as claimed in claim 1, comprising storing, by the processor, meta data corresponding to the replacement of the machine generated network instance name with the user defined network instance name in a database (235).

5. A system (120) for assigning a network instance name, the system (120) comprising:
a receiving unit (220) configured to receive a request for assigning a user defined network instance name corresponding to a machine generated network instance name;
a mapping unit (225) configured to map the machine generated network instance name to the user defined network instance name; and
a replacing unit (230) configured to replace the machine generated network instance name with the user defined network instance name.

6. The system (120) as claimed in claim 6, wherein the machine generated network instance name indicating a name of a network instance of a network slice.

7. The system (120) as claimed in claim 6, wherein the mapping unit (225) is configured to validate the machine generated network instance name with the user defined network instance name.

8. The system (120) as claimed in claim 6, wherein the mapping unit (225) is configured to instruct to store the meta data corresponding to the replacement of the machine generated network instance name with the user defined network instance name in a database (235).