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 UPLOADING ONE OR MORE IMAGE FILES IN A REGISTRY
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 relates to data storage, more particularly relates to a method and a system for uploading one or more image files in a registry.
BACKGROUND OF THE INVENTION
[0002] Generally, now days, data storage has become a major concern across the globe, since for storing large amounts of data, data storage facilities and equipment are required, which requires a substantial amount of investment. Further, data owners while storing the data in storage means are also concerned about how secure the data will be stored at these storage means.
[0003] In order to mitigate investments in storage facilities and equipment, data owners (herein referred to as ‘third-party vendors’) may seek assistance from data storage service providers to store data at a registry. With respect to storing data of images, images which are uploaded at a registry or repository are generally a Containerized Network Function (CNF) image. The CNF image is a file used to execute code in a container. The images act as a set of instructions to build a container, like a template. The registry or repository may also store data of the service providers. In general, a CNF is a service that performs network duties in software as opposed to purpose-built hardware. Examples of CNFs may be at least one of, but not limited to, network functions, network routers, bridges, firewalls, and virtual private network (VPN) gateway services.
[0004] In response to a request by the third-party vendor, the service provider generally provides access to the third-party vendor to upload files at the registry or repository. By providing access to the registry, the service provider by default may also provide access to data of the service provider itself or data of any other third party other than the current vendor. This may lead to security breach or data leakage. Further, the process of uploading the images to the registry of the service provider is time consuming since the images are uploaded in their original size without compressing or carrying out any operation that may reduce the size of the images, due to which the efficiency is reduced and further leads to over utilization of the memory in the registry.
[0005] In view of the above, there is a dire need for a system and method for uploading images from CNF of multiple formats in a registry, which ensures that time consumed for uploading is substantially reduced and confidentiality of data is not breached.
SUMMARY OF THE INVENTION
[0006] One or more embodiments of the present disclosure provide a method and system for uploading one or more image files in a registry.
[0007] In one aspect of the present invention, the system for uploading the one or more images in the registry is disclosed. The system includes a receiving unit configured to receive a request to upload one or more image files from a User Equipment (UE). The system further includes a checking unit configured to check for information pertaining to the one or more image files at a database. The system further includes an uploading unit configured to upload the received one or more image files at a registry, if the information pertaining to the one or more image files are not available in the database. The system further includes a transmitting unit configured to transmit a notification to the UE, when the information pertaining to the one or more image files are available in the database.
[0008] In an embodiment, the one or more image files corresponds to Containerized Network Functions (CNF).
[0009] In an embodiment, the one or more image files are uploaded in the registry in the one or more formats including at least one of, a Tape Archive (TAR), an ISO format and a ZIP.
[0010] In an embodiment, the information pertaining to the one or more image files includes, at least one of, file name, file format, file size, version, location-path, and upload timestamp.
[0011] In an embodiment, upon uploading the received one or more image files at the registry, the transmitting unit, configured to transmit, the information pertaining to the one or more image files to a secondary repository.
[0012] In an embodiment, the secondary repository includes a Release Management Repository (RMR).
[0013] In an embodiment, the receiving unit, configured to receive a response from the secondary registry, on receiving the information pertaining to the one or more image files.
[0014] In an embodiment, the system comprises a deleting unit, configured to delete, the one or more image files from the UE on uploading the received one or more image files at the registry.
[0015] In another aspect of the present invention, the method for uploading the one or more image files in the registry is disclosed. The method includes the step of receiving a request to upload one or more image files from a User Equipment (UE). The method further includes the step of checking for information pertaining to the one or more image files at a database. The method further includes the step of uploading, the received one or more image files at a registry, if the information pertaining to the one or more image files are not available in the database. The method further includes the step of transmitting a notification to the UE, when the information pertaining to the one or more image files are available in the database.
[0016] In another aspect of the invention, a non-transitory computer-readable medium having stored thereon computer-readable instructions is disclosed. The computer-readable instructions are executed by a processor. The processor is configured to receive, a request to upload one or more image files from a User Equipment (UE). The processor is configured to check, for information pertaining to the one or more image files at a database. The processor is configured to upload, the received one or more image files at a registry, if the information pertaining to the one or more image files are not available in the database. The processor is configured to transmit, a notification to the UE, when the information pertaining to the one or more image files are available in the database.
[0017] In another aspect of invention, a User Equipment (UE) is disclosed. The UE includes one or more primary processors communicatively coupled to one or more processors, the one or more primary processors coupled with a memory. The processor causes the UE to transmit a request to the one or more processors to upload one or more image files at a registry and receive, and receives a notification when the information pertaining to the one or more image files are available in the database.
[0018] 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
[0019] 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.
[0020] FIG. 1 is an exemplary block diagram of an environment for uploading one or more image files in a registry, according to one or more embodiments of the present invention;
[0021] FIG. 2 is an exemplary block diagram of a system for uploading the one or more image files in the registry, according to one or more embodiments of the present invention;
[0022] FIG. 3 is a schematic representation of a workflow of the system of FIG. 1, according to the one or more embodiments of the present invention;
[0023] FIG. 4 is an exemplary block diagram of an architecture implemented in the system of the FIG. 2, according to one or more embodiments of the present invention;
[0024] FIG. 5 is a signal flow diagram for uploading the one or more image files in the registry, according to one or more embodiments of the present invention; and
[0025] FIG. 6 is a schematic representation of a method for uploading the one or more image files in the registry, according to one or more embodiments of the present invention.
[0026] The foregoing shall be more apparent from the following detailed description of the invention.
DETAILED DESCRIPTION OF THE INVENTION
[0027] 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.
[0028] 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.
[0029] 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.
[0030] The present invention is able to ensure that a registry of a service provider is not exposed to a third-party vendor. Disclosed system and method is aimed at enhancing efficiency of the service provider and third-party vendor relationship by ensuring that the images uploaded by the third-party vendor at the registry may be of any format. In other words, the present invention provides a unique approach of supporting different types of images formats so that the third-party vendor may upload the images thereby substantially reducing time.
[0031] FIG. 1 illustrates an exemplary block diagram of an environment 100 for uploading one or more image files in a registry, according to one or more embodiments of the present disclosure. In this regard, the environment 100 includes a User Equipment (UE) 102, a server 104, a network 106 and a system 108 communicably coupled to each other for uploading the one or more image files in the registry 220 (shown in FIG. 2). The registry 220 refers to a secure, user-defined repository used for storing and managing image files, such as container images. The container images are lightweight, standalone, executable packages that include everything needed to run a piece of software, including the code, runtime, libraries, environment variables, and configuration files.
[0032] As per the illustrated embodiment and for the purpose of description and illustration, the UE 102 is one of, but is not limited to, a first UE 102a, a second UE 102b, and a third UE 102c, and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the UE 102 may include a plurality of UEs as per the requirement. For ease of reference, each of the first UE 102a, the second UE 102b, and the third UE 102c, will hereinafter be collectively and individually referred to as the “User Equipment (UE) 102”.
[0033] In an embodiment, the UE 102 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 a 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 computing device.
[0034] The environment 100 includes the server 104 accessible via the network 106. The server 104 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.
[0035] The network 106 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 106 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.
[0036] The network 106 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 106 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.
[0037] The environment 100 further includes the system 108 communicably coupled to the server 104 and the UE 102 via the network 106. The system 108 is configured to upload the one or more image files in the registry 220. As per one or more embodiments, the system 108 is adapted to be embedded within the server 104 or embedded as an individual entity.
[0038] Operational and construction features of the system 108 will be explained in detail with respect to the following figures.
[0039] FIG. 2 is an exemplary block diagram of the system 108 for uploading the one or more image files in the registry 220, according to one or more embodiments of the present invention.
[0040] As per the illustrated embodiment, the system 108 includes one or more processors 202, a memory 204, a user interface 206, and a database 208. Further, the system 108 is communicably coupled with the registry 220 and a secondary repository 222. For the purpose of description and explanation, the description will be explained with respect to one processor 202 and should nowhere be construed as limiting the scope of the present disclosure. In alternate embodiments, the system 108 may include more than one processor 202 as per the requirement of the network 106. The one or more processors 202, hereinafter referred to as the processor 202 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.
[0041] As per the illustrated embodiment, the processor 202 is configured to fetch and execute computer-readable instructions stored in the memory 204. 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 RAM, or non-volatile memory such as disk memory, EPROMs, FLASH memory, unalterable memory, and the like.
[0042] In an embodiment, the user interface 206 includes a variety of interfaces, for example, interfaces for a graphical user interface, a web user interface, a Command Line Interface (CLI), and the like. The user interface 206 facilitates communication of the system 108. In one embodiment, the user interface 206 provides a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the UE 102 and the database 208.
[0043] The database 208 is one of, but not limited to, 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 208 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.
[0044] In order for the system 108 to upload the one or more image files in the registry 220, the processor 202 includes one or more modules. In one embodiment, the one or more modules includes, but not limited to, a receiving unit 210, a checking unit 212, an uploading unit 214, a transmitting unit 216 and a deleting unit 218 communicably coupled to each other for uploading the one or more image files in the registry 220.
[0045] In one embodiment, each of the one or more modules, but not limited to, the receiving unit 210, the checking unit 212, the uploading unit 214, the transmitting unit 216 and the deleting unit 218 are used in combination or interchangeably for uploading the one or more image files in the registry 220.
[0046] The receiving unit 210, the checking unit 212, the uploading unit 214, the transmitting unit 216 and the deleting unit 218 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 202. 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 202 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 204 may store instructions that, when executed by the processing resource, implement the processor. In such examples, the system 108 may comprise the memory 204 storing the instructions and the processing resource to execute the instructions, or the memory 204 may be separate but accessible to the system 108 and the processing resource. In other examples, the processor 202 may be implemented by electronic circuitry.
[0047] In one embodiment, the receiving unit 210 is configured to receive a request from the UE 102. The request from the UE 102 is to upload the one or more files in a registry 220. The request includes, but is not limited to, identification information, file metadata, file data. The identification information includes the details of the UE 102 such as device ID, user credentials, or session tokens to authenticate the source of the request. The file metadata includes the information about the one or more image files intended for upload. The file data includes the one or more image files reference (e.g., file path) to the uploaded in the registry. In an embodiment, the registry 220 is a private repository 406 (as shown in FIG. 4). The private repository 406 is used for storing and managing container images, which can include containerized applications and services.
[0048] In an embodiment, the one or more image files corresponds to container images, which are executable packages that include everything needed to run a piece of software, such as code, runtime, system tools, libraries, and settings. The container image refers to a standalone, executable software package that includes everything needed to run an application. In another embodiment, the one or more image files corresponds to Containerized Network Functions (CNF). The CNF refers to network functions that are specifically designed and optimized to run in cloud environments using containerization technologies. The network functions refer to specific, modular tasks or operations that are essential for managing and facilitating network 106 communication and services. The network functions include, but are not limited to, routing, switching, firewalling, load balancing or network functions associated with 5G core network (5GCN). The containerization technologies refer to a set of tools and processes that package software applications and their dependencies into lightweight, portable containers. The containerization technologies include, but are not limited to, container engine, container orchestration, container registries, container build tools, container storage. In an embodiment, the one or more image files are compressed and uploaded in the registry 220 in the one or more formats. The one or more formats includes at least one of, a Tape Archive (TAR), an ISO format and a ZIP.
[0049] Upon receiving the request from the UE 102, the checking unit 212 is configured to check for information pertaining to the one or more image files at the database 208. In an embodiment, the database 208 is accessed by both the checking unit 212 and the secondary repository 222. The information pertaining to the one or more image file includes, but not limited to, file name, file format, file size, version, location-path, upload timestamp. In particular the checking unit 212 checks whether the information pertaining to the one or more image files is available or not at the database 208. In another embodiment, the checking unit 212 checks whether the information pertaining to the one or more image files is available or not at the database 208 by comparing the information pertaining to the one or more image files present at the database 208 with the information pertaining to the one or more image files received via request from the UE 102.
[0050] Upon checking by comparing the information pertaining to the one or more image files, if the information pertaining to the one or more image files received via request from the UE 102 is not available at the database 208, then the uploading unit 214 is configured to upload the received one or more image files at the registry 220.
[0051] Alternatively, upon checking by comparing the information pertaining to one or more image files, if the information pertaining to one or more image files received via request from the UE 102 is available at the database 208, then the transmitting unit 216 is configured to transmit a notification to the UE 102. The notification includes that the one or more image files are already present at the private repository 406.
[0052] In an embodiment, upon uploading the information pertaining to the one or more image files at the registry 220, the deleting unit 218 is configured to delete the one or more image files from the UE 102.
[0053] Upon uploading the received one or more image files to the registry 220, the transmitting unit 216 is configured to transmit the information pertaining to the one or more image files to the secondary repository 222. The secondary repository 222 includes a Release Management Repository (RMR) 404 (as shown in FIG. 4). The RMR 404 is the secondary repository 222 designed to manage and oversee the versions and histories of image files and related assets. The RMR 404 includes, but not limited to, version control, release tracking, spawning versions, metadata management.
[0054] In an embodiment, upon receiving the information pertaining to the one or more image files, the secondary repository 222 checks whether the information pertaining to the received one or more image files is available or not. More specifically, the secondary repository 222 checks whether the information pertaining to the received one or more image files is available or not at the database 208 by comparing the information pertaining to one or more image files present at the database 208 with the information pertaining to the received one or more image files.
[0055] Upon comparing the information pertaining to the received one or more image files, the receiving unit 210 is configured to receive a response from the secondary repository 222. The response includes the availability of the information pertaining to the received one or more image files at the database 224 of the secondary repository 222.
[0056] By doing so, the system 108 optimally utilizes the memory at the registry 220 by preventing duplication of one or more image files. Further, the system 108 prevents the registry 220 from security breaches by not providing the access to the registry 220 for the third-party vendors.
[0057] FIG. 3 describes a preferred embodiment of the system 108 of FIG. 2, according to various embodiments of the present invention. It is to be noted that the embodiment with respect to FIG. 3 will be explained with respect to the first UE 102a and the system 108 for the purpose of description and illustration and should nowhere be construed as limited to the scope of the present disclosure.
[0058] As mentioned earlier in FIG. 1, each of the first UE 102a, the second UE 102b, and the third UE 102c may include an external storage device, a bus, a main memory, a read-only memory, a mass storage device, communication port(s), and a processor. The exemplary embodiment as illustrated in FIG. 3 will be explained with respect to the first UE 102a without deviating from the scope of the present disclosure and the limiting the scope of the present disclosure. The first UE 102a includes one or more primary processors 302 communicably coupled to the one or more processors 202 of the system 108.
[0059] The one or more primary processors 302 are coupled with a memory 304 storing instructions which are executed by the one or more primary processors 302. Execution of the stored instructions by the one or more primary processors 302 enables the first UE 102a to transmit the request to the one or more processors 202 to upload one or more image files at the registry 220. Further, the first UE 102a receives the notification when the information pertaining to the one or more image files are available in the database 208.
[0060] As mentioned earlier in FIG. 2, the one or more processors 202 of the system 108 is configured for processing data in the network 106. As per the illustrated embodiment, the system 108 includes the one or more processors 202, the memory 204, the user interface 206, and the database 208. Further, the system 108 is communicably coupled with the registry 220 and the secondary repository 222. The operations and functions of the one or more processors 202, the memory 204, the user interface 206, and the database 208 are already explained in FIG. 2. For the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition.
[0061] Further, the processor 202 includes the receiving unit 210, the checking unit 212, the uploading unit 214, the transmitting unit 216 and the deleting unit 218. The operations and functions of the receiving unit 210, the checking unit 212, the uploading unit 214, the transmitting unit 216 and the deleting unit 218 are already explained in FIG. 2. Hence, for the sake of brevity, a similar description related to the working and operation of the system 108 as illustrated in FIG. 2 has been omitted to avoid repetition. The limited description provided for the system 108 in FIG. 3, should be read with the description as provided for the system 108 in the FIG. 2 above, and should not be construed as limiting the scope of the present disclosure.
[0062] FIG. 4 is an exemplary block diagram of an architecture 400 of the system 108 for uploading the images in the registry 220, according to one or more embodiments of the present invention.
[0063] The architecture 400 includes the User Interface (UI) 206, a container orchestrator 402, the Release Management Repository (RMR) 404 and the private repository 406.
[0064] In an embodiment, the container orchestrator 402 is an interface between the UI 206 and the registry 220. The interface is an Application programming interface (API). The container orchestrator 402 helps in uploading the one or more image files at the registry 220. In an embodiment, the container orchestrator 402 helps in transmitting the one or more image files information to the secondary repository 222. In an embodiment, the container orchestrator 402 can manage clusters, and establish containers at one or more network nodes. In an embodiment, the container orchestrator helps in transmitting the one or more image files information to the RMR 404.
[0065] The container orchestrator 402 receives the request from the UE 102 via UI 206. The request is to upload the one or more image files at the private repository 406. The one or more image files are uploaded in the one or more formats including at least one of, the Tape Archive (TAR), the ISO format and the ZIP. The one or more image files corresponds to Containerized Network Functions (CNF).
[0066] Upon receiving the request from the UE 102 via the UI 206, the container orchestrator 402 checks the information pertaining to the one or more image files at the database 208. In an embodiment the database 208 is accessed by both the container orchestrator 402 and the RMR 404. The information pertaining to the one or more image file includes, but not limited to, file name, file format, file size, version, location-path, upload timestamp. In particular the container orchestrator 402 checks whether the information pertaining to the one or more image files is available or not at the database 208. In an embodiment, the container orchestrator 402 checks whether the information pertaining to the one or more image files is available or not at the database 208 by comparing the information pertaining to the one or more image files present at the database 208 with the information pertaining to the one or more image files received via request from the UI 206.
[0067] Upon checking by comparing the information pertaining to the one or more image files, if the information pertaining to the one or more image files received via request from the UI 206 is not available at the database 208, then the container orchestrator 402 uploads the received one or more image files at the private repository 406.
[0068] Alternatively, upon checking by comparing the information pertaining to the one or more image files, if the information pertaining to the one or more image files received via request from the UI 206 is available at the database 208, then the container orchestrator 402 transmits a notification to the UE 102 via the UI 206. The notification includes that the one or more image files are already present at the private repository 406.
[0069] In an embodiment, upon uploading the information pertaining to the one or more image files at the private repository 406, the container orchestrator 402 deletes the one or more image files from the UE 102 via the UI 206.
[0070] Upon uploading the received one or more image files to the private repository 406, the container orchestrator 402 transmits the information pertaining to the one or more image files to the RMR 404
[0071] In an embodiment, upon receiving the information pertaining to the one or more image files from the container orchestrator 402, the RMR 404 checks whether the information pertaining to the received one or more image files is available or not. In particular, the RMR 404 checks whether the information pertaining to the one or more image files is available or not at the database 208 for comparing the information pertaining to the one or more image files present at the database 208 with the information pertaining to the received one or more image files.
[0072] Upon comparing the information pertaining to the received one or more image files, the RMR 404 transmits the response to the container orchestrator 402. The response includes the availability of the information pertaining to the received one or more image files at the database 208.
[0073] FIG. 5 is a signal flow diagram for uploading one or more image files in the registry 220, according to one or more embodiments of the present invention.
[0074] At step 502, the container orchestrator 402 receives the request from the UE 102 via the UI 206 to upload the one or more image files at the private repository 406. The one or more image files are uploaded in the one or more formats including at least one of, the Tape Archive (TAR), the ISO format and the ZIP. The one or more image files corresponds to Containerized Network Functions (CNF).
[0075] At step 504, upon receiving the request, the container orchestrator 402 checks for the information pertaining to the one or more image files at the database 208. In particular, the container orchestrator 402 checks for the information pertaining to the one or more image files available or not at the database 208. The information pertaining to the one or more image file includes, but not limited to, file name, file format, file size, version, location-path, upload timestamp.
[0076] At step 506, upon checking at the database 208, if the information pertaining to the one or more image files are not available in the database 208, the container orchestrator 402 uploads the received one or more image files at the private repository 406.
[0077] At step 508, upon checking at the database 208, if the information pertaining to the one or more image files are available in the database 208, the container orchestrator transmits the notification to the UE 102 via the UI 206. The notification includes that the one or more image files are already present at the private repository 406.
[0078] At step 510, upon uploading the received one or more image files at the private repository 406, the container orchestrator 402 deletes the one or more image files from the UE 102 via the UI 206.
[0079] At step 512, subsequently, upon uploading the received one or more image files at the private repository 406, the container orchestrator 402 transmits the information pertaining to the one or more image files to the RMR 404.
[0080] At step 514, in an embodiment, upon receiving the information pertaining to the one or more image files, the RMR 404 checks the availability of the information pertaining to the one or more image files received from the container orchestrator 402 at the database 208.
[0081] At step 516, upon checking at the database 208, the RMR 404 transmits the response to the container orchestrator 402. The response includes the availability of the information pertaining to the one or more image files received from the container orchestrator 402.
[0082] FIG. 6 is a flow diagram of a method 600 for uploading one or more image files in the registry 220, according to one or more embodiments of the present invention. For the purpose of description, the method 600 is described with the embodiments as illustrated in FIG. 2 and should nowhere be construed as limiting the scope of the present disclosure.
[0083] At step 602, the method 600 includes the step of receiving the request to upload the one or more image files from the UE 102 by the receiving unit 210. the one or more image files corresponds to containerized Network Functions (CNF). the one or more image files are uploaded in the registry in the one or more formats including at least one of, a Tape Archive (TAR), an ISO format and a ZIP.
[0084] At step 604, the method 600 includes the step of checking for information pertaining to the one or more image files at the database 208 by the checking unit 212. The information pertaining to the one or more image files includes, at least one of, file name, file format, file size, version, location-path, and upload timestamp.
[0085] At step 606, the method 600 includes the step of uploading the received one or more image files at a registry 220 by the uploading unit 214, if the information pertaining to the one or more image files are not available in the database 208. Upon uploading the received one or more image files at the registry 220, the deleting unit 218 deletes the one or more image files from the UE 102.
[0086] Subsequently, upon uploading the received one or more image files at the registry 220, the transmitting unit 216 is configured to transmit the information pertaining to the one or more image files to the secondary repository 222. The secondary repository includes the RMR 404. Thereafter, the receiving unit 210 is configured to receive the response from the secondary repository 222 on receiving the information pertaining to the one or more image files.
[0087] At step 608, the method 600 includes the step of transmitting the notification to the user when the information pertaining to the one or more image files are available at the database 208 by the transmitting unit 216
[0088] The present invention further discloses a non-transitory computer-readable medium having stored thereon computer-readable instructions. The computer-readable instructions are executed by the processor 202. The processor 202 is configured to receive the request to upload one or more image files from the UE 102. The processor 202 is further configured to check for the information pertaining to the one or more image files at the database 208. The processor 202 is further configured to upload the received one or more image files at the registry 220, if the information pertaining to the one or more image files are not available in the database 208. The processor 202 is further configured to transmit the notification to the UE 102, when the information pertaining to the one or more image files are available in the database 208.
[0089] A person of ordinary skill in the art will readily ascertain that the illustrated embodiments and steps in description and drawings (FIG.1-6) 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.
[0090] The present disclosure incorporates technical advancement of optimally utilizing the memory at the registry by preventing duplication of one or more image files. Further, the present invention prevents the registry from exposing to security breaches such as Distributed Denial of Service (DDOS) attack from external environment. Further, the different formats of the image files can be uploaded.
[0091] 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.

