Description:RELATED ART

[0001] Embodiments of the present specification relate generally to networks, and more particularly to a network transformation system adapted to enable a network function to automatically provide network services to different entities.
[0002] Network functions refer to specific tasks or operations performed within a network architecture. The network functions are building blocks that enable a network to operate efficiently and are crucial for managing data flow, ensuring connectivity, and maintaining security of the network. In the telecommunication industry, the network functions are usually part of a service-based architecture such that these network functions provide services to authorized network functions and to external entities such as end users. Modern-day network functions are designed to meet a set of objectives corresponding to increased demands for integration, automation, and dynamic coordination across network elements. Such modern-day network functions are previously in-built with application programming interface (API) support, which helps the network functions to meet the previously noted objectives.
[0003] However, certain older network functions deployed in the past still lack proper API support, which makes integration, automation, and dynamic coordination across the network elements difficult. For example, some older versions of Huawei’s network functions providing firewall services or router services often rely on command line interface (CLI) or graphical user interface (GUI) based network configurations. These network functions do not include any in-built or native API support. Hence, network administrators typically need to manually configure these network functions and provide specific instructions to enable the network functions to provide requested firewall or router services to end users. Such manual intervention largely affects automation and scalability of the network functions, and increases overall time taken to provide requested services to the end users, which affects overall user experience.
[0004] In order to address the aforementioned issues, such older network functions need to be converted into API supported network functions. Additionally, those network functions may also need to be updated upon subsequent upgrades that introduce new features and functionalities into these network functions. Conventionally, creation of custom APIs or update of APIs is achieved via a significant amount of manual efforts. Specifically, users such as network engineers need to review several complex user manuals that include information corresponding to the unsupported or upgraded network functions to manually develop software packages whose deployment provide the necessary API support to these network functions. However, such manual development of software packages is inefficient, time-consuming and unreliable as the development depends primarily on the experience, skill, expertise, and effort expended by the network engineers.
[0005] Accordingly, there remains a need for a system that automatically provides API support to both the API unsupported and upgraded network functions without any manual intervention.

BRIEF DESCRIPTION

[0006] It is an objective of the present disclosure to provide a method for providing one or more network services to one or more entities. The method includes transmitting one or more application programming interface commands stored in an application programming interface command database from a network transformation system to a selected network function deployed in a network infrastructure manager that is communicatively coupled to the network transformation system. Further, the method includes determining if the selected network function natively supports any particular application programming interface standard by the network transformation system based on one or more responses received from the selected network function in response to the one or more application programming interface commands. Furthermore, the method includes identifying a desired application programming interface standard associated with a service provider network that needs to be supported by the selected network function for providing one or more specific services requested by the one or more entities. In addition, the method includes automatically generating and deploying an application programming interface request handler in the selected network function to transform the selected network function into a supported network function upon determining that the selected network function is an unsupported network function that does not natively support any particular application programming interface standard. The application programming interface request handler is generated based on one or more features that are available in the selected network function and corresponding execution commands, and the desired application programming interface standard associated with the service provider network.
[0007] Further, the method includes automatically identifying the one or more specific services requested by the one or more entities via the application programming interface request handler deployed in the supported network function. Furthermore, the method includes automatically providing the one or more specific services requested by the one or more entities by the network function supported by the application programming interface request handler. Determining if the selected network function natively supports any particular application programming interface standard includes determining that the selected network function natively supports a particular application programming interface standard that is different from the desired application programming interface standard associated with the service provider network. Further, the method includes automatically generating and deploying a customized application programming interface wrapper in the selected network function that translates one or more application programming interface service requests received from a service provider device in the desired application programming interface standard to the particular application programming interface standard for enabling the network function to identify and provide the one or more specific services requested by the one or more entities.
[0008] Identifying the desired application programming interface standard includes monitoring one or more network packets exchanged between a plurality of network components associated with the service provider network. Determining if the selected network function natively supports any particular application programming interface standard includes transmitting the application programming interface commands sequentially from the network transformation system to the selected network function to determine if the selected network function supports any application programming interface standard. Each of the application programming interface commands adheres to a different application programming interface standard. Further, the method includes determining that the selected network function natively supports a specific application programming interface standard when the network transformation system receives a first type of response in response to a specific application programming interface command transmitted to the selected network function. The specific application programming interface command adheres to the specific application programming interface standard. Furthermore, the method includes determining that the selected network function does not natively support any application programming interface standard when the network transformation system receives a second type of response in response to each of the application programming interface commands transmitted to the selected network function. The second type of response is different from the first type of response.
[0009] Automatically generating and deploying the application programming interface request handler in the selected network function includes fetching information corresponding to one or more of a vendor, a version, and a specific type of the selected network function from a corresponding network function descriptor stored previously in an orchestrator platform. Further, the method includes identifying a personalized command that is used to obtain a current configuration information of the selected network function from a plurality of commands stored in the application programming interface command database based on one or more of the vendor, the version, and the specific type of the selected network function fetched from the corresponding network function descriptor. Furthermore, the method includes transmitting the identified personalized command from the network transformation system to the selected network function, and thereby obtaining the current configuration information of the selected network function by the network transformation system. Automatically generating and deploying the application programming interface request handler in the selected network function includes transmitting one or more test commands from the network transformation system to the selected network function to test and identify one or more features that are available in the selected network function. Further, the method includes transmitting one or more wildcard commands from the network transformation system to the selected network function to identify a plurality of execution commands available in the selected network function.
[0010] Furthermore, the method includes mapping each of the features identified to be available in the selected network function to a corresponding execution command selected from the plurality of execution commands. In addition, the method includes automatically generating the application programming interface request handler by the network transformation system based on the one or more features that are identified to be available in the selected network function and corresponding mapped execution commands, and the desired application programming interface standard associated with the service provider network. Automatically generating and deploying the application programming interface request handler in the selected network function includes transmitting the one or more test commands from the network transformation system to the selected network function upon update of the selected network function. Further, the method includes automatically identifying one or more of a feature that is newly added and a feature that is modified in the updated network function based on one or more responses received back from the updated network function in response to the transmitted test commands. Furthermore, the method includes updating the application programming interface request handler associated with the selected network function, thereby generating an updated application programming interface request handler based on identification of one or more of the feature that is newly added and the feature that is modified in the updated network function. Moreover, the method includes deploying the updated application programming interface request handler in the updated network function to provide updated application programming interface support to the updated network function.
[0011] Automatically providing the one or more specific services requested by the one or more entities includes receiving a service request from a user device associated with an end user at a service provider device associated with a service provider. Further, the method includes converting the service request into an application programming interface service request that adheres to the desired application programming interface standard associated with the service provider network. Furthermore, the method includes transmitting the application programming interface service request from the service provider device to the network transformation system via a communications link, and identifying a specific service requested by the end user from the application programming interface service request received from the service provider device by the network transformation system. In addition, the method includes identifying if a particular feature selected from the one or more features available in the selected network function that allows the selected network function to provide the specific service requested by the end user. Moreover, the method includes forwarding the application programming interface service request from the network transformation system to the selected network function only when the particular feature is available in the selected network function. Further, the method includes identifying the specific service requested by the end user by the selected network function that is the unsupported network function and does not natively support any particular application programming interface standard using the application programming interface request handler. Furthermore, the method includes identifying a specific execution command that is mapped to the particular feature that allows the selected network function to provide the specific service requested by the end user. Moreover, the method includes executing the identified specific command for automatically providing the specific service requested by the end user to the end user.
[0012] Automatically generating and deploying the application programming interface request handler includes generating a new application programming interface request handler upon update of the selected network function. The selected network function is one of a network function that natively supports an application programming interface standard that is different from the desired application programing interface standard and a network function that natively supports an application programming interface standard that is same as the desired application programing interface standard. Automatically generating and deploying the application programming interface request handler includes deploying an updated native application programming interface adhering to the particular application programming interface standard along with the customized application programming interface wrapper in the selected network function upon update of the selected network function that natively supports the particular application programming interface standard that is different from the desired application programing interface standard.
[0013] Automatically providing the one or more specific services requested by the one or more entities includes receiving a service request from a user device associated with an end user by a service provider device associated with a service provider. Further, the method includes converting the service request into an application programming interface service request that adheres to the desired application programming interface standard associated with the service provider network. Furthermore, the method includes transmitting the application programming interface service request from the service provider device to the selected network function that natively supports the particular application programming interface standard that is different from the desired application programming interface standard associated with the service provider via a communications link. Moreover, the method includes translating the application programming interface service request adhering to the desired application programming interface standard to the particular application programming interface standard using the customized application programming interface wrapper deployed in the selected network function. In addition, the method includes identifying a specific service requested by the end user from the application programming interface service request translated to the particular application programming interface standard. Further, the method includes identifying a specific command from a plurality of commands that the selected network function needs to execute in order to provide the specific service requested by the end user from a native application programming interface associated with the selected network function. The method also includes executing the specific command and thereby automatically providing the specific service to the end user by the selected network function.
[0014] It is another objective of the present disclosure to provide a digital transformation system for providing one or more services to one or more entities. The digital transformation system includes a network infrastructure manager that hosts a plurality of network functions, a northbound system, and a network transformation system. The northbound system is communicatively coupled to the network infrastructure manager via a communications link and configured to enable deployment of a selected network function on top of the network infrastructure manager. The network transformation system includes an application programming interface command database that is communicatively coupled to the network infrastructure manager and the northbound system via the communications link. The network transformation system is configured to transmit one or more application programming interface commands stored in the application programming interface command database to the selected network function deployed in the network infrastructure manager. Further, the network transformation system determines if the selected network function natively supports any particular application programming interface standard based on one or more responses received from the selected network function in response to the one or more application programming interface commands.
[0015] Furthermore, the network transformation system identifies a desired application programming interface standard associated with a service provider network that needs to be supported by the selected network function for providing one or more specific services requested by the one or more entities. Moreover, the network transformation system automatically generates and deploys an application programming interface request handler in the selected network function to transform the selected network function into a supported network function upon determining that the selected network function is an unsupported network function that does not natively support any particular application programming interface standard. The application programming interface request handler is generated based on one or more features that are available in the selected network function and corresponding execution commands, and the desired application programming interface standard associated with the service provider network. The supported network function automatically identifies the one or more specific services requested by the one or more entities via the API request handler, and provides the one or more specific services requested by the one or more entities. The network transformation system is implemented as one of a standalone system and a subsystem within one or more of the northbound system, the service provider network, and an orchestrator platform deployed in one of a telecommunications network, a connected vehicle network, a connected healthcare network, an internet-of-things network, a cloud service providing network, an internet service provider network, and a leased line network.

