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 INTEGRATING SUBSCRIPTION DATA IN A
BILLING ENTITY”
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 INTEGRATING SUBSCRIPTION DATA IN A BILLING
ENTITY
TECHNICAL FIELD
5
[0001] Embodiments of the present disclosure generally relate to a billing facilitation service. More particularly, embodiments of the present disclosure relate to a method and system for integrating subscription data in a billing entity for enhancing a user experience during a subscription purchase event associated with the user.
10
BACKGROUND
[0002] The following description of the 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
15 related to various features of the present disclosure. However, it should be appreciated that this section
is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each
20 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. The third-generation (3G) technology marked
the introduction of high-speed internet access, mobile video calling, and location-based services. The
25 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. Further, reducing call
30 drops and latency is of paramount importance in the telecommunications industry. Call drops can be
frustrating for users, and they can also result in lost revenue for service providers. Latency, on the other hand, refers to the time it takes for data to travel from one device to another and can cause delays and disruptions in communication. The introduction of 5G technology promises to address these issues
2

by delivering ultra-low latency and high-speed data transmission. With 5G, call drops are going to be
minimized, and users are going to experience seamless, uninterrupted communication. Additionally,
5G technology may enable the development of new applications and services that require high-speed,
low-latency communication, such as remote surgeries, autonomous vehicles, and virtual reality. The
5 reduction of call drops and latency is crucial in ensuring that users have access to reliable and efficient
communication services, and the 5G technology is a significant step towards achieving this goal.
[0004] A user has to pay some amount when they buy or subscribe to a subscription plan. In order to maintain billing for the subscription, a billing system is utilized, and the subscription plan is
10 maintained by a subscription engine (SE). Both the billing system and the Subscription Engine (SE)
are required for a successful and smooth buying and subscribing of the subscription plan. Conventionally, both the billing system and the SE are different systems. Further, both the billing system and the SE need to be synchronized in order to maintain smooth usage of the subscription and allow the transmittal of a subscription data records (SDR) files and a payment data records (PDR) files
15 in various file formats in a timely manner between the billing system and the SE. The SDR files and
the PDR files consumed by the billing system, respectively, can be of various formats and may contain information under various headers such as, but not limited to, Name, Billing Address, Gender, Age (no gender or age), Subscription Plan Details, Geographical Location, and the like. Further, every subscription platform has a pre-defined limit on the data that it can download or upload.
20
[0005] Further, over the period of time, various solutions have been developed to integrate the Subscription Data Record (SDR) and the Payment Data Record (PDR) into the subscription engine. However, there are certain challenges with existing solutions. The existing solutions for the present disclosure do not provide a mechanism to sync the purchase and subscription information from the SE
25 to the billing system. Further, the existing solutions do not allow for providing the data in a
configurable format or headers based on the needs of the user. Furthermore, the existing solutions do not provide a mechanism to group records based, but not limited to, on product, system IP, date, time, geographical location, and the like. Also, the existing solutions do not have the capability to select the file format that is generated during SDR-PDR. Further, an over-the-top (OTT) platforms do not have
30 the capability to store files according to their storage or the capability to select the data record in a file.
[0006] Thus, there exists an imperative need in the art for integration of a Subscription Data Record (SDR) and a Payment Data Record (PDR) in a subscription engine for a successful and smooth subscription of the subscription plan, which the present disclosure aims to address.
35
3

SUMMARY OF THE DISCLOSURE
[0007] 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
5 identify the key features or the scope of the claimed subject matter.
[0008] An aspect of the present disclosure may relate to a method for integrating subscription data in a billing entity. The method comprises producing, by a production unit at a subscription engine, a subscription and payment data in an event of performance of a payment related to an order by one or
10 more users. The method further comprises preparing, by a records preparation unit at the subscription
engine, a set of one or more subscription data records (SDR) and payment data records (PDR) files based on the subscription and payment data and a predefined set of rules. The method further comprises sending, by the records preparation unit at the subscription engine, the set of one or more SDR and PDR files to one or more servers, wherein a FTP details and a file location of the one or
15 more SDR and PDR files are shared using at least one of a push mechanism and a pull mechanism.
The method further comprises receiving, by a billing unit at the subscription engine, the set of one or more SDR and PDR files for facilitating integration of subscription data in the billing entity.
[0009] In an exemplary aspect of the present disclosure, the preparing, by the records preparation
20 unit, the set of one or more SDR and PDR files comprises determining, by the records preparation
unit, one of an availability and an absence, of last file dump details, wherein the last file dump details
are determined available in an event the last file dump details are available, and the last file dump
details are determined absent in an event the last file dump details are not available, determining, by
the records preparation unit, one of a new file creation indication and an existing file modification
25 indication, in an event the last file dump details are determined available, creating, by the records
preparation unit, a new set of one or more SDR and PDR files, in an event of one of: the last file dump
details are determined absent, and the new file creation indication is determined, and writing, by the
records preparation unit, one of: the subscription and payment data in the new set of one or more SDR
and PDR files in an event of creation of the new set of one or more SDR and PDR files, and the
30 subscription and payment data in an existing set of one or more SDR and PDR files in an event of
determination of existing file modification indication.
[0010] In an exemplary aspect of the present disclosure, a filename associated with each file from the one or more SDR and PDR files is based on one or more pre-defined templates.
4

