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 AUTOMATICALLY
CUSTOMIZING A DEDUPLICATION RULES
IMPLEMENTATION”
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 AUTOMATICALLY CUSTOMIZING A DEDUPLICATION RULES IMPLEMENTATION
FIELD OF INVENTION
5
[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to automatically customizing a deduplication rules implementation. 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
15 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 is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
20 [0003] Recently there has been a great expansion of on-demand service
environments in all areas of life. Telecommunication operators have to adhere to government regulatory in various domains, with one such domain being Data Deduplication. With increased coverage of a network service provider’s services across an area such as a nation and ease in availing products and services, a large
25 number of individuals knowingly and unknowingly tend to purchase huge number
of connections on their identity. To ensure moderation and that the individual is unable to purchase more than certain number of connections, various Customer relationship management (CRM) solutions have been developed and deployed to manage the resources and exchange of the information between such resources.
30 Customer relationship management (CRM) is the combination of technologies,
practices and strategies that companies use to manage and analyse customer/client
2

and/or lead interactions and data throughout the customer life cycle. Various
operations such as on boarding new customer, modifying customer details such as
personal details, account details and services are accomplished by accepting order
from front-end channels. The order is tracked from submission to completion
5 through unique order identifier called Order ID and details of the same are also
provided on custom User Interface that CRM provides. The objective is to improve customer service relationships, reduce time-to-market for new business requirement, modifications and adaptations and assisting in customer retention and to drive sales growth. CRM systems compile customer data across different
10 channels, or points of contact, between the customer and the company, which could
include the company's website, telephone, live chat, mail, marketing materials, social networks and like others. CRM systems can give customer-facing staff members detailed information on customers' personal information, order history, preferences and concerns.
15
[0004] An order is an entity that is created in a database and helps in tracking the progress of an operation, such as new customer onboarding, modifications in customer profile etc, through milestones. Orders can be categorized differently depending on their characteristics. At present, many types of orders exist at granular
20 level based on various order characteristics. Accordingly, it may be said that order
refers to an activity or task performed on the CRM portal. Order includes, such as but not limited to, ‘New Customer Onboarding’ order, ‘Modification in Customer Details/Profile’ order, ‘Modification of Customer Services’ order, ‘Porting of Customer Services’ order, and/or the like. Each order is defined by a number of
25 milestones, which are required to be undertaken/achieve in a specified format
termed ‘Workflow’.
[0005] A milestone is an entity or simply, a subset of order that is created in a
database and helps in tracking the progress of an order. A milestone can be referred
30 to as a step in the workflow of performing any order. The milestones may embody,
such as but not limited to, Know Your Customer (KYC) milestone, ‘Customer
3

Approval’ milestone, ‘Customer Verification’ milestone, ‘Tele-verification’ milestone, and/or ‘Installation’ milestone.
[0006] Furthermore, one or more of the aforementioned milestones are followed in
5 a specific manner (termed ‘workflow’) to complete execution of an order. In an
exemplary embodiment, for execution of ‘New Customer Onboarding’ order, the workflow is defined to perform each of the ‘KYC’ milestone, ‘Customer Approval’ milestone, ‘Customer Verification’ milestone, ‘Tele-verification’ milestone, and the ‘Installation’ milestone, in the specified sequence. Notably, the execution of
10 ‘New Customer Onboarding’ order may include other milestones as well, and the
concepts of the present disclosure should not be limited to only the aforementioned milestones. In light of the aforementioned, it is understood that ‘KYC’ milestone is an important milestone, particularly, for execution of ‘New Customer Onboarding’ order.
15
[0007] It may further be noted that the CRM system is equipped to define a number of rules, for deduplication of customer details, during ‘KYC’ milestone of ‘New Customer Onboarding’ order. ‘Rules’ may be referred to as a process of allowing/restricting the execution of order. Particularly, the telecommunication
20 regulatory authorities define a maximum number of connections that can be given
to a customer per circle. Accordingly, the CRM system defines the number of rules, for restricting the total number of connections that can be given to a customer, up to the maximum allowed of connections.
25 [0008] In order to perform such rules of deduplication of customer details during
execution of ‘New Customer Onboarding’ order, the CRM system is enabled to: receive a plurality of customer attributes of a new customer from order details coming from channel; prepare an entry of one or more customer attributes selected from the plurality of customer attributes; compare the entry of the one or more
30 customer attributes with a plurality of entries of the one or more corresponding
customer attributes, stored in a database of the CRM system; retrieve a number of
4

entries of the one or more corresponding customer attributes stored in the database
of the CRM system, wherein each of the one or more corresponding customer
attributes of the number of customer attributes matches with the one or more
customer attributes of the received entry; count the number of entries of the one or
5 more corresponding customer attributes retrieved thereon; compare the count of the
number of entries of the one or more corresponding customer attributes retrieved thereon with a threshold value; allow the ‘New Customer Onboarding’ order to proceed further in case the count of the number of retrieved entries is below the threshold value; and reject the ‘New Customer Onboarding’ order to proceed
10 further in case the count of the number of retrieved entries is above the threshold
value. Rejection of the ‘New Customer Onboarding’ order may include either of: terminating the ‘New Customer Onboarding’ order; or seeking permission from an operator to resume the ‘New Customer Onboarding’ order. Under such rules, the plurality of customer attributes may embody, such as but not limited to,
15 customer_date_of_birth, customer_name, and customer_father_name,
Proof_of_Identification (POI) Identification Type, POI_ID_Value,
Proof_of_Adress (POA) Identification Type, POA_ID_Value, and the like. Notably, in the aforementioned step of: comparing the entry of the one or more customer attributes with the plurality of entries of the one or more corresponding
20 customer attributes, the CRM system is enabled to perform either of ‘Exact match’
or a ‘Fuzzy match’, wherein Exact match refers to word to word match of the customer attribute with the corresponding customer attribute, while fuzzy match refers to similar matching of the customer attribute with the corresponding customer attribute.
25
[0009] Various types of rules can be implemented in the CRM system, based on user requirement. In an example, a total of around thirty rules are defined that can be implemented by the CRM system, for deduplication of customer details during execution of ‘New Customer Onboarding’ order. For example, under Rule 1 of
30 deduplication of customer details, under the step of preparing the entry, the CRM
prepares the aforementioned entry of the one or more customer attributes including
5

customer_date_of_birth, customer_name, and customer_father_name.
Additionally, in the same Rule 1 of deduplication of customer details, under the
step of comparing the entry of the one or more customer attributes with the plurality
of entries of the one or more corresponding customer attributes, the CRM system
5 compares the one or more attributes including customer_date_of_birth,
customer_name, and customer_father_name, with the entry of the one or more
attributes including corresponding customer_date_of_birth, corresponding
customer_name, and corresponding customer_father_name. For comparison of
customer_date_of_birth, an exact match may be defined. For comparison of each
10 of customer_name, and customer_father_name, a similar match may be defined.
[0010] Furthermore, under Rule 2 of deduplication of customer details, under the step of preparing the entry, the CRM prepares the aforementioned entry of the one or more customer attributes including POI_Identification_Type, POI_value,
15 POA_Identification_Type, POA_ID_value, PAN, and Aadhaar. Additionally, in
the same Rule 1 of deduplication of customer details, under the step of comparing
the entry of the one or more customer attributes with the plurality of entries of the
one or more corresponding customer attributes, the CRM system compares the one
or more attributes including POI_Identification_Type, POI_value,
20 POA_Identification_Type, POA_ID_value, PAN, and Aadhaar, with the entry of
the one or more attributes including corresponding POI_Identification_Type,
corresponding POI_value, corresponding POA_Identification_Type,
corresponding POA_ID_value, corresponding PAN, and corresponding Aadhaar. For comparison of each of the POI_Identification_Type, POI_value,
25 POA_Identification_Type, POA_ID_value, PAN, and Aadhaar, an exact match
may be defined.
[0011] Conventionally, the CRM system is programmed to enable/disable one or
more of such rules defined therein. There may be situations, wherein the CRM
30 system may require to be enabled/disabled one or more of the aforementioned rules
defined within the CRM system. Additionally, there may also be situations, wherein
6

one or more of the aforementioned rules may require to be redefined by changing
the match type of the customer attributes to be compared in the rule, between either
of ‘Exact match’ or a ‘Fuzzy match’. Moreover, there may be situations, when one
or more of the aforementioned rules may require to be redefined by changing the
5 rejection action type of the one or more rule. Such activity of
enabling/disabling/redefining any of the aforementioned rules require a coding effort, by a coding expert personnel. This may be a time-consuming and expert-resource consuming process and is not an efficient manner of managing the CRM system.
10
[0012] Thus, there exists an imperative need in the art to provide a method for customized implementation of rules for deduplication of customer details during execution of ‘New Customer Onboarding’ order, which the present disclosure aims to address.
15
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.
20 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 may relate to a method for automatically customizing a deduplication rules implementation. The method comprises
25 receiving, by a user interface, an input order comprising a set of input order
parameters. The method further comprises retrieving, by a transceiver unit from a database, a set of deduplication rules configuration based on the input order. The method thereafter comprises receiving, by a processing unit, a selection of a rejection action type, based on a user input, wherein the rejection action type is one
30 of an auto-rejection type and an agent-consent type. The method further comprises
identifying, by an identification unit, an enabled rule status associated with one or
7

more deduplication rules from the set of deduplication rules. Thereafter, the method
comprising identifying, by the identification unit, a plurality of target deduplication
rules from the one or more deduplication rules based on at least the enabled rule
status associated each of the plurality of target deduplication rules and the set of
5 input order parameters. The method further comprises validating, by a validation
unit, the input order based on the plurality of target deduplication rules. The method then comprises determining, by a determination unit, one of a positive validation status and a negative validation status associated with the input order. The method further comprises transmitting, by the transceiver unit, an input order accept status
10 based on the positive validation status. Thereafter, the method comprises
automatically customizing, by the processing unit, the deduplication rules implementation associated with the input order based on at least the input order accept status associated with the input order, and the positive validation status associated with the input order.
15
[0015] In an exemplary aspect of the present disclosure, wherein the set of deduplication rules comprises at least an addition rule, a modification rule, and a deletion rule.
20 [0016] In an exemplary aspect of the present disclosure, wherein identifying, by the
identification unit, the enabled rule status associated with the one or more deduplication rules is further based on at least one of the input order, at least one input order parameter from the set of input order parameters, and a predefined rule status associated with the one or more deduplication rules.
25
[0017] In an exemplary aspect of the present disclosure, wherein identifying, by the identification unit, the plurality of target deduplication rules from the one or more deduplication rules is further based on at least a predefined priority associated with each deduplication rule from the one or more deduplication rules, and at least one
30 input order parameter from the set of input order parameters.
8

[0018] In an exemplary aspect of the present disclosure, wherein validating, by the validation unit, the input order based on the plurality of target deduplication rules is further based on a predefined validating configuration associated with each target deduplication rule from the plurality of target deduplication rules. 5
[0019] In an exemplary aspect of the present disclosure, wherein the positive validation status associated with the input order is determined by the processing unit in an event a successful validation associated the set of input order parameters based on the predefined validating configuration is detected by the processing unit.
10
[0020] Another aspect of the present disclosure may relate to a system for automatically customizing a deduplication rules implementation. The system comprises a user interface configured to receive, an input order comprising a set of input order parameters. The system also comprises a transceiver unit connected to
15 at least the user interface, the transceiver unit configured to retrieve, from a
database, a set of deduplication rules based on the input order. The system further comprises a processing unit connected to at least the transceiver unit, the processing unit configured to receive a selection of a rejection action type, based on a user input, wherein the rejection action type is one of an auto-rejection type and an
20 agent-consent type. The system also comprises an identification unit connected to
at least the processing unit, the identification unit configured to: identify an enabled rule status associated with one or more deduplication rules from the set of deduplication rules, and identify a plurality of target deduplication rules from the one or more deduplication rules based on at least the enabled rule status associated
25 each of the plurality of target deduplication rules and the set of input order
parameters. The system comprises a validation unit connected to at least the identification unit, the validation unit configured to validate, the input order based on the plurality of target deduplication rules. The system further comprises a determination unit connected to at least the validation unit, the determination unit
30 configured to determine, one of a positive validation status and a negative validation
status associated with the input order. The transceiver unit is further configured to
9

transmit an input order accept status based on the positive validation status. The
processing unit is further configured to automatically customizing, the
deduplication rules implementation associated with the input order based on at least
the input order accept status associated with the input order, and the positive
5 validation status associated with the input order.
[0021] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for automatically customizing a deduplication rules implementation, the instructions include
10 executable code which, when executed by one or more units of a system, causes: a
user interface of the system to receive, an input order comprising a set of input order parameters; a transceiver unit of the system to retrieve, from a database, a set of deduplication rules based on the input order; a processing unit of the system to receive a selection of a rejection action type, based on a user input, wherein the
15 rejection action type is one of an auto-rejection type and an agent-consent type; an
identification unit of the system to: identify an enabled rule status associated with one or more deduplication rules from the set of deduplication rules, and identify a plurality of target deduplication rules from the one or more deduplication rules based on at least the enabled rule status associated each of the plurality of target
20 deduplication rules and the set of input order parameters; a validation unit of the
system to validate, the input order based on the plurality of target deduplication rules; a determination unit of the system to determine, one of a positive validation status and a negative validation status associated with the input order; the transceiver unit of the system to transmit an input order accept status based on the
25 positive validation status; the processing unit of the system to automatically
customize, the deduplication rules implementation associated with the input order based on at least the input order accept status associated with the input order, and the positive validation status associated with the input order.
30 OBJECTS OF THE DISCLOSURE
10

[0022] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0023] It is an object of the present disclosure to provide a system and method for
5 automatically customizing a deduplication rules implementation.
[0024] It is another object of the present disclosure to provide a system (for e.g., a
Customer Relationship Management (CRM) system), and a method for customized
implementation of rules for deduplication of customer details during execution of
10 ‘New Customer Onboarding’ order in the CRM system.
[0025] It is another object of the present disclosure to provide a system and method
for automatically customizing a deduplication rules implementation that improves
customer service relationships, reduces time-to-market for new business
15 requirement, provides modifications and adaptations, assists in customer retention,
and drives sales growth.
[0026] It is yet another object of the present disclosure to provide a system and
method for automatically customizing a deduplication rules implementation that
20 helps in tracking the progress of an order such as new customer onboarding,
modifications in customer profile etc., through milestones.
DESCRIPTION OF THE DRAWINGS
25 [0027] 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 drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present
30 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
11

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 or circuitry commonly used to implement such components. 5
[0028] 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 present disclosure.
10 [0029] FIG. 2 illustrates an exemplary block diagram of a system for automatically
customizing a deduplication rules implementation, in accordance with exemplary implementations of the present disclosure.
[0030] FIG. 3 illustrates a method flow diagram for automatically customizing a
15 deduplication rules implementation, in accordance with exemplary
implementations of the present disclosure.
[0031] FIG. 4 illustrates a system architecture for automatically customizing a
deduplication rules implementation, in accordance with exemplary
20 implementations of the present disclosure.
[0032] FIG. 5 illustrates an exemplary network architecture for automatically customizing a deduplication rules implementation, in accordance with exemplary implementations of the present disclosure. 25
[0033] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
30
12

