EP-4740502-A1 - METHOD AND SYSTEM FOR ROUTING MOBILE TERMINATING CALL TO USER WITH SET OF USER DEVICES

EP4740502A1EP 4740502 A1EP4740502 A1EP 4740502A1EP-4740502-A1

Abstract

The present disclosure relates to a method and a system for routing a Mobile Terminating (MT) call to a user associated with a set of user devices The method comprises: receiving, the MT call associated with the user of the set of user devices; determining, via (SIB), a user profile status with user, wherein the user profile status is one of a user profile available status and a user profile unavailable status; fetching, a user profile based on the determined user profile status; identifying, 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, target user device(s) from the set of user devices based on the identified forking type; and routing, the MT call based on the identified forking type to the target user device(s).

Inventors

SINHA, ANURAG
Kelkar, Priti
KUMAR, ABHAY
Solanki, Mehul
BHATNAGAR, AAYUSH
Bisht, Birendra Singh
Singh, Harbinder Pal

Assignees

Jio Platforms Limited

Dates

Publication Date: 20260513
Application Date: 20240701

Claims (18)

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 predefined 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.
18. A non-transitory computer-readable storage medium storing instruction for routing a Mobile Terminating (MT) call to a user associated with a set of user devices, the storage medium comprising 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 associated with the set of user devices; a determination unit [204] of the system 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] of the system to fetch a user profile associated with the user based on the determined user profile status; 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 determination unit [204] of the system to determine one or more target user devices from the set of user devices based on the identified forking type; and a routing unit [210] 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 the user.

Description

METHOD AND SYSTEM FOR ROUTING MOBILE TERMINATING CALL TO USER WITH SET OF USER DEVICES TECHNICAL FIELD [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. BACKGROUND [0002] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art. [0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users. [0004] 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 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 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. [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. 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. [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 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 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 routing, by a routing 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 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 associ