FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“SYSTEM AND METHOD FOR CONFIGURING SYNCHRONOUS AND AN
ASYNCHRONOUS RESPONSE MECHANISM IN FULFILMENT
MANAGEMENT SYSTEM”
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.

SYSTEM AND METHOD FOR CONFIGURING SYNCHRONOUS AND AN ASYNCHRONOUS RESPONSE MECHANISM IN FULFILMENT
MANAGEMENT SYSTEM
FIELD OF THE DISCLOSURE
[0001] The present disclosure relates generally to the field of wireless communication systems. In particular, the present disclosure relates to application programming interface (API) communication and interaction mechanisms. More particularly, the present disclosure relates to system and method for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system (FMS).
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 second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The 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] Many traditional systems show incompatibility with other systems. If one system uses only synchronous APIs and another system uses only asynchronous APIs, there might be compatibility issues when they try to interact with each other. The systems might not be able to communicate effectively because they are designed to handle requests and responses differently. Synchronous APIs can be less efficient than asynchronous ones, especially for complex or time-consuming operations. When a request is made using a synchronous API, the client must wait for the response before it can continue processing. This "blocking" nature can lead to inefficient usage of resources, especially if the server takes a long time to respond. Asynchronous APIs allow the client to continue processing while waiting for the server's response. While this approach can be more efficient, it also introduces complexity because the client must be able to handle the response whenever it arrives. Further, for traditional systems, each time a system needs to interact with a new interface or third-party system, developers might need to write custom code to accommodate the specific sync or async API requirements of that system. This increases development time and effort. Furthermore, for existing systems, if a system only supports synchronous APIs, it might struggle to scale because each active request ties up resources until the response is received. On the other hand, while asynchronous APIs can help with scalability, they come with their own challenges in managing and coordinating responses, which can get more complex as the system scales up.

[0005] Thus, there exists an imperative need in the art for configuring a synchronous response mechanism and an asynchronous response mechanism to provide an improved compatibility, efficiency, and scalability, while also reducing development and integration effort. The present disclosure aims to address this solution.
OBJECTS OF THE PRESENT DISCLOSURE
[0006] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0007] It is an object of the present disclosure to provide a system and method for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system.
[0008] It is another object of the present disclosure to provide a system and method for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system that offers flexibility in API interactions. The system is designed to support both sync and async API calls, which can adapt to different interfaces and third-party systems, irrespective of whether they support sync or async interactions.
[0009] It is another object of the present disclosure to provide a system and a method for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system that by offering both sync and async response capabilities, ensures that system resources are used optimally, avoiding bottlenecks that can occur from waiting for responses in sync interactions or managing responses in async interactions.

[0010] It is another object of the present disclosure to provide a system and a method for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system, that simplifies the process of integration with multiple interfaces and third-party systems. This functionality can significantly reduce the development and integration effort, as custom solutions will not need to be created for each unique system.
[0011] It is another object of the present disclosure to provide a system and method for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system, that ensures compatibility with a wide range of other systems. By being able to interact using both sync and async responses, the system can seamlessly communicate with any system, regardless of its API response capabilities.
[0012] It is yet another object of the present disclosure to provide a system and a method for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system, that aims to provide better scalability. The system can efficiently manage increasing loads of requests without getting bogged down or overly complex, as might be the case with systems that support only one type of interaction.
SUMMARY
[0013] 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.
[0014] An aspect of the present disclosure provides a method for configuring a
synchronous response mechanism and an asynchronous response mechanism in a

fulfilment management system (FMS). The method includes receiving, by a transceiver unit at the FMS, a request for interaction from a requesting system, the requesting system comprising at least one of a northbound interface (NBI) system and a third-party system. The method further includes determining, by a determination unit at the FMS, a type of application programming interface (API) interaction supported by the requesting system based on the received request, wherein the type of API interaction is one of a synchronous interaction and an asynchronous interaction. The method further includes configuring the FMS, by an analysis unit at the FMS, to generate a response based on the determined type of API interaction. Thereafter, the method further includes transmitting, by the transceiver unit, the generated response to the requesting system based on the determined type of API interaction.
[0015] In an aspect, the request is one of a call type requests and a command type request.
[0016] In an aspect, the one of the call type requests and the command type request is associated with performing a set of tasks on a data in the FMS.
[0017] In an aspect, the determining the type of API interaction comprises analysing, by the analysis unit, the request for determining one of the synchronous interactions and the asynchronous interaction supported by the requesting system.
[0018] In an aspect, the synchronous interaction corresponds to a blocking operation, and the asynchronous interaction corresponds to a non-blocking operation, wherein the blocking operation comprises waiting, by the requesting

operation comprises continuing, by the requesting system, with other operations without waiting for a response.
[0019] In an aspect, the configuring the FMS, by the analysis unit at the FMS, to generate the response comprises one of: structuring the response for immediate transmission for the synchronous interaction, and preparing the response for later transmission for the asynchronous interaction.
[0020] In an aspect, the transmitting, by the transceiver unit, the generated response comprises one of: sending, by the transceiver unit, an immediate response for the synchronous interaction, and sending, by the transceiver unit, an acknowledgment when ready for the asynchronous interaction, aligning with the configured type of API interaction.
[0021] Another aspect of the present disclosure relates to a system for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system (FMS), the FMS further comprising a transceiver unit configured to receive a request for interaction from a requesting system, the requesting system comprising at least one of a northbound interface (NBI) system and a third-party system. The FMS further comprises a determination unit connected at least to the transceiver unit, the determination unit configured to determine a type of application programming interface (API) interaction supported by the requesting system based on the received request, wherein the type of API interaction is one of a synchronous interaction and an asynchronous interaction. The FMS further comprises an analysis unit connected at least to the determination unit, the analysis unit configured to configure the FMS to generate a response based on the determined type of API interaction. The FMS further comprises the