[0011] In an exemplary aspect of the present disclosure, the filename associated with each file from
the one or more SDR and PDR files, comprise dynamic attributes in, the dynamic attributes comprising
5 a Service Type attribute, a Business Interaction attribute, a Subscription Type attribute, a Circle
attribute, a CDR Type attribute, an Instance identity attribute, a Date and Time attribute, and a Sequence Number attribute.
[0012] In an exemplary aspect of the present disclosure, the set of one or more SDR and PDR files
10 are sent by the records preparation unit to one or more servers after a pre-defined configurable time
period.
[0013] In an exemplary aspect of the present disclosure, the method further comprises storing, by a local storage unit at the subscription engine, the one or more SDR and PDR files.
15
[0014] In an exemplary aspect of the present disclosure, the predefined set of rules comprise a creation of new SDR and PDR files during the preparing of the one or more SDR and PDR files, in an event of satisfaction of one or more conditions comprising a change of hour condition, a threshold file size breach condition, a threshold records number breach condition, and a change of data condition.
20
[0015] An aspect of the present disclosure may relate to a system for integrating subscription data in a billing entity, the system comprising a subscription engine, the subscription engine further comprises a production unit configured to produce a subscription and payment data in an event of performance of a payment related to an order by one or more users. The subscription engine further comprises a
25 records preparation unit connected to at least the production unit, the records preparation unit
configured to prepare a set of one or more subscription data records (SDR) and payment data records (PDR) files based on the subscription and payment data and a predefined set of rules. The records preparation unit is further configured to send the set of one or more SDR and PDR files to one or more server, wherein a FTP details and a file location of the one or more SDR and PDR files are shared
30 using at least one of a push mechanism and a pull mechanism. The subscription engine further
comprises a billing unit connected to at least the records preparation unit, the billing unit configured to receive the set of one or more SDR and PDR files for facilitating integration of subscription data in the billing entity.
5

[0016] An aspect of the present disclosure may relate to a user equipment (UE) comprising: a
production unit configured to produce a subscription and payment data in an event of performance of
a payment related to an order by one or more users; a records preparation unit connected to at least the
5 production unit, the records preparation unit configured to: prepare a set of one or more subscription
data records (SDR) and payment data records (PDR) files based on the subscription and payment data
and a predefined set of rules, and send the set of one or more SDR and PDR files to one or more server,
wherein a FTP details and a file location of the one or more SDR and PDR files are shared using at
least one of a push mechanism and a pull mechanism; and a billing unit connected to at least the
10 records preparation unit, the billing unit configured to receive the set of one or more SDR and PDR
files for facilitating integration of subscription data in the billing entity.
[0017] An aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for provisioning one or more subscriber user equipment, the instructions
15 including executable code, the executable code when executed, may cause: a production unit to
produce a subscription and payment data in an event of performance of a payment related to an order by one or more users; a records preparation unit to prepare a set of one or more subscription data records (SDR) and payment data records (PDR) files based on the subscription and payment data and a predefined set of rules, and send the set of one or more SDR and PDR files to one or more servers,
20 wherein a FTP details and a file location of the one or more SDR and PDR files are shared using at
least one of a push mechanism and a pull mechanism; and a billing unit to receive the set of one or more SDR and PDR files for facilitating integration of subscription data in the billing entity.
OBJECTS OF THE INVENTION
25
[0018] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0019] It is an object of the present disclosure to provide a system and a method for integrating
30 subscription data in a billing entity.
6

[0020] It is an object of the present disclosure to provide a system and a method for integration of SDR and PDR in the subscription engine for a successful and smooth buying/subscription of the subscription plan.
5 DESCRIPTION OF THE DRAWINGS
[0021] 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 parts throughout the different drawings. Components in the
10 drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the
principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components
15 or circuitry commonly used to implement such components.
[0022] FIG. 1 illustrates an exemplary block diagram of a computing device upon which the features
of the present disclosure may be implemented in accordance with exemplary implementation of the
20 present disclosure.
[0023] FIG. 2 illustrates an exemplary block diagram of a system for integrating subscription data in a billing entity, in accordance with exemplary implementations of the present disclosure.
25 [0024] FIG. 3 illustrates a method flow diagram for integrating subscription data in a billing entity,
in accordance with exemplary implementations of the present disclosure.
[0025] FIG. 4 illustrates a method flow diagram for preparing a set of one or more subscription data
records (SDR) and payment data records (PDR), in accordance with exemplary implementations of
30 the present disclosure.
7

