System and method for providing fixed mobile convergence services

Abstract

The present disclosure relates to a system and method for providing FMC services. The system receives a contact number / short code of a first user dialed by a second user, and establishes a connection between a BTAS and an IMS server when the second user dials a mobile number. The system invokes an FMC creation / update service, converts the short code, sends an invite request message (RM) to an IMS core network (CN), and triggers a ring mode on a mobile / fixed line device. In response to the conversion, the system sends an invite RM to an IMS CN of a mobile number associated with a fixed line (FL), and in response to the sending, triggers a ring mode on a mobile device and a FL device. The system establishes a telephone call between the mobile device and the fixed line device of the second user, respectively, and the FL device / mobile device of the first user.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to wireless communication systems. More specifically, the present disclosure relates to systems and methods for providing Fixed Mobile Convergence (FMC) services using a Business Telephony Application Server (BTAS) associated with a Central exchange (Centrex) group.

Background Art

[0002] The following description of related art is intended to provide background information related to the field of the present disclosure. This section may include some aspects of technologies related to various features of the present disclosure. However, it should be understood that this section is used only to enhance the reader's understanding of the present disclosure, not as an approval of the prior art.

[0003] Generally, one or more enterprise users may be assigned a desktop landline phone within the office premises, and the mobile number of each user may be associated with the desktop landline phone assigned to the first user. When a second user makes a call to the first user using a short code (i.e., an internal line) or the full number of the desktop phone (from outside the Central exchange (Centrex) group), the phone call may branch to both the desktop phone of the first user and the associated mobile number / phone (in parallel or sequentially). During an established phone call, the user can also perform seamless call pickup from the associated mobile / landline phone.

[0004] Furthermore, simultaneous ringing can be a private branch exchange (PBX) feature that allows incoming calls to be routed to multiple phones simultaneously. A phone call can be forwarded to a user's desk phone, computer, and mobile device, as well as to multiple users. However, traditional systems may not offer speed code dialing from mobile phones in addition to the corporate user's landline. Traditional systems may not provide a single extension / number / speed dial for a user to receive incoming calls on both devices (i.e., mobile and landline) outside of a closed user group / PBX. [Overview of the Initiative] [Problems that the invention aims to solve]

[0005] Considering the requirements for speed dialing from mobile devices in addition to fixed-line telephones (Centrex group) of corporate users, it may be necessary in the art to provide a system and method that can overcome the shortcomings of existing prior art by providing a system and method for providing Fixed Mobile Convergence (FMC) services using the Business Telephony Application Server (BTAS) associated with the Central exchange (Centrex) group.

[0006] Purpose of this disclosure Some of the purposes of this disclosure that are satisfied by at least one embodiment of this specification are listed below.

[0007] In a general embodiment, this disclosure provides a system and method for providing Fixed Mobile Convergence (FMC) services using a Business Telephony Application Server (BTAS) associated with the Central exchange (Centrex) group.

[0008] In another aspect, the Disclosure provides a system and method for converting abbreviated codes into associated landline numbers to ring both mobile and landline lines.

[0009] In another embodiment, the disclosure determines whether a telephone call is answered on a landline or a mobile device, and then, when the telephone call is answered on a landline or mobile phone, disconnects the mobile phone or landline telephone call, respectively.

[0010] In another aspect, the disclosure enables speed dialing from mobile phones in addition to landlines for enterprise users within the Cloud Internet Protocol (IP) Central Exchange (Centrex).

[0011] In another aspect, the disclosure provides a single extension / number for a user to receive incoming calls on both devices (i.e., mobile and landline).

[0012] In another aspect, the disclosure enables user experiences including dialing from mobile phones, dialing from landlines, telephone calls from external corporate users to landlines, and seamless call pickup from associated landlines or mobile phones.

[0013] In another embodiment, the Disclosure enables seamless call pickup, in which telephone calls are answered from mobile numbers (e.g., C-party) associated with each fixed line (e.g., B-party). [Means for solving the problem]

[0014] This section is provided in a simplified form to introduce some of the objects and aspects of the invention, which will be further described below in the modes for carrying out the invention. This summary is not intended to identify any important features or scope of the claimed subject matter.

[0015] In one embodiment, the Disclosure provides a system for providing Fixed Mobile Convergence (FMC) services. The system receives at least one of a contact number and a short code associated with a first user of a Central exchange (Centrex) group, which is dialed by a second user using at least one of a mobile device or a fixed-line device. The contact number and short code correspond to at least one of a mobile number and a fixed-line number associated with the first user of the Centrex group. Furthermore, the system establishes a connection between the BTAS and an IMS core network associated with an Internet Protocol Multimedia Subsystem (IMS) server when the second user dials the mobile number and the fixed line is associated with the mobile number. Furthermore, once the system has established a connection between the BTAS and the IMS core network, it invokes at least one of a Fixed Mobile Convergence (FMC) creation service and an FMC update service to trigger a modification of Initial Filter criteria (IFC) service chain data in the IMS core network. Furthermore, when the second user dials the short code, the system translates the short code to at least one associated with the fixed-line number and mobile number. Subsequently, in response to the conversion, the system sends one or more invite request messages to the IMS core network associated with the mobile number linked to the fixed line. Furthermore, in response to the transmission, the system activates ringing mode on the mobile device and the fixed line device to establish a telephone call. In addition, the system establishes telephone calls between at least one of the mobile device or fixed line device associated with the second user and at least one of the fixed line device and mobile device associated with the first user.

[0016] In another aspect, the Disclosure provides a method for providing a Fixed Mobile Convergence (FMC) service. The method includes receiving at least one of a contact number and a short code associated with a first user of a Central exchange (Centrex) group, which is dialed by a second user using at least one of a mobile device or a fixed-line device. The contact number and short code correspond to at least one of a mobile number and a fixed-line number associated with the first user of the Centrex group. Furthermore, the method includes establishing a connection between the BTAS and an IMS core network associated with an Internet Protocol Multimedia Subsystem (IMS) server when the second user dials the mobile number and the fixed line is associated with the mobile number. Furthermore, once the connection between the BTAS and the IMS core network is established, the method includes calling at least one of a Fixed Mobile Convergence (FMC) creation service and an FMC update service to trigger a modification of Initial Filter criteria (IFC) service chain data in the IMS core network. In addition, the method includes the step of converting a shortened code to at least one of a fixed-line number and a mobile number when a second user dials the shortened code. Furthermore, the method includes the step of sending one or more invite request messages to the IMS core network associated with the mobile number linked to the fixed line in response to the conversion. Furthermore, the method includes the step of activating ringing mode on the mobile device and the fixed-line device in response to the transmission to establish a telephone call. In addition, the method includes the step of having the processor establish a telephone call between at least one of the mobile device or fixed-line device associated with the second user and at least one of the fixed-line device or mobile device associated with the first user, respectively.

[0017] In another aspect, the disclosure relates to user equipment for providing FMC. User equipment may include a processor and memory coupled to the processor, the memory comprising, when executed, a processor-executable instruction causing the processor to transmit at least one of a contact number and a short code associated with a first user of a Central exchange (Centrex) group, which is dialed by a second user using at least one of the user equipment, the contact number and short code corresponding to at least one of a mobile number and a landline number associated with the first user, thereby establishing a telephone call between user equipment associated with the second user and user equipment associated with the first user.

[0018] In another aspect, the Disclosure receives at least one of a contact number and a short code associated with a first user of a Central exchange (Centrex) group, which is dialed by a second user using at least one of a mobile device or a fixed-line device, and the contact number and short code correspond to at least one of a mobile number and a fixed-line number associated with the first user of a Centrex group, and when the second user dials the mobile number and the fixed line is linked to the mobile number, a connection is established between the Business Telephony Application Server (BTAS) and the IMS core network associated with the Internet Protocol Multimedia Subsystem (IMS) server, and once the connection between the BTAS and the IMS core network is established, a Fixed Mobile The present invention relates to a non-temporary computer-readable medium containing machine-readable instructions that can be executed by a processor to call at least one of the Convergence (FMC) creation service and the FMC update service; when a second user dials a short code, convert the short code to at least one associated fixed-line number and a mobile number; in response to the conversion, send one or more invite request messages to the IMS core network associated with a mobile number linked to a fixed line; in response to the transmission, activate ringing mode on a mobile device and a fixed-line device to establish a telephone call, and establish a telephone call between at least one of the mobile device or fixed-line device associated with the second user and at least one of the fixed-line device or mobile device associated with the first user, respectively.

