Method and apparatus for generating JavaScript object notation configuration files and implementing network functions.

Abstract

The method includes processing a data file including one or more parameters for configuring a network function provided by a network device. The data file is processed to recognize and extract the one or more parameters included in the data file. The method also includes causing one or more of a plurality of parameter fields included in a graphical user interface to be filled with the one or more parameters extracted from the data file according to a mapping between the one or more parameters extracted from the data file and corresponding parameter fields included in the graphical user interface. The method further includes processing the parameters included in the parameter fields to generate a JavaScript Object Notation (JSON) configuration file. The method further includes causing the JSON configuration file to be transmitted to the network device to implement the network function according to the JSON configuration file.

Description

Technical Field

[0001] This disclosure relates to the generation of JavaScript Object Notation (JSON) configuration files sent to network devices to implement network functions.

Background Art

[0002] Network operators, network service providers, and device manufacturers (e.g., wireless, cellular, etc.) are constantly striving to provide consumers with value and convenience by offering attractive communication networks and network services that are, for example, reliable, flexibly constructed, scalable, diverse, and economically operable.

Summary of the Invention

Means for Solving the Problems

[0003] One aspect of this specification relates to a method, comprising a processor, for processing a data file containing one or more parameters for configuring network functions provided by a network device. The data file is processed to recognize and extract one or more parameters contained in the data file. The method also includes ensuring that one or more of a plurality of parameter fields in a graphical user interface are populated with one or more parameters extracted from the data file, according to a mapping between the extracted parameters and one or more corresponding parameter fields in the plurality of parameter fields in the graphical user interface. The method further includes processing the parameters contained in the parameter fields in the graphical user interface to generate a JavaScript Object Notation (JSON) configuration file. The method further includes ensuring that the JSON configuration file is sent to a network device in order to implement network functions according to the JSON configuration file.

[0004] Another aspect of this specification relates to an apparatus comprising a processor and memory storing instructions, when executed by the processor, that cause the apparatus to process a data file containing one or more parameters for configuring network functions provided by a network device. The data file is processed to recognize and extract one or more parameters contained in the data file. The apparatus is also made to populate one or more of a plurality of parameter fields in a graphical user interface with one or more parameters extracted from the data file, according to a mapping between one or more parameters extracted from the data file and one or more corresponding parameter fields in the plurality of parameter fields in the graphical user interface. The apparatus is further made to process the parameters contained in the parameter fields in the graphical user interface in order to generate a JavaScript Object Notation (JSON) configuration file. The apparatus is further made to send the JSON configuration file to a network device in order to implement network functions according to the JSON configuration file.

[0005] Another aspect of this specification relates to a non-temporary, computer-readable file containing instructions, when executed by a processor, that cause a device to process a data file containing one or more parameters for configuring network functions provided by a network device. The data file is processed to recognize and extract one or more parameters contained in the data file. The device is also caused to populate one or more of a plurality of parameter fields in a graphical user interface with one or more parameters extracted from the data file, according to a mapping between the one or more parameters extracted from the data file and one or more corresponding parameter fields in the plurality of parameter fields in the graphical user interface. The device is further caused to process the parameters contained in the parameter fields in the graphical user interface in order to generate a JavaScript Object Notation (JSON) configuration file. The device is further caused to send the JSON configuration file to a network device in order to implement network functions according to the JSON configuration file.

[0006] The aspects of this disclosure will be best understood from the following detailed description when read in conjunction with the accompanying drawings. Note that, in accordance with standard industry practice, various features are not depicted to a constant scale. In practice, the dimensions of various features may be increased or decreased as appropriate for the sake of clarity in discussion. [Brief explanation of the drawing]

[0007] [Figure 1] This is a diagram of a communication system according to one or more embodiments. [Figure 2] This is a diagram of a graphical user interface according to one or more embodiments. [Figure 3] This is a diagram of a graphical user interface according to one or more embodiments. [Figure 4]This is a flowchart of the process for generating a JSON configuration file and implementing network functionality, using one or more embodiments. [Figure 5] This is a functional block diagram of a computer or processor-based system in which one embodiment is implemented. [Modes for carrying out the invention]

[0008] The following disclosure provides many different embodiments or examples for implementing different features of the subject matter provided. For simplicity, specific examples of components and arrangements are described below. Naturally, these are merely examples and are not intended to be limiting. For example, the formation or positioning of a first feature above or on a second feature in the following description may include embodiments in which the first and second features are formed or arranged in direct contact, and may also include embodiments in which additional features may be formed or arranged between the first and second features so that they do not come into direct contact. In addition, the disclosure may repeat reference numbers and / or letters in various examples. This repetition is for brevity and clarity and does not in itself determine the relationships between the various embodiments and / or configurations discussed.