BRIEF DESCRIPTION OF DRAWINGS

[0016] These and other features, aspects, and advantages of the claimed subject matter will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
[0017] FIG. 1 illustrates a block diagram depicting an exemplary digital transformation system that transforms one or more network functions that do not natively support API standards into API supported network functions, in accordance with aspects of the present disclosure; and
[0018] FIGS. 2A-C illustrate a flow diagram depicting an exemplary method for transforming a network function that does not natively support any API standards into an API supported VF network function using the digital transformation system of FIG. 1, in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

[0019] The following description presents an exemplary network transformation system. Particularly, embodiments described herein disclose a network transformation system and associated method for automatically transforming a newly deployed network function or an existing network function that does not natively support API standards into an API supported network function without any manual intervention.
[0020] As noted previously, certain older network functions deployed in the past may not natively support any API standards. Such network functions need to be digitalized or transformed into API supported network functions, which benefits network or telecommunication service providers in multiple ways. For example, transforming typical network functions into API supported network functions enables the network or telecommunication service providers to automate network provisioning, monitoring, and management tasks, which saves operational costs for the service providers. Further, network transformation provides the API supported network functions an ability to communicate with different types of systems developed by different types of vendors, which eliminates software dependencies and the need for the service providers to purchase software components from a particular vendor who is especially expensive. Moreover, network transformation allows the service providers to quickly roll out new features to their customers, and to easily scale network services to a large number of customers on need basis. Furthermore, network transformation also adapts emerging technologies such as software defined networks, network function virtualization, and cloud native architectures, which allow network functions and associated infrastructures to evolve with agility and meet growing demands of dynamic and on demand services. Overall, network transformation facilitates automation, integration, and dynamic coordination across network elements, and further drives efficiency and innovation in modern network infrastructures.
[0021] Presently, transforming the network functions that do not natively support API standards into API supported network functions is performed predominantly manually, which requires a significant amount of human expertise and efforts. Even when automated network solutions are available, these allow only an operator to create and deploy a new network function that already or natively supports an API standard such as a TeleManagement Forum (TM Forum), an open application programming interface (OpenAPI), simple object access protocol (SOAP), network configuration protocol (NETCONF), representational state transfer configuration protocol (RESTCONF), or any other vendor’s proprietary standard. However, such automated network solutions do not transform an existing network function or a newly deployed network function that does not natively support any API standards into an API supported network function.
[0022] In contrast, the network transformation system described in the present disclosure automatically identifies a new network function when deployed by an operator and/or any upgrades if any made to an existing network function. Further, the network transformation system identifies if the new or upgraded network function natively supports any API standard. When the network transformation system identifies that the new or upgraded network function does not natively support any API standard, the network transformation system automatically generates an API request handler including a software package. Further, the network transformation system deploys the API request handler in the new or upgraded network function for transforming the new or upgraded network function into an API supported network function. Alternatively, when the new or upgraded network function natively supports any one specific API standard, the network transformation system identifies that specific API standard. Further, the network transformation system generates and deploys a customized API wrapper in the network function. The customized API wrapper, thus deployed in the network function, translates API service requests received from a service provider device into the specific API standard supported by the network function for enabling the network function to provide network services to different entities and/or end users.
[0023] It may be noted that different embodiments of the present network transformation system may be used for automatically digitizing or transforming different types of network functions. For example, the network transformation system may be used to transform a new or an existing network function that lacks native API support and provides telecommunications services such as 5G services to end customers into an API supported 5G network function. Similarly, the network transformation system may be used to transform network functions such as telecommunication network function, a virtual network function, and/or a router network function that lack native API support and provide virtual services such as a virtual firewall service, a video conferencing service, a layer 2 virtual private network (L2VPN) service, a layer 3 virtual private network (L3VPN) service, or a router related service, to end customers into a corresponding API supported network function. However, for clarity, an embodiment of the present network transformation system is described herein in greater detail with reference to transforming a network function that lacks native API support for providing a virtual firewall service to end customers into an API supported network function.
[0024] FIG. 1 illustrates a block diagram depicting an exemplary digital transformation system (100) that transforms one or more network functions that do not natively support API standards into API supported network functions. To that end, the digital transformation system (100) includes a service provider device (102) that is associated with a service provider such as a telecommunication service provider or a network service provider. Examples of the service provider device (102) include a network server, a desktop, a laptop, a smartphone, and a tablet. In one embodiment, the service provider device (102) allows a user such as a network engineer associated with the service provider to login into an associated northbound system (104) via a user account of the user registered with the northbound system (104). Subsequently, the user may use one or more user interfaces associated with the northbound system (104) to deploy a selected network function (106A). Examples of the northbound system (104) that allows the user to deploy the network function (106A) via the associated user interfaces include an operations support system (OSS), a business support system (BSS), or any other information technology (IT) system.
[0025] As used herein, the term network function corresponds to a software application running in a virtualized environment, a physical device or system, or a cloud-native component, that is used to provide a specific network service to end customers and/or different entities. For example, the network function (106A) deployed by the user using the northbound system (104) may correspond to a 5G network function that may provide 5G services to end customers. In another example, the network function (106A) deployed by the user using the northbound system (104) may correspond to a virtual firewall network function that may offer firewall related services to end customers. In yet another example, the network function (106A) deployed by the user using the northbound system (104) may correspond to a L3VPN network function that may provide L3VPN services to enterprises.
[0026] In one embodiment, the network function (106A), thus deployed by the user using the northbound system (104), along with a set of other network functions (106B-N) deployed previously by the user are all running on top of a network infrastructure manager (108) such as a virtual infrastructure manager (108), as depicted in FIG. 1. In one embodiment, the virtual infrastructure manager (108) includes a computing system (110), a storage system (112), and a networking system (114). The computing system (110) allocates memory resources and computing resources required for operations of the network functions (106A-N). The storage system (112) provides storage space for the network functions (106A-N). The networking system (114) provides communications interfaces that satisfy communication requirements of the network functions (106A-N). In addition, the networking system (114) provides network connectivity to the network functions (106A-N) such that the network functions (106A-N) interact with one or more of external networks, a service provider network (116) such as an internet protocol (IP) network, the service provider device (102), an orchestrator platform (118), and a network transformation system (120) via a communications link (122). Examples of the communications link (122) include a Wi-Fi network, an Ethernet, and a cellular data network. In one embodiment, the network transformation system (120) is communicatively coupled to the service provider network (116) via the communications link (122). The network transformation system (120) may be implemented as a standalone system or as a subsystem within one or more of the northbound system (104), the service provider network (116), and the orchestrator platform (118) deployed in one of a telecommunications network, a connected vehicle network, a connected healthcare network, an internet-of-things network, a cloud service providing network, an internet service provider network, and a leased line network.
[0027] In one embodiment, the network transformation system (120) automatically identifies a particular API standard that the service provider uses in the associated service provider network (116), as described subsequently in detail with reference to FIGS. 2A-C. Examples of the particular API standard that the service provider may be using in the associated service provider network (116) include an open application programming interface (OpenAPI), simple object access protocol (SOAP), network configuration protocol (NETCONF), representational state transfer configuration protocol (RESTCONF), TM Forum, or any other proprietary vendor standard.
[0028] Moreover, the network transformation system (120) receives a notification message from the orchestrator platform (118) when the user deploys the network function (106A) using the northbound system (104). The term “orchestrator platform (118)” described herein throughout various embodiments of the present disclosure refers to a platform that is used for intent driven deployment and management of one or more of the network functions (106A-N). Upon receiving the notification message from the orchestrator platform (118), the network transformation system (120) retrieves a set of information associated with the deployed network function (106A) from an associated network function descriptor stored previously in the orchestrator platform (118). For example, the network transformation system (120) may use the network function descriptor to identify the vendor who has deployed the network function (106A), a version of the deployed network function (106A), and/or a type of the deployed network function (106A) that indicates a specific type of network service that the deployed network function (106A) provides to different entities such as end users or customers. The network transformation system (120) may also use the network function descriptor to identify if the network function (106A) is a new network function or an updated version of a previously deployed network function.
[0029] In addition, the network transformation system (120) also automatically identifies if the network function (106A) deployed by the user natively supports any API standard by transmitting one or more API requests to the network function (106A), as described in detail with reference to FIGS. 2A-C. When the network transformation system (120) identifies that the network function (106A) does not natively support any of API standards, the network transformation system (120) automatically identifies a current configuration information of the network function (106A) by transmitting a personalized command to the network function (106A), as described subsequently in detail with reference to FIGS. 2A-C.
[0030] Additionally, the network transformation system (120) generates and transmits a plurality of additional commands including a set of test commands to identify all features that are available in the network function (106A). For example, when the network function (106A) deployed by the user corresponds to the virtual firewall (VF) network function (106A), the network transformation system (120) generates a first test command that is used to test if the VF network function (106A) supports a “network address translation (NAT) policies” feature. Subsequently, the network transformation system (120) transmits the generated first test command to the VF network function (106A). Based on a response to the first test command received from the VF network function (106A), the network transformation system (120) identifies if the VF network function (106A) supports “NAT Policies” feature allowing dynamic update of firewall rules, as described in detail with reference to FIGS. 2A-C.
[0031] In another example, the network transformation system (120) generates and transmits a second test command to the VF network function (106A) for testing and identifying if the VF network function (106A) supports a “quality of service (QoS) policies” feature. Based on a response to the second test command received back from the VF network function (106A), the network transformation system (120) identifies if the VF network function (106A) supports the “QoS Policies” feature that allows for dynamic addition of new firewall rules. Similarly, it is to be understood that the network transformation system (120) generates and transmits a plurality of other additional test commands to test and identify all other features that are available in the network function (106A).
[0032] Moreover, the network transformation system (120) automatically generates an API request handler (123) including a software package based on the identified features of the network function (106A) and the particular API standard that the service provider uses in the associated service provider network (116). In one embodiment, the API request handler (123) is the software package that enables the network function (106A) to identify one or more services requested by one or more end users without needing to generate any custom APIs. For example, the network transformation system (120) generates the API request handler (123) in accordance with OpenAPI standard when the particular API standard that the service provider uses in the associated service provider network (116) corresponds to the OpenAPI standard. In another example, the network transformation system (120) generates the API request handler (123) in accordance with TM Forum standard when the service provider network (116) uses the TM Forum standard. Further, the network transformation system (120) deploys the API request handler (123) including the software package in the network function (106A).
[0033] In certain embodiments, the API request handler (123), thus deployed in the network function (106A), provides an API support to the network function (106A) that does not natively support any API standards. Post deploying the API request handler (123), the API request handler (123) may receive an API service request as an input from one or more of the previously deployed network functions (106B-N), network applications, the orchestrator platform (118), the northbound system (104), the network transformation system (120), the service provider network (116), and the service provider device (102). From the received API service request, the API request handler (123) identifies a specific service requested by a user. In addition, the API request handler (123) also identifies a set of commands in the network function (106A) that needs to be executed in order to provide the specific service to the user. The network function (106A) then executes the set of commands identified by the API request handler (123), and provides the specific service to the user, as described in greater detail with reference to FIGS. 2A-C.
[0034] In certain embodiments, the network function (106A) deployed by the user may support a particular API standard that is different from an API standard used by the service provider in the associated service provider network (116). For example, the network function (106A) deployed by the user may support TM Forum standard. However, the service provider may use OpenAPI standard in the associated service provider network (116). In such a scenario, the network transformation system (120) automatically generates a customized API wrapper (126) that includes a software package, for example using Tata Elxsi’s proprietary NeuronTM platform or the Kong API platform. Further, the network transformation system (120) deploys the generated customized API wrapper (126) in the network function (106A). The customized API wrapper (126), thus deployed in the network function (106A), acts as an API translator. When an API service request is received, for example, in OpenAPI standard from the service provider device (102) while the network function (106A) is using the TM Forum standard, the customized API wrapper (126) converts the API service request received in the OpenAPI standard to the TM Forum standard. In one embodiment, the customized API wrapper (126) converts the API service request to the TM Forum standard by parsing and validating the API service request, and further by mapping OpenAPI fields in the API service request to TM Forum data models. Conversion of the API service request from the OpenAPI standard to the TM Forum standard provides the capability to the network function (106A) to identify a specific service that is requested from the network function (106A) by a user. Conversion of the API service request to the TM Forum standard also enables the network function (106A) to execute specific set of commands related to the specific service requested by the user, and thereby provide the specific service to the user. Thus, even when the network function (106A) supports only a particular API standard that is different from the API standard used by the service provider or the network function (106A) does not completely support any API standard, the network transformation system (120) still transforms the network function (106A) into an API supported network function (106A).
[0035] In one embodiment, the digital transformation system (100) and the associated systems including the northbound system (104), virtual infrastructure manager (108), computing system (110), storage system (112), networking system (114), service provider network (116), orchestrator platform (118), and network transformation system (120), for example, may include one or more of general-purpose processors and specialized processors. In certain embodiments, the digital transformation system (100), northbound system (104), virtual infrastructure manager (108), computing system (110), storage system (112), networking system (114), service provider network (116), orchestrator platform (118), and network transformation system (120) may include one or more of graphical processing units, microprocessors, programming logic arrays, field programming gate arrays, integrated circuits, system on chips, and/or other suitable computing devices. Additionally, certain operations of the digital transformation system (100), northbound system (104), virtual infrastructure manager (108), computing system (110), storage system (112), networking system (114), service provider network (116), orchestrator platform (118), and network transformation system (120) may be implemented by suitable code on a processor-based system, such as a general-purpose or a special-purpose computer. An exemplary method used for transforming an unsupported network function (106A) that lacks native API support into a supported network function (106A) is described in detail with reference to FIGS. 2A-C.
[0036] FIGS. 2A-C illustrate a flow diagram depicting an exemplary method (200) for transforming a network function (106A) that does not natively support any API standards into an API supported VF network function (106A) using the digital transformation system (100) of FIG. 1. FIGS. 2A-C specifically describe the method (200) for transforming a virtual firewall (VF) network function (106A) that does not natively support any API standards into an API supported VF network function (106A). However, it is to be understood that the method (200) can also be used for transforming any of API unsupported network functions (106A) into API supported network functions (106A). For example, the method (200) may be used for transforming an API unsupported 5G network function into a corresponding API supported network function. The term “API unsupported network function (106A)” used herein throughout various embodiments of the present disclosure refers to a network function that lacks ability to automatically interpret API service requests received from one or more network components and provide requested network services to different end users and/or entities. The term “API supported network function (106A)” refers to a network function that automatically interprets API service requests received from one or more network components and provides requested network services to different end users and/or entities. The order in which the exemplary method is described is not intended to be construed as a limitation, and any number of the described blocks may be combined in any order to implement the exemplary method disclosed herein, or an equivalent alternative method. Additionally, certain blocks may be deleted from the exemplary method or augmented by additional blocks with added functionality without departing from the claimed scope of the subject matter described herein.
[0037] At step (202), the network transformation system (120) identifies a particular API standard that the service provider uses in the associated service provider network (116). To that end, the network transformation system (120) is communicatively coupled to the service provider network (116) via the communications link (122). Further, the network transformation system (120) is provided with access to one or more network packets that a plurality of network components such as a router, firewalls, load balancers, and 5G cores in the service provider network (116) use for exchanging information among themselves. The network transformation system (120) accesses the network packets and identifies the particular API standard that the service provider uses in the associated service provider network (116) from the network packets. For example, the network transformation system (120) may access a network packet that is transmitted from the router to the 5G core of the service provider network (116). Further, the network transformation system (120) identifies that the service provider is using OpenAPI standard in the associated service provider network (116) from the network packet. At step (204), the northbound system (104) enables a user associated with the service provider to deploy the VF network function (106A) on top of the virtual infrastructure manager (108). As noted previously with reference to FIG. 1, the northbound system (104) includes one or more associated user interfaces. The northbound system (104) allows the user to login into the northbound system (104) via his or her user account with the northbound system (104) and further allows the user to deploy the VF network function (106A) via the associated user interfaces.
[0038] At step (206), the network transformation system (120) receives a notification message from the orchestrator platform (118) post deploying the VF network function (106A) on top of the virtual infrastructure manager (108). For example, the network transformation system (120) receives an exemplary notification message “{nf_id: a29e1822-2f34-4541-8e78-39c40082cf0c, operationState: DEPLOYED}” from the orchestrator platform (118) post the deployment of the VF network function (106A). In one embodiment, the notification message thus received by the network transformation system (120) indicates to the network transformation system (120) that the user has newly deployed certain network function (106A) on top of the virtual infrastructure manager (108).
[0039] At step (208), the network transformation system (120) fetches a set of information associated with the deployed VF network function (106A) from a corresponding network function descriptor stored previously in the orchestrator platform (118). For example, the network function descriptor includes the set of information related to the VF network function (106A) such as a name of the service provider who deployed the VF network function (106A), a version number of the VF network function (106A), and/or a type of the VF network function (106A) that indicates that the VF network function (106A) is for providing firewall related services to end customers. The network function descriptor may also include information that indicates if the VF network function (106A) is a new network function or an updated version of a previously VF network function. The network transformation system (120) fetches this set of information related to the VF network function (106A) from the associated network function descriptor.
[0040] At step (210), the network transformation system (120) automatically identifies if the VF network function (106A) natively supports any API standards. To that end, the network transformation system (120) stores a plurality of API commands in an associated API command database (124). For example, the network transformation system (120) stores the following exemplary API commands in the API command database (124) that are used to identify if the VF network function (106A) supports any API standards.