[0019] The accompanying drawings incorporated herein constitute part of the present invention and illustrate exemplary embodiments of the disclosed methods and systems, and similar reference numerals refer to the same parts across different drawings. Components in the drawings are not necessarily to scale, and instead, the focus is on clearly illustrating the principles of the invention. Some drawings may use block diagrams to show components and may not show the internal circuitry of each component. It will be understood by those skilled in the art that the inventions in such drawings include inventions of electrical components, electronic components, or circuits commonly used to implement such components. [Brief explanation of the drawing]

[0020] [Figure 1A] This figure shows an exemplary network architecture in which a system of the present disclosure may be implemented, in or using, according to one embodiment of the present disclosure. [Figure 1B] This figure shows an exemplary network architecture in which a system of the present disclosure may be implemented, in or using, according to one embodiment of the present disclosure. [Figure 2A] This figure shows an exemplary representation of a network device in relation to Figure 1A, according to one embodiment of the present disclosure. [Figure 2B] This is an illustrative flowchart illustrating an integrated architecture of a network device or BTAS according to embodiments of the present disclosure. [Figure 3A] This is an exemplary sequence diagram representation of a parallel telephone call branching flow according to one embodiment of the present disclosure. [Figure 3B] This is an exemplary sequence diagram representation of a parallel telephone call branching flow according to one embodiment of the present disclosure. [Figure 3C] This is an exemplary sequence diagram representation of a parallel telephone call branching flow according to one embodiment of the present disclosure. [Figure 4] This is an exemplary sequence diagram representation of a call flow for seamless call pickup according to one embodiment of the present disclosure. [Figure 5]An exemplary sequence diagram representation of a call flow (activation / deactivation) of an FMC service according to an embodiment of the present disclosure. [Figure 6] An exemplary flowchart of a method for providing a Fixed Mobile Convergence (FMC) service according to an embodiment of the present disclosure. [Figure 7] A diagram showing an exemplary computer system in which or by which embodiments of the present invention may be utilized according to an embodiment of the present disclosure. **DETAILED DESCRIPTION OF THE INVENTION**

[0021] The above will become apparent from the following more detailed description of the present invention.

[0022] In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be evident, however, that embodiments of the present disclosure may be practiced without these specific details. Some of the features described hereinafter may be used independently of each other or in any combination with other features. Individual features may not address all of the problems discussed above, or may only address some of the problems discussed above. Some of the problems discussed above may not be fully addressed by any of the features described herein. <http: / / www.w3.org / TR / xhtml1 / DTD / xhtml1-transitional.dtd>

[0023] [[ID=二十一]] [[ID=二十二]]The following description provides only exemplary embodiments and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the following description of exemplary embodiments will enable those skilled in the art to implement the exemplary embodiments. It should be understood that various changes may be made in the functions and arrangements of the elements without departing from the spirit and scope of the invention as described.

[0024] Specific details are given in the following description to provide a complete understanding of the embodiments. However, it will be understood by those skilled in the art that embodiments can be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in the form of block diagrams so as not to obscure the embodiments with unnecessary details. In other cases, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary details to avoid obscuring the embodiments.

[0025] Furthermore, it should be noted that individual embodiments may be described as processes, which may be represented as flowcharts, flow diagrams, data flow diagrams, structural diagrams, or block diagrams. While flowcharts may describe operation as a sequential process, many operations may be performed in parallel or simultaneously. In addition, the order of operations may be rearranged. A process terminates when its operations are complete, but may have additional steps not shown in the diagram. A process may correspond to a method, function, procedure, subroutine, subprogram, etc. When a process corresponds to a function, its termination may correspond to the function returning to the calling function or the main function.

[0026] The terms “exemplary” and / or “empirical” are used herein to mean that they serve as examples, cases, or illustrations. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, no embodiment or design described herein as “exemplary” and / or “empirical” should necessarily be construed as preferable or advantageous to any other embodiment or design, nor is it intended to exclude exemplary equivalent structures and techniques known to those skilled in the art. Furthermore, to the extent that the terms “include,” “have,” “contain,” and other similar terms are used in any embodiment for carrying out the invention or in the claims, such terms are intended to be inclusive, in a similar manner to the term “equipped” as an open transitional term, without excluding any additional or other elements.

[0027] Throughout this specification, any reference to “one embodiment,” “a certain embodiment,” “a certain case,” or “one example” means that a particular feature, structure, or characteristic described in relation to an embodiment is included in at least one embodiment of the present invention. Therefore, occurrences of the phrase “in one embodiment” or “in a certain embodiment” in various places throughout this specification do not necessarily all refer to the same embodiment. Furthermore, a particular feature, structure, or characteristic may be combined in any suitable manner from one or more embodiments.

[0028] The terms used herein are intended to describe only specific embodiments and are not intended to limit the invention. Where used herein, the singular forms “a,” “an,” and “the” are intended to include the plural form unless the context otherwise explicitly indicates. The terms “comprises” and / or “comprising,” when used herein, specify the presence of the described features, integers, steps, actions, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, actions, elements, components, and / or groups thereof. Where used herein, the term “and / or” includes all combinations of one or more of the related enumerated terms.

[0029] Various embodiments of this disclosure provide systems and methods for providing Fixed Mobile Convergence (FMC) services. This disclosure can convert abbreviations to associated fixed-line numbers and ring both mobile and fixed-line connections. This disclosure determines whether a call is answered on a fixed-line device or a mobile device, and then, when a call is answered on a fixed-line / mobile connection, disconnects the mobile / fixed-line call, respectively. The FMC service may enable abbreviation dialing from mobile phones in addition to corporate users' fixed-line phones within a Cloud Internet Protocol (IP) Central Exchange (Centrex). This disclosure provides a single extension / number for a user to receive incoming calls on both devices (i.e., mobile and fixed-line). The user experience may include dialing from mobile phones, dialing from fixed-line phones, calls from external corporate users to fixed-line phones, and seamless call pickup from associated fixed-line or mobile phones. This disclosure enables seamless call pickup, where the call is answered from a mobile number (C-party) associated with each fixed-line (B-party).

[0030] Figures 1A and 1B show exemplary network architectures (100) and (150) in which the System (100) of the Disclosure may be implemented, in accordance with certain embodiments of the Disclosure, or using them. As shown in the network architecture (100) (or System 100) of Figure 1A, a network device (102) (hereinafter interchangeably referred to as Business Telephony Application Server (102) or BTAS (102)) may be configured to facilitate the provision of Fixed Mobile Convergence (FMC) services to a user device (110). The network device (or BTAS) (102) may be configured as an application server, may operate communicatively, or may be integrated with an Internet Protocol Multimedia Subsystem (IMS) server (106) (interchangeably referred to as IMS Server (106) or IMS Core Network (106)). The IMS server (106) may relate to a vendor or network / service provider for providing Fixed Mobile Convergence (FMC) services to a user device (110). In some embodiments, a BTAS (102) or network device (102) may be implemented in an existing IMS implementation to facilitate network services corresponding to a communications network (112). In some examples, the communications network (112) may relate to, but is not limited to, third-generation (3G) network services, fourth-generation (4G) network services, fifth-generation (5G) network services, sixth-generation (6G) network services, New Radio (services), Open Radio Access Network (O-RAN) services, Internet of Things (IoT) network services, etc.In one embodiment, the BTAS(102) / network device(102) may be communicably coupled to a Centralized Data Layer (CDL) server(104) or CDL framework(104) which may enable access to information stored across different physical hosts across multiple or different circles / clusters, in order to enable other aspects or features related to Fixed Mobile Convergence (FMC) services.

[0031] A user device (110) (also interchangeably referred to as user equipment (110), UE (110), or terminal (110)) may be at least one of a wired device or a wireless device. For example, a wired device may be a landline telephone, a terminal device, or any other stationary device through which communication can be established. A wireless device may be a mobile device, which may include, for example, a tablet, a phablet, and a mobile phone such as a feature phone or smartphone, and other devices. A user device (110) may include, but is not limited to, any of the devices mentioned above, any type of device capable of wired or wireless communication, such as a mobile phone, a tablet computer, a personal digital assistant (PDA), a personal computer (PC), a laptop computer, a wearable computer, a media center, a workstation, and other such devices. In some embodiments, a user device (110) may be at least one of a wireless or wired device that is contracted to or registered with a network service provided by a network / service provider. In one exemplary embodiment, the network / service may relate to a 3G / 4G / 5G / 6G / NR / O-RAN / IoT network, but is not limited to this. Furthermore, the network / service provider may provide network services corresponding to at least one of the following: cellular network services, private network services, satellite network services, or convergence network services.

