FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR OPTIMISING A NETWORK
PROCEDURE”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR OPTIMISING A NETWORK
PROCEDURE
FIELD OF THE DISCLOSURE
[0001] The present disclosure relates generally to the field of wireless communication systems. More particularly, the present disclosure relates to methods and systems for optimising a network procedure.
BACKGROUND
[0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. Third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless

communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] In the existing solutions, the process of firing multiple service provisioning requests to onboard enterprise services in 4G IP Multimedia System (IMS) network pertaining to a single or multiple telecom circles for an enterprise at a Business Telephony Application Server (BTAS) located at multiple circles is carried out by network provisioning nodes. The service provisioning request may be a request by which the enterprises or customers request a particular service or resource allocation from the network. This approach possesses significant shortcomings and limitations. Firstly, the onboarding of enterprise service provisioning is a cumbersome process that requires substantial time and effort. The provisioning nodes must know the exact topology of the network in order to decide the circle(s) and BTAS node instances individually, to which particular provisioning data is required to be sent. In case, if a particular BTAS network node instance is unavailable due to reasons like IP fluctuation, how and when to retry for the same request needs to be addressed. Also, if the network grows (e.g. new BTAS node instances are added), network provisioning nodes need to keep track of all this information in order to replicate the provisioning request data consistently. So, provisioning mechanism at all these BTAS network node instances at a single time is prone to errors, delays, and inconsistencies, leading to inefficient service provisioning. Moreover, as the number of services chosen by an enterprise increase, the complexity of the process escalates, further exacerbating the inefficiencies. Therefore, there exists a need for an improved method or system that addresses these shortcomings and automates the process of firing service provisioning requests, enhancing efficiency and accuracy in the telephony application server.
[0005] Further, over the period of time various solutions have been developed to improve the performance of communication devices and to optimise network procedures. However, there are certain challenges with existing solutions. Onboarding of enterprise services at multiple circles involves repetitive tasks that

are prone to human error, leading to potential mistakes and delays in the provisioning of services. Furthermore, the approach lacks efficiency and consistency. Each provisioning request needs to be checked at each location for execution success and resynced if any failures are observed further increasing the chances of inconsistencies in the process. This can result in delays, service disruptions, and customer dissatisfaction. Furthermore, as the number of services chosen by an enterprise increase, the complexity of the services onboarding process also grows. Managing a large volume of provisioning requests across multiple circles becomes increasingly challenging, leading to decreased scalability and operational difficulties. Also, the prior known solutions fail to incorporate automation into the service provisioning process. This absence of automated mechanisms limits the ability to streamline operations, reduce human intervention, and optimize resource allocation. Additionally, manually handling enterprise service provisioning requests increases the likelihood of errors, such as incorrect data entry or missing requests. These errors can lead to delays in the activation of services, negatively impacting the user experience and business operations.
[0006] Moreover, increase in clusters (nodes) in any location needs to be tracked every time and so provisioning consistency of on-boarding requests becomes a big task.
[0007] Thus, there exists an imperative need in the art for optimising a network procedure associated with a service request, which the present disclosure aims to address.
OBJECTS OF THE DISCLOSURE
[0008] Some of the objects of the present disclosure, which at least one implementation disclosed herein satisfies are listed herein below.

[0009] It is an object of the present disclosure to provide a system and a method for optimising a network procedure associated with a service request provisioning.
[0010] It is another object of the present disclosure to provide a solution that
5 verifies, the network service request data associated with the network.
[0011] It is yet another object of the present disclosure to provide a solution to
identify, a set of target specialised business telephony application servers (a set of
target BTAS) from one or more specialised business telephony application servers
10 (BTAS) associated with the network.
[0012] It is yet another object of the present disclosure to provide a solution to identify the network changes that are required to be adjusted for addition or deletion of new clusters into network. 15
[0013] It is yet another object of the present disclosure to provide a solution to identify target BTAS from the set of target BTAS for the network for a particular enterprise service onboarding.
20 [0014] It is yet another object of the present disclosure to provide a solution to
identify the available or unavailable BTAS and handle the onboarding services directed to them.
[0015] It is yet another object of the present disclosure to provide a solution to
25 identify BTAS that were unavailable and to resync with them the pending enterprise
service provisioning requests.
[0016] It is yet another object of present disclosure to provide efficient method to
do service provisioning request in parallel fashion towards BTAS node instances
30 wherever possible by improvising the BTAS circle deployment architecture in
5

which all BTAS instances in a particular circle shares common service provisioning database.
[0017] It is yet another object of the present disclosure to address all the
5 orchestration challenges and complexities which otherwise OSS/BSS entities need
to address.
SUMMARY
10 [0018] This section is provided to introduce certain aspects of the present disclosure
in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
15 [0019] An aspect of the present disclosure relates to a method for optimising a
network procedure. The method comprises receiving by a transceiver unit, a service
provisioning request from one or more nodes of a network, wherein the service
provisioning request comprises at least a network service request data. The method
further comprises retrieving, by a processing unit, a set of predefined data pre-
20 requisites based on the service provisioning request. The method further comprises
verifying, by the processing unit, the network service request data based on the set
of predefined data pre-requisites. The method further comprises identifying, by the
processing unit, a set of specialised business telephony application server (BTAS)
associated with the network based on at least the verified network service request
25 data. The method further comprises receiving, by the transceiver unit, an
availability status associated with one or more BTAS from the set of BTAS, wherein
the availability status associated with the one or more BTAS is one of a positive
availability response associated with said BTAS and a negative availability
response associated with said BTAS. The method further comprises identifying, by
30 the processing unit, a target BTAS from the set of BTAS based on the positive
availability response associated with the target BTAS. The method further
6