[0009] Furthermore, spatially relative terms such as “beneath,” “below,” “lower,” “above,” and “upper” may be used herein to facilitate descriptions of the relationship between one element or feature and another, as shown in the figures. Spatially relative terms are intended to encompass different orientations of a device or object in use or operation, in addition to the orientation shown in the figures. A device may be oriented in other directions (rotated 90 degrees or in other orientations), and the spatially relative descriptors used herein may be interpreted accordingly.

[0010] Communication networks and network services are often provided by static or inflexible systems that are difficult to configure, scale, and deploy across various target areas. Network operators may coordinate and deploy communication networks and / or network services, including network services (e.g., hardware, software, etc.) provided by one or more network service providers. To facilitate the provision of communication networks and network services, various network functions are implemented by one or more network devices associated with the communication network. Such communication networks often include network services spanning multiple domains such as radio area networks (RANs), base station subsystems (BSSs), platforms, and core networks; various technologies (e.g., 3G, 4G, LTE, 5G, etc.); multiple locations; various software interfaces; and multiple devices that are dedicated and / or optimized by a particular network service provider.

[0011] As communication networks evolve and improve, a single communication network may include a constantly changing number of network service providers for providing network services and / or related to the provision of network services related to various aspects of the communication network (e.g., domain, technology, location of service, etc.). As a result, the state of the communication network may change dynamically through additions and / or reductions of network service providers, changes to one or more network services, network functions, and so on.

[0012] Newly developed software or applications undergo an onboarding process. Part of this onboarding process often involves pushing configuration files to one or more network devices. Traditionally, network orchestrators are involved in the configuration and onboarding of network services and network functions. Such network orchestrators are typically managed by network operators to control the communication network, with network service providers relying on them for configuring dynamic parameters and pushing configuration files to network devices. As a result, network service providers cannot directly control or initiate configuration pushes for configuring network functions and / or network devices. In other words, network service providers rely on network orchestrators to initiate configuration pushes.

[0013] Occasionally, network service providers initiate configuration pushes by uploading configuration files in a specific format, such as JavaScript Object Notation (JSON), Extensible Markup Language (XML), or some other suitable format or file type.

[0014] Network service providers often manually generate JSON configuration files for uploading to network orchestrators, which then push these JSON configuration files to the appropriate network devices. This traditional process is susceptible to human error and delays. For example, manual generation of JSON configuration files requires users to track parameter repetitions along with precise identifier details, which is a tedious task and, along with other human-related errors such as typos, incorrect inputs, and interpretation problems, makes validating manually generated JSON configuration files more cumbersome. Because network service providers cannot push configurations to network devices on demand, delays caused by the error-prone manual process of generating JSON configuration files, and latency resulting from the reliance on network orchestrators, can lead to communication network reliability issues, reduced quality of service, and increased costs.

[0015] Figure 1 shows a communication system 100 according to one or more embodiments. The system 100 enables the automatic generation of a JSON configuration file based on data files provided by a network service provider and / or one or more user inputs. The system 100 also facilitates the implementation of network functions by pushing the generated JSON configuration to one or more network devices outside the network orchestrator.

[0016] System 100 comprises a configuration manager 101, data storage 103, one or more network devices 105a to 105n (collectively referred to as network devices 105), user equipment (UE) 107, and a network orchestrator 109. The configuration manager 101, data storage 103, one or more network devices 105, UE 107, and / or network orchestrator 109 are connected in a communicative manner via a communication network 111. In some embodiments, the communication network 111 is orchestrated by the network orchestrator 109, which combines multiple network services provided by one or more network service providers via the network devices 105.

[0017] In some embodiments, the configuration manager 101, when executed by a processor such as processor 503 (Figure 5), includes a set of computer-readable instructions that cause the configuration manager 101 to perform a process discussed according to one or more embodiments.

[0018] In some embodiments, the configuration manager 101 is located remotely from the network device 105. In some embodiments, the configuration manager 101 is at least partially implemented by the UE 107. In some embodiments, the configuration manager 101 is one or more parts of the network device 105. In some embodiments, one or more processes and / or components of the configuration manager 101 configured to run are distributed among one or more of the network device 105, one or more UE 107, and / or one or more processors located remotely from the network device 105 and / or one or more UE 107.

[0019] The data storage 103 is a memory such as a memory 505 (Figure 5) that can be queried or store data according to one or more embodiments. In some embodiments, the data storage 103 stores searchable information, including stored information related to the communication network 111, such as a network device 105 identifier, physical cell identification information (PCI), frequency information, route sequence index, preamble information, key performance indicator (KPI) data, network function configuration parameters, network device configuration parameters, other appropriate configuration information, or other appropriate system data.