[0032] In one embodiment, the communication network (112) relating to the implementation of the BTAS-based IMS may be a 3G / 4G / 5G / 6G / NR / O-RAN / IoT network, which may include at least one of a wireless network, a wired network, or a combination thereof. The communication network (112) may be implemented as one of several different types of networks, such as an intranet, a local area network (LAN), a wide area network (WAN), or the internet. Furthermore, the communication network (112) may be either a dedicated network or a shared network. A shared network may represent an association of several different types of networks that can use various protocols, such as Hypertext Transfer Protocol (HTTP), Transmission Control Protocol / Internet Protocol (TCP / IP), Wireless Application Protocol (WAP), Automatic Repeat Request (ARQ), etc. In one embodiment, the communication network (112) may relate to a 3G / 4G / 5G / 6G / NR / O-RAN / IoT network, which may be facilitated through, for example, a Global System for Mobile communication (GSM) network, Universal Terrestrial Radio Network (UTRAN), Enhanced Data rates for GSM Evolution (EDGE) Radio Access Network (GERAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), Wireless Fidelity (Wi-Fi), or other LAN access networks, or satellite or terrestrial wide-area access networks such as Wireless Microwave Access (WiMAX) networks.In one exemplary embodiment, a communications network (112) may enable a 3G / 4G / 5G / 6G / NR / O-RAN / IoT network based on a contract relating to a user / user device (110) and / or through a subscriber identification module (SIM) card. Various other types of communications networks (110) or networks / services may be possible.

[0033] In one example, the communication network (112) may utilize different types of air interfaces, such as code division multiple access (CDMA), time division multiple access (TDMA), or frequency division multiple access (FDMA) air interfaces, and other implementations. In one exemplary embodiment, a wired / fixed-line user device may use a wired access network, either alone or in combination with a wireless access network, including, for example, Plain Old Telephone Service (POTS), Public Switched Telephone Network (PSTN), Asynchronous Transfer Mode (ATM), and other network technologies configured to carry Internet Protocol (IP) packets.

[0034] In one embodiment, system 100 may perform BTAS(102) to receive at least one of a contact number and a short code associated with a first user of a Central exchange (Centrex) group, which is dialed by a second user using at least one of a mobile device or a fixed-line device (i.e., user device 110). The contact number and short code may correspond to at least one of a mobile number and a fixed-line number associated with the first user of the Centrex group.

[0035] In one embodiment, the system (100) may execute BTAS (102) to establish a connection between BTAS (102) and an IMS core network (106) associated with an Internet Protocol Multimedia Subsystem (IMS) server (106) when a second user dials a mobile number and a fixed line is linked to the mobile number.

[0036] In one embodiment, once the system (100) establishes a connection between the BTAS (102) and the IMS core network (106), it may execute the BTAS (102) to invoke at least one of the Fixed Mobile Convergence (FMC) creation service and the FMC update service in order to trigger a modification of Initial Filter criteria (IFC) service chain data in the IMS core network (106).

[0037] In one embodiment, the system (100) may perform a BTAS (102) to convert a speed code to at least one of the relevant landline numbers and mobile numbers when a second user dials the speed code.

[0038] In one embodiment, the system (100) may perform a BTAS (102) to send one or more invite request messages to the IMS core network (106) associated with a mobile number linked to a fixed line in response to the conversion.

[0039] In one embodiment, the system (100) may perform a BTAS (102) to activate ringing mode on the mobile device (110) and the fixed-line device (110) in response to a transmission and to establish a telephone call. In one embodiment, activating ringing mode on the mobile device (110) and the fixed-line device (110) further includes at least one of the following: ringing the fixed-line device (110) and the mobile device (110) simultaneously based on a pre-configured parallel branching mode or sequential branching mode; and ringing the fixed-line device (110) first and then ringing the mobile device (110) sequentially. In one embodiment, when ringing mode is activated on at least one of the fixed-line device (110) and the mobile device (110), the first user instead answers the telephone call on an alternate contact number by dialing a service code from an alternate contact number.

[0040] In one embodiment, the system (100) may perform a BTAS (102) to periodically determine whether a telephone call is answered by a fixed-line device (110) or a mobile device (110).

[0041] In one embodiment, when a telephone call is answered on a fixed-line device (110) or a mobile device (110), the system (100) may perform a BTAS (102) to disconnect the telephone call on the mobile device (110) or the fixed-line device (110), respectively.

[0042] In one embodiment, when the system (100) disconnects a telephone call on a mobile device (110) or a fixed-line device (110), it may perform a BTAS (102) to establish a telephone call between at least one of the mobile devices (110) or fixed-line devices (110) associated with a second user and at least one of the fixed-line devices (110) or mobile devices (110) associated with a first user.

[0043] In one embodiment, a fixed-line device (110) associated with the first user displays a Calling Line Identification (CLI), and a mobile device (110) associated with the first user displays the mobile phone number of the second user. In another embodiment, a fixed-line device (110) associated with the second user displays a Calling Line Identification (CLI), and a mobile device (110) associated with the second user displays the abbreviated code of the first user.

[0044] In one embodiment, the FMC service is activated when a pin is input via Dual-Tone Multi-Frequency Tones (DTMF), the FMC service is deactivated when a pin is input via DTMF, and the FMC service is not removed during deactivation.

[0045] In one embodiment, when a shortened code corresponds to a landline number, the system (100) may perform BTAS(102) to convert the dialed shortened code to a landline number using a virtual private branch exchange (VPBX) service. Furthermore, the system (100) may perform BTAS(102) to cause the Online Charging System (OCS) (not shown in Figure 1A) to charge the second user using a Credit Control Request (CCR). The OCS returns a Credit Control Answer (CCA) corresponding to the CCR. In addition, the system (100) may perform BTAS(102) to interact with a Serving Call Session Control Function (SCSCF) associated with the IMS core network (106). The SCSCF may apply Initial Filter Criteria (IFC) based on at least one of the first user's mobile number and landline number. Furthermore, system (100) may perform BTAS(102) to determine the appropriate FMC service to be called for Fixed Mobile Convergence (FMC) data associated with at least one of the mobile and fixed-line numbers of the first user. Furthermore, system (100) may perform BTAS(102) to provide at least one of notification and ringtone to the second user. In addition, system (100) may perform BTAS(102) to route invite to the fixed-line number associated with the first user and to route invite request messages to the IMS core network(106) associated with the mobile number. Furthermore, system (100) may perform BTAS(102) to activate ringing mode on the mobile device(110) and the fixed-line device(110) in order to establish a telephone call. Furthermore, the system (100) may perform BTAS (102) to cause the OCS to update the billable number to at least one of the fixed-line number and the mobile number, respectively, based on the response of a telephone call by a first user on a fixed-line device (110) or a mobile device (110).In addition, when a telephone call is answered on a fixed-line device (110) or a mobile device (110), the system (100) may perform BTAS(102) to disconnect the telephone call on the mobile device (110) or the fixed-line device (110), respectively. Furthermore, once the system (100) has disconnected the telephone call on the mobile device (110) or the fixed-line device (110), it may perform BTAS(102) to establish a telephone call between the fixed-line device (110) associated with a second user and at least one of the fixed-line devices (110) or mobile devices (110) associated with a first user.

[0046] In one embodiment, responding to a telephone call further includes an event in which the telephone call is established on a fixed-line number associated with a second user, and the telephone call is responded to from a mobile number associated with a third user. System (100) may execute BTAS(102) to establish a telephone call between the first user and the third user once the third user has inserted the telephone call details and routing details into the Centralized Data Layer (CDL) server (104). Furthermore, System (100) may execute BTAS(102) to fetch the telephone call details and routing details from the CDL server (104) by the BTAS associated with the second user. Furthermore, System (100) may execute BTAS(102) to establish a telephone call between the first user and the second user.

[0047] In relation to Figure 1B, the network service (corresponding to (112) in Figure 1A) may be provided to multiple entities or enterprises, such as Enterprise 1 (154-1), Enterprise 2 (154-2), Enterprise 3 (154-3), and Enterprise 4 (154-4) (collectively referred to as enterprises (154) and individually as enterprises (154)). In one embodiment, at least one of the enterprises (154) may include an Internet Protocol Private Branch Exchange (IP-PBX) (not shown in Figure 1B) to enable switching telephone calls between user devices (110) over local wiring. Each enterprise 154 may communicate with a communication network / server through Enterprise Session Border Controllers (E-SBCs) (156-1, 156-2, 156-3, and 156-4). As shown in Figure 1B, each enterprise 154, for example, enterprise 1 (154-1), enterprise 2 (154-2), enterprise 3 (154-3), and enterprise 4 (154-4), may be supported by network services (such as 3G / 4G / 5G / 6G / NR / O-RAN / IoT network services) via E-SBCs (156-1, 156-2, 156-3, and 156-4), respectively. The E-SBC (156) may be a set of executable instructions to enable connectivity and security related to the enterprise and service provider networks. The IP-PBX may be an in-house branch exchange or telephone exchange system within the enterprise, which may, for example, enable switching telephone calls between users within the enterprise. In one embodiment, the BTAS (102) may be coupled communicatively with other components, such as IP phones and provisioning servers. In one exemplary embodiment, the IP-PBX may communicate with the E-SBC (156) via Session Initiation Protocol (SIP) techniques. A business can relate to an entity that includes, but is not limited to, organizations, companies, stores, educational institution premises, office premises, shopping centers, residential areas / communities, and various other entities that may wish to use a communication network provided by a service provider.In one embodiment, the communication network may be available only within a predetermined area (authorized area) of the company. Various other types of entities / provisions are possible.