comprises transmitting, by the transceiver unit to the target BTAS, the network service request data based on the positive availability response. The method further comprises optimising, by the processing unit, the network procedure based on at least transmitting the network service request data to the target BTAS. 5
[0020] According to another aspect of the present disclosure, the verifying the network service request data by the processing unit is based on at least one predefined data pre-requisite from the set of predefined data pre-requisites.
10 [0021] According to another aspect of the present disclosure, generating at least
one of a success response and a failure response based the verifying the network service request data.
[0022] According to another aspect of the present disclosure, in an event of receipt
15 of the negative availability response, the method further comprises identifying by
the processing unit, the availability status associated with the one or more BTAS from the set of BTAS based on a heartbeat message.
[0023] According to another aspect of the present disclosure, the positive
20 availability response associated with the one or more BTAS is identified by the
processing unit in an event a successful response associated with the heartbeat
message is received by the transceiver unit from the one or more BTAS, and
wherein the negative availability response associated with the one or more BTAS
is identified by the processing unit in an event an unsuccessful response associated
25 with the heartbeat message is received by the transceiver unit from the one or more
BTAS.
[0024] Another aspect of the present disclosure may relate to a system for
optimising a network procedure. The system comprises a transceiver unit and a
30 processing unit connected to each other. The transceiver unit is configured to
receive, a service provisioning request from one or more nodes of a network,
7

wherein the service provisioning request comprises at least a network service
request data. Further, the processing unit is configured to retrieve, a set of
predefined data pre-requisites based on the service provisioning request. Further,
the processing unit is configured to verify the network service request data based
5 on the set of predefined data pre-requisites. Further, the processing unit is
configured to identify, a set of specialised business telephony application server (BTAS) associated with the network based on at least the verified network service request data. Further, the transceiver unit is further configured to receive, an availability status associated with one or more BTAS from the set of BTAS, wherein
10 the availability status associated with the one or more BTAS is one of a positive
availability response and a negative availability response. Further, the processing unit is configured to identify, a target BTAS from the set of BTAS based on the positive availability response associated with the target BTAS. Further, the transceiver unit is configured to transmit, to the target BTAS, the network service
15 request data based on the positive availability response. Further, the processing unit
is configured to optimise, the network procedure based on at least transmitting the network service request data to the target BTAS.
20 [0025] Another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing one or more instructions for optimising a network procedure. The storage medium comprising executable code which, when executed by one or more units of a system, causes the one or more units to perform certain functions. The executable code when executed causes a transceiver
25 unit of the system to receive, a service provisioning request from one or more nodes
of a network, wherein the service provisioning request comprises at least a network service request data. The executable code when executed further causes a processing unit of the system to retrieve, a set of predefined data pre-requisites based on the service provisioning request. The executable code when executed
30 further causes the processing unit of the system to verify the network service request
data based on the set of predefined data pre-requisites. The executable code when
8

executed further causes the processing unit of the system to identify, a set of
specialised business telephony application server (BTAS) associated with the
network based on at least the verified network service request data. The executable
code when executed further causes the transceiver unit of the system to receive, an
5 availability status associated with one or more BTAS from the set of BTAS, wherein
the availability status associated with the one or more BTAS is one of a positive availability response and a negative availability response. The executable code when executed further causes the processing unit of the system to identify, a target BTAS from the set of BTAS based on the positive availability response associated
10 with the target BTAS. The executable code when executed further causes the
transceiver unit to transmit, to the target BTAS, the network service request data based on the positive availability response. The executable code when executed further causes the processing unit of the system to optimise, the network procedure based on at least transmitting the network service request data to the target BTAS.
15
BRIEF DESCRIPTION OF DRAWINGS
[0026] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary implementations of the disclosed
20 methods and systems in which like reference numerals refer to the same parts
throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be
25 appreciated by those skilled in the art that disclosure of such drawings includes
disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0027] FIG.1 illustrates an exemplary block diagram of a system for optimising a
30 network procedure, in accordance with exemplary implementations of the present
disclosure.
9

[0028] FIG.2 illustrates an exemplary scenario block diagram for optimising a network procedure, in accordance with exemplary implementations of the present disclosure. 5
[0029] FIG.3 illustrates an exemplary method flow diagram indicating the process for optimising a network procedure, in accordance with exemplary implementations of the present disclosure.
10 [0030] FIG.4 depicts an exemplary diagram, depicting a scenario for optimising a
network procedure, in accordance with exemplary implementations of the present disclosure.
[0031] FIG.5 illustrates an exemplary block diagram of a computing device upon
15 which the features of the present disclosure may be implemented in accordance with
exemplary implementation of the present disclosure.
[0032] The foregoing shall be more apparent from the following more detailed description of the disclosure. 20
DETAILED DESCRIPTION
[0033] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of
25 implementations of the present disclosure. It will be apparent, however, that
implementations of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the
30 problems discussed above. Some of the problems discussed above might not be
fully addressed by any of the features described herein. Exemplary implementations
10

of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
5 [0034] The ensuing description provides exemplary implementations only, and is
not intended to limit the scope, applicability, or configuration of the disclosure.
Rather, the ensuing description of the exemplary implementations will provide
those skilled in the art with an enabling description for implementing an exemplary
implementation. It should be understood that various changes may be made in the
10 function and arrangement of elements without departing from the spirit and scope
of the disclosure as set forth.
[0035] It should be noted that the terms "mobile device", "user equipment", "user device", “communication device”, “device” and similar terms are used
15 interchangeably for the purpose of describing the disclosure. These terms are not
intended to limit the scope of the disclosure or imply any specific functionality or limitations on the described implementations. The use of these terms is solely for convenience and clarity of description. The disclosure is not limited to any particular type of device or equipment, and it should be understood that other
20 equivalent terms or variations thereof may be used interchangeably without
departing from the scope of the disclosure as defined herein.
[0036] Specific details are given in the following description to provide a thorough understanding of the implementations. However, it will be understood by one of
25 ordinary skill in the art that the implementations may be practiced without these
specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the implementations in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without
30 unnecessary detail in order to avoid obscuring the implementations.
11

[0037] Also, it is noted that individual implementations may be described as a
process which is depicted as a flowchart, a flow diagram, a data flow diagram, a
structure diagram, or a block diagram. Although a flowchart may describe the
operations as a sequential process, many of the operations can be performed in
5 parallel or concurrently. In addition, the order of the operations may be re-arranged.
A process is terminated when its operations are completed but could have additional steps not included in a figure.
[0038] The word “exemplary” and/or “demonstrative” is used herein to mean
10 serving as an example, instance, or illustration. For the avoidance of doubt, the
subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques
15 known to those of ordinary skill in the art. Furthermore, to the extent that the terms
“includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
20
[0039] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing
25 function/s, communicating with other user devices and transmitting data to the
other user devices. The user equipment may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low
30 Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance,
the user equipment may include, but not limited to, a mobile phone, smartphone,
12

virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure. 5
[0040] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor
10 (DSP), a plurality of microprocessors, one or more microprocessors in association
with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system
15 according to the present disclosure. More specifically, the processor is a hardware
processor.
[0041] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data
20 transfer are also expected to evolve and replace the older generations of
technologies. In the field of wireless data communications, the dynamic advancement of various generations of cellular technology are also seen. The development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourth generation (4G), and now fifth generation (5G),
25 and more such generations are expected to continue in the forthcoming time.
[0042] It is to be noted that a business telephony application server (BTAS) as used
herein, sometimes known in a telephony context only as a telephony application
server (TAS) or an application server (AS), is a generic collaborative framework to
30 rapidly develop and fulfil the service needs of enterprise and residential customers.
It is used in the core network of a telecom network operator to provide telephony
13

applications and additional multimedia functions for handling enterprise services.
It may also interact with core IP-Multimedia services (IMS) on an IMS Service
Control (ISC) interface to host cloud telephony services for enterprise customers.
The BTAS may also be a platform used for providing services such as SIP Trunk,
5 IP Centrex, toll-free calling, fixed mobile convergence, etc, and helps in routing the
calls based on a procedure which may be predefined or dynamic. IP Centrex is a
service where the functionalities of a PBX are simulated on the Cloud to provide a
highly scalable and cost-effective Enterprise voice communication solution. SIP
Trunk acts as a solution for an organization’s phone connections and its Internet
10 Telephony Service Provider.
[0043] As discussed in the background section, the current known solutions to
optimise network procedures have several shortcomings such as requirement for
multiple service provisioning requests for an enterprise at a business telephony
15 application server located at multiple circles. This is time-consuming, error-prone,
and inefficient, leading to delays, inconsistencies, and potential service disruptions.
[0044] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by optimising the selection and
20 transmission of service provisioning requests to specialised business telephony
application servers (BTAS). The present disclosure provides a solution in which provisioning can be done at a single point EPS (Enterprise Provisioning Server), which sends data to respective BTAS located at different circles. The EPS provides a centralized interface for managing enterprise-specific service data. EPS has
25 knowledge of geographical locations for which an enterprise-specific service is
applicable. Based on this knowledge, it propagates the service data changes to IMS application servers of relevant locations. Based on the implementation of features as disclosed in the present disclosure, the EPS employs a predefined format for network service request data and implements verification and availability checks
30 and ensures seamless and reliable provisioning of various network services. Further,
the solution as disclosed in the present disclosure involves a combination of
14

predefined format utilisation, data verification, and intelligent BTAS selection,
tracking of BTAS nodes in the network and maintaining availability data. The
availability data is associated with the availability of the BTAS. Unlike
conventional methods, which often lack standardised data formats and robust
5 verification mechanisms for handling network service requests, the present solution
offers a unified approach for handling network service requests.
[0045] Further, the method and system as disclosed, addresses the challenges of service provisioning by providing a step-by-step solution. First, a transceiver unit
10 receives a service provisioning request from one or more nodes of a network, like
OSS/BSS, containing at least a network service request data. Then a processing unit, retrieves a set of predefined data pre-requisites based on the service provisioning request. This set of predefined data pre-requisite maybe a pre agreement between the provisioning server and service request generator node.
15 Further, to ensure data integrity, the processing unit performs a verification process.
The network service request data is then verified based on the set of predefined data pre-requisites. This verification step guarantees the compatibility and accuracy of the request data, minimising errors and potential disruptions during the provisioning process. Further, upon successful verification and processing of the data and storing
20 into the repository, the processing unit transmits a corresponding response,
indicating either a successful processing or a failure. This immediate feedback loop enhances the efficiency and reliability of service provisioning by enabling prompt corrective actions or proceeding to the next step when successful. The OSS/BSS node can do further provisioning actions based on positive response from EPS, as
25 EPS is now the single point. Further, in order to optimise the provisioning
procedure, the processing unit identifies a set of specialised business telephony application servers, BTAS, associated with the network based on at least the verified network service request data. An availability status check is done periodically and is sent to the set of BTAS to determine their readiness for receiving data. Further,
30 based on the availability check responses, which can be positive availability
response or negative availability response, the processing unit intelligently selects
15

a target list of BTAS that is in a ready state. The processing unit resyncs the data to
unavailable BTAS when positive check response is received, until that time data is
stored at EPS. This selection process ensures efficient utilisation of resources and
minimises delays or bottlenecks during service provisioning. Thereafter, the
5 transceiver unit transmits the service provisioning request to the selected target list
of BTAS, leveraging the positive availability check response. This targeted transmission streamlines the provisioning process, reducing network congestion and optimising resource allocation.
10 [0046] Therefore, by combining predefined format utilisation, data verification,
and intelligent BTAS selection, the present disclosure provides an innovative solution that significantly improves the efficiency, accuracy, and reliability of service provisioning in a network.
15 [0047] Hereinafter, exemplary implementations of the present disclosure will be
described with reference to the accompanying drawings.
[0048] Referring to FIG.1, an exemplary block diagram of a system [100] for optimising a network procedure is shown, in accordance with the exemplary
20 implementations of the present disclosure. The system [100] comprises at least one
transceiver unit [102] and at least one processing unit [104]. In an implementation of the present disclosure, the system [100] may also comprise at least one storage unit [106] that may be used by the system [100] for implementation of the present disclosure. The transceiver unit [102] is a device capable of transmission and
25 reception of data and/or signals. The processing unit [104] is a processor capable of
processing data. Also, all of the components/ units of the system [100] are assumed to be connected to each other unless otherwise indicated below. Also, in FIG. 1 only a few units are shown, however, the system [100] may comprise multiple such units or the system [100] may comprise any such numbers of said units, as required to
30 implement the features of the present disclosure. Further, in an implementation, the
system [100] may reside wholly or partially in a server or a network entity. In yet
16