http:///tmf-api/v1/
http:///openapi/data/
http:///restconf/data/
http:///api/v1/
http:///restapi/
http:///v1/
http:///v1.0/
http:///api/v2/

[0041] In certain embodiments, the network transformation system (120) transmits one or more API commands selected from the plurality of API commands sequentially to the VF network function (106A) to identify if the deployed network function (106A) supports any API standard. For example, the network transformation system (120) first transmits a first API command “http:///tmf-api/v1/” selected from the plurality of API commands to the VF network function (106A). Further, the network transformation system (120) identifies that the VF network function (106A) natively supports TM Forum standard when the network transformation system (120) receives a first type of response from the VF network function (106A) in response to the first API command transmitted to the VF network function (106A). Examples of the first type of response that indicates to the network transformation system (120) that the VF network function (106A) natively supports an API standard include a first hypertext transfer protocol (HTTP) code “200”, a first extensible markup language (XML) response, or a first Javascript object notation (JSON) response.
[0042] Alternatively, the network transformation system (120) identifies that the VF network function (106A) does not support TM Forum standard when the network transformation system (120) receives a second type of response from the VF network function (106A) in response to the first API command transmitted to the VF network function (106A). Examples of the second type of response that indicates to the network transformation system (120) that the VF network function (106A) does not natively support an API standard include a second HTTP error code “404” or “405”, a second XML response, or a second JSON response.
[0043] When the network transformation system (120) identifies that the VF network function (106A) does not natively support TM Forum standard, the network transformation system (120) transmits a second API command “http:///openapi/data/” selected from the plurality of API commands to the VF network function (106A). Further, the network transformation system (120) identifies if the VF network function (106A) supports OpenAPI standard based on whether the first type of response or the second type of response is received back from the VF network function (106A) in response to the second API command transmitted to the VF network function (106A).
[0044] In an exemplary scenario, the network transformation system (120) identifies that the VF network function (106A) does not natively support OpenAPI standard either. In such a scenario, the network transformation system (120) may subsequently transmit all other API commands selected from the plurality of API commands sequentially to identify if the VF network function (106A) supports SOAP, NETCONF, RESTCONF, or any other vendor’s proprietary standard. For example, the network transformation system (120) may transmit a fourth API command that adheres to a proprietary API standard developed by a particular telecommunication vendor to the VF network function (106A). Further, the network transformation system (120) identifies if the VF network function (106A) supports the proprietary API standard developed by the particular telecommunication vendor depending upon a particular type of response corresponding to the first or second type of response received back from the VF network function (106A). Further, the network transformation system (120) transmits additional proprietary API commands to the VF network function (106A) sequentially when the network transformation system (120) identifies that the VF network function (106A) fails to natively support the proprietary API standard developed by the particular telecommunication vendor. The additional proprietary API commands correspond to commands that adhere to proprietary API standards developed by different telecommunication vendors. In addition, the network transformation system (120) identifies if the VF network function (106A) natively supports one of the other proprietary API standards based on the first or second type of responses received from the VF network function (106A).
[0045] At step (212), the network transformation system (120) transmits a personalized command to the VF network function (106A) and obtains an associated current configuration information when the VF network function (106A) is identified not to natively support any API standards. To that end, in one embodiment, the network transformation system (120) corresponds to a learning system such as a machine learning-based system, an artificial intelligence-based system, or a large language model-based system. The network transformation system (120) is previously trained to identify personalized commands to be transmitted to various network functions (106A-N) in order to obtain their configuration information based on training data, for example, including the type, version, and/or vendor information associated with a plurality of network functions (106A-N). Based on the prior training provided to the network transformation system (120), the network transformation system (120) automatically identifies that the personalized command to be transmitted to the VF network function (106A) in order to obtain the associated configuration information is “show running-config” when the VF network function (106A) corresponds to Cisco’s firewall network function. In another example, the network transformation system (120) identifies that the personalized command to be transmitted to the VF network function (106A) in order to obtain the associated configuration information is “show running” when the VF network function (106A) corresponds to Palo Alto’s firewall network function based on the prior training. Further, the network transformation system (120) transmits the identified personalized command to the VF network function (106A) and thereby obtains the associated current configuration information.
[0046] At step (214), the network transformation system (120) transmits one or more wildcard commands to the VF network function (106A) to identify all execution commands available in the VF network function (106A). Examples of the wildcard commands transmitted to the VF network function (106A) include manual and/or help wildcard commands. At step (216), the network transformation system (120) transmits a set of test commands to identify all features that are available in the VF network function (106A) when the VF network function (106A) is identified not to natively support any API standards. For example, the network transformation system (120) may transmit a first test command “show access-list” to the VF network function (106A) to identify if the VF network function (106A) supports a “security policy status provider” feature, which allows a user to check if associated firewall security policies are active. If the VF network function (106A) fails to respond back to the network transformation system (120) with a corresponding response that indicates a current status of the firewall security policies, the network transformation system (120) identifies that the VF network function (106A) does not support the “security policy status provider” feature.
[0047] However, if the VF network function (106A) provides a response that indicates the current status of the firewall security policies, the network transformation system (120) identifies that the VF network function (106A) supports the “security policy status provider” feature. For example, the VF network function (106A) may provide the following exemplary response to the network transformation system (120) upon receiving the first test command “show access-list” from the network transformation system (120).
“access-list outside_access_in extended permit tcp any host 192.168.1.1 eq 80
access-list outside_access_in extended deny ip any any”
[0048] In the previously noted example, the response received from the VF network function (106A) indicates to the network transformation system (120) that the VF network function (106A) currently includes active access control lists (ACLs) that permit only HTTP traffic to one or more specific hosts via a TCP port 80 and further deny all other traffic. The response specifically indicates to the network transformation system (120) that the firewall security policies are active such that the policies allow only HTTP traffic via the noted TCP port. Therefore, in the previously noted example, the network transformation system (120) identifies that the VF network function (106A) supports the “security policy status provider” feature.
[0049] In another example, the network transformation system (120) may identify if the VF network function (106A) supports a “NAT Policy” feature, which allows a user to dynamically configure or update NAT policies in the VF network function (106A). To that end, the network transformation system (120) may transmit an exemplary second test command “show configuration security NAT static” to the VF network function (106A). In one embodiment, the second test command indicates to the VF network function (106A) that the VF network function (106A) needs to list the associated NAT policies. When the VF network function (106A) supports the “NAT policy” feature, the VF network function (106A) lists the associated NAT policies based on the second test command received from the network transformation system (120). Further, the VF network function (106A) transmits a confirmation message to the network transformation system (120), which confirms listing of the NAT policies by the VF network function (106A). Thus, based on the confirmation message received from the VF network function (106A), the network transformation system (120) identifies that the VF network function (106A) supports the “NAT Policy” feature.
[0050] Alternatively, when the VF network function (106A) does not support the “NAT Policy” feature, the VF network function (106A) may not list the associated NAT policies and may not share back the confirmation message with the network transformation system (120). Accordingly, the network transformation system (120) identifies that the VF network function (106A) does not support the “NAT Policy” feature when the network transformation system (120) fails to receive the confirmation message back from the VF network function (106A).
[0051] In yet another example, the network transformation system (120) may identify if the VF network function (106A) supports a “firewall rules addition” feature, which allows a user to dynamically add new firewall rules of the VF network function (106A). To that end, the network transformation system (120) may transmit an exemplary third test command “access-list outside_access_in extended?” to the VF network function (106A). In one embodiment, the third test command provides configuration options such as HTTP protocol configuration, SSH protocol configuration, and/or port configuration 80/22 to the VF network function (106A) to add a new firewall rule. When the VF network function (106A) supports the “firewall rules addition” feature, the VF network function (106A) responds to the network transformation system (120) with a confirmation message that indicates denial or permitting of the configuration options by the VF network function (106A). Based on the confirmation message received from the VF network function (106A), the network transformation system (120) identifies that the VF network function (106A) supports the “firewall rules addition” feature.
[0052] Alternatively, when the VF network function (106A) does not support the “firewall rules addition” feature, the VF network function (106A) may not share back the confirmation message with the network transformation system (120). Accordingly, the network transformation system (120) identifies that the VF network function (106A) does not support the “firewall rules addition” feature when the network transformation system (120) fails to receive the confirmation message back from the VF network function (106A). It is to be understood that the network transformation system (120) similarly transmits a plurality of other test commands. Based on the confirmation messages received back from the VF network function (106A), the network transformation system (120) automatically identifies all the features that are available in the VF network function (106A).
[0053] At step (218), the network transformation system (120) maps all the identified features of the VF network function (106A) to appropriate execution commands available in the VF network function (106A). For example, the network transformation system (120) may map the “security policy status provider” feature of the VF network function (106A) to a first execution command in the VF network function (106A). Execution of the first execution command may allow a user to check if firewall security policies associated with the VF network function (106A) are active. In another example, the network transformation system (120) may map the “NAT policy” feature of the VF network function (106A) to a second execution command in the VF network function (106A). Execution of the second execution command may allow a user to dynamically configure NAT policies of the VF network function (106A). In yet another example, the network transformation system (120) may map the “firewall rules addition” feature of the VF network function (106A) to a third execution command in the VF network function (106A). Execution of the third execution command allows a user to dynamically add new firewall rules of the VF network function (106A). Similarly, the network transformation system (120) maps each of other features available in the VF network function (106A) to corresponding execution commands in the VF network function (106A).
[0054] At step (220), the network transformation system (120) automatically generates the API request handler (123) based on the features identified to be available in the VF network function (106A) and the particular API standard that the service provider uses in the associated service provider network (116). In one embodiment, the network transformation system (120) uses artificial intelligence, machine learning, generative artificial intelligence, and/or large language models (LLMs) for automatically generating the API request handler (123) based on the features of the VF network function (106A) and the particular API standard used by the service provider. For example, the network transformation system (120) may generate the API request handler (123) using LLMs in accordance with the OpenAPI standard when the service provider network (116) uses the OpenAPI standard. Further, the network transformation system (120) deploys the generated API request handler (123) in the VF network function (106A). In certain embodiments, the API request handler (123), thus deployed in the network function (106A), provides required API support to the network function (106A), which does not natively support any API standards.
[0055] At step (222), the service provider device (102) receives a new service request from a user device associated with an end user. For example, the new service request may specify that current firewall settings of his/her user device such as his/her gateway device allow only HTTP traffic and does not allow SSH traffic. The new service request may also specify that the end user wishes the VF network function (106A) to allow SSH traffic to his or her user device. In one embodiment, the user device may share this new service request from the end user with the service provider device (102), for example, via an email, a message, or a chatbot option provided by the service provider. Alternatively, the end user may directly dial a call center number operated by the service provider and place the new service request.
[0056] At step (224), the service provider device (102) converts the new service request received from the user device into a corresponding API service request and then transmits the API service request to the network transformation system (120). For example, the service provider device (102) converts the previously noted new service request from the end user that specifies that the end user intends to activate SSH traffic into a corresponding API service request using a business support system or customer relationship management system. Subsequently, the service provider device (102) transmits the API service request to the network transformation system (120).
[0057] At step (226), the network transformation system (120) identifies a specific service that is requested by the end user and further identifies if the VF network function (106A) is capable of providing the specific service to the end user based on the API service request received from the service provider device (102). For example, upon receiving the API service request from the service provider device (102), the network transformation system (120) identifies that the end user has requested the service provider to allow the SSH traffic to his/her user device. The network transformation system (120) also identifies that allowing the SSH traffic to the end user’s user device requires a dynamic addition of a new firewall rule. Subsequently, the network transformation system (120) identifies if the VF network function (106A) includes a feature that allows dynamic addition of the new firewall rule. Upon identifying that the VF network function (106A) includes the feature that allows dynamic addition of the new firewall rule, the network transformation system (120) identifies that the VF network function (106A) is capable of providing the specific service requested by the end user.
[0058] At step (228), the network transformation system (120) forwards the API service request received from the service provider device (102) to the VF network function (106A) only when the VF network function (106A) is identified to be capable of providing the specific service requested by the end user. It is to be noted that if the VF network function (106A) is an unsupported network function (106A) that does not natively support any API standards, the VF network function (106A) would conventionally fail to identify the specific service requested by the end user from the received API service request. This is because, the unsupported network function (106A) will fail to process the received API service request and identify the specific service requested by the end user due to lack of API support. In order to address the aforementioned issues, the present network transformation system (120) generates the API request handler (123), and deploys the generated API request handler (123) in the VF network function (106A). The API request handler (123), thus deployed in the VF network function (106A), acts as the API request interpreter and provides the necessary API support for the VF network function (106A), thereby converting the unsupported VF network function (106A) into an API supported VF network function (106A). Specifically, the API request handler (123) enables the VF network function (106A) to identify the specific service requested by the user from the API service request received from the network transformation system (120).
[0059] At step (230), the API request handler (123) deployed in the VF network function (106A) identifies a specific execution command in the VF network function (106A) that needs to be executed in order to provide the specific service requested by the end user. To that end, the API request handler (123) first identifies a particular feature in the VF network function (106A) that is related to the service request requested by the user. The API request handler (123) then identifies an execution command that is already mapped to the identified feature. Subsequently, the API request handler (123) determines the identified execution command as the specific command that needs to be executed in order to provide the specific service requested by the end user. For example, with respect to the previously noted example, the API request handler (123) first identifies a feature that is related to the user’s service request is “firewall rules addition” feature in the VF network function (106A). The API request handler (123) then identifies an execution command, for example, the execution command “access-list outside_access_in extended permit tcp any any eq 22”, which is already mapped to the “firewall rules addition” feature. The API request handler (123) then determines the identified execution command “access-list outside_access_in extended permit tcp any any eq 22” as the specific command that needs to be executed in order to provide the specific service for allowing the SSH traffic to the end user’s user device as requested by the end user. At step (232), the VF network function (106A) executes the specific command identified by the API request handler (123), and thereby automatically provides the specific service requested by the end user. For example, the VF network function (106A) executes the specific command “access-list outside_access_in extended permit tcp any any eq 22” identified by the API request handler (123), which enables the VF network function (106A) to automatically permit the SSH traffic to the user device of the end user via the TCP port 22.
[0060] In one embodiment, the VF network function (106A) requests the user device to share information related to bandwidth available to the user device prior to executing the specific command “access-list outside_access_in extended permit tcp any any eq 22.” In one embodiment, the VF network function (106A) executes the specific command and permits the SSH traffic to the user device only when the bandwidth available to the user device is more than a designated threshold. Otherwise, the VF network function (106A) does not execute the specific command and denies the SSH traffic to the user device when the bandwidth available to the user device is lesser than the designated threshold.
[0061] Thus, the API request handler (123) deployed in the VF network function (106A) helps the VF network function (106A) in identifying the specific service requested by the end user, and the specific command that needs to be executed in order to provide the specific service requested by the end user without requiring development of a custom API. In absence of the present API request handler (123) generated and deployed in the VF network function (106A), the VF network function (106A) that does not natively support an API standard will fail to identify the specific service requested by the end user. Further, the VF network function (106A) will fail to identify the specific command that needs to be executed in order to provide the specific service requested by the end user. The API request handler (123) provides the VF network function (106A) the capability to identify specific services requested by different end users and provide those services to the end users, and thereby converts the VF network function (106A) that does not natively support any API standard into the API supported VF network function (106A).
[0062] In an alternative scenario, a VF network function (106B) previously deployed on top of the virtual infrastructure manager (108) by the user may natively support a specific API standard. However, the specific API standard supported by the VF network function (106B) may be different from the particular API standard that the service provider uses in the associated service provider network (116). For example, the VF network function (106B) may support the OpenAPI standard, whereas the service provider may be using the TM Forum standard in the associated service provider network (116). In the previously noted example, the end user may place a new service request with the service provider device (102). The service provider device (102) then converts the new service request into an API service request in accordance with the TM Forum standard as the service provider device (102) supports only the TM Forum standard. Subsequently, the service provider device (102) transmits the API service request generated according to the TM Forum standard to the VF network function (106B) that supports the OpenAPI standard. However, the VF network function (106B) may not be able to identify a specific service that is requested by the end user from the API service request generated according to the TM Forum standard as the VF network function (106B) only understands the API service request generated according to the OpenAPI standard. Therefore, in such a scenario, the VF network function (106B) may not able to typically provide the specific service requested by the end user.
[0063] In order to address the aforementioned issues, the present network transformation system (120) automatically generates a customized API wrapper (126). In one embodiment, the network transformation system (120) generates the customized API wrapper (126), for example, using the Tata Elxsi proprietary “Neuron” platform or using the Kong API platform. Further, the network transformation system (120) deploys the customized API wrapper (126) in the VF network function (106B). The customized API wrapper (126), thus deployed in the VF network function (106B), includes a software package that acts as an API translator. In one example, the VF network function (106B) that supports the OpenAPI standard may initially receive the API service request in the TM Forum standard from the service provider device (102). The customized API wrapper (126) deployed in the VF network function (106B) automatically converts the API service request received in the TM Forum standard to the OpenAPI standard. Further, the customized API wrapper (126) provides the API service request converted to the OpenAPI standard as an input to the VF network function (106B) such that the VF network function (106B) is able to identify the specific service requested by the end user. Furthermore, the VF network function (106B) selects a specific command from a plurality of associated stored commands that needs to be executed in order to provide the specific service requested by the end user from a native API support associated with the VF network function (106B). Subsequently, the VF network function (106B) executes the specific command and automatically provides the end user with the specific service requested by the end user. The customized API wrapper (126), thus allows the VF network function (106B) to interact with various components (102, 104, 118, 120, and 116) of the digital transformation system (100) and fulfill service needs of end users even when the VF network function (106B) uses an API standard that is different from the desired API standard that the service provider uses in the associated service provider network (116).
[0064] In certain embodiments, the network transformation system (120) does not enable the network function (106A) to fulfill all service requests received from end users in all scenarios. Instead, the network transformation system (120) first identifies performance metrics of the network function (106A) and further determines if the network function (106A) is capable of handling any new service requests received from the end users. The network transformation system (120) allows the network function (106A) to provide the services requested by the end users only when the performance metrics of the network function (106A) is above a designated threshold.
[0065] For example, a network engineer associated with the service provider newly deploys a Unified Data Repository (UDR) network function (106A) that does not natively support any API standard. In the previously noted example, the network transformation system (120) generates the API request handler (123) based on the features that are available in the UDR network function (106A) and the particular API standard that the service provider uses in the associated service provider network (116), as noted previously in detail with reference to FIGS. 2A-C. Subsequently, the network transformation system (120) deploys the API request handler (123) in the UDR network function (106A) such that the UDR network function (106A) supports the particular API standard and further provides requested services to end users.
[0066] In certain embodiments, the API request handler (123), thus deployed in the UDR network function (106A), enables the network engineer to selectively enable or disable one or more features of the UDR network function (106A). Further, the API request handler (123) allows the network transformation system (120) to query the UDR network function (106A) and obtain a set of information related to the UDR network function (106A). For example, the API request handler (123) allows the network transformation system (120) to query and obtain performance metrics, license capacity, and resources availability details associated with the UDR network function (106A). Examples of the resources availability details include central processing unit (CPU) availability, memory availability, network bandwidth availability, and disk input/output and storage availability.
[0067] In another example, an end user located at a particular radio access network (RAN) site may need a specific service from the UDR network function (106A). Specifically, the end user needs a video conferencing feature to be enabled in his or her user device. In the previously noted example, the end user may share a new service request to the service provider device (102). Subsequently, the service provider device (102) converts the new service request into an API service request, and transmits the API service request to the network transformation system (120). Upon receiving the API service request, the network transformation system (120) identifies that the end user needs the video conferencing feature to be enabled in his or her user device from the received API service request.
[0068] Subsequently, the network transformation system (120) queries and obtains the set of information including performance metrics, license capacity, and/or details related to current availability of resources of the UDR network function (106A). The set of information, thus obtained by the network transformation system (120), indicates to the network transformation system (120) a number of end users at the RAN site who are all using the video conferencing feature, and a number of complaints related to video conference call quality raised in the past by those end users. When the number of such complaints related to the video conference call quality is greater than a designated threshold, the network transformation system (120) identifies that the quality of the video conference calls is already unsatisfactory at the particular RAN site. Accordingly, the network transformation system (120) blocks the API service request and does not enable the video conferencing feature in the user device of the end user. Alternatively, when the number of such complaints related to the video conference call quality is lesser than the designated threshold, the network transformation system (120) identifies that the quality of the video conference calls is satisfactory at the particular RAN site. Accordingly, the network transformation system (120) forwards the API service request to the UDR network function (106A). Subsequently, the UDR network function (106A) enables the video conferencing feature in the user devices of the end user based on the API service request received from the network transformation system (120).
[0069] Generally, a telecommunication service provider and/or a network service provider periodically updates an older version of the network function (106A) previously deployed by them by modifying existing features in the network function (106A) and/or by introducing new features into the network function (106A). However, once updates are made to the network function (106A), the API support available with the older version of the network function (106A) is no longer valid for an upgraded version of the network function (106A).
[0070] It may be noted that conventional automated network solutions do not automatically update API support available to an existing network function when the existing network function is upgraded to a newer version. Further, conventional automated network solutions allow only the service provider to automatically create and deploy a new network function that natively supports an API standard. Such conventional automated network solutions do not transform the existing network function (106A) or the newly deployed network function (106A) that does not natively support any API standards into the API supported network function.
[0071] In contrast, the present network transformation system (120) automatically updates the API support available with the older version of the network function (106A) by updating the associated API request handler (123) in order to provide adequate API support to the upgraded version of the network function (106A) without requiring manual intervention. For example, a network engineer associated with a service provider deploys the network function (106A) that does not natively support any API standard. In this example, the network transformation system (120) generates and deploys the API request handler (123) in the network function (106A), and thereby provides a required API support to the network function (106A), as described in detail previously with reference to FIGS. 2A-C. However, when the network function (106A) is upgraded to a newer version, the API request handler (123) associated with an older version of the network function (106A) is no longer valid for the upgraded version of the network function (106A). The network transformation system (120) needs to automatically update the API request handler (123) to provide an adequate API support to the upgraded version. To that end, the network transformation system (120) receives a notification message from the orchestrator platform (118) when the telecommunication or network service provider deploys the upgraded version of the network function (106A) on top of the virtual infrastructure manager (108). The network transformation system (120) then transmits the set of test commands to the updated or upgraded network function (106A), as described previously with reference to FIGS. 2A-2C. Based on responses received back from the upgraded network function (106A), the network transformation system (120) identifies one or more features that are newly added and/or one or more features in the older version of the network function (106A) that are modified in the upgraded network function (106A).
[0072] Further, the network transformation system (120) automatically replaces the API request hander associated with the older version of the network function (106A) with a new or an updated API request handler (123) generated based on the newly added features and/or the modified features. Furthermore, the network transformation system (120) deploys the updated API request hander in the upgraded network function (106A) to provide an updated API support to the upgraded network function (106A), thereby allowing the upgraded network function (106A) to provide new and enhanced services to end users via the newly added and/or modified features of the upgraded network function (106A). Transforming the API unsupported network function (106A) to the API supported network function enables the service provider to provide the services requested by end users in an expedited manner.
[0073] In certain embodiments, there are certain network functions that are developed by network function vendors such as Huawei, Ericsson, Cisco, and Samsung include native API supports. However, such network functions developed by the network function vendors do not necessarily use the same API standard that a service provider uses in the associated service provider network (116). For example, a network function (106B) developed and deployed by a network function vendor in a virtual infrastructure manager (108) may natively support a particular API standard that is different from a desired API standard that the service provider uses in the associated service provider network (116). In this example, the network transformation system (120) generates and deploys the customized API wrapper (126) into the network function (106B), which provides abilities to the network function (106B) to provide requested services to various end users, as noted previously. When the network function vendor updates the network function (106B) to a newer version after a designated period of time, the network function vendor by default also updates a native API support available with an older version of the network function (106B). Updating and providing an updated native API support to the upgraded network function (106B) by the network function vendor ensures that the upgraded network function (106B) can continue to use the same customized API wrapper (126) associated with the older version of the network function (106B) for providing services requested by the end users. However, when the network function vendor fails to update the native API support while updating the network function (106B), the digital transformation system (100) is configured to treat the upgraded network function (106B) as an unsupported network function (106B). In this exemplary scenario, the digital transformation system (100) generates and deploys a requisite new API request handler (123) in the upgraded network function (106B) based on an access to the upgraded network function (106B) provided by the network function vendor such that the new API request handler (123) provides the updated API support to the upgraded network function (106B).
[0074] In certain other embodiments, there are certain network functions that are deployed by service providers or network function vendors come with native API supports that are same as the desired API standard that the service provider uses in the associated service provider network (116). For example, a second designated network function (106C) deployed by a service provider or a network function vendor may natively support a particular API standard that is same as the desired API standard. In this example, the digital transformation system (100) neither requires the API request handler (123) nor the customized API wrapper (126) to be generated and deployed in the network function (106C) as the existing network function (106C) itself includes a requisite API support. When the network function vendor upgrades the network function (106C) to a newer version, the network function vendor if applicable also updates the API support available with an older version of the network function (106C) for enabling the upgraded network function (106C) to provide services requested by the end users. However, when the network function vendor fails to update the native API support while updating the network function (106C), the digital transformation system (100) is configured to treat the upgraded network function (106C) as an unsupported network function (106C). Further, the digital transformation system (100) generates and deploys a requisite new API request handler (123) in the upgraded network function (106C) based on an access to the upgraded network function (106C) provided by the service provider or network function vendor for providing the updated API support to the upgraded network function (106C).
[0075] Although specific features of various embodiments of the present systems and methods may be shown in and/or described with respect to some drawings and not in others, this is for convenience only. It is to be understood that the described features, structures, and/or characteristics may be combined and/or used interchangeably in any suitable manner in the various embodiments shown in the different figures.
[0076] While only certain features of the present systems and methods have been illustrated and described herein, many modifications and changes will occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes.