[0048] The IMS server (106 in Figure 1A) may include one or more modules or components that enable the IMS server to perform one or more functions. For example, the IMS server (106) may be an existing IMS core that includes components / modules handling various functions, such as a Serving-Call Session Control Function (S-CSCF) module (158), an Interrogating-Call Session Control Function (I-CSCF) module (162), and a Proxy-Call Session Control Function (P-CSCF) module (152). In one embodiment, a BTAS (102) may be integrated with the network of the IMS core (106) and other application servers to provide network services related to, for example, a 4G / 5G / 6G network. For example, the other application servers may include a Telephony Application Server (TAS) (160), which may be a common component used in a communication network to provide telephone applications and additional multimedia functions. In another example, other application servers may include a Mobile Number Portability (MNP) server (124), which may provide users with number portability, for example, by enabling them to retain the same number when changing service providers. Various other servers may be integrated into a BTAS-enabled IMS implementation to enable one or more services related to communication networks or 3G / 4G / 5G / 6G / NR / O-RAN / IoT networks without deviating from the scope of the description being given.

[0049] In relation to the components of the IMS server (106), the S-CSCF module (158) may be the primary node within the IMS server (106) responsible for session control. In one embodiment, to facilitate the routing of Session Initiation Protocol (SIP) messages as part of the service establishment procedure, a list of subscribers may be assigned to each S-CSCF module (158) at the time of IMS registration. In operation, the S-CSCF module (158) may enable downloading subscriber profiles from the Home Subscriber Server (HSS) (120) at the time of IMS registration. The I-CSCF module (162) may also be an important element of the IMS server (106) and may enable routing of any request from multiple S-CSCFs in the network to the appropriate S-CSCF module (158). The I-CSCF module (162) may also query the HSS (120) to obtain the address of the relevant S-CSCF module (158) for processing SIP initiation requests. As shown in Figure 1B, the P-CSCF module (152) can function as an entry point to or exit point from the service provider's IMS domain with respect to the IMS client. The P-CSCF module (152) can perform common functions such as registering with the correct node in the communication network and forward routing session requests, updating the S-CSCF module (158), maintaining a secure connection with the user device (110), and other such functions. In one embodiment, the network device (102) or BTAS (102) may be communicably coupled or integrated with one or more functional components, such as a Session Initiation Protocol (SIP) based application server. The SIP server may be built with features relevant to the type of enterprise (154).

[0050] Furthermore, as shown in Figure 1B, to provide various forms of network services (e.g., related to 3G / 4G / 5G / 6G / NR / O-RAN / IoT networks), the components of the IMS server (106) (S-CSCF, I-CSCF modules, etc.) may also include function-related components / modules, such as the Breakout Gateway Control Function (BGCF) module (118), the Media Gateway Control Function (MGCF) module (122), the Interconnect Border Control Function (IBCF) (116), and other components / modules. In one common implementation, the BGCF module (118) may enable routing of telephone call signaling to or from the most appropriate S-CSCF module (158). In this implementation, the BGCF module (118) may enable routing of telephone calls to the respective BTAS (102) for providing FMC services. Generally, the MGCF module (122) may be a SIP endpoint that can interface with a security gateway (SGW) (not shown in Figure 1B) and also control resources in the media gateway (MGW) (130). The IBCF module (116) may enable boundary control between various service provider networks, thus providing network security for BTAS-enabled IMS with respect to signaling information. The IMS server (106) may also include other existing components, such as components related to the Multimedia Resource Function (MRF) module (126). The MRF module (126), in conjunction with other IMS components, may be responsible for performing various processing tasks on media streams associated with specific services. Furthermore, as shown in Figure 1B, the BTAS-IMS-based implementation may be associated with a Point of Interconnection (POI) (134), which may be a physical interface between changing service provider or enterprise media gateways.

[0051] In one embodiment, the FMC service may depend on the service provider's core network. In an alternative embodiment, the core network may belong to the same service provider or to two or more service providers. The FMC service may operate on a single service provider network or on two or more service provider networks.

