Abstract: A virtual Radio Access Network (vRAN) system (300) for provisioning a virtual Radio Access Network (RAN) that is portable across one or more RAN hardware platforms is provided. The virtual Radio Access Network (vRAN) system (300) includes a waveform development kit (WDK) (302), and a waveform execution environment (304). The waveform development kit (302) defines at least one portable Radio Access Network (RAN) application into a form that is instantiated on a RAN hardware (326). The waveform execution environment (304) (i) monitors real-time schedulable resources in real-time, and (ii) collects one or more statistics and monitors the one or more statistics for network automation. The waveform execution environment (304) includes a RAN hypervisor (314) that virtualizes at least one attribute of a spectral resource required to provision the RAN that is portable across at least one hardware platform of the one or more RAN hardware platforms in the RAN hardware.

Abstract: A system for deploying a Radio Access Network Containerized Network Function (RAN CNF) that is portable across a plurality of RAN hardware platforms is provided. The system includes a Software Development Kit (SDK), a schedule generator and a scheduler runtime unit. The SDK enables providing a RAN functionality in a physical layer (L1) software code in a platform-independent manner as a RAN pipeline of a plurality of RAN tasks. The RAN tasks include a first and second RAN task. The first RAN task invokes an Application programming interface (API) from a plurality of Application Programming Interfaces to call to the second RAN task. The schedule generator generates a schedule for allocating a node in the RAN pipeline to one or more processing elements. The scheduler runtime unit loads the RAN tasks corresponding to nodes in the RAN pipeline, based on the schedule generated by the schedule generator.

Abstract: Configurations of a system and a method for optimizing an allocation of computing resources via a disaggregated architecture, are described. In one aspect, the disaggregated architecture may include a Layer 2 (L2) controller that may be configured to optimize an allocation of computing resources in a virtualized radio access network (vRAN). The disaggregated architecture in a distributed unit may disaggregate an execution of the operations of the distributed unit by the computing resources deployed therein. Further, the disaggregated architecture may provision statistical multiplexing and provision a mechanism for allocating the computing resources based on real-time conditions in the network. The disaggregated architecture may provision a mechanism that may enable dynamic swapping, allocation, scaling up, management, and maintenance of the computing resources deployed in the distributed unit (DU).

Abstract: A method for operating a hardware-software interface (HSI) executable specification unit by means of an executable hardware-software interface (HSI) specification for a computing device is provided. The executable HSI specification is a form of a Device Programming Specification (DPS). The HSI executable specification unit includes a HSI analyser, at least one skeletal driver and a HSI executable specification interpreter.

Abstract: A processor-implemented method for transforming co-routines to equivalent sub-routines is provided. An input is received at a first user device from a user for a first language and a first operating environment. The first language includes the co-routines and is supported in a first hardware environment. The first language is analyzed to transform the co-routines of the first language into the sub-routines of a second language for implementing the co-routines of the first language in a second hardware environment.

Abstract: A method for operating a hardware-software interface (HSI) executable specification unit by means of an executable hardware-software interface (HSI) specification for a computing device is provided. The executable HSI specification is a form of a Device Programming Specification (DPS). The HSI executable specification unit includes a HSI analyser, at least one skeletal driver and a HSI executable specification interpreter.

Abstract: A processor-implemented method for transforming co-routines to equivalent sub-routines is provided. The method includes (i) receiving, an input from user for first language and first operating environment, and (ii) analyzing first language to transform co-routines of first language into sub-routines of second language by (a) determining at least one automatic variable for persistent variables and non-persistent variables across suspend cycles or resume cycles of co-routines, (b) transforming persistent variables and non-persistent variables into sub-routines of second language based on determined automatic variables, (c) determining return statements and yield statements in co-routines of first language for transforming the return statements and yield statements into sub-routines of the second language, and (d) translating the co-routines of first language into sub-routines of second language and second operating environment.

Abstract: A system and a processor implemented method for customizing an archive of a device driver generator tool for a user is provided. The system includes (i) a memory unit that stores a database, and a set of modules, and (ii) a processor. The template file obtaining module is configured to obtain information associated with the template files and template files. The configuration file obtaining module is configured to obtain information associated with the configuration files and configuration files. The archive configuration file verification module is configured to verify whether an archive for the configuration files and the template files is pre-existing in the database. The archive file appending module is configured to (i) append the template files and the configuration files to the archive pre-existing in the database. The archive file appending module generates the archive for template files and configuration files upon the archive not pre-existing in the database.