[0026] FIG.5 illustrates an exemplary method call flow diagram indicating the process for integrating subscription data in a billing entity, in accordance with exemplary embodiments of the present disclosure.
5 [0027] The foregoing shall be more apparent from the following more detailed description of the
disclosure.
DETAILED DESCRIPTION
10 [0028] 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 embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems
15 discussed above or might address only some of the problems discussed above.
[0029] 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
20 implementing an exemplary embodiment. It should be understood that various changes may be made
in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0030] Specific details are given in the following description to provide a thorough understanding of
25 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, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
30 [0031] 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 structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be
8

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.
5 [0032] 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 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
10 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.
15 [0033] As used herein, a “processing unit” or “processor” or “operating processor” includes one or
more processors, wherein processor refers to any logic circuitry for processing instructions. A 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 (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific
20 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 according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
25 [0034] 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 user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a
30 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 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.
9

[0035] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable
medium including any mechanism for storing information in a form readable by a computer or similar
machine. For example, a computer-readable medium includes read-only memory (“ROM”), random
5 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 functions.
[0036] As used herein “interface” or “user interface refers to a shared boundary across which two or
10 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 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.
15 [0037] All modules, units, components used herein, unless explicitly excluded 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
20 circuits (FPGA), any other type of integrated circuits, etc.
[0038] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information, or a combination thereof between units/components within the system and/or connected with the system.
25
[0039] As used herein the term ‘provisioning’ herein refers to an addition of a subscriber information
of one or more subscribers to a subscriber data stored in a Policy Control Function (PCF) storage unit
of a PCF. Further, the term ‘deprovisioning’ refers to a deletion of the subscriber data stored in the
PCF storage unit of the PCF. For ease in reference and understanding, the present disclosure is
30 discussed for provisioning of the subscriber information to the subscriber data stored in the PCF
storage unit of the PCF, however, similar concept may be applied to deprovisioning of the subscriber information from the subscriber data stored in the PCF storage unit of the PCF.
10

[0040] The present solution as disclosed by the present disclosure addresses several problems
encountered in integrating Subscription Data Records (SDR) and a Payment Data Records (PDR)
within a subscription engine. As discussed in the background section, the current known solutions lack
synchronization between purchase and subscription information and failed to offer customizable data
5 formats or grouping options. Additionally, they couldn't select file formats or organize records
efficiently.
[0041] The present solution as disclosed by the present disclosure involves several steps, firstly, user-generated subscription and payment data are shared, and then the user-generated subscription and
10 payment data are consumed by a Batch Management System (MS) to create a SDR and PDR files
locally. These files are then transferred to servers and stored locally by the Batch MS. Further, as disclosed by the present disclosure, the SDR and PDR files can be generated in various formats, including.txt,.csv,.pdf, and.xlsx, catering to user preferences. Further, the subscription engine initiates SDR and PDR file generation when customers interact with it, sending these files to the servers for
15 billing system consumption. Dynamic rules can be configured to trigger file creation based on various
conditions, such as time intervals, file size, or record count, ensuring efficient data management. Additionally, rules can format file names for easy identification. Moreover, this system enables the analysis of revenue through manual or automatic means, leveraging machine learning and AI models trained on historical and real-time data contained in the generated SDR and PDR files. This
20 multifaceted approach revolutionizes subscription management, offering flexibility, efficiency, and
analytical capabilities.
[0042] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
25
[0043] FIG. 1 illustrates an exemplary block diagram of a computing device [1000] 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 [1000] may also implement a
method for integrating subscription data in billing entity. In another implementation, the computing
30 device [1000] itself implements the method integrating subscription data the billing entity using one
or more units configured within the computing device [1000], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
11

[0044] The computing device [1000] may include a bus [1002] or other communication mechanism
for communicating information, and a hardware processor [1004] coupled with the bus [1002] for
processing information. The hardware processor [1004] may be, for example, a general purpose
microprocessor. The computing device [1000] may also include a main memory [1006], such as a
5 random access memory (RAM), or other dynamic storage device, coupled to the bus [1002] for storing
information and instructions to be executed by the processor [1004]. The main memory [1006] also
may be used for storing temporary variables or other intermediate information during execution of the
instructions to be executed by the processor [1004]. Such instructions, when stored in non-transitory
storage media accessible to the processor [1004], render the computing device [1000] into a special-
10 purpose machine that is customized to perform the operations specified in the instructions. The
computing device [1000] further includes a read only memory (ROM) [1008] or other static storage
device coupled to the bus [1002] for storing static information and instructions for the processor
[1004].
15 [0045] A storage device [1010], such as a magnetic disk, optical disk, or solid-state drive is provided
and coupled to the bus [1002] for storing information and instructions. The computing device [1000] may be coupled via the bus [1002] to a display [1012], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [1014], including alphanumeric and other
20 keys, touch screen input means, etc. may be coupled to the bus [1002] for communicating information
and command selections to the processor [1004]. Another type of user input device may be a cursor control [1016], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [1004], and for controlling cursor movement on the display [1012]. This input device typically has two degrees of freedom in two axes, a first axis
25 (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
[0046] The computing device [1000] 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 [1000] causes or programs the computing device [1000] to be
30 a special-purpose machine. According to one implementation, the techniques herein are performed by
the computing device [1000] in response to the processor [1004] executing one or more sequences of one or more instructions contained in the main memory [1006]. Such instructions may be read into the main memory [1006] from another storage medium, such as the storage device [1010]. Execution of the sequences of instructions contained in the main memory [1006] causes the processor [1004] to
12

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.
[0047] The computing device [1000] also may include a communication interface [1018] coupled to
5 the bus [1002]. The communication interface [1018] provides a two-way data communication coupling
to a network link [1020] that is connected to a local network [1022]. For example, the communication
interface [1018] may be an integrated service 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 [1018] may be a local area network (LAN)
10 card to provide a data communication connection to a compatible LAN. Wireless links may also be
implemented. In any such implementation, the communication interface [1018] sends and receives electrical, electromagnetic, or optical signals that carry digital data streams representing various types of information.
15 [0048] The computing device [1000] can send messages and receive data, including program code,
through the network(s), the network link [1020] and the communication interface [1018]. In the Internet example, a server [1030] might transmit a requested code for an application program through the Internet [1028], the ISP [1026], the Host [1024], the local network [1022] and the communication interface [1018]. The received code may be executed by the processor [1004] as it is received, and/or
20 stored in the storage device [1010], or other non-volatile storage for later execution.
[0049] Referring to FIG. 2, an exemplary block diagram of a system [200] for integrating subscription data in a billing entity, is shown, in accordance with the exemplary implementations of the present disclosure. The system [200] comprises a subscription engine [201], wherein the
25 subscription engine [201] further comprises at least one a production unit [202], at least one records
preparation unit [204], at least one billing unit [206], and at least one local storage unit [208]. Also, all of the components/ units of the system [200] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG.. 2 only a few units are shown, however, the
30 system [200] may comprise multiple such units or the system [200] may comprise any such numbers
of said units, as required to implement the features of the present disclosure. Further, in an implementation, the system [200] may be present in a user device to implement the features of the present disclosure. The system [200] may be a part of the user device / or may be independent of but in communication with the user device (may also referred herein as a UE). In another implementation,
13

the system [200] may reside in a server or a network entity. In yet another implementation, the system [200] may reside partly in the server/ network entity and partly in the user device.
[0050] The system [200] is configured for integrating subscription data in the billing entity, with the
5 help of the interconnection between the components/units of the system [200].
[0051] 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
10 recognized that various 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 of the present disclosure.
15
[0052] As disclosed by the present disclosure, the production unit [202] is configured to produce a
subscription and payment data in an event of performance of a payment related to an order by one or
more users. It is to be noted that as used herein the term the payment related to an order by one or
more users may refers to any transaction where the one or more users have made payments in
20 connection with their orders within the subscription service, including the payments for a subscription
renewal order, an service upgrade order, an additional service order, or any other transactions directly linked to the order by the one or more users. The term encompasses all instances where the one or more users have initiated the payments for services and/or products associated with a product/service.
25 [0053] Further, as used herein, the subscription renewal order is a request from a user of a
telecommunication service or process to continue using the telecommunication service beyond a current subscription period associated with the user.
30 [0054] Further, as used herein, the service upgrade order is a request from the user of the
telecommunication service or process to improve or expand the features or capacity of the telecommunication service, such as a request to upgrade from a 4G network service to a 5G network service.
14

[0055] Further, as used herein, the additional service order is a request from the user of the telecommunication service or process to add extra features or options to an existing telecommunication service, such as a request to add extra data usage units to the existing data usage units associated with the user.
5
[0056] Further, the records preparation unit [204] connected to at least the production unit [202], the records preparation unit [204] configured to prepare a set of one or more subscription data records (SDR) and payment data records (PDR) files based on the subscription and payment data and a predefined set of rules. 10
[0057] Further, as disclosed by the present disclosure, a filename associated with each file from the one or more SDR and PDR files is based on one or more pre-defined templates.
[0058] Further, in an implementation of the present solution as disclosed herein, the filename
15 associated with each file from the one or more SDR and PDR files comprise dynamic attributes, the
dynamic attributes comprising a Service Type attribute, a Business Interaction attribute, a Subscription Type attribute, a Circle attribute, a CDR Type attribute, an Instance identity attribute, a Date and Time attribute, and a Sequence Number attribute.
20 [0059] Further, as disclosed by the present disclosure the predefined set of rules comprise a creation
of new SDR and PDR files during the preparation of the one or more SDR and PDR files, in an event of satisfaction of one or more conditions comprising a change of hour condition, a threshold file size breach condition, a threshold records number breach condition, and a change of data condition.
25 [0060] Further, in an implementation of the present solution as disclosed herein, the records
preparation unit [204], for preparing the set of one or more SDR and PDR file, is configured to determine one of an availability and an absence of last file dump details, wherein the last file dump details are determined available in an event the last file dump details are available, and the last file dump details are determined absent in an event the last file dump details are not available.
30
[0061] Further, in order to prepare the set of one or more SDR and PDR file the records preparation unit [204] is further configured to determine one of a new file creation indication and an existing file modification indication, in an event the last file dump details are determined available.
15

[0062] Further, in order to prepare the set of one or more SDR and PDR file the records preparation
unit [204] is further configured to create a new set of one or more SDR and PDR files, in an event of
one of: the last file dump details are determined absent, and the new file creation indication is
5 determined.
[0063] Further, in order to prepare the set of one or more SDR and PDR file the records preparation
unit [204] is further configured to write one of: the subscription and payment data in the new set of
one or more SDR and PDR files in an event of creation of the new set of one or more SDR and PDR
10 files, and the subscription and payment data in an existing set of one or more SDR and PDR files in
an event of determination of existing file modification indication.
[0064] Further, the records preparation unit [204] is configured to send the set of one or more SDR
and PDR files to one or more servers, wherein a FTP details and a file location of the one or more
15 SDR and PDR files are shared using at least one of a push mechanism and a pull mechanism.
[0065] Further, as disclosed herein the FTP details and the file location of the one or more SDR and
PDR files are shared using the push mechanism in an event the FTP details and the file location of the
one or more SDR and PDR files are sent by the records preparation u] a[104] at the subscription engine
20 [201] without receiving from the subscription engine [201] a request to fetch the FTP details and the
file location of the one or more SDR and PDR files.
[0066] Further, as disclosed herein the FTP details and the file location of the one or more SDR and
PDR files are shared using the pull mechanism in an event the FTP details and the file location of the
25 one or more SDR and PDR files are sent by the records preparation unit [204] at the subscription
engine [201] upon receiving from the subscription engine [201] a request to fetch the FTP details and the file location of the one or more SDR and PDR files.
[0067] Further, it is to be noted that the FTP details and file location of the SDR and PDR files are
30 shared utilizing the push mechanism and the pull mechanism which may further involve one or more
techniques that might be apparent to those skilled in the relevant art and/or a novel approach.
Furthermore, nothing in this disclosure should be interpreted to restrict the scope of the invention. The
16

disclosure is intended to encompass all variations and modifications thereof, which would be apparent to a person skilled in the art.
[0068] As disclosed by the present disclosure the set of one or more SDR and PDR files are sent by
5 the records preparation unit [204] to servers after a pre-defined configurable time period.
[0069] Further, the pre-defined configurable time period, as disclosed herein, may be a dynamically configured time period, meaning it adjusts automatically based on certain conditions (such as 5 min, 12 min etc. which may further be adjusted based on certain conditions such as if a predefined SDR
10 file volume is reached), or it may be a manually configured time period by a user/or an administrator
such as every 7 minutes. Further, in an implementation a combination of both the dynamically configured time period and the manually configured time period may be implemented to implement the solution of the present disclosure based on a specific needs and preference of an operation. Furthermore, based on detection of expiry of a time period associated with the dynamically configured
15 time period and the manually configured time period i.e., the pre-defined configurable time period the
set of one or more SDR and PDR files are sent by the records preparation unit [204] to one or more servers i.e., the one of the FTP servers and the NAS server.
[0070] Further, the billing unit [206] connected to at least the records preparation unit [204], the
20 billing unit [206] configured to receive the set of one or more SDR and PDR files for facilitating
integration of subscription data in the billing entity. It is to be noted that as used herein the term
“facilitating integration” refers to a process of making it easier for the subscription data to be combined
and/or merged with the set of one or more SDR and PDR files in a billing system i.e., the billing unit
[206]. In other words, the facilitating integration of subscription data in the billing entity refers to
25 helping the subscription data to smoothly become part of the billing process without any difficulties
and/or hindrance.
[0071] Furthermore, in an implementation of the present disclosure the subscription engine [201] further comprises a local storage unit [208] configured to store the one or more SDR and PDR files. 30
[0072] Further, as depicted in FIG. 2, the subscription engine [201] is connected to the Network Attached Storage (NAS) server. The NAS server provides a Non Access Stratum (NAS) location [203] (i.e., the location of the NAS server) to a Passive Mediation Zone (Passive MZ) [205] via a Secure File Transfer Protocol (SFTP). Further, the passive MZ [205] is associated with a Systems Application
17

and Products business intelligence module (SAP-BI) [207]. The SAP-BI [207] is a centralized suite for reporting data, data visualization and data sharing. Furthermore, the SAP-BI [207] may transform the subscription data into one or more insights for enhancing the user experience.
5 [0073] Further, Passive MZ [205] is a purpose-built software that seamlessly connects with network
and Information technology (IT) systems, applications, devices and other sources. It collects, processes and distributes usage data into the processes of billing and revenue systems of across multiple verticals of a business entity.
10 [0074] In addition to the this the passive MZ [205] is associated with a SAP Convergent Invoicing
(SAP-CI) module [209] which allows to manage and streamline an invoicing and billing processes for managing one or more financial transactions such as invoicing, payment, and collections.
[0075] Further, the passive MZ [205] is connected with a revenue assurance module [211] that utilizes
15 one or more data quality and process improvement methods for improving profits, revenues, and cash
flows without influencing demands.
[0076] Further, the passive MZ [205] is connected to a fraud management module [213] that performs
a set of activities such as real -time monitoring, anomaly detection, investigation workflows and risk
20 assessment for preventing one or more fraudulent attacks. Further, the passive MZ [205] is connected
to one or more third party settlement systems [215] which may refer to multilateral arrangements system for clearing, settlement and recording of one or more payments, one or more securities, one or more derivatives and other financial transactions.
25 [0077] Referring to FIG. 3, an exemplary method [300] flow diagram for integrating subscription
data in a billing entity, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [300] is performed by the system [200]. Further, in an implementation, the system [200] may be present in a server device to implement the features of the present disclosure. Also, as shown in Figure 4, the method [300] starts at step [302].
30
[0078] At step [304], the method [300] further comprises producing, by a production unit [202] at a
subscription engine [201], a subscription and payment data in an event of performance of a payment
related to an order by one or more users. It is to be noted that as used herein the term the payment
related to an order by one or more users may refers to any transaction where the one or more users
35 have made payments in connection with their orders within the subscription service, including the
18

payments for a subscription renewal order, an service upgrade order, an additional service order, or any other transactions directly linked to the order by the one or more users. The term encompasses all instances where the one or more users have initiated the payments for services and/or products associated with a product/service. 5
[0079] Next at step [306], the method [300] further comprises preparing, by a records preparation
unit [204] at the subscription engine [201], a set of one or more subscription data records (SDR) and
payment data records (PDR) files based on the subscription and payment data and a predefined set of
10 rules. The predefined set of rules may be prestored list of instructions associated with the SDR and the
PDR based on which the SDR and the PDR may be prepared. Further, the predefined set of rules may define a format associated with the SDR and the PDR.
[0080] Further, as disclosed by the present disclosure, the predefined set of rules comprise a creation
15 of new SDR and PDR files during the preparing of the one or more SDR and PDR files, in an event
of satisfaction of one or more conditions comprising a change of hour condition, a threshold file size breach condition, a threshold records number breach condition, and a change of data condition.
[0081] Now, referring to FIG. 4, an exemplary method [400] flow diagram for preparing a set of one
20 or more subscription data records (SDR) and payment data records (PDR), in accordance with
exemplary implementations of the present disclosure is shown. In an implementation the method [400] is performed by the system [200]. Further, in an implementation, the system [200] may be present in a server device to implement the features of the present disclosure. Also, as shown in Figure 5, the method [400] starts at step [402].
25
[0082] Further, as disclosed herein the preparing, by the records preparation unit [204], the set of one
or more SDR and PDR files comprises at step [404], the method [400] comprises determining, by the
records preparation unit [204], one of an availability and an absence, of last file dump details, wherein
the last file dump details are determined available in an event the last file dump details are available,
30 and the last file dump details are determined absent in an event the last file dump details are not
available.
[0083] Next, at step [406], the method [400] further comprises determining, by the records
preparation unit [204], one of a new file creation indication and an existing file modification
35 indication, in an event the last file dump details are determined available.
19

[0084] Next, at step [408], the method [400] further comprises creating, by the records preparation unit [204], a new set of one or more SDR and PDR files, in an event of one of: the last file dump details are determined absent, and the new file creation indication is determined.
5
[0085] Next, at step [410], the method [400] further comprises writing, by the records preparation
unit [204], one of: the subscription and payment data in the new set of one or more SDR and PDR
files in an event of creation of the new set of one or more SDR and PDR files, and the subscription
and payment data in an existing set of one or more SDR and PDR files in an event of determination
10 of existing file modification indication.
[0086] Thereafter, the method [400] terminates at step [412]
15 [0087] Referring again to FIG.3, further, as disclosed by the present disclosure, a filename associated
with each file from the one or more SDR and PDR files is based on one or more pre-defined templates.
[0088] Further, in an implementation of the present disclosure, the filename associated with each file
from the one or more SDR and PDR files, comprise dynamic attributes in, the dynamic attributes
20 comprising a Service Type attribute, a Business Interaction attribute, a Subscription Type attribute, a
Circle attribute, a CDR Type attribute, an Instance identity attribute, a Date and Time attribute, and a Sequence Number attribute.
[0089] Next at step [308], the method [300] further comprises sending, by the records preparation
25 unit [204] at the subscription engine [201], the set of one or more SDR and PDR files to one or more
servers. In an implementation of the present disclosure as disclosed herein the one or more servers is of a file transfer protocol (FTP) server and a network-attached storage (NAS) server.
[0090] Further, in an implementation of the present disclosure a FTP details and a file location of the
30 one or more SDR and PDR files are shared using at least one of a push mechanism and a pull
mechanism.
20

[0091] Further, as disclosed herein the FTP details and the file location of the one or more SDR and
PDR files are shared using the push mechanism in an event the FTP details and the file location of the
one or more SDR and PDR files are sent by the records preparation u] a[104] at the subscription engine
[201] without receiving from the subscription engine [201] a request to fetch the FTP details and the
5 file location of the one or more SDR and PDR files.
[0092] Further, as disclosed herein the FTP details and the file location of the one or more SDR and
PDR files are shared using the pull mechanism in an event the FTP details and the file location of the
one or more SDR and PDR files are sent by the records preparation unit [204] at the subscription
10 engine [201] upon receiving from the subscription engine [201] a request to fetch the FTP details and
the file location of the one or more SDR and PDR files.
[0093] Further, it is to be noted that the FTP details and file location of the SDR and PDR files are
shared utilizing the push mechanism and the pull mechanism which may further involve one or more
15 techniques that might be apparent to those skilled in the relevant art and/or a novel approach.
Furthermore, nothing in this disclosure should be interpreted to restrict the scope of the invention. The disclosure is intended to encompass all variations and modifications thereof, which would be apparent to a person skilled in the art.
20 [0094] Further, as disclosed by the present disclosure, the set of one or more SDR and PDR files are
sent by the records preparation unit [204] to one or more servers after a pre-defined configurable time period. Further, in an implementation of the present disclosure as disclosed herein the set of one or more SDR and PDR files are sent by the records preparation unit [204] to one of the FTP servers and the NAS server after the pre-defined configurable time period.
25
[0095] Further, the pre-defined configurable time period, as disclosed herein, may be a dynamically
configured time period, meaning it adjusts automatically based on certain conditions, or it may be a
manually configured time period by a user/or administrator. Further, in an implementation a
combination of both the dynamically configured time period and the manually configured time period
30 may be implemented to implement the solution of the present disclosure based on a specific needs and
preference of an operation. Furthermore, based on detection of expiry of a time period associated with the dynamically configured time period and the manually configured time period i.e., the pre-defined configurable time period the set of one or more SDR and PDR files are sent by the records preparation unit [204] to one or more servers i.e., the one of the FTP servers and the NAS server.
21