another implementation, the system [100] may be in connection with the server/ network entity.
[0049] The system [100] is configured for optimising a network procedure, with
5 the help of the interconnection between the components/units of the system [100].
[0050] In order to optimise the network procedure, the transceiver unit [102] of the system [100] is configured to receive, a service provisioning request from one or more nodes of a network, wherein the service provisioning request comprises at
10 least a network service request data. The system [100] provides a solution to
provision enterprise services using a single point Enterprise Provisioning Server (EPS), which send the data to respective BTAS located at different circles. This minimises user efforts in provisioning the services in circle databases and then segregating the data in databases. This way the system [100] provides an optimised
15 solution for provisioning services and hence provides solution for optimizing the
network procedure of provisioning enterprise services. As used herein a network procedure may refer to one or more functions performed within the network by an Enterprise Provisioning Server (EPS), wherein the EPS may refer to the specialized server or platform that is designed to handle the provisioning and management of
20 services specifically tailored for enterprises.
[0051] The service provisioning request may be a request by which the one or more network nodes request a particular service or resource allocation from the network and the service provisioning request comprises at least the network service request
25 data. The network service request data may refer to the data information or data
exchanged between the one or more network nodes when requesting the particular network function/services provided by the network. For instance, network service request data may be related to services, such as, a call forwarding service, a call waiting service, a call barring service, a call debarring service, etc. The network
30 may refer to the 5G telecommunications network and may also related to other types
of RATs also. For example, the network service request data may comprise a request
17

to create an enterprise/organization record for an enterprise/organization for provisioning multiple numbers for user profiles/ groups, and services for the provisioned numbers. The services requested to be provisioned for the numbers may be such as call waiting services, call forwarding services, etc. 5
[0052] In a non-limiting preferred implementation of the present disclosure, the
transceiver unit [102] and the processing unit [104] may reside in an enterprise
provisioning server (EPS). Consider an example, a service provisioning request is
received from an enterprise/organization for generating a record for the
10 enterprise/organization. Therefore, the service provisioning request will comprise
the name of the enterprise/organization.
[0053] Further, the processing unit [104] of the system [100] is configured to retrieve, a set of predefined data pre-requisites based on the service provisioning
15 request. The set of predefined data pre-requisites are the specified requirements
which are defined in the system [100] and are customisable based on the requirements of the system [100]. Based on the above example, one of the predefined data pre-requisites may be an existence of an enterprise/organization record, if the service provisioning request is for a call forwarding service on
20 multiple numbers for the enterprise/organization.
[0054] Further, the processing unit [104] of the system [100] is configured to verify
the network service request data based on at least one predefined data prerequisite
from the set of predefined data pre-requisites. Considering the above example, if
25 the enterprise/organization record does not exist or is not created, then the service
provisioning request will not be processed or the service provisioning request will be considered as false data, based on verification of the network service request data.
30 [0055] In an implementation of the present disclosure, the processing unit [104] is
configured to verify the network service request data based on at least one
18

predefined data pre-requisite from the set of predefined data pre-requisites. The at
least one predefined data pre-requisite is the one of the specified requirements from
the set of predefined data pre-requisites. If the predefined data pre-requisite is found
to be existing i.e., the pre-requisite or requirement is fulfilled, then it may be an
5 event that the network service request data is verified. However, in case the
predefined data pre-requisite is not existing i.e., the pre-requisite or requirement is
not fulfilled, then it may be the event that the network service request data is not
verified. Considering the above example, if the service provisioning request is
received for a call barring service on the phone numbers of the
10 enterprise/organization, then in such a case, the predefined data pre-requisite may
be such as checking whether the phone numbers provided in the service provisioning request exist or not.
[0056] The processing unit [104] is further configured to generate at least one of a
15 success response and a failure response based on the verification of the network
service request data. The success response may refer to the response for a successful
verification of the network service request data based on the presence of the at least
one predefined data pre-requisite from the set of the predefined data pre-requisites.
The failure response may refer to the response for an unsuccessful verification of
20 the network service request data based on the absence of the at least one predefined
data pre-requisite from the set of the predefined data pre-requisites.
[0057] In an implementation of the present solution, the success response is based
on a successful provisioning of the request into the repository of EPS. In another
25 implementation of the present solution, the failure response is based on an
unsuccessful provisioning of the network service request data or incorrect data received which is not as per defined data pre-requisites.
[0058] Further, the processing unit [104] of the system [100] is configured to
30 identify, a set of specialised business telephony application server (BTAS)
associated with the network based on at least the verified network service request
19

data. The set of specialised BTAS may refer to the set of dedicated servers or
platforms that may be specially designed for telephony applications tailored for the
businesses that are capable of providing advanced telephone solutions. Further, the
identification of the set of specialised BTAS is based on the verification of the
5 network service request data.
[0059] The transceiver unit [102] of the system [100] is further configured to receive, an availability status associated with one or more BTAS from the set of BTAS, wherein the availability status associated with the one or more BTAS is one
10 of a positive availability response and a negative availability response. The
availability status may refer to the status of availability of the one or more BTAS to handle the service provisioning request. Once the set of BTAS is identified, the system [100] further checks the availability of one or more BTAS from the identified set of BTAS. The successful availability response received from the one
15 or more BTAS is the response showing availability of the one or more BTAS. The
negative availability response associated with the one or more BTAS refers to an unsuccessful response received from the one or more BTAS or the response showing that the one or more BTAS are not available. Further, if the transceiver unit [102] receives no response associated with the one or more BTAS it may be
20 identified as an unsuccessful response, or the negative availability response
received from the one or more BTAS.
[0060] Further, the processing unit [104] of the system [100] is configured to identify, a target BTAS from the set of BTAS based on the positive availability
25 response associated with the target BTAS. The target BTAS may refer to the one or
more BTAS from the set of BTAS to which the service provisioning request is to be forwarded. In case of positive availability of multiple BTAS from the set of BTAS, then the processing unit [104] identifies the target BTAS based on the configuration of the set of BTAS in a database storing information associated with the set of
30 BTAS. The database is checked, and then based on the ordering/numbering of the
20