[0034] 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
5 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 discussed above or might address only some of the problems discussed above.
10 [0035] 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
15 arrangement of elements without departing from the spirit and scope of the
disclosure as set forth.
[0036] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of
20 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.
25 [0037] 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 performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process
30 is terminated when its operations are completed but could have additional steps not
included in a figure.
13

[0038] 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
5 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 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
10 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.
[0039] As used herein, a “processing unit” or “processor” or “operating processor”
15 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
[0040] 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
30 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
14

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 unit(s) which
5 are required to implement the features of the present disclosure.
[0041] 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
10 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 functions.
15
[0042] 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 communication or interaction of one or more modules or one or more units with
20 each other, which also includes the methods, functions, or procedures that may be
called.
[0043] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a
25 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 circuits (FPGA), any other type of integrated circuits, etc.
30
15

[0044] 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. 5
[0045] As discussed in the background section, the current known solutions have
several shortcomings. The present disclosure aims to overcome the above-
mentioned and other existing problems in this field of technology by providing
method and system of automatically customizing a deduplication rules
10 implementation.
[0046] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
15 [0047] FIG. 1 illustrates an exemplary block diagram of a computing device [100]
(also referred to herein as a computer system [100]) 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 [100] may also implement a method for automatically customizing a
20 deduplication rules implementation utilising the system. In another implementation,
the computing device [100] itself implements the method for automatically customizing a deduplication rules implementation using one or more units configured within the computing device [100], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
25
[0048] The computing device [100] may include a bus [102] or other communication mechanism for communicating information, and a hardware processor [104] coupled with the bus [102] for processing information. The hardware processor [104] may be, for example, a general-purpose microprocessor.
30 The computing device [100] may also include a main memory [106], such as a
random-access memory (RAM), or other dynamic storage device, coupled to the
16