[0096] Next at step [310], the method [300] further comprises receiving, by a billing unit [206] at the subscription engine [201], the set of one or more SDR and PDR files for facilitating integration of subscription data in the billing entity.
5
[0097] As used herein the term “facilitating integration” refers to a process of making it easier for the
subscription data to be combined and/or merged with the set of one or more SDR and PDR files in a
billing system i.e., the billing unit [206]. In other words, the facilitating integration of subscription
data in the billing entity refers to helping the subscription data to smoothly become part of the billing
10 process without any difficulties and/or hindrance.
[0098] Furthermore, in an implementation of the present disclosure, storing, by a local storage unit [208] at the subscription engine [201], the one or more SDR and PDR files.
15 [0099] Thereafter, the method [300] terminates at step [312].
[0100] FIG.5 illustrates an exemplary method [500] call flow diagram indicating the process for
integrating subscription data in a billing entity, in accordance with exemplary embodiments of the
present disclosure. In an implementation the method [500] is performed by the system [200]. As shown
20 in Figure 5, the method [500] starts at step [502].
[0101] At step [504], the method [500] as disclosed by the present disclosure comprises instructing
a User Management System (MS)/Producer [500(a)] to produce a Subscription data and sharing to a
Microservice [500(b)]. The User Management System (MS)/Producer [500(a)] may manage one or
25 more users and their one or more accounts. The microservice [500(b)] refers to a architecture where a
collection of independent services communicate through one or more application programming interfaces (APIs).
[0102] Next, at step [506], the method [500] as disclosed by the present disclosure comprises
30 instructing consumption of a Subscription data record (SDR) and a Payment Data record (PDR) from
the Microservice [500(b)] using a Batch MS [500(c)] and generate the SDR and the PDR files locally
on their instance.
22