set of BTAS, the available BTAS which is at the first order/number in the database is identified as the target BTAS.
[0061] Further, the transceiver unit [102] of the system [100] is configured to
5 transmit, to the target BTAS, the network service request data based on the positive
availability response.
[0062] Further, the processing unit [104] of the system [100] is configured to optimise, the network procedure based on transmitting the network service request
10 data to the target BTAS. Since, the present disclosure provides a single point of
interaction to the enterprise for the service provisioning request, and thereafter the EPS itself identifies the target BTAS and provisions the network service request data in the set of BTAS, the present disclosure optimises the network procedure. The optimisation of network procedure is done by reducing the required time for
15 provisioning the request to the BTAS, reducing the resources used for provisioning
the network service request data with the set of BTAS.
[0063] In an implementation of the present disclosure, in an event of receipt of the negative availability response to the availability status, the processing unit [104] is
20 configured to identify the availability status associated with one or more BTAS
from the set of BTAS based on a heartbeat message. The heartbeat message may refer to a periodical signal or packet sent between the one or more network nodes for indication of the operational status or the running status of the one or more network nodes showing that the one or more network nodes are running and
25 connected. For example, the heartbeat message may be an HTTP request and
comprise a HTTP status codes for a success response or a failure response.
[0064] The present disclosure further discloses that in the event of receipt of the
negative availability response, the processing unit [104] is configured to identify
30 the positive availability response associated with the one or more BTAS in an event
a successful response associated with the heartbeat message is received by the
21

transceiver unit [102] from the one or more BTAS. The event of the successful
response associated with the heartbeat message may refer to an active state of the
one or more BTAS and shows that the one or more BTAS are ready for receiving
the network service request data. The processing unit [104] is configured to identify
5 the negative availability response associated with the one or more BTAS in an event
an unsuccessful response associated with the heartbeat message is received by the transceiver unit [102] from the one or more BTAS. The event of the unsuccessful response associated with the heartbeat message may refer to an inactive state of the one or more BTAS showing that they are not in operational and running status, and
10 not ready for receiving the network service request data. Further, in an event the
processing unit [104] receives no response associated with the one or more BTAS, the processing unit [104] identifies the event as an unsuccessful response associated with the heartbeat message received by the transceiver unit [102] from the one or more BTAS.
15
[0065] In another implementation of the present disclosure, the system [100] may reside within the Enterprise Provisioning Server (EPS).
[0066] FIG. 2 illustrates a block diagram depicting an exemplary scenario for
20 optimising the network procedure, in accordance with exemplary implementations
of the present disclosure. Further, the FIG. 2 depicts various components of a
telecom network, such as the Enterprise Provisioning Server (EPS) unit [204] and
Enterprise Provisioning Server (EPS) unit [206] which further comprises an EPS
(active) [204A] and an EPS (standby) [204B] at a primary location and an EPS
25 (active) [206A] and an EPS (standby) [206B] at a geo redundant location
respectively. FIG. 2 also comprises an Operations Support System – Business
Support System (OSS-BSS) /Network Provisioning Platform [202], involved in
implementation of the features of the present disclosure. OSS-BSS system controls
and manages all provisioning operations pertaining to enterprise services. It is a
30 centralized system designed to leverage APIs exposed by various endpoints from
subscriber provisioning in the Home Subscriber Server (HSS) to service
22

provisioning in BTAS. The Network Provisioning Platform dictates provisioning
requests to BTAS. The Network Provisioning Platform efficiently manages all cases
of service provisioning such as IP Centrex and SIP Trunk. IP Centrex is a service
where the functionalities of a PBX are simulated on the Cloud to provide a highly
5 scalable and cost-effective Enterprise voice communication solution. SIP Trunk
acts as a solution for an organization’s phone connections and its Internet Telephony Service Provider. The Network Provisioning Platform also purposefully represents all subscriber data in a Graphical Environment which can be customized as per customer requirements.
10
[0067] The EPS [206] at the geo-redundant location operates as a redundancy in case the primary location EPS [204] fails. may be different geographic location at which the servers are distributed across multiple data centres. The EPS [204] at the primary location and the EPS [206] at the geo-redundant location communicate
15 with each other by sending heartbeat messages and requesting synchronisation. The
EPS (active) [204A] and [206A] may refer to a functional EPS that is provided at the primary location and at the georedundant location. The EPS (standby) [204B] and EPS (standby) [206B] act as backup EPS that is provided at the primary location and at the georedundant location respectively, which may become active in case the
20 EPS (active) [204A] or EPS (active) [206A] become inactive for some reason such
as natural calamities, faults, etc.
[0068] Referring to FIG. 3 an exemplary method flow diagram [300], for
optimising a network procedure, in accordance with exemplary implementations of
25 the present disclosure is shown. In an implementation the method [300] is
performed by the system [100]. As shown in FIG.3, the method [300] starts at step [302].
[0069] At step [304], in the method [300] as disclosed by the present disclosure,
30 comprises receiving, by a transceiver unit [102], a service provisioning request from
one or more nodes of a network, wherein the service provisioning request comprises
23

at least a network service request data. The method [300] provides a solution to
provision enterprise services using a single point Enterprise Provisioning Server
(EPS), which send the data to respective BTAS located at different circles. This
minimises user efforts in provisioning the services in circle databases and then
5 segregating the data in databases. This way the method [300] provides an optimised
solution for provisioning services and hence provides solution for optimizing the network procedure of provisioning enterprise services. As used herein, a network procedure may refer to one or more functions performed within the network by an EPS, wherein the EPS may refer to the specialised server or platform that is
10 designed to handle the provisioning and management of services specifically
tailored for enterprises. The service provisioning request may be a request by which the one or more network nodes request a particular service or resource allocation from the network and the service provisioning request comprises at least the network service request data. The network service request data may refer to the data
15 information or data exchanged between the one or more network nodes when
requesting the particular network function/services provided by the network. For instance, the network service request data may be related to services, such as, a call forwarding service request, a call waiting service, a call barring service, a call debarring service, etc. The network may refer to the 5G telecommunications
20 network and may also related to other types of RATs also. For example, the network
service request data may comprise a request to create an enterprise/organization record for an enterprise/organization for provisioning multiple numbers for user profiles/ groups, and services for the provisioned numbers. The services requested to be provisioned for the numbers may be such as call waiting services, call
25 forwarding services, etc.
[0070] Next at step [306], the method [300] comprises retrieving, by the processing
unit [104] of the system [100], a set of predefined data pre-requisites based on the
service provisioning request. The set of predefined data pre-requisites are the
30 specified requirements which are defined in the method [300] and are customisable
based on the requirements of the method [300]. Based on the above example, one
24