LIST OF NUMERAL REFERENCES:

100 Digital transformation system
102 Service provider device
104 Northbound system
106A-N Network functions
108 Network infrastructure manager
110 Computing system
112 Storage system
114 Networking system
116 Service provider network
118 Orchestrator platform
120 Network transformation system
122 Communications link
123 API request handler
124 API command database
126 Customized API wrapper
200-232 Steps of a method for transforming an API unsupported network function into an API supported network function
, Claims:We claim:

1. A method for providing one or more network services to one or more entities, comprising:
transmitting one or more application programming interface commands stored in an application programming interface command database (124) from a network transformation system (120) to a selected network function (106A) deployed in a network infrastructure manager (108) that is communicatively coupled to the network transformation system (120);
determining if the selected network function (106A) natively supports any particular application programming interface standard by the network transformation system (120) based on one or more responses received from the selected network function (106A) in response to the one or more application programming interface commands;
identifying a desired application programming interface standard associated with a service provider network (116) that needs to be supported by the selected network function (106A) for providing one or more specific services requested by the one or more entities;
automatically generating and deploying an application programming interface request handler (123) in the selected network function (106A) to transform the selected network function (106A) into a supported network function (106A) upon determining that the selected network function (106A) is an unsupported network function (106A) that does not natively support any particular application programming interface standard, wherein the application programming interface request handler (123) is generated based on one or more features that are available in the selected network function (106A) and corresponding execution commands, and the desired application programming interface standard associated with the service provider network (116);
automatically identifying the one or more specific services requested by the one or more entities via the application programming interface request handler (123) deployed in the supported network function (106A); and
automatically providing the one or more specific services requested by the one or more entities by the network function (106A) supported by the application programming interface request handler.