[0020] The configuration manager 101 is configured to automatically generate a JSON configuration file and send it to one or more network devices 105 via an external communication channel of the network orchestrator 109. Automatically generating a JSON configuration file and sending it via an external communication channel of the network orchestrator 109 helps improve network reliability while enhancing the scalability of the communication network by enabling the timely and cost-effective deployment of changes, updates, deletions, and / or additions to network functions while reducing the impact on system resources. For example, network functions can be changed, updated, deleted, and / or added in a way that reduces response times, lowers costs, and increases user confidence in the reliability of the communication network, without relying on a manual process for generating the JSON configuration file and / or on the network orchestrator 109 initiating the push of the JSON configuration file to network devices.

[0021] In some embodiments, the configuration manager 101 generates a graphical user interface that is output to a display by a UE 107 or a terminal associated with the configuration manager 101 for a user (e.g., a network service provider) to enable the user to implement network functions and to enable a JSON configuration file to be sent to one or more of the network devices 105 for implementing the network functions. In some embodiments, the graphical user interface is accessible via a web browser, such as by a website or a web browser plugin.

[0022] In some embodiments, the graphical user interface is configured to facilitate uploading of a data file containing one or more parameters for configuring a network function provided by one or more of the network devices 105 to the configuration manager 101. The data file is processed to recognize, parse, and extract one or more parameters contained in the data file. In some embodiments, the data file is a raw data file in binary interchange file format (BIFF), an.xls file, or some other suitable format.

[0023] In some embodiments, the graphical user interface includes a plurality of parameter fields that can be used to indicate values ​​or information applicable to configuring network functions. The configuration manager 101 ensures that one or more of the plurality of parameter fields included in the graphical user interface are populated with one or more parameters extracted from a data file, according to a mapping between one or more parameters extracted from a raw data file and one or more corresponding parameter fields among the plurality of parameter fields included in the graphical user interface. In some embodiments, the raw data file is based on a template that includes one or more input fields configured to receive one or more parameters and information for configuring network functions and to facilitate the mapping between one or more parameters extracted from the data file and one or more corresponding parameter fields among the plurality of parameter fields included in the graphical user interface.

[0024] In some embodiments, the configuration manager 101 processes parameter fields included in the graphical user interface to determine whether all parameter fields have content based on mappings of one or more parameters extracted from a data file, or whether one or more of the parameter fields included in the graphical user interface are empty. In response to determining that one or more of the parameter fields included in the graphical user interface are empty and that one or more parameters extracted from the data file lack mappings to one or more of the parameter fields determined to be empty, the configuration manager 101 retrieves one or more database parameters from the data storage 103 to fill one or more of the parameter fields determined to be empty before generating the JSON configuration file. In some embodiments, the database parameters correspond to previous versions of the JSON configuration file set or applied to previous network functions implemented by the network device 105, previous network functions implemented by one or more different network devices 105, or parameters set or applied to some other suitable basis to fill missing parameters specified by the configuration manager 101 as necessary to generate the JSON configuration file to configure the network functions. In some embodiments, the database parameters include one or more pre-set default values. In some embodiments, database parameters include combinations of values ​​according to rules that define situations in which a particular database parameter is used instead of other database parameters and / or one or more default values.

[0025] In some embodiments, at least one of the parameter fields included in the graphical user interface is configured to be modified based on user input. In some embodiments, the user input is performed by selecting from an option drop-down menu, a list of options, an array of options, by entering text, or by any other suitable method. For example, if the user wants to change the value of a populated parameter field, the graphical user interface enables selection of alternative options that will be used to generate a JSON configuration file. In some embodiments, the alternative options are retrieved from the data storage 103 and provided to the graphical user interface in the form of a drop-down menu, list, array, or other suitable method.

[0026] The configuration manager 101 processes the parameters included in the parameter fields within the graphical user interface to generate a JSON configuration file. In some embodiments, the graphical user interface is configured to facilitate the generation of a JSON configuration file that includes multiple configurations for network functions to be implemented by the network device 105 according to the scheduling parameters included in the data file. In some embodiments, the scheduling parameters are set in the graphical user interface. In some embodiments, the scheduling parameters include a first-day configuration and a second-day configuration, whereby the JSON configuration file includes both the first-day configuration and the second-day configuration for execution by the receiving network device 105 to implement network functions according to the first-day configuration and the second-day configuration without the need to separately generate and / or process individual JSON configuration files for each of the first day and the second day.

[0027] The configuration manager 101 ensures that the generated JSON configuration file is sent to the network device 105 in order to implement network functions according to the JSON configuration file. In some embodiments, the JSON configuration file is sent to the network device 105 by the configuration manager 101 to implement network functions via a communication channel that is not intercepted by the network orchestrator 109. In some embodiments, the JSON configuration file is sent directly to the network device 105 by the configuration manager 101 to implement network functions. In some embodiments, the JSON configuration file is sent to the network device 105 via the configuration manager 101 and a UE 107 having connectivity to a display on which a graphical user interface is output. In some embodiments, the JSON configuration file is optionally downloaded to the UE 107 on which a user is viewing a graphical user interface.