[0103] Further, the Batch MS [500(c)] is used to consume large amounts of subscription data and
process the bulk data and send it to the Microservice [500(b)]. Further, it also creates the SDR and the
PDR and maintains a subscription lifecycle state. It sends mail notifications to the required users
5 through a notification hub, may also generate an invoice metadata.
[0104] Next, at step [508], the method [500] as disclosed by the present disclosure comprises
instructing to process by the Batch MS [500(c)] to move files from local instance (i.e., last file dump)
to a File Transfer Protocol (FTP) server [500(d)] and/or Network-attached storage (NAS) server.
10 Further, the FTP server [500(d)] is a server that facilitates a file transfer process across the internet.
While the transmission of the file using the FTP server [500(d)], the file is either uploaded or downloaded to the FTP server [500(d)], as the FTP server [500(d)] acts a midpoint between a sender and a recipient of the file.
15 [0105] Next, at step [510], the method [500] as disclosed by the present disclosure comprises
instructing to keep copy of the SDR and PDR files in a processed folder locally by the Batch MS [500(c)].
[0106] Further, the method [500] as disclosed by the present disclosure may comprise instructing the
20 SDR and PDR files to be pushed towards passive mediation for configurable period.
[0107] Further, the method [500] as disclosed by the present disclosure may further comprise generation of the Bills by the billing entity.
25 [0108] The present disclosure further discloses a user equipment (UE) comprising: a production unit
[202] configured to produce a subscription and payment data in an event of performance of a payment related to an order by one or more users; a records preparation unit [204] connected to at least the production unit [202], the records preparation unit [204] configured to: prepare a set of one or more subscription data records (SDR) and payment data records (PDR) files based on the subscription and
30 payment data and a predefined set of rules, and send the set of one or more SDR and PDR files to one
or more server, wherein a FTP details and a file location of the one or more SDR and PDR files are shared using at least one of a push mechanism and a pull mechanism; and a billing unit [206] connected
23