2. The method as claimed in claim 1, wherein determining if the selected network function (106A) natively supports any particular application programming interface standard comprises:
determining that the selected network function (106A) natively supports a particular application programming interface standard that is different from the desired application programming interface standard associated with the service provider network (116); and
automatically generating and deploying a customized application programming interface wrapper (126) in the selected network function (106A) that translates one or more application programming interface service requests received from a service provider device (102) in the desired application programming interface standard to the particular application programming interface standard for enabling the network function (106A) to identify and provide the one or more specific services requested by the one or more entities.

3. The method as claimed in claim 2, wherein identifying the desired application programming interface standard comprises monitoring one or more network packets exchanged between a plurality of network components associated with the service provider network (116).

4. The method as claimed in claim 3, wherein determining if the selected network function (106A) natively supports any particular application programming interface standard comprises:
transmitting the application programming interface commands sequentially from the network transformation system (120) to the selected network function (106A) to determine if the selected network function (106A) supports any application programming interface standard, wherein each of the application programming interface commands adheres to a different application programming interface standard;
determining that the selected network function (106A) natively supports a specific application programming interface standard when the network transformation system (120) receives a first type of response in response to a specific application programming interface command transmitted to the selected network function (106A), wherein the specific application programming interface command adheres to the specific application programming interface standard; and
determining that the selected network function (106A) does not natively support any application programming interface standard when the network transformation system (120) receives a second type of response in response to each of the application programming interface commands transmitted to the selected network function (106A), wherein the second type of response is different from the first type of response.