bus [102] for storing information and instructions to be executed by the processor
[104]. The main memory [106] also may be used for storing temporary variables or
other intermediate information during execution of the instructions to be executed
by the processor [104]. Such instructions, when stored in non-transitory storage
5 media accessible to the processor [104], render the computing device [100] into a
special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [100] further includes a read only memory (ROM) [108] or other static storage device coupled to the bus [102] for storing static information and instructions for the processor [104].
10
[0049] A storage device [110], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [102] for storing information and instructions. The computing device [100] may be coupled via the bus [102] to a display [112], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
15 Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
displaying information to a computer user. An input device [114], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [102] for communicating information and command selections to the processor [104]. Another type of user input device may be a cursor controller [116], such as
20 a mouse, a trackball, or cursor direction keys, for communicating direction
information and command selections to the processor [104], and for controlling cursor movement on the display [112]. 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.
25
[0050] The computing device [100] 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 [100] causes or programs the computing device [100] to be a special-purpose machine.
30 According to one implementation, the techniques herein are performed by the
computing device [100] in response to the processor [104] executing one or more
17

sequences of one or more instructions contained in the main memory [106]. Such
instructions may be read into the main memory [106] from another storage medium,
such as the storage device [110]. Execution of the sequences of instructions
contained in the main memory [106] causes the processor [104] to perform the
5 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.
[0051] The computing device [100] also may include a communication interface
10 [118] coupled to the bus [102]. The communication interface [118] provides a two-
way data communication coupling to a network link [120] that is connected to a
local network [122]. For example, the communication interface [118] 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
15 telephone line. As another example, the communication interface [118] may be a
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 [118] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing
20 various types of information.
[0052] The computing device [100] can send messages and receive data, including program code, through the network(s), the network link [120] and the communication interface [118]. In the Internet example, a server [130] might
25 transmit a requested code for an application program through the Internet [128], the
ISP [126], the local network [122], the host [124] and the communication interface [118]. The received code may be executed by the processor [104] as it is received, and/or stored in the storage device [110], or other non-volatile storage for later execution.
30
18