transceiver unit further configured to transmit the generated response to the requesting system based on the determined type of API interaction.
[0022] Another aspect of the present disclosure provides a user equipment (UE)
5 for configuring a synchronous response mechanism and an asynchronous response
mechanism in a fulfilment management system (FMS). The UE includes a processor configured to transmit a request for interaction to a requesting system, the requesting system comprising at least one of a northbound interface (NBI) system and a third-party system; determine a type of application programming
10 interface (API) interaction supported by the requesting system based on the
received request, wherein the type of API interaction is one of a synchronous interaction and an asynchronous interaction; configure the FMS to generate a response based on the determined type of API interaction; and receive the generated response from the requesting system based on the determined type of API
15 interaction.
[0023] According to yet another aspect, a non-transitory computer-readable storage medium storing instruction for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management
20 system (FMS) is disclosed. The storage medium comprising executable code which,
when executed by one or more units of a system, causes: a transceiver unit to receive a request for interaction from a requesting system, the requesting system comprising at least one of a northbound interface (NBI) system and a third-party system; a determination unit connected at least to the transceiver unit, the
25 determination unit to determine a type of application programming interface (API)
interaction supported by the requesting system based on the received request, wherein the type of API interaction is one of a synchronous interaction and an asynchronous interaction; an analysis unit connected at least to the determination unit, the analysis unit to configure the FMS to generate a response based on the
8

determined type of API interaction; and the transceiver unit to further transmit the generated response to the requesting system based on the determined type of API interaction.
5 BRIEF DESCRIPTION OF DRAWINGS
[0024] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same
10 parts throughout the different drawings. Components in the drawings are not
necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such
15 drawings includes disclosure of electrical components, electronic components or
circuitry commonly used to implement such components.
[0025] FIG. 1 illustrates an exemplary block diagram of a system for configuring
a synchronous response mechanism and an asynchronous response mechanism in a
20 fulfilment management system, in accordance with exemplary embodiments of the
present disclosure.
[0026] FIG. 2 illustrates an exemplary block diagram of a system architecture for
configuring a synchronous response mechanism and an asynchronous response
25 mechanism in a fulfilment management system, in accordance with exemplary
embodiments of the present disclosure.
[0027] FIG. 3 illustrates an exemplary method flow diagram indicating the process for configuring a synchronous response mechanism and an asynchronous
9

response mechanism in a fulfilment management system, in accordance with exemplary embodiments of the present disclosure.
[0028] FIG. 4 illustrates an exemplary block diagram of a computing device upon
5 which an embodiment of the present disclosure may be implemented.
[0029] The foregoing shall be more apparent from the following more detailed description of the disclosure.
10 DETAILED DESCRIPTION
[0030] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that
15 embodiments 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 problems discussed above. Some of the problems discussed above might not be
20 fully addressed by any of the features described herein. Example embodiments 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.
25 [0031] The ensuing description provides exemplary embodiments only, and is not
intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and
10

arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0032] It should be noted that the terms "mobile device", "user equipment", "user
5 device", “communication device”, “device” and similar terms are used
interchangeably for the purpose of describing the invention. These terms are not
intended to limit the scope of the invention or imply any specific functionality or
limitations on the described embodiments. The use of these terms is solely for
convenience and clarity of description. The invention is not limited to any particular
10 type of device or equipment, and it should be understood that other equivalent terms
or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.
[0033] Specific details are given in the following description to provide a
15 thorough understanding of the embodiments. However, it will be understood by one
of ordinary skill in the art that the embodiments 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 embodiments in unnecessary detail. In other instances, well-known
20 circuits, processes, algorithms, structures, and techniques may be shown without
unnecessary detail in order to avoid obscuring the embodiments.
[0034] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a
25 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 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.
30
11

[0035] The word “exemplary” and/or “demonstrative” is used herein to mean
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
5 necessarily to be construed as preferred or advantageous over other aspects or
designs, nor is it meant to preclude equivalent exemplary structures and techniques
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
10 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0036] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic
15 circuitry for processing instructions. The processor may be a general-purpose
processor, a special purpose processor, a conventional processor, a digital signal processor, 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
20 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 according to the present disclosure. More specifically, the processor is a hardware processor.
25 [0037] As used herein, “a user equipment”, “a user device”, “a smart-user-
device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The
30 user equipment/device may include, but is not limited to, a mobile phone, smart
12

phone, laptop, a general-purpose computer, desktop, personal digital assistant,
tablet computer, wearable device or any other computing device which is capable
of implementing the features of the present disclosure. Also, the user device may
contain at least one input means configured to receive an input from at least one of
5 a transceiver unit, a processing unit, a storage unit, a detection unit and any other
such unit(s) which are required to implement the features of the present disclosure.
[0038] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a
10 form readable by a computer or similar machine. For example, a computer-readable
medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective
15 functions.
[0039] As used herein “interface” or “user interface refers to a shared boundary
across which two or more separate components of a system exchange information
or data. The interface may also be referred to a set of rules or protocols that define
20 communication or interaction of one or more modules or one or more units with
each other, which also includes the methods, functions, or procedures that may be called.
[0040] All modules, units, components used herein, unless explicitly excluded
25 herein, may be software modules or hardware processors, the processors being a
general-purpose processor, a special purpose processor, a conventional processor,
a digital signal processor (DSP), a plurality of microprocessors, one or more
microprocessors in association with a DSP core, a controller, a microcontroller,
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
30 circuits (FPGA), any other type of integrated circuits, etc.
13