5. The method as claimed in claim 1, wherein automatically generating and deploying the application programming interface request handler (123) in the selected network function (106A) comprises:
fetching information corresponding to one or more of a vendor, a version, and a specific type of the selected network function (106A) from a corresponding network function descriptor stored previously in an orchestrator platform (118);
identifying a personalized command that is used to obtain a current configuration information of the selected network function (106A) from a plurality of commands stored in the application programming interface command database (124) based on one or more of the vendor, the version, and the specific type of the selected network function (106A) fetched from the corresponding network function descriptor; and
transmitting the identified personalized command from the network transformation system (120) to the selected network function (106A), and thereby obtaining the current configuration information of the selected network function (106A) by the network transformation system (120).

6. The method as claimed in claim 1, wherein automatically generating and deploying the application programming interface request handler (123) in the selected network function (106A) comprises:
transmitting one or more test commands from the network transformation system (120) to the selected network function (106A) to test and identify one or more features that are available in the selected network function (106A);
transmitting one or more wildcard commands from the network transformation system (120) to the selected network function (106A) to identify a plurality of execution commands available in the selected network function (106A);
mapping each of the features identified to be available in the selected network function (106A) to a corresponding execution command selected from the plurality of execution commands; and
automatically generating the application programming interface request handler (123) by the network transformation system (120) based on the one or more features that are identified to be available in the selected network function (106A) and corresponding mapped execution commands, and the desired application programming interface standard associated with the service provider network (116).