[0028] In some embodiments, the configuration manager 101 allows the network service provider to download or create an underlying .xls-based template, which is then populated with information about various parameters and uploaded to the configuration manager 101 to generate a JSON-formatted configuration file that can be directly or indirectly pushed from the configuration manager 101 to the network orchestrator 109 based on selected configuration files, unified hostnames, etc., on each of the network devices 105's Internet Protocol addresses and ports, thus minimizing or eliminating the manual effort required to create, validate, and send the JSON configuration file. In some embodiments, one or more of the parameters provided in the data file by the network service provider / user are dynamic parameters that can be added and / or modified by the network service provider / user when adding information to the template for generating the data file.

[0029] In some embodiments, the configuration manager 101 is configured to generate JSON Day 1 / Day 2 configuration files based on a given xpath and value (default value), as well as / or a support list type parameter for which the network service provider / user provides a unique identifier or parsing logic (for example, for a list parameter, the key and value are two parameters that go into a specific programmable logic device record). In some embodiments, in scenarios where details of one or more parameters are not available or provided by a data file uploaded or known to the user, the configuration manager 101 facilitates the generation of the JSON configuration file even when all parameters are unknown to the user attempting to generate the JSON configuration file by generating the parameters based on data in data storage 103, retrieving parameters from data storage 103, or providing default values ​​for the parameters. In some embodiments, the data file template format provides the network service provider / user with tags identifiable by the parsing logic and / or configuration manager 101 to facilitate recognition of parameters in the data file for parsing and extraction, and provides an opportunity to fill in parameter fields in a graphical user interface.

[0030] According to various embodiments, the ability to provide information via template / data files, add parsing logic, modify parameters, and so on, along with the ease of uploading and using data files to the configuration manager, and the ability to manipulate and autonomously generate JSON configuration files outside of the network orchestrator 109, are added to the network service provider / user's ability to control the deployment of JSON-formatted configuration files to the appropriate network devices 105.

[0031] According to various embodiments, the ability to define, create, and / or push multi-day configurations, such as the discussed Day 1 / Day 2 options, provides the network service provider / user with oversight over the multi-day implementation of the network functions of the corresponding network device 105. In some embodiments, the configuration manager 101 receives status updates from the network device 105 to which the generated JSON configuration file is sent, so that the configuration manager 101 is notified whether the network functions, Day 1 configuration, Day 2 configuration, and / or any other day configuration are successful or unsuccessful. Such ability gives the network service provider / user visibility into the success of the network function configuration and the success / failure of the JSON configuration file created by the network service provider / user.

[0032] The configuration manager 101 thus saves time, money, and system resources by reducing or eliminating the manual tasks typically involved in generating and validating JSON configuration files. Furthermore, the graphical user interface generated by the configuration manager 101 provides network service providers / users with complete visibility from configuration generation to configuration push, without requiring an orchestrator.

[0033] Figure 2 shows a graphical user interface 200 according to one or more embodiments. The graphical user interface 200 is a configuration manager user interface that includes a configuration file list 201 and label rows 203. The configuration file list 201 is configured to display a configuration file 205. For ease of explanation, the configuration file list 201 is shown in Figure 2 as having one configuration file 205. In some embodiments, the configuration file list 201 includes two or more configuration files 205. In some embodiments, the configuration file list 201 is empty until a configuration file 205 is generated and added to the configuration file list 201.

[0034] Configuration file 205 is a JSON configuration file. Configuration file 205 included in configuration file list 201 is optionally another type of configuration file, such as an XML configuration file, or any other appropriate file type. Configuration file 205 included in configuration file list 201 has multiple parameters. The parameters of configuration file 205 correspond to labels included in label row 203. In the graphical user interface 200, label row 203 contains parameter headings for Unified Host Name (UHN), Network Service (NS) version, NS Identifier (ID), Technology, Equipment Type, Network Element (NE) version, Network Function (NF) type, NF Label, Vendor Domain (or Network Service Provider Domain), Day 1 Configuration Status, Day 2 Configuration Status, and Data Model Type.

[0035] The graphical user interface 200 facilitates editing of a configuration file 205 by selecting the configuration file 205 and toggling an edit icon included in the graphical user interface 200, or any other appropriate graphical user interface icon. In some embodiments, selecting a configuration file 205 toggles the editing of the selected configuration file 205. The graphical user interface 200 also facilitates the creation of a new configuration file 205 by selecting, for example, a "+" symbol, or any other appropriate graphical user interface icon. In some embodiments, in response to selecting a configuration file 205 to be edited, or in response to a selection to create a new configuration file 205, the configuration manager 101 (Figure 1) displays the graphical user interface 300 (Figure 3) for editing and / or creating the configuration file 205.