REFERENCE NUMERALS

[0092] Environment- 100
[0093] User Equipment (UE)- 102
[0094] Server- 104
[0095] Network- 106
[0096] System -108
[0097] Processor- 202
[0098] Memory- 204
[0099] User Interface- 206
[00100] Database- 208
[00101] Receiving Unit- 210
[00102] Checking Unit- 212
[00103] Uploading unit- 214
[00104] Transmitting Unit- 216
[00105] Deleting Unit-218
[00106] Registry- 220
[00107] Secondary Repository- 222
[00108] One or more primary processors- 302
[00109] Memory- 304
[00110] Container orchestrator- 402
[00111] RMR- 404
[00112] Private repository- 406
,CLAIMS:CLAIMS:
We Claim:

1. A method (600) for uploading one or more image files in a registry (220), the method (600) comprises the steps of:
receiving, by one or more processors (202), a request to upload one or more image files from a User Equipment (UE) (102);
checking, by the one or more processors (202), for information pertaining to the one or more image files at a database (208);
uploading, by the one or more processors (202), the received one or more image files at a registry (220), if the information pertaining to the one or more image files are not available in the database (208); and
transmitting, by the one or more processors (202), a notification to the UE (102), when the information pertaining to the one or more image files are available in the database (208).

2. The method (600) as claimed in claim 1, wherein the one or more image files corresponds to containerized Network Functions (CNF).