Abstract: A system and method for automatically generating device driver codes for a device model based on an operation of said device model in verification environments is provided. The System includes a computing device. The computing device includes a device programming specification receiving module, a run time specification parsing module, a verification environment determination module and a driver generation module. The device programming specification receiving module receives at least one device programming specification aspects associated with an operation of device model in verification environment to determine a type of device driver code to be generated. The run time specification parsing module parses a run time specification file that includes verification environment parameters in run time specification. The verification environment determination module determines whether the verification environment equals to a part of a simulation/emulation in run time specification.

Abstract: A system and method for automatically generating device driver codes for a device model based on an operation of said device model in verification environments is provided. The System includes a computing device. The computing device includes a device programming specification receiving module, a run time specification parsing module, a verification environment determination module and a driver generation module. The device programming specification receiving module receives at least one device programming specification aspects associated with an operation of device model in verification environment to determine a type of device driver code to be generated. The run time specification parsing module parses a run time specification file that includes verification environment parameters in run time specification. The verification environment determination module determines whether the verification environment equals to a part of a simulation/emulation in run time specification.

Abstract: A system for generating a device driver based on an archived template code using a device driver generation tool is provided. The device driver generation tool is configured to extract configuration files and template files from a template archive stored in a database, each of the files comprises high level configuration files and low level configuration files, each comprising one or more labels, parse a high-level configuration file, corresponding to a class of a device, and an operating system for which the driver is being generated, process a label from the high-level configuration file, extract template code from the template files to obtain an extracted template code, and generate a portion of the driver based on the extracted template code when a block label is identified, parse a low-level configuration file, and generate the driver using a first specification and a second specification when the label is a file label.

Abstract: A system and a processor implemented method for customizing an archive of a device driver generator tool for a user is provided. The system includes (i) a memory unit that stores a database, and a set of modules, and (ii) a processor. The template file obtaining module is configured to obtain information associated with the template files and template files. The configuration file obtaining module is configured to obtain information associated with the configuration files and configuration files. The archive configuration file verification module is configured to verify whether an archive for the configuration files and the template files is pre-existing in the database. The archive file appending module is configured to (i) append the template files and the configuration files to the archive pre-existing in the database. The archive file appending module generates the archive for template files and configuration files upon the archive not pre-existing in the database.

Abstract: A method of generating and validating a device driver for a hardware device is provided. The method include (i) dynamically querying the hardware device for a device programming specification, (ii) dynamically querying a run time environment for a run time specification, (iii) obtaining the device programming specification that is specific to the hardware device, (iv) obtaining the run time specification that is specific to the hardware device and the run time environment, (v) dynamically synthesizing a device driver, by a device driver generation tool to obtain a synthesized device driver, (vi) automatically testing, by the device driver generation tool, the synthesized device driver based on a device class of the hardware device, and (vii) automatically evaluating, by the device driver generation tool, a performance of the synthesized driver with respect to standard performance parameters for the device class of the hardware device for validating the synthesized device driver.

Abstract: A system for generating a device driver based on an archived template code using a device driver generation tool is provided. The device driver generation tool is configured to extract configuration files and template files from a template archive stored in a database, each of the files comprises high level configuration files and low level configuration files, each comprising one or more labels, parse a high-level configuration file, corresponding to a class of a device, and an operating system for which the driver is being generated, process a label from the high-level configuration file, extract template code from the template files to obtain an extracted template code, and generate a portion of the driver based on the extracted template code when a block label is identified, parse a low-level configuration file, and generate the driver using a first specification and a second specification when the label is a file label.

Abstract: A method of generating and validating a device driver for a hardware device is provided. The method include (i) dynamically querying the hardware device for a device programming specification, (ii) dynamically querying a run time environment for a run time specification, (iii) obtaining the device programming specification that is specific to the hardware device, (iv) obtaining the run time specification that is specific to the hardware device and the run time environment, (v) dynamically synthesizing a device driver, by a device driver generation tool to obtain a synthesized device driver, (vi) automatically testing, by the device driver generation tool, the synthesized device driver based on a device class of the hardware device, and (vii) automatically evaluating, by the device driver generation tool, a performance of the synthesized driver with respect to standard performance parameters for the device class of the hardware device for validating the synthesized device driver.

Abstract: Generating device drivers for different user systems to facilitate communication with a hardware device. A device specification containing a program logic specifying the manner in, which external devices can communicate with the hardware device, is received as one input. A software specification specifying various characteristics of a runtime environment (e.g., operating system, processor, hardware components) is received as another input. A device driver generator then programmatically parses the input specifications and automatically generates the device driver code.

Abstract: Generating device drivers for different user systems to facilitate communication with a hardware device. A device specification containing a program logic specifying the manner in, which external devices can communicate with the hardware device, is received as one input. A software specification specifying various characteristics of a runtime environment (e.g., operating system, processor, hardware components) is received as another input. A device driver generator then programmatically parses the input specifications and automatically generates the device driver code.