[0053] Referring to FIG. 2, an exemplary block diagram of a system [200] for
automatically customizing a deduplication rules implementation is shown, in
accordance with the exemplary implementations of the present disclosure. The
system [200] comprises at least one user interface [202], at least one transceiver
5 unit [204], at least one processing unit [208], at least one identification unit [210],
at least one validation unit [212] and at least one determination unit [214]. 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
10 FIG. 2 only a few units are shown, however, the 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 reside in a server or a network entity and is in connection with Customer relationship management (CRM) module/platforms.
15
[0054] The system [200] is configured for automatically customizing a deduplication rules implementation, with the help of the interconnection between the components/units of the system [300].
20 [0055] More specifically, for automatically customizing the deduplication rules
implementation, the user interface [202] is configured to receive, an input order comprising a set of input order parameters. The present disclosure encompasses that the user interface serves as a means for interaction between the system [200] and users, facilitating the reception of input orders. These input orders consist of a
25 collection of parameters relevant to the task at hand. The deduplication rules refer
to predefined parameters used to identify and manage duplicate data entries within a dataset. The set of deduplication rules comprises at least an addition rule, a modification rule, and a deletion rule. Further, the deduplication rules are a set of mandatory checks mandated to be applied during the onboarding of new customers
30 for telecom products. These rules aim to ensure that a customer does not exceed the
specified number of connections, which varies by telecom circle (e.g., a maximum
19

of 6 connections for the Mumbai circle, and 9 for others). The set of input order
determine the sequence or priority of input data. This may be involving parameters
such as timestamps, data relevance scores, or user-defined preferences. Further, the
deduplication rules are already implemented by Customer relationship management
5 (CRM) module/platform connected to the system [200] and the system [200]
automatically customizes the deduplication rules implementation.
[0056] For example, an exemplary screenshot depicting the process has been shown in FIG. 5 under an exemplary rule implemented by a CRM module say Rule ABC
10 of deduplication of customer details, under the step of preparing an entry, the CRM
prepares the entry of the one or more customer attributes including
customer_Date_of_birth, customer_Name, customer_Father’s_name,
customer_Postal_code, customer_House_number and customer_Address_part_1. Additionally, in an exemplary rule say Rule DEF of deduplication of customer
15 details, under the step of comparing the entry of the one or more customer attributes
with the plurality of entries of the one or more corresponding customer attributes,
the CRM system compares the one or more attributes including
customer_Date_of_birth, customer_Name, customer_Father’s_name,
customer_Postal_code, customer_House_number and customer_Address_part_1,
20 with the entry of the one or more attributes including corresponding date of birth
corresponding customer_date_of_birth, corresponding customer_Name,
corresponding customer_Father’s_name, corresponding customer_Postal_code,
corresponding customer_House_number and corresponding
Customer_Address_part_1. For comparison of customer_date_of_birth, an exact
25 match may be defined by the system [200] to automatically customize the
deduplication rules implementation. For comparison of each of customer_name, customer_father_name customer_Postal_code, customer_House_number and customer_Address_part_1, a similar match may be defined by the system [200] to automatically customize the deduplication rules implementation.
30
20

[0057] The deduplication rules are a set of mandatory checks mandated to be
applied during the onboarding of new customers for telecom products. These rules
aim to ensure that a customer does not exceed the specified number of connections,
which varies by telecom circle (e.g., a maximum of 6 connections for the Mumbai
5 circle, and 9 for others).
[0058] In an example, customers may attempt to bypass the connection limits by:
Providing a different ID proof than previously used. Registering under a slightly
altered name (e.g., changes in surname or the addition of a middle name).Using a
10 different address and acquiring additional connections using the names of different
family members.
[0059] The deduplication rules may be dynamically configured. The configuration
options include:
15
[0060] Rule Application: Whether a rule is to be enforced or suppressed.
[0061] Rule Validation Outcome: If a rule validation fails, whether to automatically
reject the order or leave the decision to an administrator.
20
[0062] Maximum Number of Connections: The permissible number of connections
per rule. These requirements to be adaptable and configurable to address varying
regulatory and operational needs.
25 [0063] Further, the transceiver unit [204] is connected to at least the user interface
[202], and the transceiver unit [204] is configured to retrieve, from a database, a set of deduplication rules based on the input order. The present disclosure encompasses the user interface [202] receives an input order from a user. This input order comprises various parameters relevant to the process. Upon receiving the input
30 order, the transceiver unit [204] initiates a retrieval process to fetch relevant
deduplication rules from the database [206]. The transceiver unit [204] communicates with the database [206] to recovery a set of deduplication rules.
21

These rules are predefined and stored in the database, and they correspond to the
parameters of the input order. The recovery deduplication rules are then configured
for further processing within the system [200]. The set of deduplication rules refers
to a collection of predefined checks that are applied to identify and manage
5 duplicate data entries
[0064] For example, in an e-commerce scenario, if a user submits an order
containing product details and customer information through the user interface
[202], the transceiver unit [204] interacts with the database to fetch deduplication
10 rules pertinent to the order. These rules may include criteria for identifying and
managing duplicate orders or customer entries. By retrieving the deduplication rules based on the input order, the system [200] ensures that the data processing aligns with the established database.
15 [0065] Further, the processing unit [208] is connected to at least the transceiver unit
[204], and the processing unit [208] is configured to receive a selection of a rejection action type, based on a user input, wherein the rejection action type is one of an auto-rejection type and an agent-consent type. The present disclosure encompasses that the processing unit [208] is configured to accept a user's selection
20 of a rejection action type, which is based on user input. The rejection action type
can be either an auto-rejection type or an agent-consent type. The auto-rejection types describe automated processes that reject duplicate data entries based on predefined rules. On the other hand, agent-consent types may be involved where human approval is required before certain actions are taken.
25
[0066] For example, when a customer of a network service provider submits an order for a service package, the system [200] detects a likely duplicate order with matching details, including the service plan, billing address, and payment method. If configured for auto-rejection, the system [200] would automatically cancel the
30 duplicate order to avoid redundant transactions and preventing billing errors.
Alternatively, if set to agent-consent mode, the system [200] would alert a
22

designated agent to review the duplicate order. The agent assesses factors like customer history and specific circumstances before approving or rejecting the order. Once the agent provides consent, the system [200] proceeds accordingly, either approving or rejecting the order based on their decision. 5
[0067] Further, the identification unit [210] is connected to at least the processing unit [208], and the identification unit [210] is configured to: identify an enabled rule status associated with one or more deduplication rules from the set of deduplication rules; and identify a plurality of target deduplication rules from the
10 one or more deduplication rules based on at least the enabled rule status associated
each of the plurality of target deduplication rules and the set of input order parameters. The present disclosure encompasses that the identification unit [210] is programmed to determine the enabled rule status linked to one or more deduplication rules within the set of deduplication rules. The input order parameter
15 is received from the user such as user identification information etc. associated with
the input order. More specifically, the enabled rule status associated with the one or more deduplication rules is identified by the identification unit [210] based on at least one of the input orders, at least one input order parameter from the set of input order parameters, and a predefined rule status associated with the one or more
20 deduplication rules. The identification unit [210] checks the predefined rule status
of each rule in the set of deduplication rules. Based on the analysis, the identification unit [210] identifies which rules are enabled (active) and should be applied. The plurality of target deduplication rules from the one or more deduplication rules is identified by the identification unit [210] based on at least a
25 predefined priority associated with each deduplication rule from the one or more
deduplication rules, and at least input order parameter from the set of input order parameters. The predefined rule status refers to the preconfigured state of each deduplication rule, indicating whether it is active or inactive. This status is stored in the system and is used by the identification unit [210] to determine which rules
30 to apply during the deduplication process. The preconfigured state denotes the
initial setup or arrangement of deduplication rules within the system. The target
23