[0036] In some embodiments, the graphical user interface 200 includes a search field and / or filter options so that the user can search for configuration files 205 included in the configuration file list 201 according to various keywords, parameters, or some other suitable basis for reducing the number of configuration files that can be viewed within the configuration file list 201.

[0037] The graphical user interface 200 includes a download icon. In response to the selection of a configuration file 205 and the detection and toggling of the download icon, the configuration manager 101 ensures that the selected configuration file 205 is downloaded, for example, to the UE 107 (Figure 1) used to access the graphical user interface 200.

[0038] The graphical user interface 200 also includes an upload icon. In response to the selection of a configuration file 205 and the detected toggle of the upload icon, the configuration manager 101 ensures that the selected configuration file 205 is sent, uploaded, or pushed to the corresponding network device 105 (Figure 1), either directly or via the UE 107, in order to implement network functions according to the selected configuration file 205. In some embodiments, the method, communication channel, and / or timing by which the selected configuration file 205 is sent, uploaded, or pushed to the corresponding network device 105 are based on instructions contained in the selected configuration file. In some embodiments, the method, communication channel, and / or timing by which the selected configuration file 205 is sent, uploaded, or pushed to the corresponding network device 105 are based on communication rules executed by the configuration manager 101 in response to one or more parameters contained in the selected configuration file 205.

[0039] Figure 3 shows a graphical user interface 300 in one or more embodiments. The graphical user interface 300 is displayed in response to an instruction in the graphical user interface 200 (Figure 2) to add a configuration file or edit a selected configuration file. The graphical user interface 300 includes several parameter fields for identifying parameters associated with configuring network functions according to the configuration file being added or edited. The parameter fields include options for selecting or entering UHN name / UUID (Universal Unique Identifier), domain, vendor (or network service provider) information, technology, software version, IP address, and port number. In some embodiments, the graphical user interface 300 includes options for configuring day 1 and day 2 configurations, send or push commands, download commands, destination addresses, commands to directly push day 1 and day 2 configurations in sequence, commands to push day 1 and day 2 configurations together in a single configuration file, scheduling parameter commands for when the configuration manager 101 sends or pushes the generated configuration file to the network device 105, routing information that instructs how the generated configuration file is sent to the network device 105 and / or UE 107, or additional details such as any other appropriate details, commands or rules.

[0040] The graphical user interface 300 includes an upload file workspace 301 where data files are uploaded to the configuration manager 101 (Figure 1) for processing via drag-and-drop operations. In some embodiments, the graphical user interface 300 optionally includes an upload icon to facilitate uploading and sending data files to the configuration manager 101 for processing.

[0041] When a data file is uploaded to the configuration manager 101 via the graphical user interface 300 during use, the configuration manager 101 processes the data file to recognize, parse, and extract the parameters contained in the data file that correspond to the parameter fields contained in the graphical user interface 200. The configuration manager 101 then ensures that the parameter fields are filled with the parameters contained in the data file. For example, if one or more parameter fields are empty after filling the parameter fields according to the parameters contained in the data file, the configuration manager 101 ensures that the empty parameter fields are filled based on default values ​​and / or one or more database parameters obtained from the data storage 103 (Figure 1). In some embodiments, parameter fields are configured to be editable. In some embodiments, editing of a parameter field is performed by one or more of the following appropriate actions: text input, drop-down menus, selection from an array, or any other appropriate action that allows editing or deleting information in the parameter field, or adding information in the parameter field.

[0042] After adding, filling, or editing parameters included in the parameter fields, regardless of whether such actions are based on user input or parameters included in an uploaded data file, the configuration manager 101 ensures that a JSON configuration file is generated in response to user selection of a "Submit" icon, a save icon, or any other appropriate user-based instruction, or interaction with the graphical user interface 300.

[0043] The generated JSON configuration file is then added to the configuration file list 201 in the graphical user interface 200. If the graphical user interface 300 is used to edit the selected configuration file 205, the generated JSON configuration file replaces or updates the selected configuration file 205 included in the configuration file list 201. In some embodiments, the generated JSON configuration file is sent or pushed to the network device 105 immediately upon transmission or saving of the generated JSON configuration file.

[0044] Figure 4 is a flowchart of process 400 for generating a JSON configuration file and implementing network functions, according to one or more embodiments. In some embodiments, the configuration manager 101 (Figure 1) executes process 400.

[0045] In step 401, the configuration manager 101 processes a data file containing one or more parameters for configuring network functions provided by a network device. The data file is processed to recognize, parse, and extract one or more parameters contained within it. In some embodiments, the data file is a raw data file in binary exchange file format. In some embodiments, the raw data file is based on a template containing one or more input fields configured to receive one or more parameters and information for configuring network functions and to facilitate mapping between one or more parameters extracted from the data file and one or more corresponding parameter fields of a plurality of parameter fields contained in a graphical user interface.