of the predefined data pre-requisites may be an existence of an enterprise/organization record, if the service provisioning request is for a call forwarding service on multiple numbers for the enterprise/organization.
5 [0071] Next, at step [308], the method [300] as disclosed by the present disclosure
comprises verifying, by the processing unit [104], the network service request data
based on at least one predefined data prerequisite from the set of predefined data
pre-requisites. The at least one predefined data pre-requisite is the one of the
specified requirements from the set of predefined data pre-requisites. Considering
10 the above example, if the enterprise/organization record does not exist or is not
created, then the service provisioning request will not be processed or the service provisioning request will be considered as false data, based on verification of the network service request data.
15 [0072] In the implementation of the present disclosure, the method further
comprises verifying, by the processing unit [104], the network service request data based on at least one predefined data pre-requisite from the set of predefined data pre-requisites. The at least one predefined data pre-requisite is the one of the specified requirements from the set of predefined data pre-requisites. If the
20 predefined data pre-requisite is found to be existing i.e., the pre-requisite or
requirement is fulfilled, then it may be an event that the network service request data is verified. However, in case the predefined data pre-requisite is not existing i.e., the pre-requisite or requirement is not fulfilled, then it may be the event that the network service request data is not verified. Considering the above example, if
25 the service provisioning request is received for a call barring service on the phone
numbers of the enterprise/organization, then in such a case, the predefined data pre¬requisite may be such as checking whether the phone numbers provided in the service provisioning request exist or not.
30 [0073] The method [300] as disclosed by the present disclosure further discloses
generating, by the processing unit [104], at least one of a success response and a
25

failure response based on the verification of the network service request data. The
success response may refer to the response for a successful verification of the
network service request data based on the presence of the at least one predefined
data pre-requisite from the set of the predefined data pre-requisites. The failure
5 response may refer to the response for an unsuccessful verification of the network
service request data based on the absence of the at least one predefined data pre-requisite from the set of the predefined data pre-requisites.
[0074] In an implementation of the present solution, the success response is based
10 on a successful provisioning of the request into the repository of EPS. In another
implementation of the present solution, the failure response is based on an unsuccessful provisioning of the network service request data or incorrect data received which is not as per defined data pre-requisites.
15 [0075] Next, at step [310], in the method [300] as disclosed by the present
disclosure comprises identifying, by the processing unit [104], a set of specialised business telephony application server (BTAS) associated with the network based on at least the verified network service request data. The set of specialised BTAS may refer to the set of dedicated servers or platforms that may be specially designed
20 for telephony applications tailored for the businesses that are capable of providing
advanced telephone solutions. Further, the identification of the set of specialised BTAS is based on the verification of the network service request data.
[0076] Next, at step [312], in the method [300] as disclosed by the present
25 disclosure comprises receiving, by the transceiver unit [102], an availability status
associated with one or more BTAS from the set of BTAS wherein the availability
status associated with the one or more BTAS is one of a positive availability
response and a negative availability response. The availability status may refer to
the status of availability of the one or more BTAS to handle the network service
30 request data. Once the set of BTAS is identified, the system [100] further checks
the availability of one or more BTAS from the identified set of BTAS. The
26

successful availability response received from the one or more BTAS is the
response showing availability of the one or more BTAS. The negative availability
response associated with the one or more BTAS refers to an unsuccessful response
received from the one or more BTAS or the response showing that the one or more
5 BTAS are not available. Further, if the transceiver unit [102] receives no response
associated with the one or more BTAS it may be identified as an unsuccessful response, or the negative availability response received from the one or more BTAS.
[0077] Next, at step [314], in the method [300] as disclosed by the present
10 disclosure comprises identifying, by the processing unit [104], a target BTAS from
the set of BTAS based on the positive availability response associated with the
target BTAS The target BTAS may refer to the one or more BTAS from the set of
BTAS to which the network service request is to be forwarded. In case of positive
availability of multiple BTAS from the set of BTAS, then the processing unit [104]
15 identifies the target BTAS based on the configuration of the set of BTAS in a
database storing information associated with the set of BTAS. The database is
checked, and then based on the ordering/numbering of the set of BTAS, the
available BTAS which is at the first order/number in the database is identified as
the target BTAS.
20
[0078] Next, at step [316], in the method [300] as disclosed by the present disclosure comprises transmitting, by the transceiver unit [102] to the target BTAS, the network service request data based on the positive availability response.
25 [0079] Next, at step [318], in the method [300] as disclosed by the present
disclosure comprises optimising, by the processing unit [104], the network procedure based on the transmission of the service provisioning request to the target list of BTAS. Since, the present disclosure provides a single point of interaction to the enterprise for the service provisioning request, and thereafter the EPS itself
30 identifies the target BTAS and provisions the network service request data in the set
of BTAS, the present disclosure optimises the network procedure. The optimisation
27

of network procedure is done by reducing the required time for provisioning the request to the BTAS, reducing the resources used for provisioning the network service request data with the set of BTAS.
5 [0080] In an implementation of the present disclosure, in an event of receipt of the
negative availability response to the availability status, the processing unit [104] is
configured to identify the availability status associated with one or more BTAS
from the set of BTAS based on a heartbeat message. The heartbeat message may
refer to a periodical signal or packet sent between the one or more network nodes
10 for indication of the operational status or the running status of the one or more
network nodes showing that the one or more network nodes are running and connected. For example, the heartbeat message may be an HTTP request and comprise a HTTP status codes for a success response or a failure response.
15 [0081] The present disclosure further discloses that in the event of receipt of the
negative availability response, the method further comprises, identifying, by the processing unit [104], the positive availability response associated with the one or more BTAS in an event a successful response associated with the heartbeat message is received by the transceiver unit [102] from the one or more BTAS. The event of
20 the successful response associated with the heartbeat message may refer to an active
state of the one or more BTAS and shows that the one or more BTAS are ready for receiving the service provisioning data. The processing unit [104] is configured to identify the negative availability response associated with the one or more BTAS in an event an unsuccessful response associated with the heartbeat message is received
25 by the transceiver unit [102] from the one or more BTAS. The event of the
unsuccessful response associated with the heartbeat message may refer to an inactive state of the one or more BTAS showing that they are not in operational and running status, and not ready for receiving the service provisioning data. Further, in an event the processing unit [104] receives no response associated with the one or
30 more BTAS, the processing unit [104] identifies the event as an unsuccessful
28