[0052] In one embodiment, Voice over Long-Term Evolution (VoLTE) subscribers may be served by a vendor TAS (160). Furthermore, the IMS network (106) and BTAS (102) may serve only fixed-line enterprise subscribers. Whenever the FMC function is activated, the FMC creation service data, FMC update service data, or FMC deletion service data application programming interface (API) operation is invoked by BTAS (102), it is assumed that the Independent System Operator (ISO) may enable the modification of the Initial Filter Criteria (IFC) in the Home Subscriber Server (HSS) 120 / CFX for VoLTE subscribers (i.e., this controls all services on an all-IP network and enables new subscriber services such as VoLTE, Voice over Wi-Fi (VoWiFi), Rich Communication Service (RCS), and Web Real-Time communications (WebRTC). For example, whenever BTAS(102) calls the FMC creation service data API, it is assumed that the ISO process call flow modifies the VoLTE subscriber IFC service chain data to ensure that BTAS(102) comes before TAS(160) in the originating and incoming IFC legs. In another example, whenever BTAS(102) calls the FMC update service data, it may be assumed that the ISO process call flow modifies the previously configured subscriber's VoLTE subscriber IFC service chain data to ensure that only TAS(160) comes in the newly configured subscriber's phone call routing to ensure that BTAS(102) is not involved in the originating and incoming IFC legs and that BTAS(102) comes before TAS(160) in the originating and incoming IFC legs.Furthermore, whenever BTAS(102) calls the FMC creation service data API, it can be assumed that the ISO process call flow modifies the VoLTE subscriber IFC service chain data to ensure that BTAS(102) precedes TAS(160) in the originating and incoming IFC legs. In addition, the VoLTE subscriber service profile may remain unchanged, and all auxiliary services may be handled solely by TAS(160).

[0053] For example, changes may be required from a network perspective, such as for HSS(120) and the Online Charging Server (OCS) (not shown in Figure 1B). For HSS(120), whenever an association between a fixed line and a VoLTE subscriber can be established using the BTAS API, the ISO may be required to modify the VoLTE subscriber IFC in HSS(120) in the originating and receiving legs, prioritizing BTAS (first priority) and TAS / Converge TAS (CTAS) (second priority). Furthermore, whenever an association between a fixed line and a VoLTE subscriber is removed using the BTAS API, the IFC may have to be modified for the VoLTE subscriber so that BTAS(102) cannot be involved in the VoLTE subscriber's phone call.

[0054] In OCS, billing for VoLTE subscribers may be handled by the VoLTE TAS. Furthermore, BTAS(102), when activated, can send billing triggers only to fixed lines (Mobile Originated (MO), Mobile Terminated (MT), proxy mode). By default, the Enterprise Centrex "Ro" trigger may be disabled.

[0055] The system (100) can facilitate Fixed Mobile Convergence (FMC) services through a combination of hardware and software implementations. Figure 2A, in relation to Figure 1A, shows an exemplary representation of a network device (102) / BTAS (102) according to one embodiment of the present disclosure. The system (100) includes a network device (102) or a BTAS (102) which may include one or more processors (202). The network device (102) or BTAS (102) may be integrated with an IMS server (106) to provide network services to a user device (110) (as shown in Figure 1A). In one embodiment, the network device (102) may include one or more processors (202) coupled with a memory (204). The memory (204) may store instructions that, when executed by one or more processors (202), cause the system (100) to perform steps such as those described herein. The network device (102) or BTAS (102) can cause the system (100) to receive routed requests through the IMS server (106 in Figure 1A).

[0056] One or more processors (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuits, and / or any device that processes data based on operational instructions. Among other capabilities, one or more processors (202) may be configured to fetch and execute computer-readable instructions stored in the memory (204) of the BTAS (102). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-temporary computer-readable storage medium, which may be fetched and executed to create or share data packets over network services. The memory (204) may comprise any non-temporary storage device, including, for example, volatile memory such as RAM, or non-volatile memory such as EPROM, flash memory, etc.

[0057] In one embodiment, BTAS(102) may include an interface (206). Interface (206) may provide interfaces for various types of interfaces, such as I / O devices, storage devices, and so on, for data input and output devices. Interface (206) may facilitate communication of BTAS(102). Interface (206) may also provide a communication path for one or more components of BTAS(102). Examples of such components, but not limited to, include a processing engine (208), a database (210), and a Centralized Data Layer (CDL) agent (230).

[0058] The processing engine (208) may be implemented as a combination of hardware and programming (e.g., programmable instructions) to implement one or more functions of the processing engine (208). In the examples described herein, such a combination of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine (208) may be processor-executable instructions stored in a non-temporary machine-readable storage medium, and the hardware for the processing engine (208) may comprise processing resources (e.g., one or more processors) for executing such instructions. In this example, the machine-readable storage medium may store instructions that implement the processing engine (208) when executed by the processing resources. In such an example, BTAS(102) may comprise a machine-readable storage medium for storing instructions or processing resources for executing instructions, or the machine-readable storage medium may be separate but accessible to both BTAS(102) and the processing resources. In other examples, the processing engine (208) may be implemented by electronic circuits.

[0059] The network device processing engine (208) may include one or more components (as shown in Figure 2A), including a session manager (SM) (212), an operations and maintenance (OAM) manager (214), a provisioning agent (216), a database manager (DM) (218), a troubleshooting manager (TM) (220), and other engines (222). The SM (212) may function as a core function distribution module responsible for processing telephone calls and executing service chain logic in the case of a BTAS (102). The SM (212) may further include one or more submodules, such as a telephone call initiation module (not shown) for initiating communication with multiple emergency services. The OAM manager (214) may be configured to manage the failure, configuration, and performance aspects of the BTAS / network device (102). The OAM manager (214) may provide an operations and maintenance contact point to the system (100) or BTAS (102). DM(218) may manage the database cluster, while BTAS(102) may store subscriber-specific service information. In one embodiment, service data modification requests that may be received by the provisioning agent(216) may be persistently stored using the DM manager(218). The provisioning agent(216) may be responsible for handling provisioning requests received from a centralized provisioning server for persistent changes to the database(210). The provisioning agent(216) may also ensure that various session managers(212) can be updated for any dynamic changes in service data. TM(220) may aggregate logs and debug information from all function managers for troubleshooting. TM(220) may also provide flexibility for generating debugging information, for example, on a per-module, per-process, and per-system basis. Various other functions of the components may be possible. In one embodiment, the database(210) may contain data that may be stored or generated as a result of functions implemented by any of the components of the processing engine(208) of BTAS(102).

[0060] In one embodiment, SM(212) may receive at least one of a contact number and a short code associated with a first user of a Central exchange (Centrex) group, which is dialed by a second user using at least one of a mobile device or a fixed-line device (i.e., a user device (110)). The contact number and short code may correspond to at least one of a mobile number and a fixed-line number associated with the first user of the Centrex group.

[0061] In one embodiment, SM(212) may establish a connection between BTAS(102) and an IMS core network(106) associated with an Internet Protocol Multimedia Subsystem (IMS) server(106) when a second user dials a mobile number and the fixed line is linked to the mobile number.

[0062] In one embodiment, once SM(212) establishes a connection between BTAS(102) and the IMS core network(106), SM(212) may execute BTAS(102) to call at least one of the Fixed Mobile Convergence (FMC) creation service and the FMC update service in order to trigger the modification of Initial Filter criteria (IFC) service chain data in the IMS core network(106).

[0063] In one embodiment, SM(212) may convert the abbreviation code to at least one of the relevant landline numbers and mobile numbers when a second user dials the abbreviation code.

[0064] In one embodiment, SM(212) may, in response to the conversion, send one or more invite request messages to the IMS core network(106) associated with the mobile number linked to the fixed line.

[0065] In one embodiment, SM(212) may activate ringing mode on the mobile device (110) and the fixed-line device (110) in response to a transmission to establish a telephone call. In one embodiment, activating ringing mode on the mobile device (110) and the fixed-line device (110) further includes at least one of the following: ringing the fixed-line device (110) and the mobile device (110) simultaneously, and ringing the fixed-line device (110) first and then ringing the mobile device (110) sequentially, based on a pre-configured parallel branching mode or sequential branching mode. In one embodiment, when ringing mode is activated on at least one of the fixed-line device (110) or the mobile device (110), the first user instead answers the telephone call on an alternate contact number by dialing a service code from the alternate contact number.

[0066] In one embodiment, SM(212) may periodically determine whether a telephone call is answered by a fixed-line device (110) or a mobile device (110).

[0067] In one embodiment, the SM(212) may disconnect the telephone call on the mobile device (110) or the fixed-line device (110) when the telephone call is answered on the mobile device (110) or the fixed-line device (110), respectively.

[0068] In one embodiment, when the SM(212) disconnects a telephone call on a mobile device (110) or a fixed-line device (110), it may establish a telephone call between at least one of the mobile devices (110) or fixed-line devices (110) associated with a second user and at least one of the fixed-line devices (110) or mobile devices (110) associated with a first user.

[0069] In one embodiment, a fixed-line device (110) associated with the first user displays a Calling Line Identification (CLI), and a mobile device (110) associated with the first user displays the mobile phone number of the second user. In another embodiment, a fixed-line device (110) associated with the second user displays a Calling Line Identification (CLI), and a mobile device (110) associated with the second user displays the abbreviated code of the first user.

[0070] In one embodiment, the FMC service is activated when a pin is input via Dual-Tone Multi-Frequency Tones (DTMF), the FMC service is deactivated when a pin is input via DTMF, and the FMC service is not removed during deactivation.

[0071] In one embodiment, when a shortened code corresponds to a fixed-line number, system 100 may perform BTAS(102) to convert the dialed shortened code to a fixed-line number using a virtual private branch exchange (VPBX) service. Furthermore, system (100) may perform BTAS(102) to cause the Online Charging System (OCS) (not shown in Figure 1A) to charge the second user using a Credit Control Request (CCR). The OCS returns a Credit Control Answer (CCA) corresponding to the CCR. In addition, system (100) may perform BTAS(102) to interact with a Serving Call Session Control Function (SCSCF) associated with the IMS core network (106). The SCSCF may apply Initial Filter Criteria (IFC) based on at least one of the first user's mobile number and fixed-line number. Furthermore, system (100) may perform BTAS(102) to determine the appropriate FMC service to be called for Fixed Mobile Convergence (FMC) data associated with at least one of the mobile and fixed-line numbers of the first user. Furthermore, system (100) may perform BTAS(102) to provide at least one of notification and ringtone to the second user. In addition, system (100) may perform BTAS(102) to route invite to the fixed-line number associated with the first user and to route invite request messages to the IMS core network(106) associated with the mobile number. Furthermore, system (100) may perform BTAS(102) to activate ringing mode on the mobile device(110) and the fixed-line device(110) in order to establish a telephone call. Furthermore, the system (100) may perform BTAS (102) to cause the OCS to update the billable number to at least one of the fixed-line number and the mobile number, respectively, based on the response of a telephone call by a first user on a fixed-line device (110) or a mobile device (110).In addition, when a telephone call is answered on a fixed-line device (110) or a mobile device (110), the system (100) may perform BTAS(102) to disconnect the telephone call on the mobile device (110) or the fixed-line device (110), respectively. Furthermore, once the system (100) has disconnected the telephone call on the mobile device (110) or the fixed-line device (110), it may perform BTAS(102) to establish a telephone call between the fixed-line device (110) associated with a second user and at least one of the fixed-line devices (110) or mobile devices (110) associated with a first user.

[0072] In one embodiment, responding to a telephone call further includes responding to a telephone call from a mobile number associated with a third user when the telephone call is established on a fixed-line number associated with a second user. System 100 may execute BTAS(102) to establish a telephone call between the first user and the third user once the third user has inserted the telephone call details and routing details into the Centralized Data Layer (CDL) server (104). Furthermore, System (100) may execute BTAS(102) to fetch the telephone call details and routing details from the CDL server (104) by the BTAS associated with the second user. Furthermore, System (100) may execute BTAS(102) to establish a telephone call between the first user and the second user.

[0073] Figure 2B shows an exemplary flowchart representation of an integrated architecture (250) of a network device or BTAS(102) according to embodiments of the present disclosure. As shown in Figure 2B, the BTAS(102) may be integrated or coupled with various hardware / software components or servers to enable one or more functions relating to FMC services. The BTAS(102) may be integrated with an IMS server (106) to enable communication processing relating to user devices within an enterprise (154), as shown in Figure 1B. In one exemplary embodiment, the BTAS(102) may be integrated with the IMS server (106) to establish and control communication connections via network protocols, including, but not limited to, a Session Initiation Protocol (SIP). Since communication may also involve the use of one or more forms of media, the BTAS(102) may be integrated with a Multimedia Resource Function (MRF)(126). BTAS(102) may interface with an Enterprise Provisioning Server (EPS)(260) via the Representational State Transfer (REST) ​​protocol to enable the provisioning of service data.

[0074] In one exemplary embodiment, BTAS(102) may be integrated with MRF(126) to enable functions such as media mixing, notification control, and other such purposes via a network protocol including, for example, Session Initiation Protocol Media Server Markup Language (SIP-MSML), but not limited to such protocols. In one exemplary embodiment, BTAS(102) may be integrated or coupled with other components / services such as Mobile Number Portability (MNP)(124) (via SIP) to enable number portability dipping. In another exemplary embodiment, BTAS(102) and EPS(260) may be integrated or coupled independently with Element Management System (EMS)(256) via the REST protocol. EMS(256) may include hardware and software implementations for exchanging messages relating to five critical aspects, namely Fault, Configuration, Accounting, Performance, and Security (FCAPS) functions, via the representational state transfer (REST) ​​protocol, which may use the Hypertext Transfer Protocol (HTTP) to transport messages. EMS can provide a foundation for implementing Operations Support System (OSS) or Business Support Systems (BSS)(262) based architectures, enabling service providers to meet customer demands for faster service deployments, for example, to provide satisfactory quality service requirements and other such services. EMS(256) may interface with OSS / BSS(262) via the REST protocol to enable a northbound interface for FCAPS data in BTAS(102) or EPS(260).The term northbound interface may refer to an interface that allows a specific component of a network to communicate with a higher-level component. OSS / BSS(262) may interface with EPS(260) via the REST protocol to enable functions such as service data management requests.

[0075] Furthermore, as shown in Figure 2B, BTAS(102) may be integrated or coupled with a Diameter Routing Agent (DRA)(268) via the diameter protocol, which may be a standard protocol for authentication, authorization, and billing information in IMS server-based networks. The DRA diameter may be a functional element that can provide real-time routing capabilities to ensure that messages are routed between the correct elements in the network. Integration of BTAS(102) with DRA(268) may enable integration with an Online Charging System (OCS)(272) to facilitate "Ro" billing. OCS(272) may be a system that enables a service provider to bill users or customers in real time based on service usage, and "Ro" billing relates to a protocol that enables triggers for generating billing events. In one embodiment, BTAS(102) may also be integrated with a component relating to Customized Caller Ring Back Tone (CRBT)(266) to enable personalized Ring Back Tone (RBT) at the stage of establishing communication. For example, this could primarily relate to a ringtone that may be played while a user device (252) is connected to telephone call communications with multiple emergency services.

[0076] Figures 3A to 3C show exemplary sequence diagram representations of a parallel telephone call branching flow according to one embodiment of the present disclosure.

[0077] As shown in Figures 3A to 3C, the originating network may include B-TAS(102), and the incoming network may include SCSCF(158), BTAS(102), MRF(126), MNP(124), and TAS(160). Furthermore, OCS(272) for billing telephone calls may be included.

[0078] In step (302-1), the dialed abbreviation is converted to a fixed-line number by BTAS(102) using the Virtual PBX (VPBX) service. In step (302-2), BTAS(102) may trigger a charge to OCS(272) using a Credit-Control-Request (CCR), and OCS(272) may return a Credit-Control-Answer (CCA) to BTAS(102). In step (302-3), BTAS(102) may interact with SCSCF on the originating network.

[0079] In step (302-4), SCSCF(158) may apply Initial Filter Criteria (IFC) based on the incoming number. In step (302-5), BTAS(102) may check the FMS service for FMC data for this number and extract the algorithm to be applied and the fixed and mobile numbers of the FMC.

[0080] In step (302-6), a notification is played on the recipient. In step (302-7), BTAS (102) may initiate a charge to OCS (272). In step (302-8), the invite may be routed to the recipient (fixed-line number). In step (302-9), the INVITE message is sent to the recipient's mobile network.

[0081] In step (302-10), both the mobile device (110) and the fixed-line device (110) are made to ring. In step (302-11), the telephone call is answered by the receiving end, for example, the fixed line. In step (302-12), a billable update for the fixed line is triggered to the OCS (272). In step (302-13), when the telephone call is answered on the fixed line, the telephone call to the receiving mobile network is disconnected. In step (302-14), a telephone call is established between the caller and the fixed line, and the mobile line is disconnected. Other steps in the sequence diagram may be common call flows known to those skilled in the art.

[0082] Figure 4 shows an exemplary sequence diagram representation of a call flow for seamless call pickup according to one embodiment of the present disclosure.

[0083] Consider a scenario in which a telephone call may be answered from a mobile number (C-party) (406) associated with a fixed line (B-party) (412). In step (422-1), C-party (406) inserts the telephone call details and routing details into the CDL server (104), so that a telephone call can be established between A party (ORIG (402)) and C party (406). In step (422-2), B-BTAS (410) of B party (412) fetches the telephone call details and routing details from the CDL server (104). In step (422-3), a telephone call is established between A party (402) and B party (412). Other steps in the sequence diagram may be typical call flows known to those skilled in the art.

[0084] Figure 5 shows an exemplary sequence diagram representation of a call flow (activation / deactivation) of an FMC service according to one embodiment of the present disclosure.

[0085] Activation from a Centrex user provisioning the FMC involves, for example, dialing "*333". In step (512-1), MRF(126) may prompt the user to enter a four-digit PIN via Dual-Tone Multi-Frequency (DTMF) tones. Only after the correct PIN is entered can the service be activated. Deactivation from a Centrex user provisioning the FMC involves dialing "#333". This may prompt the user to provide a four-digit PIN via DTMF tones. Only after the correct PIN is entered in step (512-1) can the service be deactivated. The FMC service may not be removed, but may be deactivated until activated by the user. Only activation / deactivation may be enabled using facility codes. Provisioning of the FMC service may be performed only via EPS(260). Other steps in the sequence diagram may be common call flows known to those skilled in the art.

[0086] Figure 6 shows an exemplary flowchart of a method (600) of providing a Fixed Mobile Convergence (FMC) service according to one embodiment of the present disclosure.

[0087] In block (602), the method (600) may include the step of receiving, by a processor (202) associated with a Business Telephony Application Server (BTAS) (102), at least one of a contact number and a short code associated with a first user of a Central exchange (Centrex) group, based on performing SM(212), which is dialed by a second user using at least one of a mobile device or a fixed-line device (i.e., a user device (110)). The contact number and short code may correspond to at least one of a mobile number and a fixed-line number associated with the first user of the Centrex group.

[0088] In block (604), method (600) may include the step of establishing a connection between BTAS (102) and an IMS core network (106) associated with an Internet Protocol Multimedia Subsystem (IMS) server (106) by a processor (202) running SM (212) when a second user dials a mobile number and a fixed line is associated with the mobile number.

[0089] In block (606), method (600) may include the step of having a processor (202) running SM (212) establish a connection between BTAS (102) and the IMS core network (106), and then calling at least one of the Fixed Mobile Convergence (FMC) creation service and the FMC update service to trigger a modification of Initial Filter criteria (IFC) service chain data in the IMS core network (106).

[0090] In block (608), method (600) may include the step of having a processor (202) performing SM(212) convert the abbreviation code to at least one of the relevant landline numbers and mobile numbers when a second user dials the abbreviation code. The function performed in step 608 may be similar to the functions performed in steps 302-1, 302-3, 302-5, and 302-6 in Figure 3A.

[0091] In block (610), the method (600) may include the step of having a processor (202) performing SM (212) send one or more invite request messages to an IMS core network (106) associated with a mobile number linked to a fixed line in response to a translation. The function performed in step 610 may be similar to the functions performed in steps 302-8, 302-9, 302-10, and 302-11 in Figure 3B.

[0092] In block (612), the method (600) may include the step of having a processor (202) performing SM (212) activate a ringing mode on the mobile device (110) and the fixed-line device (110) in order to establish a telephone call in response to a transmission.

[0093] In block (614), the method (600) may include the step of having a processor (202) performing SM (212) establish a telephone call between at least one mobile device (110) or fixed-line device (110) associated with a second user and at least one fixed-line device (110) or mobile device (110) associated with a first user.

[0094] Figure 7 shows an exemplary computer system (700) in which embodiments of the present invention may be used, or in part, according to embodiments of the present disclosure.

[0095] As shown in Figure 7, the computer system (700) may include an external storage device (710), a bus (720), main memory (730), read-only memory (740), a mass storage device (750), a communication port (760), and a processor (770). Those skilled in the art will understand that the computer system may include one or more processors and communication ports. The processor (770) may include various modules relevant to embodiments of the present invention. The communication port (760) may be an RS-232 port for use with a modem-based dial-up connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or any other existing or future port. The communication port (760) may be selected depending on the network, such as a local area network (LAN), a wide area network (WAN), or any network to which the computer system is connected. The memory (730) may be random access memory (RAM) or any other dynamic storage device commonly known in the art. Read-only memory (740) may be any static storage device, for example, a programmable read-only memory (PROM) chip for storing static information, such as startup or BIOS instructions for a processor (770). Mass storage (750) may be any current or future mass storage method that may be used to store information and / or instructions.Exemplary mass storage methods include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (with internal or external, for example, Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, and Redundant Array of Independent Disks (RAID) storage, such as an array of disks (for example, a SATA array).

[0096] The bus (720) connects the processor (770) to other memory, storage, and communication blocks in a communicative manner. The bus (720) may be, for example, a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), USB, etc., for connecting expansion cards, drives, and other subsystems, as well as other buses such as a front side bus (FSB) that connects the processor (770) to a software system.

[0097] Optionally, operator and management interfaces, such as a display, keyboard, and cursor control device, may also be coupled to the bus (720) to facilitate direct interaction between the computer system and the operator. Other operator and management interfaces may be provided through network connections connected via a communication port (760). The components described above are intended to illustrate various possibilities only. The exemplary computer system described above should not be used to limit the scope of this disclosure.

[0098] While preferred embodiments are given considerable emphasis in this specification, it will be understood that many embodiments can be made without departing from the principles of the present invention, and many modifications can be made in preferred embodiments. These and other modifications in preferred embodiments of the present invention will be obvious to those skilled in the art from the disclosure herein, and it should be clearly understood that the foregoing description is implemented only as an example of the present invention and not as an limitation.

[0099] Benefits of this disclosure This disclosure provides a system and method for providing Fixed Mobile Convergence (FMC) services using the Business Telephony Application Server (BTAS) associated with the Central exchange (Centrex) group.

[0100] This disclosure provides a system and method for converting abbreviated codes into associated landline numbers to cause telephones to ring on both mobile and landline lines.

[0101] This disclosure determines whether a telephone call is answered on a landline or a mobile phone, and then, when the telephone call is answered on a landline or a mobile phone, disconnects the mobile phone or landline telephone call, respectively.

[0102] This disclosure enables speed dialing from mobile phones in addition to landlines for enterprise users on the Cloud Internet Protocol (IP) Central Exchange (Centrex).

[0103] This disclosure provides a single extension / number for a user to receive incoming calls on both devices (i.e., mobile and landline).

[0104] This disclosure enables user experiences including dialing from mobile phones, dialing from landlines, telephone calls from external corporate users to landlines, and seamless call pickup from associated landlines or mobile phones.

[0105] This disclosure enables seamless call pickup, in which telephone calls are answered from a mobile number (e.g., C-party) associated with each fixed line (e.g., B-party).

[0106] Reservation of rights The disclosures in this patent document include, but are not limited to, materials subject to intellectual property rights, such as copyrights, designs, trademarks, IC layout designs, and / or trade dress protections, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred to as the Owner). The Owner does not object to any reproduction of the patent document or patent disclosure as appearing in patent applications or records with the Patent and Trademark Office, but otherwise reserves all rights. All rights to such intellectual property are fully reserved by the Owner. [Explanation of symbols]

[0107] 102 Network devices, BTAS, B-TAS 104 CDL Server 106 IMS Servers, IMS Core Network, IMS Network 110 User devices, user equipment, UE, terminals, communication networks, mobile devices, fixed-line devices 112 Communication Networks 116 IBCF, IBCF module 118 BGCF, BGCF module 120 HSS 122 MGCF, MGCF module 124 MNP 126 MRF, MRF module 130 MGW 132 BGW 134 POI 152 P-CSCF, P-CSCF module 154 companies 156 E-SBC 158 S-CSCF, S-CSCF module 160 TAS 162 I-CSCF, I-CSCF module 202 processors 204 memory 206 Interfaces 208 Processing Engines 210 Databases 212 Session Manager, SM 214 Operations and Maintenance (OAM) Manager, OAM Manager 216 Provisioning Agents 218 Database Manager, DM, DM Manager 220 Troubleshooting Manager, TM 222 Other engines 230 CDL Agents 252 User Devices 256 EMS 260 EPS 262 OSS / BSS 264 F5 266 CRBT 268 DRA 272 OCS 402 ORIG 404 C-BTAS 406 C-PARTY, mobile phone number (C-party) 408 B-TAS 410 B-BTAS 412 B-PARTY, fixed line (B-party) 502 UE-A 504 ORIG AS 506 DB 700 Computer Systems 710 External storage devices 720 Bus 730 Main memory, memory 740 Read-only memory 750 Mass Storage Devices, Mass Storage 760 communication ports 770 processor

Claims

1. A system (100) for providing Fixed Mobile Convergence (FMC) services, The system includes a Business Telephony Application Server (BTAS) (102), and the BTAS (102) is configured as follows: Processor (202), The system comprises a memory (204) coupled to the processor (202), and when the memory (204) is executed, the processor (202) receives the following information: A second user dials at least one of a contact number and a short code associated with a first user of a Central exchange (Centrex) group using at least one of a mobile device (110) or a fixed-line device (110), wherein the contact number and the short code correspond to at least one of a mobile number and a fixed-line number associated with the first user of the Centrex group. When the second user dials the mobile number and the fixed line is linked to the mobile number, a connection is established between the BTAS (102) and the IMS core network (106) associated with the Internet Protocol Multimedia Subsystem (100) (IMS) server (106). Once the connection between the BTAS (102) and the IMS core network (106) is established, the IMS core network (106) will call at least one of the Fixed Mobile Convergence (FMC) creation service and the FMC update service in order to trigger the modification of the Initial Filter criteria (IFC) service chain data. When the second user dials the abbreviation code, the abbreviation code is converted to at least one of the relevant landline numbers and mobile numbers. In response to the conversion, one or more invite request messages are sent to the IMS core network (106) associated with the mobile number linked to the fixed line. In response to the aforementioned transmission, the mobile device (110) and the fixed-line device (110) are activated in ringing mode in order to establish a telephone call. Each establishes the telephone call between at least one of the mobile device (110) or fixed-line device (110) associated with the second user and at least one of the fixed-line device (110) or mobile device (110) associated with the first user. A system (100) equipped with processor-executable instructions.

2. The processor (202) further periodically determines whether the telephone call is answered by the first user on the fixed line device (110) or on the mobile device (110), The system (100) according to claim 1, wherein when the telephone call is answered on a fixed-line device (110) or the mobile device (110), the mobile device (110) or the fixed-line device (110) associated with the first user is configured to disconnect the telephone call, and the telephone call is established when the mobile device (110) or the fixed-line device (110) disconnects the telephone call, respectively.

3. When the abbreviated code corresponds to the fixed line number, the processor (202) further: Using the Virtual Branch Exchange (VPBX) service, the dialed abbreviation is converted to the fixed line number. The Online Charging System (OCS) (272) is instructed to charge the second user using a Credit Control Request (CCR), and the OCS (272) returns a Credit Control Answer (CCA) corresponding to the CCR. The Serving Call Session Control Function (SCSCF) associated with the IMS core network (106) interacts with the SCSCF, which applies the Initial Filter Criteria (IFC) based on at least one of the first user's mobile number and landline number. Determine the appropriate FMC service to be called for Fixed Mobile Convergence (FMC) data associated with at least one of the first user's mobile number and landline number, Provide the second user with at least one of the notification and ringtones, The invite is routed to the fixed line number associated with the first user, and the invite request message is routed to the IMS core network (106) associated with the mobile number. In order to establish the aforementioned telephone call, the ringing mode is activated on the mobile device (110) and the fixed-line device (110), The system (100) according to claim 1, wherein, based on the response of the telephone call by the first user on the fixed line device (110) or the mobile device (110), the OCS (272) is configured to update the billable item to at least one of the fixed line number and the mobile number, and based on the response of the telephone call, the telephone call is established between the fixed line device (110) associated with the second user and at least one of the fixed line device (110) or the mobile device (110) associated with the first user.

4. The response to the aforementioned telephone call further includes an event in which the response to the telephone call is made from the mobile number associated with a third user when the telephone call is established on the fixed line number associated with a second user, and the processor (202) further, When the third user inserts the details of the telephone call and routing details into the Centralized Data Layer (CDL) server (104), the telephone call is established between the first user and the third user. The BTAS(102) associated with the second user fetches the details of the telephone call and routing details from the CDL server(104), The system (100) according to claim 1, configured to establish the telephone call between the first user and the second user.

5. The system (100) according to claim 1, wherein activating the ringing mode on the mobile device (110) and the fixed-line device (110) further comprises at least one of the following: ringing the fixed-line device (110) and the mobile device (110) simultaneously based on a pre-configured parallel branching mode or sequential branching mode; and ringing the fixed-line device (110) first and then ringing the mobile device (110) sequentially.

6. The system (100) according to claim 1, wherein the fixed line device (110) associated with the first user displays a Calling Line Identification (CLI), and the mobile device (110) associated with the first user displays the mobile phone number of the second user.

7. The system (100) according to claim 1, wherein the fixed line device (110) associated with the second user displays a Calling Line Identification (CLI), and the mobile device (110) associated with the second user displays the abbreviated code of the first user.

8. The system (100) according to claim 1, wherein when the ringing mode is activated on at least one of the fixed line device (110) and the mobile device (110), the first user answers the telephone call on the alternative contact number by dialing the service code from the alternative contact number instead.

9. The system (100) according to claim 1, wherein the FMC service is activated when a pin is input via Dual-Tone Multi-Frequency Tones (DTMF), the FMC service is deactivated when a pin is input via DTMF, and the FMC service is not deleted while deactivated.

10. A method for providing Fixed Mobile Convergence (FMC) services, A step of receiving at least one of a contact number and a short code associated with a first user of a Central exchange (Centrex) group, which is dialed by a second user using at least one of a mobile device (110) or a fixed-line device (110) by a processor (202) associated with a Business Telephony Application Server (BTAS) (102) in a system (100), wherein the contact number and the short code correspond to at least one of a mobile number and a fixed-line number associated with the first user of the Centrex group, When the second user dials the mobile number and the fixed line is linked to the mobile number, the processor (202) establishes a connection between the BTAS (102) and the IMS core network (106) associated with the Internet Protocol Multimedia Subsystem (100) (IMS) server (106), When the processor (202) establishes the connection between the BTAS (102) and the IMS core network (106), the IMS core network (106) calls at least one of the Fixed Mobile Convergence (FMC) creation service and the FMC update service to trigger the modification of Initial Filter criteria (IFC) service chain data. The processor (202) performs the steps of converting the abbreviation code to at least one of the relevant landline numbers and mobile numbers when the second user dials the abbreviation code, In response to the conversion, the processor (202) sends one or more invite request messages to the IMS core network (106) associated with the mobile number linked to the fixed line. In response to the transmission, the processor (202) activates ringing mode on the mobile device (110) and the fixed-line device (110) to establish a telephone call; A method comprising the step of establishing the telephone call between at least one of the mobile device (110) or fixed-line device (110) associated with the second user and at least one of the fixed-line device (110) or mobile device (110) associated with the first user, using the processor (202).

11. The processor (202) periodically determines whether the telephone call is answered by the first user on the fixed line device (110) or on the mobile device (110), The method according to claim 10, further comprising the step of the processor (202) disconnecting the telephone call on the mobile device (110) or the fixed-line device (110) associated with the first user, when the telephone call is answered on the fixed-line device (110) or the mobile device (110), respectively, wherein the telephone call is established when the telephone call is disconnected on the mobile device (110) or the fixed-line device (110), respectively.

12. When the aforementioned abbreviated code corresponds to the aforementioned fixed line number, the method is The processor (202) performs the steps of converting the dialed abbreviation code to the fixed line number using the virtual private branch exchange (VPBX) service, The steps include: causing the processor (202) to charge the second user using a Credit Control Request (CCR) in the Online Charging System (OCS) (272), wherein the OCS (272) returns a Credit Control Answer (CCA) corresponding to the CCR; The steps include: the processor (202) interacting with a Serving Call Session Control Function (SCSCF) associated with the IMS core network (106), wherein the SCSCF applies the Initial Filter Criteria (IFC) based on at least one of the first user's mobile number and landline number; The processor (202) determines an appropriate FMC service to be called for Fixed Mobile Convergence (FMC) data associated with at least one of the first user's mobile number and landline number, The processor (202) provides the second user with at least one of a notification and a ringtone, The processor (202) routes the invite to the fixed line number associated with the first user and routes the invite request message to the IMS core network (106) associated with the mobile number. The processor (202) performs the steps of activating ringing mode on the mobile device (110) and the fixed-line device (110) in order to establish the telephone call, The method according to claim 10, further comprising the step of causing the processor (202) to update the billable item to the OCS (272) as at least one of the fixed line number and the mobile number, based on the response of the telephone call by the first user on the fixed line device (110) or the mobile device (110), wherein the telephone call is established between the fixed line device (110) associated with the second user and at least one of the fixed line device (110) or the mobile device (110) associated with the first user, based on the response of the telephone call.

13. The step of responding to the telephone call further includes an event in which, when the telephone call is established on the fixed line number associated with the second user, the telephone call is responded to from the mobile number associated with the third user, and the method further, The processor (202) inserts the details of the telephone call and routing details by the third user into the Centralized Data Layer (CDL) server (104), and the steps include establishing the telephone call between the first user and the third user, The processor (202) fetches the details of the telephone call and routing details from the CDL server (104) via the BTAS (102) associated with the second user, The method according to claim 10, further comprising the step of establishing the telephone call between the first user and the second user using the processor (202).

14. The method according to claim 10, wherein the step of activating the ringing mode on the mobile device (110) and the fixed line device (110) further comprises at least one of the following steps: ringing the fixed line device (110) and the mobile device (110) simultaneously based on a pre-configured parallel branching mode or sequential branching mode; and ringing the fixed line device (110) first and then ringing the mobile device (110) sequentially.

15. The method according to claim 10, wherein the fixed line device (110) associated with the first user displays a Calling Line Identification (CLI), and the mobile device (110) associated with the first user displays the mobile phone number of the second user.

16. The method according to claim 10, wherein the fixed line device (110) associated with the second user displays a Calling Line Identification (CLI), and the mobile device (110) associated with the second user displays the abbreviated code of the first user.

17. The method according to claim 10, wherein when the ringing mode is activated on at least one of the fixed line device (110) or the mobile device (110), the first user answers the telephone call on the alternative contact number by dialing the service code from the alternative contact number instead.

18. The method according to claim 10, wherein the FMC service is activated when a pin is input via Dual-Tone Multi-Frequency Tones (DTMF), the FMC service is deactivated when a pin is input via DTMF, and the FMC service is not deleted during deactivation.

19. User equipment (UE) for providing Fixed Mobile Convergence (FMC) services, Processor and The system comprises a memory coupled to the processor, and when the memory is executed, the processor, Using at least one of the user devices, a second user dials at least one of a contact number and a short code associated with a first user in a Central exchange (Centrex) group, wherein the contact number and the short code correspond to at least one of a mobile number and a landline number associated with the first user. To establish a telephone call between the user equipment associated with the second user and the user equipment associated with the first user, A UE (Unified Engineer) equipped with processor-executable instructions.

20. A non-temporary computer-readable medium having machine-readable instructions, wherein the machine-readable instructions are The system receives at least one of a contact number and a short code associated with a first user of a Central exchange (Centrex) group, which is dialed by a second user using at least one of a mobile device (110) or a fixed-line device (110), and the contact number and the short code correspond to at least one of a mobile number and a fixed-line number associated with the first user of the Centrex group. When the second user dials the mobile number and the landline is linked to the mobile number, a connection is established between the Business Telephony Application Server (BTAS) (102) and the IMS core network (106) associated with the Internet Protocol Multimedia Subsystem (100) (IMS) server (106). When the connection between the BTAS (102) and the IMS core network (106) is established, the IMS core network (106) invokes at least one of the Fixed Mobile Convergence (FMC) creation service and the FMC update service in order to trigger the modification of the Initial Filter criteria (IFC) service chain data. When the second user dials the abbreviation code, the abbreviation code is converted to at least one of the relevant landline numbers and mobile numbers. In response to the conversion, one or more invite request messages are sent to the IMS core network (106) associated with the mobile number linked to the fixed line. In response to the aforementioned transmission, the mobile device (110) and the fixed-line device (110) activate ringing mode in order to establish a telephone call. Each establishes the telephone call between at least one of the mobile device (110) or fixed-line device (110) associated with the second user and at least one of the fixed-line device (110) or mobile device (110) associated with the first user. A non-temporary, computer-readable medium that can be executed by a processor.

Images