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 ROUTING MOBILE TERMINATING CALL TO USER WITH SET OF USER DEVICES”
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.
2
METHOD AND SYSTEM FOR ROUTING MOBILE TERMINATING CALL TO USER WITH SET OF USER DEVICES
TECHNICAL FIELD
5
[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to method and system for routing mobile terminating call to user associated with set of user devices.
10
BACKGROUND
[0002]
The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated 15 that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[0003]
Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first 20 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 fourth generation (4G) technology 25 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. 30
[0004]
Multi-device features are being offered by telecom operators now a days where the same mobile number is being honored on multiple devices. With multi-device, the operators are providing a feature of forking the call on all the devices. Call Forking, also known as Call
3
splitting, is a feature of Session Initiation Protocol (SIP) that enables an incoming call to ring
several extensions, i.e., other phones, at once. The first phone to answer takes control of the incoming call. In the existing solutions, calls can be forked in the following two ways:
•
Sequential forking or serial forking – Request will be sent to one device and if that 5 device is unavailable then the request will be sent to second device and so on.
•
Parallel forking – Request will be sent to all the device at the same time and if the call is answered by one of the devices, the request sent to the other devices are terminated by network.
10
[0005]
In the existing solutions, the type of forking to be provided to the user is statically configured at the network and there is no control of the user to select the option on the forking type. Therefore, there exists a need to provide a solution that can facilitate user-based selection of the forking type and overcome the limitations of the existing solutions.
15
SUMMARY
[0006]
This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter. 20
[0007] An aspect of the present disclosure may relate to a method for routing a Mobile Terminating (MT) call to a user associated with a set of user devices. The method comprises: receiving, by a transceiver unit, the Mobile Terminating (MT) call associated with the user, wherein the user is associated with the set of user devices; determining, by a determination 25 unit, at a System Information Block (SIB) associated with the user, a user profile status associated with the user, wherein the user profile status is one of a user profile available status and a user profile unavailable status; fetching, by an analysis unit, a user profile associated with the user based on the determined user profile status; identifying, by an identification unit, a forking type included in the fetched user profile, wherein the forking type is at least one of a 30 user-defined forking and a pre-defined forking; determining, by the determination unit, one or more target user devices from the set of user devices based on the identified forking type; and
4
routing, by a rou
ting unit, the MT call based on the identified forking type to at least one of the one or more target user devices associated with the user.
[0008]
In an exemplary aspect of the present disclosure, the user profile available status is determined by the determination unit, in an event the user profile associated with the user is 5 available at least at the SIB block, and the user profile unavailable status is determined by the determination unit, in an event the user profile associated with the user is not available at least at the SIB block.
[0009]
In an exemplary aspect of the present disclosure, fetching the user profile associated 10 with the user based on the determined user profile status comprises fetching the user profile associated with the user at least from the SIB block based on the user profile available status, and the user profile associated with the user is fetched from a server based on the user profile unavailable status.
15
[0010]
In an exemplary aspect of the present disclosure, fetching the user profile associated with the user based on the determined user profile status comprises fetching the user profile associated with the user from a server based on the user profile unavailable status.
[0011]
In an exemplary aspect of the present disclosure, the user-defined forking included in 20 the user profile is generated by the generation unit, based on a user input received via at least one of user device from the set of user devices associated with the user.
[0012]
In an exemplary aspect of the present disclosure, the generating, the user-defined forking comprises: receiving, by the transceiver unit, the user input comprising a predefined 25 star code from the user via one of the user devices, wherein the pre-defined star code is associated with one of the serial forking and the parallel forking; identifying, by the identification unit, a target forking type based on the predefined star code received from the user, wherein the target forking type is one of the serial forking and the parallel forking; mapping, by the allocation unit, the target forking type with the user profile associated with the 30 user; generating, by the generation unit, an updated user profile based on the user defined forking comprising the target forking type; and storing, by the storage unit at least at the server, the updated user profile associated with the user based on the user defined forking comprising the target forking type associated with the user.
5
[0013]
In an exemplary aspect of the present disclosure, the target forking type is identified based on matching the predefined star code received from the user and a list of network defined star code.
5
[0014]
In an exemplary aspect of the present disclosure, the MT call is routed to each target user device of the one or more target user devices in an event target forking type is the parallel forking, and the MT call is routed to one of the target user devices of the one or more target user devices in an event target forking type is the serial forking.
10
[0015] Another aspect of the present disclosure may relate to a system for routing a Mobile Terminating (MT) call to a user associated with a set of user devices. The system comprises: a transceiver unit configured to receive the Mobile Terminating (MT) call associated with the user, wherein the user is associated with the set of user devices; a determination unit connected to at least the transceiver unit, wherein the determination unit is configured to determine at a 15 System Information Block (SIB) associated with the user, a user profile status associated with the user, wherein the user profile status is one of a user profile available status and a user profile unavailable status; an analysis unit connected to at least the determination unit, wherein the analysis unit is configured to fetch, a user profile associated with the user based on the determined user profile status; an identification unit connected to at least the analysis unit, 20 wherein the identification unit is configured to identify, a forking type included in the fetched user profile, wherein the forking type is at least one of a user-defined forking and a pre-defined forking; the determination unit connected to at least the identification unit, wherein the determination unit is configured to determine, one or more target user devices from the set of user devices based on the forking type; and a routing unit connected to at least the determination 25 unit, wherein the routing unit is configured to route, the MT call based on the identified forking type to at least one of the one or more target user devices associated with user.
[0016]
Furthermore, an aspect of the present disclosure may relate to a user device comprising a processor configured to receive, a Mobile Terminating (MT) call associated with a user. The 30 user is associated with a set of user devices, and the user is associated with a user profile status, wherein the user profile status is one of a user profile available status and a user profile unavailable status. The user profile associated with the user is fetched by the system, and a forking type included in the fetched user profile is identified by the system, wherein the forking
6
type is at least one of a user
-defined forking and a predefined forking. The user device (from the set of user devices) is then determined as a target user device for the MT call based on the identified forking type.
[0017]
Yet another aspect of the present disclosure may relate to a non-transitory computer 5 readable storage medium storing instructions for routing a Mobile Terminating (MT) call to a user associated with a set of user devices. The instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit of the system to receive the Mobile Terminating (MT) call associated with the user, wherein the user is associated with the set of user devices. The instructions further include executable code which, 10 when executed, causes a determination unit of the system to determine at a System Information Block (SIB) associated with the user, a user profile status associated with the user, wherein the user profile status is one of a user profile available status and a user profile unavailable status. The instructions further include executable code which, when executed, causes an analysis unit of the system to fetch, a user profile associated with the user based on the determined user 15 profile status. The instructions further include executable code which, when executed, causes an identification unit of the system to identify, a forking type included in the fetched user profile, wherein the forking type is at least one of a user-defined forking and a pre-defined forking. The instructions further include executable code which, when executed, causes the determination unit of the system to determine, one or more target user devices from the set of 20 user devices based on the forking type; and a routing unit of the system to route, the MT call based on the identified forking type to at least one of the one or more target user devices associated with user.
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 to provide the 30 user with control over his choices of forking.
[0020]
It is another object of the present disclosure to provide a solution to make the network operator more dynamic in their forking approach keeping in mind the user preferences.
7
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 5 which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. 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 10 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.
[0022]
FIG.1 illustrates an exemplary block diagram of a computing device upon which the 15 features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0023]
Fig. 2 illustrates an exemplary block diagram of a system for routing a Mobile Terminating (MT) call to a user associated with a set of user devices, in accordance with 20 exemplary implementations of the present disclosure.
[0024]
Fig. 3 illustrates a method flow diagram [300] for routing a Mobile Terminating (MT) call to a user associated with a set of user devices in accordance with exemplary implementations of the present disclosure. 25
[0025]
Fig. 4 illustrates a method flow diagram [400] for storing updated user profile associated with the user based on the user defined forking in accordance with exemplary implementations of the present disclosure.
30
[0026]
Fig. 5 illustrates a flow diagram [500] for routing a Mobile Terminating (MT) call to a user associated with a set of user device, in accordance with exemplary implementations of the present disclosure.
8
[0027]
Fig. 6 illustrates an exemplary network side architecture [600] for routing a Mobile Terminating (MT) call to a user associated with a set of user device, in accordance with exemplary implementations of the present disclosure.
[0028]
The foregoing shall be more apparent from the following more detailed description of 5 the disclosure.
DETAILED DESCRIPTION
[0029]
In the following description, for the purposes of explanation, various specific details 10 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 discussed above or might address only some of the 15 problems discussed above.
[0030]
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 20 for 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.
[0031]
Specific details are given in the following description to provide a thorough 25 understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
30
[0032]
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
9
operations may be re
-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
[0033]
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 5 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 ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the 10 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.
[0034]
As used herein, a “processing unit” or “processor” or “operating processor” includes 15 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 Integrated Circuits, Field Programmable Gate Array 20 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
[0035]
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 30 to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a
10
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.
[0036]
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 5 computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions. 10
[0037]
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 each other, which also includes the methods, 15 functions, or procedures that may be called.
[0038]
AVP (Attribute-Value Pair): In 5G protocols such as Diameter, AVPs are used to represent and exchange attribute information between network elements, facilitating signalling and control functions within the network. 20
[0039]
Target user devices refer to the particular devices among the user's multiple devices (e.g., mobile phone, tablet, laptop) that are identified for receiving an incoming MT call.
[0040]
The pre-defined star code is a network-defined sequence, used to trigger specific call 25 handling features. For example, a star code like '21' might activate call forwarding, while '22' could enable parallel forking. These codes are recognized by the network system and mapped to corresponding actions in the user's profile.
[0041]
An updated user profile encompasses the modified user settings that include newly 30 defined forking preferences based on user input via star codes.
11
[0042]
Forking type refers to mechanism whereby an incoming call can be directed to multiple devices associated with a user, simultaneously or sequentially, based on predefined preferences or conditions. There are two main types of forking:
[0043]
In serial forking, the incoming call is routed to a sequence of designated devices in a 5 specific order until it is answered or reaches the final destination according to the user's preferences. If the first device doesn't answer or is unavailable, the call is forwarded to the next device in the sequence.
[0044]
In parallel forking, the incoming call is simultaneously directed to multiple designated 10 devices associated with the user. The call can be answered on any of these devices, and the remaining devices stop ringing once one device accepts the call.
[0045]
User devices refer to electronic devices that belong to or are used by an individual user, typically in the context of telecommunications and network services. These devices are capable 15 of receiving and/or initiating communication services. User devices may include but are not limited to smartphones, tablet, laptops, smartwatch and so on.
[0046]
SAA (Server Assignment Answer): SAA is a message or response from the HSS to the SIB (System Information Block, which is a combination of the BGCF, SCSCF and ICSCF) in 20 the network. It typically contains information requested by the network element (like SIB) from the HSS, such as user profiles or service-related data.
[0047]
SAR (Server Assignment Request): SAR is a request initiated by a network element (like SIB) towards the HSS to obtain specific information or services related to a subscriber, 25 such as user profiles, service activation status, or configuration data.
[0048]
Mobile Terminating (MT) call: It refers to a call that is directed towards a mobile device or a subscriber. In simpler terms, it's an incoming call received by a mobile phone or user device. 30
[0049]
System Information Block (SIB): In telecommunications, particularly in cellular networks like GSM (Global System for Mobile Communications) or LTE (Long-Term Evolution), SIBs are broadcasted periodically by base stations to provide essential information
12
to mobile devices. This information includes network parameters, cell configuration, and
system information necessary for mobile devices to connect and operate within the network.
[0050]
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 5 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.
10
[0051]
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.
15
[0052] 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 for routing a Mobile Terminating (MT) call to a user associated with a set of user devices.
20
[0053]
The present disclosure aims to overcome the above-mentioned and other existing problems by:
•
Providing new star codes in at servers / network end,
•
Storing/retrieving forking type information to/from Home Subscriber Server (HSS) on Cx interface, 25
•
Storing the forking type information retrieved from the HSS during per user registration,
•
Forking the call based on the stored information per subscriber, and
•
Considering default forking type if no option selected by user.
30
[0054]
Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
13
[0055]
Fig. 1 illustrates an exemplary block diagram of a computing device [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 implement a method for routing a Mobile Terminating (MT) call to a user associated with a set of user devices utilising the system [200]. In another implementation, the computing 5 device [100] itself implements the method for routing a Mobile Terminating (MT) call to a user associated with a set of user devices 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.
10
[0056]
The computing device [100] may include a bus [102] or other communication mechanism for communicating information, and a hardware processor [104] coupled with bus [102] for processing information. The hardware processor [104] may be, for example, a general-purpose microprocessor. 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 15 the 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 media accessible to the processor [104], render the computing device [100] into a special-purpose machine that is customized to 20 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].
[0057]
A storage device [110], such as a magnetic disk, optical disk, or solid-state drive is 25 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), 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 30 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 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
14
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.
[0058]
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 5 which in combination with the computing device [100] causes or programs the computing device [100] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [100] in response to the processor [104] executing one or more 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 10 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 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.
15
[0059]
The computing device [100] also may include a communication interface [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 20 corresponding type of 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 various types of information. 25
[0060]
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 transmit a requested code for an application program through the Internet [128], the ISP [126], the local network [122], the host [124] and 30 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.
15
[0061]
Referring to Fig. 2, an exemplary block diagram of a system [200] for routing a Mobile Terminating (MT) call to a user associated with a set of user devices is shown, in accordance with the exemplary implementations of the present disclosure. The system [200] comprises at least one transceiver unit [202], at least one determination unit [204], at least one analysis unit [206], at least one identification unit [208], at least one routing unit [210], at least one allocation 5 unit [212], at least one generation unit [214], and at least one storage unit [216]. Also, all of the components/ units of the system [200] are assumed to be connected to each other unless otherwise indicated below. Also, in 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. 10
[0062]
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 15 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.
20
[0063]
The system [200] is configured for routing a Mobile Terminating (MT) call to a user associated with a set of user device, with the help of the interconnection between the components/units of the system [200].
[0064]
In order for routing a mobile termination call to a user associated with a set of user 25 device, a transceiver unit [202] of the system configured to receive the Mobile Terminating (MT) call associated with the user, wherein the user is associated with the set of user devices (such as mobile phone, laptops, tablet, smartwatch). The present disclosure encompasses that the transceiver unit [202] is responsible for receiving the Mobile Terminating (MT) call associated with the user. The Mobile terminating (MT) call refers to a call initiated from a call 30 initiating device (such as smartphone, landline phone) and directed towards a call receiving device.
16
[0065]
The determination unit [204] is connected to at least the transceiver unit [202], wherein the determination unit [204] is configured to determine via a System Information Block (SIB) associated with the user, a user profile status associated with the user, wherein the user profile status is one of a user profile available status and a user profile unavailable status. The present disclosure encompasses that the SIB contains information about the user including their profile 5 and status. The user profile available status is determined by the determination unit [204] in an event the user profile associated with the user is available at least at the SIB block, and the user profile unavailable status is determined by the determination unit [204] in an event the user profile associated with the user is not available at least at the SIB block. When the determination unit [204] identifies the user profile as available, it means that the system [200] 10 can retrieve the necessary information to process the incoming call efficiently and when the determination unit [204] identifies the user profile as unavailable, it signifies that the system [200] cannot access or retrieve the user's profile information from the SIB.
[0066]
Further, the analysis unit [206] is connected to at least the determination unit [204], 15 wherein the analysis unit [206] is configured to fetch, a user profile associated with the user based on the determined user profile status. Particularly, fetching the user profile associated with the user, based on the determined user profile status comprises fetching the user profile associated with the user at least from the SIB block based on the user profile available status. Fetching the user profile associated with the user based on the determined user profile status 20 comprises fetching the user profile associated with the user from a server based on the user profile unavailable status. In an implementation, when the user profile available status is determined, the analysis unit [206] fetches the user profile directly from the System Information Block (SIB) associated with the user. If the user profile is not available at SIB when an INVITE is received at a network end from user end with activation code for activation 25 of call forking, the SIB will perform Server-Assignment-Request (SAR) towards HSS and retrieves the user profile to get the information of forking type selected by user. Further, SIB accordingly serves the INVITE request. Also, if the Server-Assignment-Answer (SAA) received from HSS does not have any Forking-Type Attribute Value Pair (AVP) information, then SIB applies the default forking option decided (configured at SIB) by the operator and 30 handles the INVITE request accordingly.
[0067]
Also, the identification unit [208] is connected to at least the analysis unit [206], wherein the identification unit [208] is configured to identify, a forking type included in the
17
fetched user profile, wherein the forking type is at least one of a user
-defined forking and a pre-defined forking. The present disclosure encompasses that identification unit [208] identifies the type of forking specified in the user's profile. Forking refers to the process of directing an incoming call to multiple devices simultaneously or sequentially based on predefined codes. The user-defined forking involves routing the call according to specific 5 preferences set by the user wherein the pre-defined forking follows predetermined routing codes established by the network provider. Further, user defined forking refers to the ability of a subscriber to specify how incoming calls should be routed among multiple devices. This is set by the user through specific actions, such as entering predefined star codes (1231 for serial, 1232 for parallel). 10
[0068]
Particularly, the generation unit [214] is configured to generate the user- defined forking based on a user input received via at least one of the user devices associated with the user. In an implementation to generate the user defined forking: the transceiver unit [202] is configured to receive, the user input comprising a predefined star code from the user via one 15 of the user devices, wherein the pre-defined star code is associated with one of the serial forking and the parallel forking; the identification unit [208] is configured to identify, a target forking type based on the predefined star code received from the user, wherein the target forking type is one of the serial forking and the parallel forking; an allocation unit [212] is configured to map, the target forking type with the user profile associated with the user; the generation unit 20 [214] is configured to generate, an updated user profile based on the user defined forking comprising the target forking type; and the storage unit [216] is configured to store, at least at the server, the updated user profile associated with the user based on the user defined forking comprising the target forking type. Also, in an implementation the target forking type is identified based on matching the predefined star code received from the user and a list of 25 network defined star code.
[0069]
After identifying the forking type from the fetched user profile, the determination unit [204] connected to at least the identification unit [208] is configured to determine, one or more target user devices from the set of user devices based on the forking type. The present 30 disclosure encompasses that the determination unit [204] examines the user's profile status and the forking type identified by the identification unit wherein the forking type is at least one of a sequential forking or serial forking and a parallelly forking, and wherein the sequential forking or serial forking means request will be sent to one device and if that device is
18
unavailable then the request will be sent to second device and so on and parallelly forking
means request will be sent to all the device at the same time and if the call is answered by one of the device, the request sent to the other devices are terminated by network.
[0070]
Further, the routing unit [210] is configured to route, the MT call based on the identified 5 forking type to at least one of the one or more target user devices associated with user. The present disclosure encompasses that the routing unit [210] ensure that the MT call is directed to the selected target user device(s) based on the sequential (i.e., serial) forking or the parallelly forking as determined from the user profile. Also, the MT call is routed to each target user device of the one or more target user devices in an event target forking type is the parallel 10 forking, and the MT call is routed to one of the target user devices of the one or more target user devices in an event target forking type is the serial forking.
[0071]
Further, an exemplary implementation according to the present disclosure is explained as below. 15
[0072]
In order to store updated user profile associated with the user based on the user defined forking, initially when a user dials a star code “1231” to activate serial fork option and “1232” to activate parallel fork option, an INVITE request is sent to the network. On receiving the INVITE request at the network, with the activation code, SIB initiates a SAR request towards 20 HSS with Forking-Type AVP (Proprietary) set to Parallel or Serial depending on the activation code received. The forking type information is stored in the HSS to provide a seamless service to the user even when the new SIB is selected for that user. Now on receiving a MT call request for this user, SIB will check the option selected by user in the stored user profile and fork the call accordingly. If the user profile is not available at SIB when the INVITE is received, SIB 25 will perform SAR towards HSS and retrieve the user profile where it gets the information of forking type selected by user and then accordingly serve the INVITE request. If the SAA received from HSS does have any Forking-Type AVP information, then SIB applies the default forking option decided (configured at SIB) by the operator and handle the INVITE request accordingly. Example: On receiving the INVITE request from the user device at the network, 30 with the activation code, SIB initiates a (Server-Assignment-Request) SAR request towards HSS with Forking-Type set to Parallel or Serial depending on the activation code received. The identification unit [208] compares it with a list of predefined codes maintained by the network. This comparison enables the system [200] to precisely identify whether the user
19
intends to implement serial forking or parallel forking for their incoming calls.
The target forking type is identified based on matching the predefined star code received from the user and a list of network defined star code, wherein the MT call is routed to each target user device of the one or more target user devices in an event target forking type is the parallel forking, and the MT call is forked to one of the target user devices of the one or more target user devices in 5 an event target forking type is the serial forking. On receiving a MT call request for the user, SIB checks the option selected by user in the stored user profile and fork the call accordingly.
[0073]
Furthermore, the storage unit [216] is to store, at least at the server, the updated user profile associated with the user based on the user defined forking comprising the target forking 10 type. Once the generation unit [214] has updated the user's profile to reflect their defined forking preferences, including the target forking type, the storage unit [216] ensures that this updated profile is securely stored, typically on a server. By storing the updated user profile, the storage unit [216] ensures that the system retains the latest information regarding the user's preferences and the forking type information is stored in the HSS to provide a seamless service 15 to the user even when the new SIB is selected for that user.
[0074]
Referring to Figure 3, an exemplary method flow diagram [300] for routing a Mobile Terminating (MT) call to a user associated with a set of user device, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the 20 method [300] is performed by the system [200]. Also, as shown in Figure 3, the method [300] starts at step [302].
[0075]
At step 304, the method comprises receiving, by a transceiver unit [202], the Mobile Terminating (MT) call associated with the user, wherein the user is associated with the set of 25 user devices (such as mobile phone, laptops, tablet, smartwatch). The present disclosure encompasses that the transceiver unit [202] is responsible for receiving the Mobile Terminating (MT) call associated with the user. The Mobile terminating (MT) call refers to a call initiated from a call initiating device (such as smartphone, landline phone) and directed towards a call receiving device. 30
[0076]
At step 306, the method comprises, determining, by a determination unit [204], via a System Information Block (SIB) associated with the user, a user profile status associated with the user, wherein the user profile status is one of a user profile available status and a user profile
20
unavailable status.
The present disclosure encompasses that the SIB contains information about the user including their profile and status. The user profile available status is determined by the determination unit [204], in an event the user profile associated with the user is available at least at the SIB block, and the user profile unavailable status is determined by the determination unit [204], in an event the user profile associated with the user is not available at least at the 5 SIB block. When the determination unit [204] identifies the user profile as available, it means that the method [300] can retrieve the necessary information to process the incoming call efficiently and when the determination unit [204] identifies the user profile as unavailable, it signifies that the method [300] cannot access or retrieve the user’s profile information from the SIB. 10
[0077]
At step 308, the method comprises, fetching, by an analysis unit [206], a user profile associated with the user based on the determined user profile status. Particularly, fetching by the analysis unit [206], the user profile associated with the user based on the determined user profile status comprises fetching the user profile associated with the user at least from the SIB 15 block based on the user profile available status, and fetching the user profile associated with the user based on the determined user profile status comprises: fetching the user profile associated with the user from a server based on the user profile unavailable status. In an implementation when the user profile available status is determined, the analysis unit [206] fetches the user profile directly from the System Information Block (SIB) associated with the 20 user. If the user profile is not available at SIB when an INVITE is received at a network end from user end with activation code for activation of call forking, the SIB will perform Server-Assignment-Request (SAR) towards HSS and retrieves the user profile to get the information of forking type selected by user. Further SIB accordingly serves the INVITE request. Also, if the Server-Assignment-Answer (SAA) received from HSS does not have any Forking-Type 25 Attribute Value Pair (AVP) information, then SIB applies the default forking option decided (configured at SIB) by the operator and handle the INVITE request accordingly.
[0078]
At step 310, the method comprises, identifying, by an identification unit [208], a forking type included in the fetched user profile, wherein the forking type is at least one of a user-30 defined forking and a pre-defined forking. The present disclosure encompasses that identification unit [208] identifies the type of forking specified in the user's profile. Forking refers to the process of directing an incoming call to multiple devices simultaneously or sequentially based on predefined rules. The user-defined forking involves routing the call
21
according to specific preferences set by the user wherein the pre
-defined forking follows predetermined routing rules established by the network provider.
[0079]
Particularly, the generation unit [214] generates the user defined forking based on a user input received via at least one of the user devices associated with the user. In an 5 implementation to generate the user defined forking: the transceiver unit [202] receives, the user input comprising a predefined star code from the user via one of the user devices, wherein the pre-defined star code is associated with one of the serial forking and the parallel forking; the identification unit [208] identifies, a target forking type based on the predefined star code received from the user, wherein the target forking type is one of the serial forking and the 10 parallel forking; an allocation unit [212] maps, the target forking type with the user profile associated with the user; the generation unit [214] generates, an updated user profile based on the user defined forking comprising the target forking type; and the storage unit [216] stores, at least at the server, the updated user profile associated with the user based on the user defined forking comprising the target forking type. Also, in an implementation the target forking type 15 is identified based on matching the predefined star code received from the user and a list of network defined star code.
[0080]
At step 312, after identifying the forking type from the fetched user profile, the method comprises, determining, by the determination unit [204], one or more target user devices from 20 the set of user devices based on the identified forking type. The present disclosure encompasses that the determination unit [204] examines the user's profile status and the forking type identified by the identification unit wherein the forking type is at least one of a sequential forking or serial forking and a parallelly forking, and wherein the sequential forking or serial forking means request will be sent to one device and if that device is unavailable then the 25 request will be sent to second device and so on and parallelly forking means request will be sent to all the device at the same time and if the call is answered by one of the device, the request sent to the other devices are terminated by network.
[0081]
At step 314, the method comprises, routing, by a routing unit [210], the MT call based 30 on the identified forking type to at least one of the one or more target user devices associated with the user. The present disclosure encompasses that the routing unit [210] ensure that the MT call is directed to the selected target user devices (s) based on the sequential (i.e., serial) forking or the parallelly forking as determined from the user profile. Also, the MT call is routed
22
to each target user device of the one or more target user devices in an event target forking type
is the parallel forking, and the MT call is routed to one of the target user devices of the one or more target user devices in an event target forking type is the serial forking.
[0082]
Thereafter, the method terminates at step [316]. 5
[0083]
Referring to Figure 4, an exemplary method flow diagram [400] for storing updated user profile associated with the user based on the user defined forking, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [400] is performed by the system [200]. Also, as shown in Figure 4, the method [400] 10 starts at step [402].
[0084]
At step 404, the method comprises receiving, by the transceiver unit [202], the user input comprising a predefined star code from the user via one of the user devices, wherein the pre-defined star code is associated with one of the serial forking and the parallel forking. In an 15 example, a star code “1231” may be used to activate a serial fork option and a star code “1232” may be used to activate a parallel fork option.
[0085]
At step 406, the method comprises, identifying, by the identification unit [208], a target forking type based on the predefined star code received from the user, wherein the target 20 forking type is one of the serial forking and the parallel forking. At step 408, the method comprises, mapping, by the allocation unit [212], the target forking type with the user profile associated with the user. The allocation unit [212] maps the identified forking type with the user's profile. This ensures that incoming calls are routed according to the user's preferences and the specified forking logic. 25
[0086]
Particularly, on receiving the INVITE request with the activation code (predefined star code), SIB initiates a (Server-Assignment-Request) SAR request towards HSS with Forking-Type set to Parallel or Serial depending on the activation code received. The identification unit [208] compares it with a list of predefined codes maintained by the network. This comparison 30 enables the system [200] to precisely identify whether the user intends to implement serial forking or parallel forking for their incoming calls. The activation codes (such as 1231 for serial forking or 1232 for parallel forking) are used by users to signal their preference for call handling methods to the network. The target forking type is identified based on matching the
23
predefined star code received from the user and a list of network defined star code wherein the
MT call is routed to each target user of the one or more target user devices in an event target forking type is the parallel forking, and the MT call is forked to one of the target user devices of the one or more target user devices in an event target forking type is the serial forking. On receiving a MT call request for the user, SIB will check the option selected by user in the stored 5 user profile and fork the call accordingly.
[0087]
After step 408, next at step 410, the method comprises, generating, by the generation unit [214], an updated user profile based on the user defined forking comprising the target forking type. If the user profile is not available at SIB when the INVITE is received, SIB will 10 perform (Server-Assignment-Request) SAR towards HSS and retrieve the user profile where it will get the information of forking type selected by user and then accordingly serve the INVITE request and if the (Server-Assignment-Answer) SAA received from HSS does have any Forking-Type AVP information, then SIB applies the default forking option decided (configured at SIB) by the operator and handle the INVITE request accordingly. 15
[0088]
At step 412, the method comprises storing, by the storage unit [216] at least at the server, the updated user profile associated with the user based on the user defined forking comprising the target forking type associated with the user. Once the generation unit [214] has updated the user's profile to reflect their defined forking preferences, including the target 20 forking type, the storage unit [216] ensures that this updated profile is securely stored, typically on a server. By storing the updated user profile, the storage unit [216] ensures that the system retains the latest information regarding the user's preferences and the forking type information is stored in the HSS to provide a seamless service to the user even when the new SIB is selected for that user. 25
[0089]
Thereafter, the method terminates at step [414].
[0090]
Referring to Figure 5, an exemplary flow diagram [500] for routing a Mobile Terminating (MT) call to a user associated with a set of user device, in accordance with 30 exemplary implementations of the present disclosure is shown.
[0091]
At step S1, the MT call received for the multidevice user.
24
[0092]
At step S2, it is checked if the user profile is available. If yes, the method proceeds to step S3, and if no it proceeds to step S4.
[0093]
At step S4, the method encompasses retrieving the user profile from HSS. Further, it proceeds to step S3. 5
[0094]
At step S3, further, it is checked if the fork option is selected by user. If yes, the method proceeds to step S5 and if not, the method leads to step S6.
[0095]
At step S5, the method encompasses forking the call according to the user option. 10
[0096]
At step S6, the method encompasses configuring default fork type in the network.
[0097]
Referring to Figure 6, an exemplary network side architecture [600] for routing a Mobile Terminating (MT) call to a user associated with a set of user device, in accordance with 15 exemplary implementations of the present disclosure is shown.
[0098]
The network side architecture [600] comprises at least one Media Gateway Control Function (MGCF) [601], at least one Telephony Application Server (TAS) [602], at least one Diameter Routing Agent (DRA) [603], at least one Home Subscriber Server (HSS) [604], at 20 least one Breakout Gateway Control Function (BGCF) [605], at least one Service Centralization and Continuity Application Server (SCFCF) [606], at least one Interrogating Call/Session Control Function (ICSCF) [607], at least one Element Management System (EMS) [608], at least one Location Information Management (LIM) [609], and at least one Proxy Call/Session Control Function (PCSCF) [610]. Also, all of the components/ units of the 25 network side architecture [600] are assumed to be connected to each other unless otherwise indicated below.
[0099]
Home Subscriber Server (HSS) [604] A database that stores information about mobile phone subscriptions. The HSS [604] is a key component of modern mobile networks, holding 30 important subscriber data such as service profiles, location information, and authentication data.
25
[0100]
MGCF (Media Gateway Control Function) [601]: MGCF [601] controls the call setup and teardown functions between circuit-switched networks (like PSTN) and packet-switched networks (like the IP network used in 5G).
[0101]
TAS (Telephony Application Server) [602]: TAS [602] hosts and executes telephony 5 applications such as voicemail, call forwarding, and interactive voice response (IVR).
[0102]
DRA (Diameter Routing Agent) [603]: DRA [603] is responsible for routing Diameter protocol messages within the network. Diameter protocol messages are used for authentication, authorization, and accounting (AAA) functions in 5G networks. 10
[0103]
BGCF (Breakout Gateway Control Function) [605]: BGCF [605] controls the routing of communication sessions between different networks in the 5G architecture.
[0104]
SCFCF (Service Centralization and Continuity Application Server) [606]: SCFCF 15 [606] manages the service continuity between different access networks (e.g., from 4G to 5G) and provides session management capabilities.
[0105]
ICSCF (Interrogating Call/Session Control Function) [607]: ICSCF [607] is responsible for call routing and session control in IP multimedia subsystems (IMS) networks, which are 20 used for multimedia communication in 5G.
[0106]
EMS (Element Management System) [608]: EMS [608] manages the configuration, monitoring, and maintenance of network elements in the 5G architecture.
25
[0107]
LIM (Location Information Management) [609]: LIM [609] manages location information for mobile devices in the network, which is crucial for services like location-based services and network optimization.
[0108]
PCSCF (Proxy Call/Session Control Function) [610]: PCSCF [610] is responsible for 30 handling SIP (Session Initiation Protocol) signalling for voice and multimedia communication sessions in IMS networks.
26
[0109]
Mj (Mobility Management Entity): Mj is an interface between (BGCF [605] and MGCF [601]).
[0110]
Mi (Management Interface): Mi is an interface between BGCF [605] and SCFCF [606].
5
[0111]
Cx (Cx Interface): Cx is an interface between (DRA [603] and HSS [604]), (DRA [603] and ICSCF [607] and (DRA [603] and SCSCF [606].
[0112]
ISC (Inter-System Coordination): ISC is an interface between TAS [602] and SCFCF [606]. 10
[0113]
Rest (Representational State Transfer): REST is an interface between BGCF [605] and EMS [608].
[0114]
X1/X2 (X2 Interface): X1 and X2 is an interface between SCFCF [606] and LIM [609]. 15
[0115]
MW (Microwave Link): MW is an interface between (ICSCF [607] and SCFCF [606]), (PCSCF [610] and SCFCF [606] and (ICSCF [607] and PCSCF [610]).
[0116]
Furthermore, an aspect of the present disclosure may relate to a user device comprising 20 a processor configured to receive, a Mobile Terminating (MT) call associated with a user. The user is associated with a set of user devices, and the user is associated with a user profile status, wherein the user profile status is one of a user profile available status and a user profile unavailable status. The user profile associated with the user is fetched by the system [200], and a forking type included in the fetched user profile is identified by the system [200], wherein 25 the forking type is at least one of a user-defined forking and a predefined forking. The user device (from the set of user devices) is then determined as a target user device for the MT call based on the identified forking type.
[0117]
Further, another aspect of the present disclosure may relate to a non-transitory computer 30 readable storage medium storing instructions for routing a Mobile Terminating (MT) call to a user associated with a set of user devices. The instructions include executable code which, when executed by one or more units of a system, causes a transceiver unit [202] of the system to receive the Mobile Terminating (MT) call associated with the user, wherein the user is
27
associated with the set of user devices
. The instructions further include executable code which, when executed causes a determination unit [204] of the system to determine at a System Information Block (SIB) associated with the user, a user profile status associated with the user, wherein the user profile status is one of a user profile available status and a user profile unavailable status. The instructions further include executable code which, when executed 5 causes an analysis unit [206] of the system to fetch, a user profile associated with the user based on the determined user profile status. The instructions further include executable code which, when executed causes an identification unit [208] of the system to identify, a forking type included in the fetched user profile, wherein the forking type is at least one of a user-defined forking and a pre-defined forking. The instructions further include executable code which, 10 when executed causes the determination unit [204] of the system to determine, one or more target user devices from the set of user devices based on the forking type; and a routing unit [210] of the system to route, the MT call based on the identified.
[0118]
As is evident from the above, the present disclosure provides a technically advanced 15 solution for forking calls based on user preference. The present solution provides many advantages over the standard practices such as:
•
Remove tight binding - There may be no mandate binding on the type of forking (sequential or serial forking or parallel) by the operator to serve calls for the multi-20 device users.
•
User control - User now have control and can change the forking type according to his wish dynamically.

[0119]
While considerable emphasis has been placed herein on the disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented 30 is illustrative and non-limiting.
WE CLAIM:
1. A method for routing a Mobile Terminating (MT) call to a user associated with a set of
user devices, the method comprising:
- receiving, by a transceiver unit [202], the Mobile Terminating (MT) call associated with the user, wherein the user is associated with the set of user devices;
- determining, by a determination unit [204], via a System Information Block (SIB) associated with the user, a user profile status associated with the user, wherein the user profile status is one of a user profile available status and a user profile unavailable status;
- fetching, by an analysis unit [206], a user profile associated with the user based on the determined user profile status;
- identifying, by an identification unit [208], a forking type included in the fetched user profile, wherein the forking type is at least one of a user-defined forking and a pre-defined forking;
- determining, by the determination unit [204], one or more target user devices from the set of user devices based on the identified forking type; and
- routing, by a routing unit [210], the MT call based on the identified forking type to at least one of the one or more target user devices associated with the user.

2. The method as claimed in claim 1, wherein the user profile available status is determined by the determination unit [204], in an event the user profile associated with the user is available at least at the SIB block, and the user profile unavailable status is determined by the determination unit [204], in an event the user profile associated with the user is not available at least at the SIB block.
3. The method as claimed in claim 1, wherein, fetching the user profile associated with the user based on the determined user profile status comprises: fetching the user profile associated with the user at least from the SIB block based on the user profile available status.
4. The method as claimed in claim 1, wherein, fetching the user profile associated with the user based on the determined user profile status comprises: fetching the user profile associated with the user from a server based on the user profile unavailable status.

5. The method as claimed in claim 1, wherein the user-defined forking included in the user profile is generated by a generation unit [214], based on a user input received via at least one user device from the set of user devices associated with the user.
6. The method as claimed in claim 5, wherein the generating the user-defined forking comprises:

- receiving, by the transceiver unit [202], the user input comprising a predefined star code from the user via one of the user devices, wherein the predefined star code is associated with one of a serial forking and a parallel forking;
- identifying, by the identification unit [208], a target forking type based on the predefined star code received from the user, wherein the target forking type is one of the serial forking and the parallel forking;
- mapping, by an allocation unit [212], the target forking type with the user profile associated with the user;
- generating, by the generation unit [214], an updated user profile based on the user defined forking comprising the target forking type; and
- storing, by a storage unit [216] at least at a server, the updated user profile associated with the user based on the user defined forking comprising the target forking type associated with the user.

7. The method as claimed in claim 6, wherein the target forking type is identified based on matching the predefined star code received from the user and a list of network defined star code.
8. The method as claimed in claim 6, wherein the MT call is routed to each target user device of the one or more target user devices in an event target forking type is the parallel forking, and the MT call is routed to one of the target user devices of the one or more target user devices in an event target forking type is the serial forking.
9. A system for routing a Mobile Terminating (MT) call to a user associated with a set of user devices, the system comprises:

a transceiver unit [202] configured to receive the Mobile Terminating (MT) call associated with the user, wherein the user is associated with the set of user devices;
a determination unit [204] connected to at least the transceiver unit [202], wherein the determination unit [204] configured to determine via a System Information Block (SIB) associated with the user, a user profile status associated with the user, wherein the user profile status is one of a user profile available status and a user profile unavailable status;
an analysis unit [206] connected to at least the determination unit [204], wherein the analysis unit [206] is configured to fetch, a user profile associated with the user based on the determined user profile status;
an identification unit [208] connected to at least the analysis unit [206], wherein the identification unit [208] is configured to identify, a forking type included in the fetched user profile, wherein the forking type is at least one of a user-defined forking and a pre-defined forking;
the determination unit [204] connected to at least the identification unit [208], wherein the determination unit [204] is configured to determine, one or more target user devices from the set of user devices based on the forking type; and
a routing unit [210] connected to at least the determination unit [204], wherein the routing unit [210] is configured to route, the MT call based on the identified forking type to at least one of the one or more target user devices associated with user.
10. The system as claimed in claim 9, wherein the determination unit [204] is configured
to determine:
the user profile available status in an event the user profile associated with the user is available at least at the SIB block, and
the user profile unavailable status in an event the user profile associated with the user is not available at least at the SIB block.
11. The system as claimed in claim 9, wherein fetching the user profile associated with the
user, based on the determined user profile status comprises fetching the user profile

associated with the user at least from the SIB block based on the user profile available status.
12. The system as claimed in claim 9, wherein, fetching the user profile associated with the user based on the determined user profile status comprises: fetching the user profile associated with the user from a server based on the user profile unavailable status.
13. The system as claimed in claim 9, wherein a generation unit [214] is configured to generate the user- defined forking based on a user input via at least one user devices from the set of user devices associated with the user.
14. The system as claimed in claim 13, wherein to generate the user defined forking:
the transceiver unit [202] is configured to receive, the user input comprising a predefined star code from the user via one of the user devices, wherein the predefined star code is associated with one of a serial forking and a parallel forking,
the identification unit [208] is configured to identify, a target forking type based on the predefined star code received from the user, wherein the target forking type is one of the serial forking and the parallel forking,
an allocation unit [212] is configured to map, the target forking type with the user profile associated with the user,
the generation unit [214] is configured to generate, an updated user profile based on the user defined forking comprising the target forking type, and
a storage unit [216] is configured to store, at least at a server, the updated user profile associated with the user based on the user defined forking comprising the target forking type.
15. The system as claimed in claim 14, wherein the target forking type is identified based on matching the predefined star code received from the user and a list of network defined star code.
16. The system as claimed in claim 14, wherein the MT call is routed to each target user device of the one or more target user devices in an event target forking type is the parallel forking, and the MT call is forked to one of the target user devices of the one or more target user devices in an event target forking type is the serial forking.

17. A user device comprising:
a processor configured to:
receive, a Mobile Terminating (MT) call associated with a user, wherein the user is associated with a set of user devices, and the user is associated with a user profile status, wherein the user profile status is one of a user profile available status and a user profile unavailable status, wherein
the user profile associated with the user is fetched by a system [200],
a forking type included in the fetched user profile is identified by the system [200], wherein the forking type is at least one of a user-defined forking and a predefined forking,
the user device from the set of user devices is determined as a target user device for the MT call based on the identified forking type.