response associated with the heartbeat message received by the transceiver unit [102] from the one or more BTAS.
[0082] Thereafter, the method terminates at step [320]. 5
[0083] Referring to FIG. 4 an exemplary process flow diagram [400] depicting a scenario for optimising a network procedure, in accordance with exemplary implementations of the present disclosure is shown. FIG. 4 illustrates a connection between an Operations Support System – Business Support System (OSS-BSS) or
10 Network Provisioning Platform [202] and the EPS [402]. The EPS [402]
communicates with a set of BTAS, such as BTAS 1 [404], a BTAS 2 [406], a BTAS 3 [408], and a BTAS n [410]. OSS-BSS system controls and manages all provisioning operations pertaining to enterprise services. It is a centralized system designed to leverage APIs exposed by various endpoints from subscriber
15 provisioning in the Home Subscriber Server (HSS) to service provisioning in
BTAS. Network Provisioning Platform dictates provisioning requests to BTAS. It efficiently manages all cases of service provisioning such as IP Centrex and SIP Trunk. IP Centrex is a service where the functionalities of a PBX are simulated on the Cloud to provide a highly scalable and cost-effective Enterprise voice
20 communication solution. SIP Trunk acts as a solution for an organization’s phone
connections and its Internet Telephony Service Provider. Network Provisioning Platform also purposefully represents all subscriber data in a Graphical Environment which can be customized as per customer requirements. Further, there can be multiple BTAS through which the EPS may communicate. The
25 communication between the EPS and the numerous BTAS may comprise of sending
a service provisioning request and transmitting the heartbeat message. The EPS [402] can transmit the service provisioning request to each of the BTAS 1 [404], the BTAS 2 [406], the BTAS 3 [408], and the BTAS n [410]. The EPS can similarly transmit and receive the heartbeat message and heartbeat response to and from each
30 of the BTAS 1 [404], the BTAS 2 [406], the BTAS 3 [408], and the BTAS n [410].
29

[0084] FIG. 5 illustrates an exemplary block diagram of a computing device [500]
upon which the features of the present disclosure may be implemented in
accordance with exemplary implementation of the present disclosure. In an
implementation, the computing device [500] may also implement the method [400]
5 for optimising a network procedure by utilising the system [100]. In another
implementation, the computing device [500] itself implements the method [400] for optimising a network procedure using one or more units configured within the computing device [500], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
10
[0085] The computing device [500] may include a bus [502] or other communication mechanism for communicating information, and a hardware processor [504] coupled with bus [502] for processing information. The hardware processor [504] may be, for example, a general-purpose microprocessor. The
15 computing device [500] may also include a main memory [506], such as a random-
access memory (RAM), or other dynamic storage device, coupled to the bus [502] for storing information and instructions to be executed by the processor [504]. The main memory [506] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the
20 processor [504]. Such instructions, when stored in non-transitory storage media
accessible to the processor [504], render the computing device [500] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [500] further includes a read only memory (ROM) [508] or other static storage device coupled to the bus [502] for storing static
25 information and instructions for the processor [504].
[0086] A storage device [510], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [502] for storing information and
instructions. The computing device [500] may be coupled via the bus [502] to a
30 display [512], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
30

displaying information to a computer user. An input device [514], including
alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [502] for communicating information and command selections to the processor
[504]. Another type of user input device may be a cursor controller [516], such as a
5 mouse, a trackball, or cursor direction keys, for communicating direction
information and command selections to the processor [504], and for controlling cursor movement on the display [512]. The input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
10
[0087] The computing device [500] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [500] causes or programs the computing device [500] to be a special-purpose machine.
15 According to one implementation, the techniques herein are performed by the
computing device [500] in response to the processor [504] executing one or more sequences of one or more instructions contained in the main memory [506]. Such instructions may be read into the main memory [506] from another storage medium, such as the storage device [510]. Execution of the sequences of instructions
20 contained in the main memory [506] causes the processor [504] to perform the
process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
25 [0088] The computing device [500] also may include a communication interface
[518] coupled to the bus [502]. The communication interface [518] provides a two-way data communication coupling to a network link [520] that is connected to a local network [522]. For example, the communication interface [518] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or
30 a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [518] may be a
31

local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be implemented. In any such
implementation, the communication interface [518] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing
5 various types of information.
[0089] The computing device [500] can send messages and receive data, including program code, through the network(s), the network link [520] and the communication interface [518]. In the Internet example, a server [530] might
10 transmit a requested code for an application program through the Internet [528], the
ISP [526], a host [524], the local network [522] and the communication interface [518]. The received code may be executed by the processor [504] as it is received, and/or stored in the storage device [510], or other non-volatile storage for later execution.
15
[0090] Another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing one or more instructions for optimising a network procedure. The storage medium comprising executable code which,
20 when executed by one or more units of a system [100], causes the one or more units
to perform certain functions. The executable code when executed causes a transceiver unit [102] of the system [100] to receive, a service provisioning request from one or more nodes of a network, wherein the service provisioning request comprises at least a network service request data. The executable code when
25 executed further causes a processing unit [104] of the system [100] to retrieve, a set
of predefined data pre-requisites based on the service provisioning request. The executable code when executed further causes the processing unit [104] of the system [100] to verify the network service request data based on the set of predefined data pre-requisites. The executable code when executed further causes
30 the processing unit [104] of the system [100] to identify, a set of specialised
business telephony application server (BTAS) associated with the network based
32