[0041] As portable electronic devices and wireless technologies continue to
improve and grow in popularity, the advancing wireless technologies for data
transfer are also expected to evolve and replace the older generations of
5 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), and more such generations are expected to continue in the forthcoming time.
10
[0042] Radio Access Technology (RAT) refers to the technology used by mobile devices/ user equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base stations, which are responsible for providing the wireless connection. Further, each
15 RAT has its own set of protocols and standards for communication, which define
the frequency bands, modulation techniques, and other parameters used for transmitting and receiving data. Examples of RATs include GSM (Global System for Mobile Communications), CDMA (Code Division Multiple Access), UMTS (Universal Mobile Telecommunications System), LTE (Long-Term Evolution),
20 and 5G. The choice of RAT depends on a variety of factors, including the network
infrastructure, the available spectrum, and the mobile device's/device's capabilities. Mobile devices often support multiple RATs, allowing them to connect to different types of networks and provide optimal performance based on the available network resources.
25
[0043] A Fulfilment management system supports translation of any kind of incoming request from a northbound interface to plurality of outgoing predefined sequence of API calls from northbound application program interface (API) to southbound API. Fulfilment management system can take a single request
30 containing superset of all attributes (of all the southbound APIs) and then execute
14

the sequence of the southbound API calls (workflow) and provide final response after completion of APIs. Fulfilment management system processes which are configured to run any process support sequential, parallel, conditional and loop workflow pattern. 5
[0044] A fulfilment management system (FMS) is a robust and flexible solution for managing complex inter-system communications, translating requests into actionable tasks, and ensuring efficient execution of these tasks based on predefined workflows. The FMS orchestrates and manages requests and responses between
10 different systems or interfaces. The key functions performed by the FMS may
include:
[0045] Translation of Requests: The FMS accepts any incoming request from a northbound interface. This request can then be translated into multiple outgoing API calls to one or more southbound interfaces.
15 [0046] Superset of Attributes: The system can handle a single request that
contains a superset of all possible attributes of all the southbound APIs. This enables it to understand and manage complex requests that might cover multiple aspects of the system's functions. [0047] Sequential Execution of API Calls: After translating the incoming
20 request, the FMS can execute a sequence of API calls to the southbound interfaces.
The sequence and number of these calls (n) can vary based on the requirements of the incoming request. A northbound interface means an interface that lets a specific component communicate with a higher-level component in the same network. A southbound interface means an interface that enables a specific component to
25 communicate with a lower-level component.
[0048] Response Generation: The FMS provides milestone or final responses after the completion of the individual or all API calls. This ensures the northbound interface is kept informed of the progress and outcomes of its requests. [0049] Workflow Pattern Support: The FMS is designed to support various
30 workflow patterns. This includes sequential execution (one step after another),
15

parallel execution (multiple steps at the same time), conditional execution (based on certain conditions), and loop execution (repeated steps). The choice of pattern depends on the specific needs of the process or request being handled.
5 [0050] As used herein, NBI refers to a Northbound Interface, which is a type of
interface within the Fulfilment Management System (FMS) that facilitates
communication and interaction with higher-level management systems, external
platforms, or user interfaces. The NBI system [202] allows these external entities
to send requests and receive responses from the FMS, enabling tasks such as service
10 activation, data retrieval, and status updates
[0051] As used herein, SBI refers to a Southbound Interface, which is a type of
interface within the Fulfilment Management System (FMS) that facilitates
communication and interaction with lower-level network components, services, or
15 devices. The SBI allows the FMS to send commands, receive data, and manage
operations on these network elements
[0052] An application programming interface (API) is a set of protocols, rules, and tools that specifies how software components should interact and communicate
20 with each other. APIs are used in all kinds of digital environments such as Web
APIs, for example, HTTP APIs or REST APIs; Operating System APIs define how different software applications interact with the operating system. For example, if a software program needs to display a window on your screen, it uses an API provided by the operating system to do so; and database APIs enable
25 communication between an application and a database. For example, if an
application needs to retrieve some data from a database, it uses a database API to send a query to the database and receive the results. In the context of the Fulfilment Management System, APIs would be used to send requests between different systems or interfaces (northbound and southbound interfaces), allowing them to
30 communicate and share data.
16

[0053] As discussed in the background section, the current known solutions for
synchronous and asynchronous response mechanism in a fulfilment management
system have several limitations related to incompatibility between systems, limited
efficiency with synchronous APIs, complexity with asynchronous APIs, increased
5 development and integration effort, and scalability issues. Traditional systems often
face compatibility issues due to the mismatch between synchronous (sync) and asynchronous (async) APIs. If one system supports only sync APIs and another only async APIs, their differing methods of handling requests and responses can hinder effective communication. Synchronous APIs require the client to wait for a
10 response before proceeding, which can lead to inefficient use of resources,
especially if responses take a long time. This is known as "blocking." Conversely, asynchronous APIs allow the client to process other tasks while waiting for a response. However, this efficiency comes with increased complexity, as the client must be equipped to handle the response whenever it arrives, demanding more
15 intricate programming and error management. Additionally, traditional systems
often require custom code each time they interact with a new interface or third-party system, increasing development time and effort. In terms of scalability, systems supporting only sync APIs can struggle because every active request ties up resources until a response is received. Asynchronous APIs can aid scalability but
20 introduce challenges in managing and coordinating responses, particularly as the
system grows.
[0054] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by introducing a configurable
25 synchronous and asynchronous response mechanism in a Fulfilment Management
System (FMS). The proposed system integrates seamlessly with multiple interfaces and third-party systems, addressing incompatibility issues by supporting both synchronous (sync) and asynchronous (async) APIs. The proposed FMS comprises a transceiver unit configured to receive requests from a variety of requesting
30 systems, including Northbound Interface (NBI) systems and third-party systems.
17