to at least the records preparation unit [204], the billing unit [206] configured to receive the set of one or more SDR and PDR files for facilitating integration of subscription data in the billing entity.
[0109] The present disclosure further discloses a non-transitory computer readable storage medium
5 storing instructions for provisioning one or more subscriber user equipment, the instructions including
executable code, the executable code when executed, may cause: a production unit [202] to produce a
subscription and payment data in an event of performance of a payment related to an order by one or
more users; a records preparation unit [204] to prepare a set of one or more subscription data records
(SDR) and payment data records (PDR) files based on the subscription and payment data and a
10 predefined set of rules, and send the set of one or more SDR and PDR files to one or more servers,
wherein a FTP details and a file location of the one or more SDR and PDR files are shared using at least one of a push mechanism and a pull mechanism; and a billing unit [206] to receive the set of one or more SDR and PDR files for facilitating integration of subscription data in the billing entity.
15 [0110] As is evident from the above, the present disclosure provides a technically advanced solution
for provisioning one or more subscriber user equipment. The present solution offers a technically advanced solution to seamlessly integrate Subscription Data Record (SDR) and Payment Data Record (PDR) within the subscription engine, ensuring a hassle-free buying or subscription process. Further, the technical advantage presented by the novel solution as disclosed herein lies in its ability to
20 seamlessly integrate Subscription Data Record (SDR) and Payment Data Record (PDR) within the
subscription engine, thereby significantly enhancing the user experience and operational efficiency. By streamlining invoice generation for subscribers, enabling Proration Calculation for resource optimization, contributing to revenue assurance, facilitating inter-billing settlement with third-party OTT platforms, and empowering robust business intelligence through comprehensive reports, this
25 advancement revolutionizes subscription management. The present solution addresses key challenges
in subscription services, offering a sophisticated yet user-friendly solution that maximizes convenience and effectiveness for both service providers and consumers alike.
[0111] While considerable emphasis has been placed herein on the disclosed implementations, it
30 will be appreciated that many implementations can be made and that many changes can be made to
the implementations without departing from the 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.
35
24