on at least the verified network service request data; the transceiver unit [102] of
the system [100] to receive, an availability status associated with one or more BTAS
from the set of BTAS, wherein the availability status associated with the one or
more BTAS is one of a positive availability response and a negative availability
5 response. The executable code when executed further causes the processing unit
[104] of the system [100] to identify, a target BTAS from the set of BTAS based on
the positive availability response associated with the target BTAS. The executable
code when executed further causes the transceiver unit [102] of the system [100] to
transmit, to the target BTAS, the network service request data based on the positive
10 availability response. The executable code when executed further causes the
processing unit [104] of the system [100] to optimise, the network procedure based on at least transmitting the network service request data to the target BTAS.
[0091] As is evident from the above, the present disclosure provides a technically
15 advanced solution for optimising the provisioning of enterprise services by a single
point solution (EPS). With the system [100] and method [300] disclosed by the
present solution as the central hub, service provisioning can be efficiently
performed by sending data to the respective specialised telephony application
servers (BTAS) located in different circles or regions. This centralised approach
20 eliminates the need for individual provisioning tasks at each BTAS, simplifying the
overall provisioning process and reducing administrative complexity.
[0092] Further, the present solution provides a technical effect by bringing about significant improvements in network management and service provisioning
25 efficiency by utilising the system [100] and method [300] as disclosed by the
present solution as a single point for provisioning. The method [300] enables streamlined provisioning operations. Additions, deletions, and modifications of data can be easily performed at the master repository of the system [100] present at EPS by using the method [300] disclosed in the present solution. These operations
30 are seamlessly synchronised with the respective BTAS servers, ensuring consistent
and accurate provisioning across the network. The present solution provides a
33

technical effect by providing an improved data management, and enhanced
synchronisation for BTAS. Further, the present solution has the technical advantage
that the system [100] and method [300] of provisioning tasks reduce unnecessary
network traffic. Instead of each BTAS individually retrieving data from various
5 sources, the system [100] and method [300] disclosed in the present solution deliver
the necessary data to the corresponding BTAS. This reduces network congestion and optimises data transfer, leading to improved network performance. Additionally, users benefit from simplified data management, as they no longer need to handle data provisioning tasks separately for each BTAS. The technical
10 effect is a reduction in network load and an improved user experience. The present
solution eliminates the need for redundant provisioning tasks at each BTAS. This reduces the overall provisioning workload and minimises the potential for errors or inconsistencies. The technical effect is improved provisioning efficiency, faster onboarding of enterprise services, and reduced provisioning effort for network
15 administrators.
[0093] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and
that many changes can be made to the implementations without departing from the
20 principles of the present disclosure. These and other changes in the implementations
of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
25 [0094] Further, in accordance with the present disclosure, it is to be acknowledged
that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The
30 functionality of specific units as disclosed in the disclosure should not be construed
as limiting the scope of the present disclosure. Consequently, alternative
34

arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.

I/We claim:
1. A method for optimising a network procedure, the method comprising:
- receiving, by a transceiver unit [102], a service provisioning request from one or more nodes of a network, wherein the service provisioning request comprises at least a network service request data;
- retrieving, by a processing unit [104], a set of predefined data pre-requisites based on the service provisioning request;
- verifying, by the processing unit [104], the network service request data based on the set of predefined data pre-requisites;
- identifying, by the processing unit [104], a set of specialised Business telephony application server (BTAS) associated with the network based on at least the verified network service request data;
- receiving, by the transceiver unit [102], an availability status associated with one or more BTAS from the set of BTAS, wherein the availability status associated with the one or more BTAS is one of a positive availability response and a negative availability response;
- identifying, by the processing unit [104], a target BTAS from the set of BTAS based on the positive availability response associated with the target BTAS;
- transmitting, by the transceiver unit [102] to the target BTAS, the network service request data based on the positive availability response; and
- optimising, by the processing unit [104], the network procedure based on at least transmitting the network service request data to the target BTAS.

2. The method as claimed in claim 1, wherein the verifying the network service request data by the processing unit [104] is based on at least one predefined data pre-requisite from the set of predefined data pre-requisites.
3. The method as claimed in claim 1, further comprises generating at least one of a success response and a failure response based on the verifying of the network service request data.

4. The method as claimed in claim 1, the method further comprises: in an event of receipt of the negative availability response, identifying by the processing unit [104], the availability status associated with the one or more BTAS from the set of BTAS based on a heartbeat message.
5. The method as claimed in claim 4, wherein the positive availability response associated with the one or more BTAS is identified by the processing unit [104] in an event a successful response associated with the heartbeat message is received by the transceiver unit [102] from the one or more BTAS, and wherein the negative availability response associated with the one or more BTAS is identified by the processing unit [104] in an event an unsuccessful response associated with the heartbeat message is received by the transceiver unit [102] from the one or more BTAS.
6. A system [100] for optimising a network procedure, the system [100] comprises:
- a transceiver unit [102], wherein the transceiver unit [102] is configured
to:
• receive, a service provisioning request from one or more nodes of a
network, wherein the service provisioning request comprises at least
a network service request data; and
- a processing unit [104] connected to at least the transceiver unit [102]
wherein the processing unit [104] is configured to:
• retrieve, a set of predefined data pre-requisites based on the service provisioning request,
• verify the network service request data based on the set of predefined data pre-requisites, and
• identify, a set of specialised Business telephony application server (BTAS) associated with the network based on at least the verified network service request data,

wherein the transceiver unit [102] is further configured to receive, an
availability status associated with one or more BTAS from the set of
BTAS, wherein the availability status associated with the one or more
BTAS is one of a positive availability response and a negative
availability response,
wherein the processing unit [104] is further configured to identify, a
target BTAS from the set of BTAS based on the positive availability
response associated with the target BTAS,
wherein the transceiver unit [102] is further configured to transmit, to the
target BTAS, the network service request data based on the positive
availability response, and
the processing unit [104] is further configured to optimise, the network
procedure based on at least transmitting the network service request data
to the target BTAS.
7. The system [100] as claimed in claim 6, wherein the network service request data is verified based on at least one predefined data pre-requisite from the set of predefined data pre-requisites.
8. The system [100] as claimed in claim 6, wherein the processing unit [104] is further configured to generate at least one of a success response and a failure response based on the verifying of the network service request data.
9. The system [100] as claimed in claim 6, wherein in an event of receipt of the negative availability response, the processing unit [104] is further configured to identify the availability status associated with the one or more BTAS from the set of BTAS based on a heartbeat message.
10. The system [100] as claimed in claim 9, wherein the processing unit [104] is configured to identify the positive availability response associated with the one or more BTAS in an event a successful response associated with the

heartbeat message is received by the transceiver unit [102] from the one or more BTAS, and wherein the processing unit [104] is further configured to identify the negative availability response associated with the one or more BTAS in an event an unsuccessful response associated with the heartbeat message is received by the transceiver unit [102] from the one or more BTAS.