Upon receiving a request, the determination unit identifies the type of API
interaction required whether it is synchronous or asynchronous. The proposed
system thus ensures that the FMS can cater to different interaction needs without
hindering communication. By configuring the FMS to handle both types of
5 interactions, the present disclosure eliminates the inefficiencies associated with
synchronous APIs, such as resource blocking, and the complexities of asynchronous APIs, like intricate programming and error management. The analysis unit within the FMS structures the response for immediate transmission in synchronous interactions, ensuring minimal wait times, and prepares responses for
10 later transmission in asynchronous interactions, allowing for efficient resource
utilization and scalability. The dual capability reduces the need for custom code with each new interface or third-party system, significantly lowering development and integration efforts. Moreover, the present disclosure enhances scalability by efficiently managing resources for synchronous requests, which tie up resources
15 until a response is received, and asynchronously handling multiple requests without
resource blocking. This flexible and dynamic response mechanism ensures that the FMS can grow and adapt to increasing demands, maintaining optimal performance even as the system scales. Thus, the configurable synchronous and asynchronous response mechanism presented in this disclosure provides a comprehensive solution
20 to the limitations found in traditional fulfilment management systems.
[0055] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
25 [0056] Referring to FIG. 1, an exemplary block diagram of a system [100] for
configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system (FMS) [101] is shown, in accordance with the exemplary embodiments of the present invention. The System [100] comprises the FMS [101]. The FMS [101] further comprises a transceiver
30 unit [102], a determination unit [104], and an analysis unit [106]. Also, all of the
18

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 number of said units, as required to implement the features
5 of the present disclosure.
[0057] The system [100] for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system (FMS) [101] comprises the transceiver unit [102]. The transceiver unit [102] is configured
10 to receive a request for interaction from a requesting system, the requesting system
comprising at least one of a northbound interface (NBI) system [202] and a third-party system. For example, an NBI system used in a telecom network sends a service activation request to the FMS [101]. The request, which might include details such as the customer's phone number and the type of service to be activated,
15 is first received by the transceiver unit [102]. The interaction refers to the process
of communication between the FMS [101] and an external requesting system, such as a northbound interface (NBI) system [202] or a third-party system. The communication involves the sending and receiving of requests and responses, where the requesting system sends a request to the FMS [101] to perform a specific
20 task or provide certain information, and the FMS [101] processes this request and
sends back an appropriate response. The third-party system refers to external platforms and services that interact with the FMS [101]. For example, a customer relationship management (CRM) system or various network nodes or network functions.
25
[0058] The request is one of a call type request or a command type request. The call type requests and the command type request are associated with performing a set of tasks on data in the FMS [101]. The call-type request includes queries for data or status updates, where the requesting system seeks information from the FMS
30 [101]. For example, a customer service platform may send a call-type request to the
19

FMS [101] to check the status of service activation or to retrieve customer account
details. The command-type request includes instructions for the FMS [101] to
perform specific actions or operations. For example, a telecom service management
platform might send a command-type request to the FMS [101] to activate a new
5 service for a customer or to update service configurations.
[0059] The system [100] comprises the determination unit [104] connected at least to the transceiver unit [102], the determination unit [104] is configured to determine a type of application programming interface (API) interaction supported
10 by the requesting system based on the received request, wherein the type of API
interaction is one of a synchronous interaction and an asynchronous interaction. For example, when a request is received from a telecom service management platform (an NBI system), the determination unit [104] analyzes the request to determine whether the platform supports synchronous or asynchronous API interactions.
15
[0060] The type of API interaction supported by the requesting system is determined based on how the requesting system handles communication and responses. In a synchronous API interaction, the requesting system sends a request and waits for an immediate response before proceeding with any other operations.
20 This type of interaction is known as "blocking" because the requesting system is
blocked from performing further actions until it receives the response. For example, a customer service portal might send a request to the Fulfillment Management System (FMS) [101] to activate a new service. The portal waits for a confirmation response from the FMS [101] before it can inform the customer that the service
25 activation is successful. This ensures that the customer receives real-time feedback.
In an asynchronous API interaction, the requesting system sends a request and does not wait for an immediate response. Instead, it continues with other tasks, and the response is processed whenever it is received. This type of interaction is known as "non-blocking" because the requesting system does not need to wait for the
30 response to continue its operations. For example, a third-party billing system might
20

send a request to the FMS [101] to update billing records. The billing system does not need an immediate response and can continue processing other billing tasks. The FMS [101] processes the request and sends a response back to the billing system when the update is completed. 5
[0061] The system [100] comprises the analysis unit [106] connected at least to the determination unit [104], the analysis unit [106] configured to configure the FMS [101] to generate a response based on the determined type of API interaction. For example, once the determination unit [104] has established that a request from
10 a customer service management platform (an NBI system) requires a synchronous
API interaction, the analysis unit [106] configures the FMS [101] to generate an immediate response. The configuration involves generating the response data and transmitting it back to the customer service management platform without delay, as the platform is waiting for this immediate feedback to proceed with further
15 operations, such as confirming a service activation to the customer.
[0062] However, if the determination unit [104] identifies that a request from a third-party billing system requires an asynchronous API interaction, the analysis unit [106] configures the FMS [101] to handle the response differently. In this case,
20 the analysis unit [106] instructs the FMS [101] to process the request and queue the
response for later transmission. The billing system does not need an immediate response and can continue with other tasks, allowing the FMS [101] to send the response once the processing is complete, thereby optimizing resource utilization and ensuring efficient processing of multiple requests.
25
[0063] The analysis unit [106] determines and implements applicable settings for the Fulfillment Management System (FMS) [101] to generate the appropriate type of response. Upon receiving the interaction type (synchronous or asynchronous), the analysis unit [106] evaluates the request details and determines the required
30 configuration settings. The analysis unit [106] may then apply the applicable
21