7. The method as claimed in claim 6, wherein automatically generating and deploying the application programming interface request handler (123) in the selected network function (106A) comprises:
transmitting the one or more test commands from the network transformation system (120) to the selected network function (106A) upon update of the selected network function (106A);
automatically identifying one or more of a feature that is newly added and a feature that is modified in the updated network function (106A) based on one or more responses received back from the updated network function (106A) in response to the transmitted test commands;
updating the application programming interface request handler (123) associated with the selected network function (106A), thereby generating an updated application programming interface request handler (123) based on identification of one or more of the feature that is newly added and the feature that is modified in the updated network function (106A); and
deploying the updated application programming interface request handler (123) in the updated network function (106A) to provide updated application programming interface support to the updated network function (106A).

8. The method as claimed in claim 7, wherein automatically providing the one or more specific services requested by the one or more entities comprises:
receiving a service request from a user device associated with an end user at a service provider device (102) associated with a service provider;
converting the service request into an application programming interface service request that adheres to the desired application programming interface standard associated with the service provider network (116);
transmitting the application programming interface service request from the service provider device (102) to the network transformation system (120) via a communications link (122);
identifying a specific service requested by the end user from the application programming interface service request received from the service provider device (102) by the network transformation system (120);
identifying if a particular feature selected from the one or more features available in the selected network function (106A) that allows the selected network function (106A) to provide the specific service requested by the end user;
forwarding the application programming interface service request from the network transformation system (120) to the selected network function (106A) only when the particular feature is available in the selected network function (106A);
identifying the specific service requested by the end user by the selected network function (106A) that is the unsupported network function (106A) and does not natively support any particular application programming interface standard using the application programming interface request handler (123);
identifying a specific execution command that is mapped to the particular feature that allows the selected network function (106A) to provide the specific service requested by the end user; and
executing the identified specific command for automatically providing the specific service requested by the end user to the end user.