deduplication rules are specific rules selected from the set of deduplication rules
based on certain criteria. These criteria include the enabled rule status, the priority
assigned to each rule, and the specific parameters of the input order. The enabled
rule status indicating whether a rule is active or not. The input order parameters
5 received from the input order that influence which rules are selected.
[0068] For example, when a customer submits an order for a new service, the
identification unit [210] assesses the input order parameters, such as service type
and customer details, along with predefined rule statuses. Based on predefined
10 priorities associated with each deduplication rule and input order parameters, the
identification unit [210] identifies multiple target deduplication rules. The
predefined priorities refer to the ordered importance assigned to each deduplication
rule. These priorities determine the sequence in which the rules are applied. The
system sets these priorities based on factors such as regulatory requirements,
15 operational policies, and business rules. These rules help streamline processes by
signalling potential duplicate orders for automatic rejection or manual review,
depending on the configured settings. The input order parameters are the specific
details and attributes associated with an input order. These parameters include
customer information, service details, timestamps, data relevance scores, and user-
20 defined preferences.
[0069] Further, the validation unit [212] is connected to at least the identification unit [210], and the validation unit [212] is configured to validate, the input order based on the plurality of target deduplication rules. The present disclosure
25 encompasses the validation unit [212] is configured to validate the input order by
utilizing the plurality of target deduplication rules identified by the identification unit [210]. The input order is a request submitted by a user to the system for processing. This validation process ensures that the input order conforms to the established deduplication rules. More specifically, the input order based on the
30 plurality of target deduplication rules is validated by the validation unit [212] based
on a predefined validating configuration associated with each target deduplication
24

rule from the plurality of target deduplication rules. The predefined validating
configuration indicates a predetermined setup or arrangement for validating data
within the system. Each deduplication rule has an associated validating
configuration that specifies:
5
[0070] Validation Criteria: Conditions that must be met for data to be considered
valid.
[0071] Validation Process: Steps involved in checking the data against the
10 validation criteria.
[0072] For example, if a customer places an order for a specific service package,
the validation unit [212] checks the order against the validating configurations
associated with the identified target deduplication rules. This validation ensures that
15 the order aligns with predefined criteria, such as service eligibility or billing
requirements, specified by each rule.
[0073] Further, the determination unit [214] connected to at least the validation unit [212], and the determination unit [214] is configured to determine, one of a positive
20 validation status and a negative validation status associated with the input order.
The present disclosure encompasses the determination unit [214] is programmed to assess and conclude either a positive validation status or a negative validation status associated with the input order. This determination is based on the outcome of the validation process conducted by the validation unit [212], wherein the input order
25 is analysed against the established deduplication rules. The positive validation
status associated with the input order is determined by the processing unit [208] in an event a successful validation associated the set of input order parameters based on the predefined validating configuration is detected by the processing unit [208]. In an example, the validation unit [212] is responsible for validating the input order
30 against the target deduplication rules. A positive validation status is achieved when
the input order meets all the predefined validation criteria, indicating that the order is valid and free from duplicates. Conversely, a negative validation status occurs
25

when the input order fails to meet these criteria, suggesting potential duplicates or other issues.
[0074] In order words, the user interface [202] receives an input order, which
5 includes various parameters related to the customer and the service they are
requesting. The processing unit [208] applies the saved deduplication rules to the
input order. The validation unit [212] validates the input order against the identified
target deduplication rules. The determination unit [214] assesses the validation
results and assigns a validation status (positive or negative) to the input order. Based
10 on the validation status, the processing unit [208] customizes the implementation
of the deduplication rules, making the handling of duplicate data to align with the validated input order.
[0075] Further, the transceiver unit [204] is configured to transmit an input order
15 accept status based on the positive validation status. The present disclosure
encompasses that the transceiver unit [204] is further programmed to transmit an input order accept status based on a positive validation status. This indicates that the input order has successfully met the validation criteria and the processing unit [208] is further configured to automatically customizing, the deduplication rules
20 implementation associated with the input order based on at least the input order
accept status associated with the input order, and the positive validation status associated with the input order. More specifically, the processing unit [208] is configured to automatically customize the implementation of deduplication rules associated with the input order. This customization is based on factors including the
25 input order accept status and the positive validation status. By analysing these
statuses, the processing unit [208] modifies the deduplication rules implementation accordingly and tailors management of duplicate data in placement with the validated input order. The tailors management of duplicate data provides a method or system for customized management of duplicate data. It includes processes that
30 adaptively handle duplicate data entries based on conditions, optimizing storage
efficiency and data performance.
26

[0076] For example, if a customer's order is accepted and successfully validated,
the processing unit [208] tailors the application of deduplication rules accordingly.
This customization ensures that validated orders proceed smoothly through the
provisioning process without unnecessary duplication checks, expediting order
5 fulfilment. Conversely, if an order faces acceptance or validation issues, the
processing unit [208] may adjust the deduplication rules to prioritize error resolution or manual review, safeguarding order accuracy and customer satisfaction in the telecommunications service provisioning pipeline.
10 [0077] Referring to FIG. 3, an exemplary method flow diagram [300] for
automatically customizing a deduplication rules implementation, 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
15 the features of the present disclosure. Also, as shown in FIG. 3, the method [300]
starts at step [302].
[0078] At step [304], the method comprises receiving, by a user interface [202], an input order comprising a set of input order parameters. The present disclosure
20 encompasses that the user interface serves as a means for interaction between the
system [200] and users, facilitating the reception of input orders. These input orders consist of a collection of parameters relevant to the task at hand. The deduplication rules refer to predefined parameters used to identify and manage duplicate data entries within a dataset. The set of deduplication rules comprises at least an addition
25 rule, a modification rule, and a deletion rule. Further, the deduplication rules are a
set of mandatory checks mandated to be applied during the onboarding of new customers for telecom products. These rules aim to ensure that a customer does not exceed the specified number of connections, which varies by telecom circle (e.g., a maximum of 6 connections for the Mumbai circle, and 9 for others). The set of input
30 order determine the sequence or priority of input data. This may be involving
parameters such as timestamps, data relevance scores, or user-defined preferences.
27

Further, the deduplication rules are already implemented by Customer relationship management (CRM) module/platforms connected to the system [200] and the system [200] automatically customizes the deduplication rules implementation.
5 [0079] For example, an exemplary screenshot depicting the process has been shown
in FIG. 5 under an exemplary rule implemented by a CRM module say Rule ABC
of deduplication of customer details, under the step of preparing the entry, an CRM
prepares the entry of the one or more customer attributes including
customer_Date_of_birth, customer_Name, customer_Father’s_name,
10 customer_Postal_code, ustomer_House_number and customer_Address_part_1.
Additionally, in an exemplary rule say Rule DEF of deduplication of customer details, under the step of comparing the entry of the one or more customer attributes with the plurality of entries of the one or more corresponding customer attributes, the CRM system compares the one or more attributes including
15 customer_Date_of_birth, customer_Name, customer_Father’s_name,
customer_Postal_code, customer_House_number and Customer_Address_part_1,
with the entry of the one or more attributes including corresponding date of birth
corresponding customer_date_of_birth, corresponding customer_Name,
corresponding customer_Father’s_name, corresponding customer_Postal_code,
20 corresponding customer_House_number and corresponding
Customer_Address_part_1. For comparison of customer_date_of_birth, an exact match may be defined by the system [200] to automatically customize the deduplication rules implementation. For comparison of each of customer_name, customer_father_name customer_Postal_code, customer_House_number and
25 customer_Address_part_1, a similar match may be defined by the system [200] to
automatically customize the deduplication rules implementation.
[0080] The deduplication rules are a set of mandatory checks mandated to be
applied during the onboarding of new customers for telecom products. These rules
30 aim to ensure that a customer does not exceed the specified number of connections,
28