[0046] In step 403, the configuration manager 101 ensures that one or more of the multiple parameter fields included in the graphical user interface are populated with one or more parameters extracted from the data file, according to the mapping between one or more parameters extracted from the data file and one or more corresponding parameter fields among the multiple parameter fields included in the graphical user interface.

[0047] In the optional step 405, the configuration manager 101 determines that one or more parameter fields included in the graphical user interface are empty, and in response to determining that one or more parameters extracted from the data file lack a mapping to one or more of the parameter fields determined to be empty, it retrieves one or more database parameters from data storage, such as data storage 103 (Figure 1), to satisfy one or more of the parameter fields determined to be empty before generating the JSON configuration file.

[0048] In some embodiments, at least one of the parameter fields included in the graphical user interface is configured to be modified based on user input indicating a selection from a dropdown menu, list, array, or text input.

[0049] In step 407, the configuration manager 101 processes the parameters contained in the parameter fields within the graphical user interface in order to generate a JSON configuration file. In some embodiments, the graphical user interface is configured to facilitate the generation of a JSON configuration file containing multiple configurations for network functions that will be implemented by the network device according to scheduling parameters contained in the data file.

[0050] In step 409, the configuration manager 101 ensures that the JSON configuration file is sent to a network device in order to implement network functions according to the JSON configuration file. In some embodiments, the network device is one of several network devices included in a communication network implemented by a network orchestrator, and the JSON configuration file is generated by a configuration manager outside of the network orchestrator. In some embodiments, the JSON configuration file is sent to the network device by the configuration manager via a communication channel that is not intercepted by the network orchestrator in order to implement network functions. In some embodiments, the JSON configuration file is sent directly to the network device by the configuration manager in order to implement network functions. In some embodiments, the JSON configuration file is sent to the network device via a user device having connectivity to the configuration manager and a display on which a graphical user interface is output.

[0051] Figure 5 is a functional block diagram of a computer or processor-based system 500 in which one embodiment is implemented.

[0052] The processor-based system 500 is programmed to generate a JSON configuration file and implement network functions, as described herein, and includes components such as a bus 501, a processor 503, and memory 505.

[0053] In some embodiments, the processor-based system is implemented as a single "system on a chip." The processor-based system 500 or a portion thereof constitutes a mechanism for performing one or more of the steps of generating a JSON configuration file and implementing network functions.

[0054] In some embodiments, the processor-based system 500 includes a communication mechanism, such as a bus 501, for transferring and / or receiving information and / or instructions between components of the processor-based system 500. The processor 503 is connected to the bus 501 to retrieve instructions for execution and process information stored, for example, in memory 505. In some embodiments, the processor 503 also includes one or more dedicated components for performing specific processing functions and tasks, such as one or more digital signal processors (DSPs) or one or more application-specific integrated circuits (ASICs). The DSP is typically configured to process real-world signals (e.g., sound) in real time, independently of the processor 503. Similarly, the ASIC can be configured to perform specialized functions that are not readily performed by a more general-purpose processor. Other specialized components that assist in performing the functions described herein optionally include one or more field-programmable gate arrays (FPGAs), one or more controllers, or one or more other dedicated computer chips.

[0055] In one or more embodiments, the processor (or more processors) 503 performs a series of operations on information specified by an instruction set stored in memory 505 in connection with generating a JSON configuration file and implementing network functions. By executing the instructions, the processor performs the specified functions.

[0056] The processor 503 and its associated components are connected to memory 505 via bus 501. Memory 505 includes one or more of dynamic memory (e.g., RAM, magnetic disks, writable optical disks, etc.) and static memory (e.g., ROM, CD-ROM, etc.) to store executable instructions that, when executed, generate a JSON configuration file and perform the steps described herein to implement network functions. Memory 505 also stores data associated with or generated by the execution of the steps.

[0057] In one or more embodiments, memory 505, such as random access memory (RAM) or any other dynamic storage device, stores information including processor instructions for generating JSON configuration files and implementing network functions. Dynamic memory can change the information it stores. RAM allows units of information stored at locations called memory addresses to be stored and retrieved independently of information at adjacent addresses. Memory 505 is also used by processor 503 to store temporary values ​​while the processor is executing instructions. In various embodiments, memory 505 is read-only memory (ROM) or any other static storage device coupled to bus 501 to store static information including instructions that cannot be changed by processor 503. Some memory consists of volatile storage that loses the information stored when power is lost. In some embodiments, memory 505 is a non-volatile (persistent) storage device for storing information including instructions that persists even when system 500 is turned off or loses power in another way, such as a magnetic disk, optical disk, or flash card.