We Claim:
1. A method for integrating subscription data in a billing entity, the method comprising:
- producing, by a production unit [202] at a subscription engine [201], a subscription and
payment data in an event of performance of a payment related to an order by one or more users;
5 - preparing, by a records preparation unit [204] at the subscription engine [201], a set of one or
more subscription data records (SDR) and payment data records (PDR) files based on the subscription and payment data and a predefined set of rules;
- sending, by the records preparation unit [204] at the subscription engine [201], the set of one
or more SDR and PDR files to one or more servers,
10 wherein a FTP details and a file location of the one or more SDR and PDR files are shared using at
least one of a push mechanism and a pull mechanism; and
- receiving, by a billing unit [206] at the subscription engine [201], the set of one or more SDR
and PDR files for facilitating integration of subscription data in the billing entity.
15
2. The method as claimed in claim 1, wherein the preparing, by the records preparation unit
[204], the set of one or more SDR and PDR files comprises:
- determining, by the records preparation unit [204], one of an availability and an absence, of
last file dump details, wherein the last file dump details are determined available in an event the last
20 file dump details are available, and the last file dump details are determined absent in an event the last
file dump details are not available,
- determining, by the records preparation unit [204], one of a new file creation indication and
an existing file modification indication, in an event the last file dump details are determined available,
- creating, by the records preparation unit [204], a new set of one or more SDR and PDR files,
25 in an event of one of: the last file dump details are determined absent, and the new file creation
indication is determined, and
- writing, by the records preparation unit [204], one of: the subscription and payment data in
the new set of one or more SDR and PDR files in an event of creation of the new set of one or more
SDR and PDR files, and the subscription and payment data in an existing set of one or more SDR and
30 PDR files in an event of determination of existing file modification indication.
3. The method as claimed in claim 1, wherein a filename associated with each file from the one
or more SDR and PDR files is based on one or more pre-defined templates.
35 4. The method as claimed in claim 3, wherein the filename associated with each file from the
one or more SDR and PDR files, comprises dynamic attributes in, the dynamic attributes comprising
a Service Type attribute, a Business Interaction attribute, a Subscription Type attribute, a Circle
25