which varies by telecom circle (e.g., a maximum of 6 connections for the Mumbai circle, and 9 for others).
[0081] In an example, customers may attempt to bypass the connection limits by:
5 Providing a different ID proof than previously used. Registering under a slightly
altered name (e.g., changes in surname or the addition of a middle name). Using a different address and acquiring additional connections using the names of different family members.
10 [0082] The deduplication rules may be dynamically configured. The configuration
options include:
[0083] Rule Application: Whether a rule is to be enforced or suppressed.
15 [0084] Rule Validation Outcome: If a rule validation fails, whether to automatically
reject the order or leave the decision to an administrator.
[0085] Maximum Number of Connections: The permissible number of connections
per rule. These requirements to be adaptable and configurable to address varying
20 regulatory and operational needs.
[0086] At step 306, the method comprises retrieving, by a transceiver unit [204] from a database [206], a set of deduplication rules configuration based on the input order. The present disclosure encompasses the user interface [202] receives an input
25 order from a user. This input order comprises various parameters relevant to the
process. Upon receiving the input order, the transceiver unit [204] initiates a retrieval process to fetch relevant deduplication rules from the database [206]. The transceiver unit [204] communicates with the database [206] to recovery a set of deduplication rules. These rules are predefined and stored in the database, and they
30 correspond to the parameters of the input order. The recovery deduplication rules
are then configured for further processing within the system [200]. The set of
29

deduplication rules refers to a collection of predefined checks that are applied to identify and manage duplicate data entries
[0087] For example, in an e-commerce scenario, if a user submits an order
5 containing product details and customer information through the user interface
[202], the transceiver unit [204] interacts with the database to fetch deduplication
rules pertinent to the order. These rules may include criteria for identifying and
managing duplicate orders or customer entries. By retrieving the deduplication rules
based on the input order, the system [200] ensures that the data processing aligns
10 with the established database.
[0088] At step 308, the method comprises receiving, by the processing unit [208], a selection of a rejection action type, based on a user input, wherein the rejection action type is one of an auto-rejection type and an agent-consent type. The present
15 disclosure encompasses the processing unit [208] is configured to accept a user's
selection of a rejection action type, which is based on user input. The rejection action type can be either an auto-rejection type or an agent-consent type. The auto-rejection types describe automated processes that reject duplicate data entries based on predefined rules. On the other hand, agent-consent types may be involved where
20 human approval is required before certain actions are taken.
[0089] For example, when a customer of a network service provider submits an order for a service package, the system [200] detects a potential duplicate order with matching details, including the service plan, billing address, and payment method.
25 If configured for auto-rejection, the system [200] would automatically cancel the
duplicate order to avoid redundant transactions, enhancing efficiency and preventing billing errors. Alternatively, if set to agent-consent mode, the system [200] would alert a designated agent to review the duplicate order. The agent assesses factors like customer history and specific circumstances before approving
30 or rejecting the order, ensuring accurate processing aligned with customer needs.
30

Once the agent provides consent, the system [200] proceeds accordingly, either approving or rejecting the order based on their decision.
[0090] At step 310, the method comprises identifying, by the identification unit
5 [210], an enabled rule status associated with one or more deduplication rules from
the set of deduplication rules. The present disclosure encompasses that the
identification unit [210] is programmed to ascertain the enabled rule status linked
to one or more deduplication rules within the set of deduplication rules. The input
order parameter is received from the user such as user identification information
10 etc. associated with the input order.
[0091] At step 312, the method comprises identifying, by the identification unit [210], a plurality of target deduplication rules from the one or more deduplication rules based on at least the enabled rule status associated each of the plurality of
15 target deduplication rules and the set of input order parameters. The present
disclosure encompasses that the identification unit [210] is programmed to ascertain the enabled rule status linked to one or more deduplication rules within the set of deduplication rules. The input order parameter is received from the user such as user identification information etc. associated with the input order. More
20 specifically, the enabled rule status associated with the one or more deduplication
rules is further identified by the identification unit [210] based on at least one of the input order, at least one input order parameter from the set of input order parameters, and a predefined rule status associated with the one or more deduplication rules. The identification unit [210] checks the predefined status of
25 each rule in the set of deduplication rules. Based on the analysis, the identification
unit [210] identifies which rules are enabled (active) and should be applied. The plurality of target deduplication rules from the one or more deduplication rules is identified by the identification unit [210] based on at least a predefined priority associated with each deduplication rule from the one or more deduplication rules,
30 and at least input order parameter from the set of input order parameters. The
predefined rule status refers to the preconfigured state of each deduplication rule,
31

indicating whether it is active or inactive. This status is stored in the system and is
used by the identification unit [210] to determine which rules to apply during the
deduplication process. The preconfigured state denotes the initial setup or
arrangement of deduplication rules within the system. The target deduplication
5 rules are specific rules selected from the set of deduplication rules based on certain
criteria. These criteria include the enabled rule status, the priority assigned to each rule, and the specific parameters of the input order. The enabled rule status indicating whether a rule is active or not. The input order parameters received from the input order that influence which rules are selected.
10
[0092] In an example, the predefined rule status and preconfigured state ensure that the system's deduplication rules are organized and ready for use. The identification unit [210] selects target deduplication rules based on specific criteria, applying them in accordance with predefined priorities and input order parameters. The
15 validation process determines the status of the input order, guiding the system in
customizing the deduplication rules implementation to manage duplicate data effectively.
[0093] For example, when a customer submits an order for a new service, the
20 identification unit [210] assesses the input order parameters, such as service type
and customer details, along with predefined rule statuses. Based on predefined
priorities associated with each deduplication rule and input order parameters, the
identification unit [210] identifies multiple target deduplication rules. The
predefined priorities refer to the ordered importance assigned to each deduplication
25 rule. These priorities determine the sequence in which the rules are applied. The
system sets these priorities based on factors such as regulatory requirements,
operational policies, and business rules. These rules help streamline processes by
signalling potential duplicate orders for automatic rejection or manual review,
depending on the configured settings. The input order parameters are the specific
30 details and attributes associated with an input order. These parameters include
32