[0058] As used herein, the term “computer-readable medium” refers to any medium involved in providing information to the processor 503, including instructions for execution. Such mediums can take many forms, but are not limited to computer-readable storage media (e.g., non-volatile media, volatile media). Non-volatile media include, for example, optical disks or magnetic disks. Volatile media include, for example, dynamic memory. Common forms of computer-readable media include, for example, floppy disks, flexible disks, hard disks, magnetic tapes, other magnetic media, CD-ROMs, CDRWs, DVDs, other optical media, punch cards, paper tapes, optical mark sheets, other physical media having hole patterns or other optically recognizable markings, RAM, PROMs, EPROMs, FLASH-EPROMs, EEPROMs, flash memory, other memory chips or cartridges, or other media that a computer can read. The term computer-readable storage medium is used herein to refer to computer-readable media.

[0059] One aspect of this specification relates to a method, comprising a processor, for processing a data file containing one or more parameters for configuring network functions provided by a network device. The data file is processed to recognize and extract one or more parameters contained in the data file. The method also includes ensuring that one or more of a plurality of parameter fields in a graphical user interface are populated with one or more parameters extracted from the data file, according to a mapping between the extracted parameters and one or more corresponding parameter fields in the plurality of parameter fields in the graphical user interface. The method further includes processing the parameters contained in the parameter fields in the graphical user interface to generate a JavaScript Object Notation (JSON) configuration file. The method further includes ensuring that the JSON configuration file is sent to a network device in order to implement network functions according to the JSON configuration file.

[0060] Another aspect of this specification relates to an apparatus comprising a processor and memory storing instructions, when executed by the processor, that cause the apparatus to process a data file containing one or more parameters for configuring network functions provided by a network device. The data file is processed to recognize and extract one or more parameters contained in the data file. The apparatus is also made to populate one or more of a plurality of parameter fields in a graphical user interface with one or more parameters extracted from the data file, according to a mapping between one or more parameters extracted from the data file and one or more corresponding parameter fields in the plurality of parameter fields in the graphical user interface. The apparatus is further made to process the parameters contained in the parameter fields in the graphical user interface in order to generate a JavaScript Object Notation (JSON) configuration file. The apparatus is further made to send the JSON configuration file to a network device in order to implement network functions according to the JSON configuration file.

[0061] Another aspect of this specification relates to a non-temporary, computer-readable file containing instructions, when executed by a processor, that cause a device to process a data file containing one or more parameters for configuring network functions provided by a network device. The data file is processed to recognize and extract one or more parameters contained in the data file. The device is also caused to populate one or more of a plurality of parameter fields in a graphical user interface with one or more parameters extracted from the data file, according to a mapping between the one or more parameters extracted from the data file and one or more corresponding parameter fields in the plurality of parameter fields in the graphical user interface. The device is further caused to process the parameters contained in the parameter fields in the graphical user interface in order to generate a JavaScript Object Notation (JSON) configuration file. The device is further caused to send the JSON configuration file to a network device in order to implement network functions according to the JSON configuration file.

[0062] The above outlines some features of embodiments so that those skilled in the art may better understand aspects of the disclosure. Those skilled in the art should understand that the disclosure may readily be used as a basis for designing or modifying other processes and structures to perform the same purposes and / or achieve the same advantages of the embodiments introduced herein. Those skilled in the art should also recognize that such equivalent configurations will not depart from the spirit and scope of the disclosure, and that various changes, substitutions, and modifications may be made herein without departing from the spirit and scope of the disclosure.

Claims

1. The processor processes a data file containing one or more parameters for configuring network functions provided by a network device, wherein the data file is processed to recognize and extract the one or more parameters contained in the data file. The graphical user interface is configured such that one or more of the multiple parameter fields included in the graphical user interface are populated with the one or more parameters extracted from the data file, according to a mapping between the one or more parameters extracted from the data file and one or more corresponding parameter fields among the multiple parameter fields included in the graphical user interface, wherein the graphical user interface is configured to facilitate the generation of a single JavaScript Object Notation (JSON) configuration file including a first configuration and a second configuration, the first configuration and the second configuration indicating the settings of the network function to be implemented by the network device at different times, To generate the single JSON configuration file, the parameters included in the parameter fields within the graphical user interface are processed, In order to implement the network function according to the single JSON configuration file, the single JSON configuration file is sent to the network device, Methods that include...

2. The method according to claim 1, further comprising determining that one or more of the parameter fields included in the graphical user interface are empty, and determining that one or more parameters extracted from the data file lack a mapping to one or more of the parameter fields determined to be empty, obtaining one or more database parameters to satisfy one or more of the parameter fields determined to be empty before generating the single JSON configuration file.