9. The method as claimed in claim 1, wherein automatically generating and deploying the application programming interface request handler (123) comprises generating a new application programming interface request handler (123) upon update of the selected network function (106A), wherein the selected network function (106A) is one of a network function (106A) that natively supports an application programming interface standard that is different from the desired application programing interface standard and a network function (106C) that natively supports an application programming interface standard that is same as the desired application programing interface standard.

10. The method as claimed in claim 2, wherein automatically generating and deploying the application programming interface request handler (123) comprises deploying an updated native application programming interface adhering to the particular application programming interface standard along with the customized application programming interface wrapper (126) in the selected network function (106A) upon update of the selected network function (106A) that natively supports the particular application programming interface standard that is different from the desired application programing interface standard.

11. The method as claimed in claim 2, wherein automatically providing the one or more specific services requested by the one or more entities comprises:
receiving a service request from a user device associated with an end user by a service provider device (102) associated with a service provider;
converting the service request into an application programming interface service request that adheres to the desired application programming interface standard associated with the service provider network (116);
transmitting the application programming interface service request from the service provider device (102) to the selected network function (106A) that natively supports the particular application programming interface standard that is different from the desired application programming interface standard associated with the service provider via a communications link (122);
translating the application programming interface service request adhering to the desired application programming interface standard to the particular application programming interface standard using the customized application programming interface wrapper (126) deployed in the selected network function (106A);
identifying a specific service requested by the end user from the application programming interface service request translated to the particular application programming interface standard;
identifying a specific command from a plurality of commands that the selected network function (106A) needs to execute in order to provide the specific service requested by the end user from a native application programming interface associated with the selected network function (106A); and
executing the specific command and thereby automatically providing the specific service to the end user by the selected network function (106A).

12. A digital transformation system (100) for providing one or more services to one or more entities, comprising:
a network infrastructure manager (108) that hosts a plurality of network functions (106A-N);
a northbound system (104) that is communicatively coupled to the network infrastructure manager (108) via a communications link (122) and configured to enable deployment of a selected network function (106A) on top of the network infrastructure manager (108); and
a network transformation system (120) comprising an application programming interface command database (124) that is communicatively coupled to the network infrastructure manager (108) and the northbound system (104) via the communications link (122), wherein the network transformation system (120) is configured to:
transmit one or more application programming interface commands stored in the application programming interface command database (124) to the selected network function (106A) deployed in the network infrastructure manager (108);
determine if the selected network function (106A) natively supports any particular application programming interface standard based on one or more responses received from the selected network function (106A) in response to the one or more application programming interface commands;
identify a desired application programming interface standard associated with a service provider network (116) that needs to be supported by the selected network function (106A) for providing one or more specific services requested by the one or more entities; and
automatically generate and deploy an application programming interface request handler (123) in the selected network function (106A) to transform the selected network function (106A) into a supported network function (106A) upon determining that the selected network function (106A) is an unsupported network function (106A) that does not natively support any particular application programming interface standard, wherein the application programming interface request handler (123) is generated based on one or more features that are available in the selected network function (106A) and corresponding execution commands, and the desired application programming interface standard associated with the service provider network (116); and
wherein the supported network function (106A) automatically identifies the one or more specific services requested by the one or more entities via the API request handler (123), and provides the one or more specific services requested by the one or more entities.

13. The digital transformation system (100) as claimed in claim 12, wherein the network transformation system (120) is implemented as one of a standalone system and a subsystem within one or more of the northbound system (104), the service provider network (116), and an orchestrator platform (118) deployed in one of a telecommunications network, a connected vehicle network, a connected healthcare network, an internet-of-things network, a cloud service providing network, an internet service provider network, and a leased line network.