customer information, service details, timestamps, data relevance scores, and user-defined preferences.
[0094] At step 314, the method comprises validating, by the validation unit [212],
5 the input order based on the plurality of target deduplication rules. The present
disclosure encompasses the validation unit [212] is configured to validate the input order by utilizing the plurality of target deduplication rules identified by the identification unit [210]. The input order is a request submitted by a user to the system for processing. This validation process ensures that the input order conforms
10 to the established deduplication rules. More specially, the input order based on the
plurality of target deduplication rules is validated by the validation unit [212] based on a predefined validating configuration associated with each target deduplication rule from the plurality of target deduplication rules. The predefined validating configuration indicates a predetermined setup or arrangement for validating data
15 within the system. Each deduplication rule has an associated validating
configuration that specifies:
[0095] Validation Criteria: Conditions that must be met for data to be considered
valid.
20
[0096] Validation Process: Steps involved in checking the data against the
validation criteria.
[0097] For example, if a customer places an order for a specific service package,
25 the validation unit [212] checks the order against the validating configurations
associated with the identified target deduplication rules. This validation ensures that the order aligns with predefined criteria, such as service eligibility or billing requirements, specified by each rule.
30 [0098] At step 316, the method comprises determining, by the determination unit
[214], one of a positive validation status and a negative validation status associated with the input order. The present disclosure encompasses the determination unit
33

[214] is programmed to assess and conclude either a positive validation status or a
negative validation status associated with the input order. This determination is
based on the outcome of the validation process conducted by the validation unit
[212], wherein the input order is analysed against the established deduplication
5 rules. The positive validation status associated with the input order is determined
by the processing unit [208] in an event a successful validation associated the set of
input order parameters based on the predefined validating configuration is detected
by the processing unit [208]. In an example, the validation unit [212] is responsible
for validating the input order against the target deduplication rules. A positive
10 validation status is achieved when the input order meets all the predefined
validation criteria, indicating that the order is valid and free from duplicates. Conversely, a negative validation status occurs when the input order fails to meet these criteria, suggesting potential duplicates or other issues.
15 [0099] In order words, the user interface [202] receives an input order, which
includes various parameters related to the customer and the service they are requesting. The processing unit [208] applies the saved deduplication rules to the input order. The validation unit [212] validates the input order against the identified target deduplication rules. The determination unit [214] assesses the validation
20 results and assigns a validation status (positive or negative) to the input order. Based
on the validation status, the processing unit [208] customizes the implementation of the deduplication rules, making the handling of duplicate data to align with the validated input order.
25 [0100] At step 318, the method comprises transmitting, by the transceiver unit
[204], an input order accept status based on the positive validation status. The present disclosure encompasses that the transceiver unit [204] is further programmed to transmit an input order accept status based on a positive validation status. This indicates that the input order has successfully met the validation criteria.
30
34

[0101] At step 320, the method comprises automatically customizing, by the
processing unit [208], the deduplication rules implementation associated with the
input order based on at least the input order accept status associated with the input
order, and the positive validation status associated with the input order. More
5 specially, the processing unit [208] is configured to automatically customize the
implementation of deduplication rules associated with the input order. This customization is based on factors including the input order accept status and the positive validation status. By analysing these statuses, the processing unit [208] modifies the deduplication rules implementation accordingly and tailors
10 management of duplicate data in placement with the validated input order. The
tailors management of duplicate data provides a method or system for customized management of duplicate data. It includes processes that adaptively handle duplicate data entries based on conditions, optimizing storage efficiency and data performance.
15
[0102] For example, if a customer's order is accepted and successfully validated, the processing unit [208] tailors the application of deduplication rules accordingly. This customization ensures that validated orders proceed smoothly through the provisioning process without unnecessary duplication checks, expediting order
20 fulfilment. Conversely, if an order faces acceptance or validation issues, the
processing unit [208] may adjust the deduplication rules to prioritize error resolution or manual review, safeguarding order accuracy and customer satisfaction in the telecommunications service provisioning pipeline.
25 [0103] Thereafter, the method terminates at step 322.
[0104] Referring to FIG. 4, an exemplary system architecture for automatically customizing a deduplication rules implementation, in accordance with exemplary implementations of the present disclosure is shown. 30
35

[0105] The CRM servers [404] containing different micro services which cater to different APIs. Each microservices serves a context, for e.g.,
⦁ COP_MS deals with order related APIs – submit order, query order, modify
order
5 ⦁ CIS instances deal with customer related APIs – create, modify or deactivate
customer
⦁ L2O instances deals with APIs that manages the lifecycle of leads and
prospects
⦁ OAM instance deals with the maintenance and operation of all the
10 microservice instances and communicate with outer products related to alarms,
KPIs or other management, health check-up information.
[0106] The channels [405] from which, the APIs to servers e.g. POS (Point of Sale) [406], Digital Marketplace (DMP) [407], Self-Care [408], CRM UI [409] etc. These
15 channels [405] are connected to servers using load balancer or FMS [403]. The
channels [405] which are tightly coupled to CRM [404] e.g. CRM UI [409] communicates directly via Load balancer while other systems which belong to different product such as self-care, POS [406] communicates to servers using FMS [403]. The FMS [403] is a middleware which links two different products and
20 performs language translations or workflow management.
[0107] Subscription Engine [401]: The subscription engine is responsible for
managing user subscriptions and related operations. It functions as the central unit
for processing subscription requests, handling activations, renewals, and
25 terminations of service subscriptions. This engine interacts with various other
system components, such as the Financial Management System (FMS) and the Enterprise Product Catalogue (EPC), to ensure that subscription details are accurately recorded and maintained.
36

[0108] EPC (Enterprise Product Catalogue) [402], a centralised data repository which drives BSS telecom operations and some network nodes too for e.g., 5G charging system, called PCF.
5 [0109] FMS (Fulfilment Management System) [403], a middleware, which acts a
mediator between two different products and at the same time, provides language translation. E.g., if one product understands SOAP protocol while other one understands RESTful services, FMS [403] will translate the messages between these 2 nodes and ensure seamless communication. 10
[0110] DIF[413] –Data Information Framework, a gold copy of CRM, EPC, Geographical Information System (GIS) which caches the business data and provides API for fast access.
15 [0111] UAP [412] – Unified Assurance Platform, which deals with the installation
processes at customer premises, handling repair mechanism and technician visit to network sites.
[0112] The databases [411] connected to servers which persist the business data
20 related to customers, orders, leads, prospects and server configurations
[0113] The present disclosure may relate to a non-transitory computer readable storage medium storing instructions for automatically customizing a deduplication rules implementation, the instructions include executable code which, when
25 executed by one or more units of a system, causes: a user interface [202] of the
system to receive, an input order comprising a set of input order parameters; a transceiver unit [204] of the system to retrieve, from a database, a set of deduplication rules based on the input order; a processing unit [208] of the system to receive a selection of a rejection action type, based on a user input, wherein the
30 rejection action type is one of an auto-rejection type and an agent-consent type; an
identification unit [210] of the system to: identify an enabled rule status associated
37