3. The method according to claim 1, wherein the data file is a raw data file in binary interchangeable file format.

4. The method of claim 3, wherein the raw data file is based on a template that includes one or more input fields configured to receive the one or more parameters and information for configuring the network function and to facilitate the mapping between the one or more parameters extracted from the data file and one or more corresponding parameter fields of the plurality of parameter fields included in the graphical user interface.

5. The method according to claim 1, wherein at least one of the parameter fields included in the graphical user interface is configured to be modified based on user input indicating a selection from a dropdown menu, list, array, or text input.

6. The method according to claim 1, wherein the network device is one of a plurality of network devices included in a communication network implemented by a network orchestrator, and the single JSON configuration file is generated by a configuration manager external to the network orchestrator.

7. The method according to claim 6, wherein the single JSON configuration file is transmitted by the configuration manager to the network device to implement the network function via a communication channel that is not intercepted by the network orchestrator.

8. The method according to claim 6, wherein the single JSON configuration file is transmitted directly to the network device by the configuration manager to implement the network function.

9. The method according to claim 6, wherein the single JSON configuration file is transmitted to the network device via a user device having connectivity to the configuration manager and a display on which the graphical user interface is output.

10. The method according to claim 1, wherein the first configuration and the second configuration for the network function are implemented by the network device according to scheduling parameters contained in the data file.

11. It is a device, Processor and When executed by the aforementioned processor, the device will Processing a data file containing one or more parameters for configuring network functions provided by a network device, wherein the data file is processed to recognize and extract the one or more parameters contained in the data file. The graphical user interface is configured such that one or more of the multiple parameter fields included in the graphical user interface are populated with the one or more parameters extracted from the data file, according to a mapping between the one or more parameters extracted from the data file and one or more corresponding parameter fields among the multiple parameter fields included in the graphical user interface, wherein the graphical user interface is configured to facilitate the generation of a single JavaScript Object Notation (JSON) configuration file including a first configuration and a second configuration, the first configuration and the second configuration indicating the settings of the network function to be implemented by the network device at different times, To generate the single JSON configuration file, the parameters included in the parameter fields within the graphical user interface are processed, In order to implement the network function according to the single JSON configuration file, the single JSON configuration file is sent to the network device, A memory containing the instruction to perform the action, A device equipped with the following features.

12. The aforementioned device The apparatus according to claim 11, wherein, in response to determining that one or more of the parameter fields included in the graphical user interface are empty, and determining that one or more parameters extracted from the data file lack a mapping to one or more of the parameter fields determined to be empty, the apparatus is further prompted to obtain one or more database parameters to satisfy one or more of the parameter fields determined to be empty before generating the single JSON configuration file.

13. The apparatus according to claim 11, wherein the data file is a raw data file in binary exchange file format.

14. The apparatus according to claim 13, wherein the raw data file is based on a template that includes one or more input fields configured to receive the one or more parameters and information for configuring the network function and to facilitate the mapping between the one or more parameters extracted from the data file and one or more corresponding parameter fields of the plurality of parameter fields included in the graphical user interface.

15. The apparatus according to claim 11, wherein at least one of the parameter fields included in the graphical user interface is configured to be modified based on user input indicating a selection from a dropdown menu, list, array, or text input.

16. The apparatus according to claim 11, wherein the network device is one of a plurality of network devices included in a communication network implemented by a network orchestrator, and the single JSON configuration file is generated by a configuration manager external to the network orchestrator.

17. The apparatus according to claim 16, wherein the single JSON configuration file is transmitted by the configuration manager to the network device to implement the network function via a communication channel that is not intercepted by the network orchestrator.

18. The apparatus according to claim 16, wherein the single JSON configuration file is transmitted directly to the network device by the configuration manager to implement the network function.

19. The apparatus according to claim 11, wherein the first and second configurations for the network function are implemented by the network device in accordance with scheduling parameters contained in the data file.

20. When executed by the processor, the device will Processing a data file containing one or more parameters for configuring network functions provided by a network device, wherein the data file is processed to recognize and extract the one or more parameters contained in the data file. The graphical user interface is configured such that one or more of the multiple parameter fields included in the graphical user interface are populated with the one or more parameters extracted from the data file, according to a mapping between the one or more parameters extracted from the data file and one or more corresponding parameter fields among the multiple parameter fields included in the graphical user interface, wherein the graphical user interface is configured to facilitate the generation of a single JavaScript Object Notation (JSON) configuration file including a first configuration and a second configuration, the first configuration and the second configuration indicating the settings of the network function to be implemented by the network device at different times, To generate the single JSON configuration file, the parameters included in the parameter fields within the graphical user interface are processed, In order to implement the network function according to the single JSON configuration file, the single JSON configuration file is sent to the network device, A non-temporary, computer-readable medium that stores instructions for performing a certain action.

Images