3. The method (600) as claimed in claim 1, wherein the one or more image files are uploaded in the registry in the one or more formats including at least one of, a Tape Archive (TAR), an ISO format and a ZIP.

4. The method (600) as claimed in claim 1, wherein the information pertaining to the one or more image files includes, at least one of, file name, file format, file size, version, location-path, and upload timestamp.

5. The method (600) as claimed in claim 1, upon uploading the received one or more image files at the registry, the method comprises the step of transmitting, by the one or more processors (202), the information pertaining to the one or more image files to a secondary repository (222).

6. The method (600) as claimed in claim 5, wherein the secondary repository (222) includes a Release Management Repository (RMR).

7. The method (600) as claimed in claim 5, wherein the method comprises the step of receiving, by the one or more processors (202), a response from the secondary repository (222) on receiving the information pertaining to the one or more image files.

8. The method (600) as claimed in claim 1, the method comprises the step of deleting, by the one or more processors (202), the one or more image files from the UE (102) on uploading the received one or more image files at the registry (220).

9. A system (108) for uploading one or more image files in a registry (220), the system (108) comprises:
receiving unit (210), configured to receive, a request to upload one or more image files from a User Equipment (UE) (102);
checking unit (212), configured to check, for information pertaining to the one or more image files at a database (208);
uploading unit (214), configured to upload, the received one or more image files at a registry (220), if the information pertaining to the one or more image files are not available in the database (208); and
transmitting unit (216), configured to transmit, a notification to the UE (102), when the information pertaining to the one or more image files are available in the database (208).