attribute, a CDR Type attribute, an Instance identity attribute, a Date and Time attribute, and a Sequence Number attribute.
5. The method as claimed in claim 1, wherein the set of one or more SDR and PDR files are sent
5 by the records preparation unit [204] to one or more servers after a pre-defined configurable time
period.
6. The method as claimed in claim 1, the method further comprising:
- storing, by a local storage unit [208] at the subscription engine [201], the one or more SDR
10 and PDR files.
7. The method as claimed in claim 1, wherein the predefined set of rules comprise a creation of
new SDR and PDR files during the preparing of the one or more SDR and PDR files, in an event of
satisfaction of one or more conditions comprising a change of hour condition, a threshold file size
15 breach condition, a threshold records number breach condition, and a change of data condition.
8. A system for integrating subscription data in a billing entity, the system comprising a
subscription engine [201], the subscription engine [201] further comprising:
- a production unit [202] configured to produce a subscription and payment data in an event of
20 performance of a payment related to an order by one or more users;
- a records preparation unit [204] connected to at least the production unit [202], the records
preparation unit [204] configured to:
o prepare a set of one or more subscription data records (SDR) and payment data records (PDR)
files based on the subscription and payment data and a predefined set of rules, and
25 o send the set of one or more SDR and PDR files to one or more server,
wherein a FTP details and a file location of the one or more SDR and PDR files are shared using at least one of a push mechanism and a pull mechanism; and
- a billing unit [206] connected to at least the records preparation unit [204], the billing unit
[206] configured to receive the set of one or more SDR and PDR files for facilitating integration of
30 subscription data in the billing entity.
9. The system as claimed in claim 8, wherein the records preparation unit [204], for preparing
the set of one or more SDR and PDR file, is configured to:
35 - determine one of an availability and an absence of last file dump details, wherein the last file
dump details are determined available in an event the last file dump details are available, and the last file dump details are determined absent in an event the last file dump details are not available,
26

- determine one of a new file creation indication and an existing file modification indication, in an event the last file dump details are determined available,
- create a new set of one or more SDR and PDR files, in an event of one of: the last file dump details are determined absent, and the new file creation indication is determined, and
5 - write one of: the subscription and payment data in the new set of one or more SDR and PDR
files in an event of creation of the new set of one or more SDR and PDR files, and the subscription and payment data in an existing set of one or more SDR and PDR files in an event of determination of existing file modification indication.
10 10. The system as claimed in claim 8, wherein a filename associated with each file from the one
or more SDR and PDR files is based on one or more pre-defined templates.
11. The system as claimed in claim 10, wherein the filename associated with each file from the
one or more SDR and PDR files comprise dynamic attributes, the dynamic attributes comprising a
15 Service Type attribute, a Business Interaction attribute, a Subscription Type attribute, a Circle attribute,
a CDR Type attribute, an Instance identity attribute, a Date and Time attribute, and a Sequence Number attribute.
12. The system as claimed in claim 8, wherein the set of one or more SDR and PDR files are sent
20 by the records preparation unit [204] to one or more servers after a pre-defined configurable time
period.
13. The system as claimed in claim 8, wherein the subscription engine [201] further comprises a
local storage unit [208] configured to:
25 - store the one or more SDR and PDR files.
14. The system as claimed in claim 8, wherein the predefined set of rules comprise a creation of
new SDR and PDR files during the preparation of the one or more SDR and PDR files, in an event of
satisfaction of one or more conditions comprising a change of hour condition, a threshold file size
30 breach condition, a threshold records number breach condition, and a change of data condition.
15. A user equipment (UE) comprising:
- a production unit [202] configured to produce a subscription and payment data in an event of
35 performance of a payment related to an order by one or more users;
- a records preparation unit [204] connected to at least the production unit [202], the records
preparation unit [204] configured to:
27

o prepare a set of one or more subscription data records (SDR) and payment data records (PDR) files based on the subscription and payment data and a predefined set of rules, and o send the set of one or more SDR and PDR files to one or more server,
wherein a FTP details and a file location of the one or more SDR and PDR files are shared using at
5 least one of a push mechanism and a pull mechanism; and
- a billing unit [206] connected to at least the records preparation unit [204], the billing unit
[206] configured to receive the set of one or more SDR and PDR files for facilitating integration of subscription data in the billing entity.
10 Dated this 14th day of July 2023
(GARIMA SAHNEY)
IN/PA-1826
AGENT FOR THE APPLICANT(S)
OF SAIKRISHNA & ASSOCIATES
15