with one or more deduplication rules from the set of deduplication rules, and
identify a plurality of target deduplication rules from the one or more deduplication
rules based on at least the enabled rule status associated each of the plurality of
target deduplication rules and the set of input order parameters; a validation unit
5 [212] of the system to validate, the input order based on the plurality of target
deduplication rules, a determination unit [214] of the system to determine, one of a
positive validation status and a negative validation status associated with the input
order; the transceiver unit [204]of the system to transmit an input order accept status
based on the positive validation status; the processing unit [208] of the system to
10 automatically customize, the deduplication rules implementation associated with
the input order based on at least the input order accept status associated with the input order, and the positive validation status associated with the input order.
[0114] As is evident from the above, the present disclosure provides a technically
15 advanced solution for automatically customizing a deduplication rules
implementation. In particular the present solution avoids a need of a manual input
for enabling/disabling/redefining the rules while implementing the rules for
deduplication of customer details, for instance during execution of ‘New Customer
Onboarding’ order. The present disclosure provides a system and method for
20 automatically customizing a deduplication rules implementation that improves
customer service relationships, reduces time-to-market for new business
requirement, provides modifications and adaptations, assists in customer retention
and drives sales growth. The system and method for automatically customizing the
deduplication rules implementation also helps in tracking the progress of an order
25 such as new customer onboarding, modifications in customer profile etc. through
milestones.
[0115] While considerable emphasis has been placed herein on the disclosed
implementations, it will be appreciated that many implementations can be made and
30 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
38

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.
5 [0116] Further, in accordance with the present disclosure, it is to be acknowledged
that the functionality described for the various components/units can be
implemented interchangeably. While specific embodiments may disclose a
particular functionality of these units for clarity, it is recognized that various
configurations and combinations thereof are within the scope of the disclosure. The
10 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.
39

We Claim:
1. A method for automatically customizing a deduplication rules
implementation, the method comprising:
5 - receiving, by a user interface [202], an input order comprising a set of input
order parameters;
- retrieving, by a transceiver unit [204] from a database [206], a set of
deduplication rules
- receiving, by a processing unit [208], a selection of a rejection action type,
10 based on a user input, wherein the rejection action type is one of an auto-
rejection types and an agent-consent type;
- identifying, by an identification unit [210], an enabled rule status associated
with one or more deduplication rules from the set of deduplication rules;
- identifying, by the identification unit [210], a plurality of target
15 deduplication rules from the one or more deduplication rules based on at
least the enabled rule status associated each of the plurality of target deduplication rules and the set of input order parameters;
- validating, by a validation unit [212], the input order based on the plurality
of target deduplication rules;
20 - determining, by a determination unit [214], one of a positive validation
status and a negative validation status associated with the input order;
- transmitting, by the transceiver unit [204], an input order accept status based
on the positive validation status; and
- automatically customizing, by the processing unit [208], the deduplication
25 rules implementation associated with the input order based on at least the
input order accept status associated with the input order, and the positive validation status associated with the input order.
2. The method as claimed in claim 1, wherein the set of deduplication rules
comprises at least an addition rule, a modification rule, and a deletion rule.
30 3. The method as claimed in claim 1, wherein identifying, by the identification
unit [210], the enabled rule status associated with the one or more

deduplication rules is further based on at least one of the input order, at least one input order parameter from the set of input order parameters, and a predefined rule status associated with the one or more deduplication rules.
4. The method as claimed in claim 1, wherein identifying, by the identification
5 unit [210], the plurality of target deduplication rules from the one or more
deduplication rules is further based on at least a predefined priority associated with each deduplication rule from the one or more deduplication rules, and at least one input order parameter from the set of input order parameters.
5. The method as claimed in claim 1, wherein validating, by the validation unit
10 [212], the input order based on the plurality of target deduplication rules is
further based on a predefined validating configuration associated with each target deduplication rule from the plurality of target deduplication rules.
6. The method as claimed in claim 5, wherein the positive validation status
associated with the input order is determined by the processing unit [208] in
15 an event a successful validation associated the set of input order parameters
based on the predefined validating configuration is detected by the processing unit [208].
7. A system [200] for automatically customizing a deduplication rules
implementation, the system comprising:
20 - a user interface [202] configured to receive, an input order comprising a set
of input order parameters;
- a transceiver unit [204] connected to at least the user interface [202], the
transceiver unit [204] configured to retrieve, from a database [206], a set of
deduplication rules based on the input order;
25 - a processing unit [208] connected to at least the transceiver unit [204], the
processing unit [208] configured to receive a selection of a rejection action type, based on a user input, wherein the rejection action type is one of an auto-rejection type and an agent-consent type;
- an identification unit [210] connected to at least the processing unit [208],
30 the identification unit [210] configured to:

o identify an enabled rule status associated with one or more
deduplication rules from the set of deduplication rules, and
o identify a plurality of target deduplication rules from the one or more
deduplication rules based on at least the enabled rule status
5 associated each of the plurality of target deduplication rules and the
set of input order parameters; and
- a validation unit [212] connected to at least the identification unit [210], the
validation unit [212] configured to validate, the input order based on the
plurality of target deduplication rules;
10 - a determination unit [214] connected to at least the validation unit [212], the
determination unit [214] configured to determine, one of a positive validation status and a negative validation status associated with the input order, wherein:
the transceiver unit [204] is further configured to transmit an input
15 order accept status based on the positive validation status, and
the processing unit [208] is further configured to automatically
customize, the deduplication rules implementation associated with the input
order based on at least the input order accept status associated with the input
order, and the positive validation status associated with the input order.
20 8. The system [200] as claimed in claim 7, wherein the set of deduplication rules
comprises at least an addition rule, a modification rule, and a deletion rule.
9. The system [200] as claimed in claim 7, wherein the enabled rule status
associated with the one or more deduplication rules is further identified by the
identification unit [210] based on at least one of the input orders, at least one
25 input order parameter from the set of input order parameters, and a predefined
rule status associated with the one or more deduplication rules.
10. The system [200] as claimed in claim 7, wherein the plurality of target
deduplication rules from the one or more deduplication rules is further
identified by the identification unit [210] based on at least a predefined priority
30 associated with each deduplication rule from the one or more deduplication

rules, and at least one input order parameter from the set of input order parameters.
11. The system [200] as claimed in claim 7, wherein the input order based on the
plurality of target deduplication rules is further validated by the validation unit
5 [212] based on a predefined validating configuration associated with each
target deduplication rule from the plurality of target deduplication rules.
12. The system [200] as claimed in claim 11, wherein the positive validation status
associated with the input order is determined by the processing unit [208] in
an event a successful validation associated the set of input order parameters
10 based on the predefined validating configuration is detected by the processing
unit [208].