10. The system (108) as claimed in claim 9, wherein the one or more image files corresponds to containerized Network Functions (CNF).

11. The system (108) as claimed in claim 9, wherein the one or more image files are uploaded in the registry in the one or more formats including at least one of, a Tape Archive (TAR), an ISO format and a ZIP.

12. The system (108) as claimed in claim 9, wherein the information pertaining to the one or more image files includes, at least one of, file name, file format, file size, version, location-path, and upload timestamp.

13. The system (108) as claimed in claim 9, upon uploading the received one or more image files at the registry (220), the transmitting unit (216), configured to transmit, the information pertaining to the one or more image files to a secondary repository (222).

14. The system (108) as claimed in claim 13, wherein the secondary repository (222) includes a Release Management Repository (RMR) (404).

15. The system (108) as claimed in claim 13, wherein the receiving unit, configured to receive a response from the secondary repository (222), on receiving the information pertaining to the one or more image files.

16. The system (108) as claimed in claim 9, the system (108) comprises a deleting unit (218), configured to delete, the one or more image files from the UE (102) on uploading the received one or more image files at the registry (220).

17. A User Equipment (UE) (102), comprising:
one or more primary processors (302) communicatively coupled to one or more processors (202), the one or more primary processors (302) coupled with a memory (304), wherein said memory (304) stores instructions which when executed by the one or more primary processors (302) causes the UE (102) to:
transmit, a request to the one or more processors (202) to upload one or more image files at a registry (220), and
receive, a notification when the information pertaining to the one or more image files are available in the database (208),
wherein the one or more processors (202) is configured to perform the steps as claimed in claim 1.