settings to the FMS [101 to generate the response. The response may correspond to
prioritizing tasks, structuring responses, allocating resources, and scheduling
operations to ensure the system responds accurately and efficiently to the request,
whether immediate for synchronous interactions or queued for asynchronous
5 interactions.
[0064] The transceiver unit [102] is further configured to transmit the generated
response to the requesting system based on the determined type of API interaction.
For example, for synchronous interactions, where the requesting system requires an
10 immediate response, the transceiver unit [102] is set up to send the response as soon
as it is generated. For instance, if a telecom service management platform (an NBI
system) requests the activation of a customer service, the transceiver unit [102]
ensures that the confirmation of this activation is transmitted back to the platform
without delay, enabling the platform to proceed with informing the customer in real-
15 time. In contrast, for asynchronous interactions, where the requesting system does
not need an immediate response, the transceiver unit [102] is configured to manage
the transmission of the response in a queued manner. An example of this would be
a third-party billing system that updates billing records. Once the FMS [101]
processes this update, the transceiver unit [102] sends the acknowledgement back
20 to the billing system when the system is ready, without requiring the billing system
to wait for the response before continuing its other operations.
[0065] The analysis unit [106] for configuring the FMS [101] is further configured
to perform one of: structuring the response for immediate transmission for the
25 synchronous interaction and preparing the response for later transmission for the
asynchronous interaction.
[0066] For example, for synchronous interactions, where the requesting system
requires an immediate response, the analysis unit [106] structures the response in a
30 way that it can be transmitted without delay. For example, if a customer service
22

platform sends a request to the FMS [101] to activate a new service, the analysis
unit [106] ensures that the service activation process is initiated promptly and that
a confirmation response is generated and sent back immediately. The structured
response includes all necessary information, such as confirmation status, activation
5 time, and any relevant customer details, ensuring that the requesting system
receives the feedback it needs to proceed with subsequent actions in real time. In contrast, for asynchronous interactions, where the requesting system does not need an immediate response, the analysis unit [106] prepares the response for later transmission. This involves processing the request and queuing the response for
10 when it is ready to be sent. For instance, if a third-party billing system sends a
request to update billing records, the analysis unit [106] processes this update and prepares an acknowledgement response. The response is then stored and scheduled for transmission once the processing is complete. The preparation includes compiling the response data, verifying the accuracy of the update, and ensuring that
15 all relevant details are included before the response is sent.
[0067] The transceiver unit [102], for transmitting the generated response, is
further configured to perform one of: sending an immediate response for the
synchronous interaction, and sending an acknowledgment when ready for the
20 asynchronous interaction, aligning with the configured type of API interaction.
[0068] For example, for synchronous interactions, the transceiver unit [102] is configured to send an immediate response. This means that when the FMS [101] receives a request that requires an immediate reply, the transceiver unit [102]
25 ensures that the response is promptly generated and sent back to the requesting
system without delay. For example, if a customer service platform sends a request to activate a service, the transceiver unit [102] facilitates the rapid transmission of the activation confirmation, enabling the customer service platform to quickly inform the customer that the service has been successfully activated. In the case of
30 asynchronous interactions, the transceiver unit [102] is configured to send an
23

acknowledgment once the response is ready. This involves processing the request
at the FMS [101] and preparing the response, which is then queued for transmission
when the processing is complete. For instance, if a third-party billing system sends
a request to update billing records, the transceiver unit [102] handles the
5 transmission of an acknowledgment that the update request has been received and
will be processed. The final response, confirming the completion of the billing update, is sent once the FMS [101] has finished processing the request.
[0069] FIG. 2 illustrates an exemplary block diagram of a system architecture
10 [200] for configuring a synchronous response mechanism and an asynchronous
response mechanism in a fulfilment management system, in accordance with
exemplary embodiments of the present disclosure. The system architecture [200]
includes the NBI [202], the FMS [101], and a plurality of network nodes (network
node 1 [204A], network node 2 [204B]……..network node N [204N]) (collectively
15 referred to as network nodes [204] herein or individually referred to as network
node [204] herein). The network nodes [204] may correspond to third-party systems. Examples of network nodes [204] includes but not limited only to PCF [522], AMF [506], and SMF [508].
20 [0070] The FMS [101] includes a transceiver unit [102], which is configured to
receive requests for interaction from requesting systems. These requesting systems can be a Northbound Interface (NBI) system [202] or any third-party system (such as the network nodes [204]). For example, an NBI system [202] might send a request for activating a telecom service, or a third-party system might request an
25 update to billing records.
[0071] Connected at least to the transceiver unit [102] is the determination unit
[104]. The determination unit [104] within the FMS [101] is configured to
determine the type of application programming interface (API) interaction
30 supported by the requesting system based on the received request. The
24

determination unit [104] analyzes the request to ascertain whether it requires a
synchronous interaction, which requires an immediate response, or an
asynchronous interaction, which allows for a delayed response. For example, if a
request from an NBI system [202] requires real-time confirmation of service
5 activation, it would be classified as synchronous. Conversely, a request for updating
billing records from a third-party system that does not require immediate confirmation might be classified as asynchronous
[0072] The analysis unit [106] is connected at least to the determination unit
10 [104]. The determination unit [104] withing the FMS [101] is configured to
configure the FMS [101] to generate a response based on the determined type of API interaction. For synchronous interactions, the analysis unit [106] ensures that the response is structured and ready for immediate transmission. For example, upon receiving a synchronous request for service activation, the analysis unit [106]
15 quickly processes the request and generates a confirmation response. For
asynchronous interactions, the analysis unit [106] prepares the response for later transmission, ensuring that the system can manage its resources efficiently. For instance, if the request involves a billing update, the response is generated and queued, to be sent once the processing is complete.
20
[0073] The transceiver unit [102] is further configured to transmit the generated response to the requesting system based on the determined type of API interaction. For synchronous interactions, the transceiver unit [102] sends the response immediately back to the requesting system, ensuring that there is minimal delay.
25 For example, the confirmation of service activation is transmitted instantly to the
NBI system [202]. For asynchronous interactions, the response is transmitted when it is ready, allowing the requesting system to continue its operations without waiting for an immediate reply. For instance, an acknowledgement of a billing update is sent once the FMS [101] has processed the update.
30
25

[0074] Referring to FIG. 3 an exemplary method flow diagram [300] for
configuring a synchronous response mechanism and an asynchronous response
mechanism in a fulfilment management system is disclosed. In an implementation,
the method [300] is performed by the system [100] or a processor associated with
5 the system [100]. As shown in FIG. 3, the process begins at step [302].
[0075] At method step [304], the method comprises receiving, by a transceiver unit [102] at the FMS [101], a request for interaction from a requesting system, the requesting system comprising at least one of a northbound interface (NBI) system
10 [202] and a third-party system. For example, an NBI system [202] used in a telecom
network sends a service activation request to the FMS [101]. The request, which might include details such as the customer's phone number and the type of service to be activated, is first received by the transceiver unit [102]. The interaction refers to the process of communication between the FMS [101] and an external requesting
15 system, such as a northbound interface (NBI) system [202] or a third-party system.
The communication involves sending and receiving of requests and responses, where the requesting system sends a request to the FMS [101] to perform a specific task or provide certain information, and the FMS [101] processes this request and sends back an appropriate response. The third-party system refers to external
20 platforms and services that interact with the FMS [101]. For example, a customer
relationship (CRM) system or various network nodes or network functions.
[0076] The request is one of a call type request or a command type request. The call type requests and the command type request are associated with performing a
25 set of tasks on data in the FMS [101]. The call-type request includes queries for
data or status updates, where the requesting system seeks information from the FMS [101]. For example, a customer service platform may send a call-type request to the FMS [101] to check the status of service activation or to retrieve customer account details. The command-type request includes instructions for the FMS [101] to
30 perform specific actions or operations. For example, a telecom service management
26

platform might send a command-type request to the FMS [101] to activate a new service for a customer or to update service configurations.
[0077] At method step [306], the method comprises determining, by a
5 determination unit [104] at the FMS [101], a type of application programming
interface (API) interaction supported by the requesting system based on the
received request, wherein the type of API interaction is one of a synchronous
interaction and an asynchronous interaction. For example, when a request is
received from a telecom service management platform (an NBI system [202]), the
10 determination unit [104] analyzes the request to determine whether the platform
supports synchronous or asynchronous API interactions.
[0078] The type of API interaction supported by the requesting system is determined based on how the requesting system handles communication and
15 responses. In a synchronous API interaction, the requesting system sends a request
and waits for an immediate response before proceeding with any other operations. This type of interaction is known as "blocking" because the requesting system is blocked from performing further actions until it receives the response. For example, a customer service portal might send a request to the Fulfillment Management
20 System (FMS) [101] to activate a new service. The portal waits for a confirmation
response from the FMS [101] before it can inform the customer that the service activation is successful. This ensures that the customer receives real-time feedback. In an asynchronous API interaction, the requesting system sends a request and does not wait for an immediate response. Instead, it continues with other tasks, and the
25 response is processed whenever it is received. This type of interaction is known as
"non-blocking" because the requesting system does not need to wait for the response to continue its operations. For example, a third-party billing system might send a request to the FMS [101] to update billing records. The billing system does not need an immediate response and can continue processing other billing tasks.
27

The FMS [101] processes the request and sends a response back to the billing system when the update is completed.
[0079] At method step [308], the method comprises configuring the FMS [101],
5 by an analysis unit [106] at the FMS [101], to generate a response based on the
determined type of API interaction. For example, once the determination unit [104]
has established that a request from a customer service management platform (an
NBI system [202]) requires a synchronous API interaction, the analysis unit [106]
configures the FMS [101] to generate an immediate response. The configuration
10 involves generating the response data and transmitting it back to the customer
service management platform without delay, as the platform is waiting for this immediate feedback to proceed with further operations, such as confirming a service activation to the customer.
15 [0080] However, if the determination unit [104] identifies that a request from a
third-party billing system requires an asynchronous API interaction, the analysis unit [106] configures the FMS [101] to handle the response differently. In this case, the analysis unit [106] instructs the FMS [101] to process the request and queue the response for later transmission. The billing system does not need an immediate
20 response and can continue with other tasks, allowing the FMS [101] to send the
response once the processing is complete, thereby optimizing resource utilization and ensuring efficient processing of multiple requests.
[0081] The analysis unit [106] determines and implements the necessary settings
25 for the Fulfilment Management System (FMS) [101] to generate the appropriate
type of response. Upon receiving the interaction type (synchronous or
asynchronous), the analysis unit [106] evaluates the request details and determines
the required configuration settings. It then applies these settings to the FMS [101],
setting up the system to generate the response. This involves prioritizing tasks,
30 structuring responses, allocating resources, and scheduling operations to ensure the
28

system responds accurately and efficiently to the request, whether immediate for synchronous interactions or queued for asynchronous interactions.
[0082] At method step [310], the method comprises transmitting, by the
5 transceiver unit [102], the generated response to the requesting system based on the
determined type of API interaction. For example, for synchronous interactions, where the requesting system requires an immediate response, the transceiver unit [102] is set up to send the response as soon as it is generated. For instance, if a telecom service management platform (an NBI system [202]) requests the
10 activation of a customer service, the transceiver unit [102] ensures that the
confirmation of this activation is transmitted back to the platform without delay, enabling the platform to proceed with informing the customer in real-time. In contrast, for asynchronous interactions, where the requesting system does not need an immediate response, the transceiver unit [102] is configured to manage the
15 transmission of the response in a queued manner. An example of this would be a
third-party billing system that updates billing records. Once the FMS [101] processes this update, the transceiver unit [102] sends the acknowledgement back to the billing system when the system is ready, without requiring the billing system to wait for the response before continuing its other operations.
20
[0083] Thereafter, the method terminates at step [312].
[0084] FIG. 4 illustrates an exemplary block diagram of a computer device [400] (also referred to herein as a computer system [400]) upon which an embodiment of
25 the present disclosure may be implemented. In an implementation, the computing
device implements the method for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system (FMS) [101] using the system [100]. In another implementation, the computing device itself implements the method for configuring a synchronous response
30 mechanism and an asynchronous response mechanism in a fulfilment management
29

system (FMS) [101] by using one or more units configured within the computing device, wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
5 [0085] The computer system [400] encompasses a wide range of electronic
devices capable of processing data and performing computations. Examples of
computer system [400] include, but are not limited only to, personal computers,
laptops, tablets, smartphones, user equipment (UE), servers, and embedded
systems. The devices may operate independently or as part of a network and can
10 perform a variety of tasks such as data storage, retrieval, and analysis. Additionally,
computer system [400] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications.
15 [0086] The computer system [400] may include a bus [402] or other
communication mechanism for communicating information, and a processor [404] coupled with bus [402] for processing information. The processor [404] may be, for example, a general-purpose microprocessor. The computer system [400] may also include a main memory [406], such as a random-access memory (RAM), or other
20 dynamic storage device, coupled to the bus [402] for storing information and
instructions to be executed by the processor [404]. The main memory [406] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [404]. Such instructions, when stored in non-transitory storage media accessible to the processor
25 [404], render the computer system [400] into a special-purpose machine that is
customized to perform the operations specified in the instructions. The computer system [400] further includes a read only memory (ROM) [408] or other static storage device coupled to the bus [402] for storing static information and instructions for the processor [404].
30
30

[0087] A storage device [410], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [402] for storing information and
instructions. The computer system [400] may be coupled via the bus [402] to a
display [412], such as a cathode ray tube (CRT), for displaying information to a
5 computer user. An input device [414], including alphanumeric and other keys, may
be coupled to the bus [402] for communicating information and command
selections to the processor [404]. Another type of user input device may be a cursor
controller [416], such as a mouse, a trackball, or cursor direction keys, for
communicating direction information and command selections to the processor
10 [404], and for controlling cursor movement on the display [412]. This 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.
[0088] The computer system [400] may implement the techniques described
15 herein using customized hard-wired logic, one or more Application-Specific
Integrated Circuits (ASICs) or Field Programmable Gate Arrays (FPGAs),
firmware and/or program logic which in combination with the computer system
[400] causes or programs the computer system [400] to be a special-purpose
machine. According to one embodiment, the techniques herein are performed by
20 the computer system [400] in response to the processor [404] executing one or more
sequences of one or more instructions contained in the main memory [406]. Such
instructions may be read into the main memory [406] from another storage medium,
such as the storage device [410]. Execution of the sequences of instructions
contained in the main memory [406] causes the processor [404] to perform the
25 process steps described herein. In alternative embodiments, hard-wired circuitry
may be used in place of or in combination with software instructions.
[0089] The computer system [400] also may include a communication interface
[418] coupled to the bus [402]. The communication interface [418] provides a two-
30 way data communication coupling to a network link [420] that is connected to a
31

local network [422]. For example, the communication interface [418] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of
telephone line. As another example, the communication interface [418] may be a
5 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 [418] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
10
[0090] The computer system [400] can send messages and receive data, including program code, through the network(s), the network link [420] and the communication interface 518. In the Internet example, a server [430] might transmit a requested code for an application program through the Internet [428], the Internet
15 Service Provider (ISP) [426], the Host [424], the local network [422] and the
communication interface [418]. The received code may be executed by the processor [404] as it is received, and/or stored in the storage device [410], or other non-volatile storage for later execution.
20 [0091] Another aspect of the present disclosure relates to a system [100] for
configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system (FMS) [101], the FMS [101] further comprising a transceiver unit [102] configured to receive a request for interaction from a requesting system, the requesting system comprising at least one of a
25 northbound interface (NBI) system [202] and a third-party system. The FMS [101]
further comprises a determination unit [104] connected at least to the transceiver unit [102], the determination unit [104] configured to determine a type of application programming interface (API) interaction supported by the requesting system based on the received request, wherein the type of API interaction is one of
30 a synchronous interaction and an asynchronous interaction. The FMS [101] further
32

comprises an analysis unit [106] connected at least to the determination unit [104],
the analysis unit [106] configured to configure the FMS [101] to generate a response
based on the determined type of API interaction. The FMS [101] further comprises
the transceiver unit [102] further configured to transmit the generated response to
5 the requesting system based on the determined type of API interaction.
[0092] Another aspect of the present disclosure provides a user equipment (UE) for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system (FMS [101]) [101]. The UE [502]
10 includes a processor configured to transmit a request for interaction to a requesting
system, the requesting system comprising at least one of a northbound interface (NBI) system [202] and a third-party system; determine a type of application programming interface (API) interaction supported by the requesting system based on the received request, wherein the type of API interaction is one of a synchronous
15 interaction and an asynchronous interaction; configure the FMS [101] to generate a
response based on the determined type of API interaction; and receive the generated response from the requesting system based on the determined type of API interaction.
20 [0093] According to yet another aspect, a non-transitory computer-readable
storage medium storing instruction for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system (FMS) [101] is disclosed. The storage medium comprising executable code which, when executed by one or more units of a system, causes: a transceiver unit
25 [102] to receive a request for interaction from a requesting system, the requesting
system comprising at least one of a northbound interface (NBI) system [202] and a third-party system; a determination unit [104] connected at least to the transceiver unit [102], the determination unit [104] to determine a type of application programming interface (API) interaction supported by the requesting system based
30 on the received request, wherein the type of API interaction is one of a synchronous
interaction and an asynchronous interaction; an analysis unit [106] connected at
33

least to the determination unit [104], the analysis unit [106] to configure the FMS [101] to generate a response based on the determined type of API interaction; and the transceiver unit [102] to further transmit the generated response to the requesting system based on the determined type of API interaction. 5
[0094] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various
10 configurations and combinations thereof are within the scope of the disclosure. The
functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope
15 of the present disclosure.
[0095] While considerable emphasis has been placed herein on the disclosed
embodiments, it will be appreciated that many embodiments can be made and that
many changes can be made to the embodiments without departing from the
20 principles of the present disclosure. These and other changes in the embodiments
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.
34

I/We Claim:
1. A method for configuring a synchronous response mechanism and an
asynchronous response mechanism in a fulfilment management system
(FMS) [101], said method comprising:
receiving, by a transceiver unit [102] at the FMS [101], a request for interaction from a requesting system, the requesting system comprising at least one of a northbound interface (NBI) system [202] and a third-party system;
determining, by a determination unit [104] at the FMS [101], a type of application programming interface (API) interaction supported by the requesting system based on the received request, wherein the type of API interaction is one of a synchronous interaction and an asynchronous interaction;
configuring the FMS [101], by an analysis unit [106] at the FMS [101], to generate a response based on the determined type of API interaction; and
transmitting, by the transceiver unit [102], the generated response to the requesting system based on the determined type of API interaction.
2. The method as claimed in claim 1, wherein the request is one of a call type requests and a command type request.
3. The method as claimed in claim 2, wherein the one of the call type requests and the command type request is associated with performing a set of tasks on a data in the FMS [101].

4. The method as claimed in claim 1, wherein the determining the type of API interaction comprises analysing, by the analysis unit [106], the request for determining one of the synchronous interactions and the asynchronous interaction supported by the requesting system.
5. The method as claimed in claim 3, wherein the synchronous interaction corresponds to a blocking operation, and the asynchronous interaction corresponds to a non-blocking operation, wherein the blocking operation comprises waiting, by the requesting system, for a response before proceeding with other tasks, and the non-blocking operation comprises continuing, by the requesting system, with other operations without waiting for a response.
6. The method as claimed in claim 1, wherein the configuring the FMS [101], by the analysis unit [106] at the FMS [101], to generate the response comprises one of: structuring the response for immediate transmission for the synchronous interaction, and preparing the response for later transmission for the asynchronous interaction.
7. The method as claimed in claim 1, wherein the transmitting, by the transceiver unit [102], the generated response comprises one of: sending, by the transceiver unit [102], an immediate response for the synchronous interaction, and sending, by the transceiver unit [102], an acknowledgment when ready for the asynchronous interaction, aligning with the configured type of API interaction.
8. A system [100] for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system (FMS) [101], the FMS [101] further comprising:

a transceiver unit [102] configured to receive a request for interaction from a requesting system, the requesting system comprising at least one of a northbound interface (NBI) system [202] and a third-party system;
a determination unit [104] connected at least to the transceiver unit [102], the determination unit [104] configured to determine a type of application programming interface (API) interaction supported by the requesting system based on the received request, wherein the type of API interaction is one of a synchronous interaction and an asynchronous interaction;
an analysis unit [106] connected at least to the determination unit [104], the analysis unit [106] configured to configure the FMS [101] to generate a response based on the determined type of API interaction; and
the transceiver unit [102] further configured to transmit the generated response to the requesting system based on the determined type of API interaction.
9. The system [100] as claimed in claim 8, wherein the request is one of a call type requests or a command type request.
10. The system [100] as claimed in claim 9, wherein the one of the call type requests and the command type request is associated with performing a set of tasks on a data in the FMS [101].
11. The system [100] as claimed in claim 8, wherein for determining the type of API interaction, the analysis unit [106] is configured to analyse the request for determining one of the synchronous interactions or the asynchronous interaction supported by the requesting system.

12. The system [100] as claimed in claim 10, wherein the synchronous interaction corresponds to a blocking operation and the asynchronous interaction corresponds to a non-blocking operation, wherein the blocking operation comprises waiting, by the requesting system, for a response before proceeding with other tasks, and the non-blocking operation comprises continuing, by the requesting system, with other operations without waiting for a response.
13. The system [100] as claimed in claim 8, wherein the analysis unit [106] for configuring the FMS [101], is configured to perform one of: structuring the response for immediate transmission for the synchronous interaction, and preparing the response for later transmission for the asynchronous interaction.
14. The system [100] as claimed in claim 8, wherein the transceiver unit [102], for transmitting the generated response, is configured to perform one of: sending an immediate response for the synchronous interaction, and sending an acknowledgement when ready for the asynchronous interaction, aligning with the configured type of API interaction.
15. A user equipment (UE) [502] for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system (FMS) [101], said UE [502] comprising:
a processor configured to:
transmit a request for interaction to a requesting system, the requesting system comprising at least one of a northbound interface (NBI) system [202] and a third-party system;
determine a type of application programming interface (API) interaction supported by the requesting system based on the request,

wherein the type of API interaction is one of a synchronous interaction and an asynchronous interaction;
configure the FMS [101] to generate a response based on the determined type of API interaction; and
receive the generated response from the requesting system based on the determined type of API interaction.
16. A non-transitory computer-readable storage medium storing instruction for configuring a synchronous response mechanism and an asynchronous response mechanism in a fulfilment management system (FMS) [101], the storage medium comprising executable code which, when executed by one or more units of a system, causes:
a transceiver unit [102] to receive a request for interaction from a requesting system, the requesting system comprising at least one of a northbound interface (NBI) system [202] and a third-party system;
a determination unit [104] connected at least to the transceiver unit [102], the determination unit [104] to determine a type of application programming interface (API) interaction supported by the requesting system based on the received request, wherein the type of API interaction is one of a synchronous interaction and an asynchronous interaction;
an analysis unit [106] connected at least to the determination unit [104], the analysis unit [106] to configure the FMS [101] to generate a response based on the determined type of API interaction; and
the transceiver unit [102] to further transmit the generated response to the requesting system based on the determined type of API interaction.