Patent Application
20240381464
The present disclosure is part of a non-provisional application claiming the priority benefit of Indian patent application No. 202321033500, filed 12 May 2023, the content of which herein being incorporated by reference in its entirety.
The present disclosure is generally related to mobile communications and, more particularly, to enhancement of normal call domain conflict resolution during a call to an emergency call center (ECC).
In wireless communications such as mobile communications under the current 3rd Generation Partnership Project (3GPP) specification, a normal call which is on a HOLD state due to a user attempting to make an emergency call may become disconnected due to domain conflict when the emergency call fails on the Internet Protocol (IP) Multimedia Subsystem (IMS) domain with New Radio (NR) as the radio access technology (RAT). This is because the emergency call needs to be redialed on Long-Term Evolution (LTE) as the RAT based on a next-RAT preference. As a result, the user experience is negatively impacted as the user would need to redial and reconnect in order to resume the normal call. Therefore, there is a need for a solution of enhancement of normal call domain conflict resolution during a call to an ECC.
The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce concepts, highlights, benefits, and advantages of the novel and non-obvious techniques described herein. Select implementations are further described below in the detailed description. Thus, the following summary is not intended to identify essential features of the claimed subject matter, nor is it intended for use in determining the scope of the claimed subject matter.
An objective of the present disclosure is to propose solutions or schemes that address the issue(s) described herein. More specifically, various schemes proposed in the present disclosure are believed to provide solutions pertaining to enhancement of normal call domain conflict resolution during a call to an ECC.
In one aspect, a method may involve, after a first call having been established between a user equipment (UE) and a wireless network on a domain via a first RAT, attempting to establish a second call between the UE and the wireless network via the first RAT. The method may also involve establishing the second call via a second RAT different than the first RAT responsive to a failure in attempting to establish the second call via the first RAT. In establishing the second call via the second RAT, the method may involve transferring the first call on the domain to the second RAT along with establishing of the second call via the second RAT.
In one aspect, a method may involve establishing a first call having between a UE and a wireless network on an IMS domain via a NR RAT. The method may also involve attempting to establish a second call between the UE and the wireless network via the NR RAT. The method may further involve establishing the second call via an LTE RAT responsive to a failure in attempting to establish the second call via the NR RAT. In establishing the second call, the method may involve transferring the first call on the IMS domain to the LTE RAT along with establishing of the second call via the LTE RAT.
In yet another aspect, an apparatus implementable in a UE may include a transceiver configured to communicate wirelessly and a processor coupled to the transceiver. The processor may, after a first call having been established between the UE and a wireless network on a domain via a first RAT, attempt to establish a second call between the UE and the wireless network via the first RAT. The processor may also establish the second call via a second RAT different than the first RAT responsive to a failure in attempting to establish the second call via the first RAT. In establishing the second call via the second RAT, the processor may transfer the first call on the domain to the second RAT along with establishing of the second call via the second RAT.
It is noteworthy that, although the description provided herein may be in the context of certain radio access technologies, networks, and network topologies such as 5th Generation (5G)/NR/Beyond Fifth-Generation (B5G) mobile communications, the proposed concepts, schemes and any variation(s)/derivative(s) thereof may be implemented in, for and by other types of radio access technologies, networks and network topologies such as, for example and without limitation, 4th Generation (4G)/LTE, LTE-Advanced, LTE-Advanced Pro, Internet-of-Things (IoT), Narrow Band Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), vehicle-to-everything (V2X), and non-terrestrial network (NTN) communications. Thus, the scope of the present disclosure is not limited to the examples described herein.
The accompanying drawings are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of the present disclosure. The drawings illustrate implementations of the disclosure and, together with the description, serve to explain the principles of the disclosure. It is appreciable that the drawings are not necessarily in scale as some components may be shown to be out of proportion than the size in actual implementation in order to clearly illustrate the concept of the present disclosure.
Detailed embodiments and implementations of the claimed subject matters are disclosed herein. However, it shall be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matters which may be embodied in various forms. The present disclosure may, however, be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided so that description of the present disclosure is thorough and complete and will fully convey the scope of the present disclosure to those skilled in the art. In the description below, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.
Implementations in accordance with the present disclosure relate to various techniques, methods, schemes and/or solutions pertaining to enhancement of normal call domain conflict resolution during a call to an ECC. According to the present disclosure, a number of possible solutions may be implemented separately or jointly. That is, although these possible solutions may be described below separately, two or more of these possible solutions may be implemented in one combination or another.
Referring to
It is noteworthy that, while the various proposed schemes may be individually or separately described below, in actual implementations some or all of the proposed schemes may be utilized or otherwise implemented jointly. Of course, each of the proposed schemes may be utilized or otherwise implemented individually or separately. Moreover, as used herein, a lower layer may refer to a layer in the 5th Generation Mobility Management (5GMM) protocol stack that is lower than the radio resource control (RRC) layer, such as a packet data convergence protocol (PDCP) layer, a radio control link (RLC) layer, a medium access control (MAC) layer, a physical (PHY) layer, or so forth.
Part (B) of
In view of the above, a general description of a proposed scheme in accordance with the present disclosure is provided below. Initially, a UE (e.g., UE 110) may be registered on a first domain (e.g., 5G domain) and a user of the UE dialed a normal call which is successful on a given domain (e.g., IMS domain) with NR being the RAT. Then, the user may dial an emergency call, which placed the normal call on HOLD, and the IMS domain with a first RAT (e.g., NR) may be selected for the emergency call to an ECC. However, the emergency call may need to be retried on the IMS domain with a second RAT (e.g., LTE) after the emergency call failed on the first RAT. Under the proposed scheme, a normal scan may be triggered and performed on the second RAT even though the normal call is on HOLD. Based on the scan result being success or failure, a next action may be taken. For instance, in case that the scan result is success, the emergency call may be attempted on the IMS domain with the second RAT and the domain of normal call may be changed from the first domain to the second domain (e.g., LTE domain) internally in the UE. The emergency call may be successfully rendered in the second domain and then disconnected successfully. Then, the normal call may be placed in an UNHOLD state on the second domain for the call to continue until the user ends the call.
Without implementation of the proposed scheme, the normal call would be disconnected due to domain conflict. In contrast, by implementing the proposed scheme, the domain of the normal call may be changed internally along with the emergency call, instead of being disconnected. Advantageously, the issue of call drop/disconnection of the normal call due to domain conflict may be avoided or otherwise alleviated. It is noteworthy that, although examples provided here may be in the context of certain domains (e.g., 5G/NR and 4G/LTE) and certain RATs (e.g., NR and LTE), implementations or the proposed schemes are not limited thereto. That is, the proposed schemes may be implemented in scenarios where domains/RATs are different from those illustrated in the examples. Moreover, although examples provided herein may be in the context of a normal call being placed on HOLD while an emergency call is being attempted, the proposed schemes may be implemented in scenarios where a different type of call (having a first priority level) is placed on HOLD while yet another type of call (having a second priority level higher than the first priority level) is being attempted.
Each of apparatus 310 and apparatus 320 may be a part of an electronic apparatus, which may be a network apparatus or a UE (e.g., UE 110), such as a portable or mobile apparatus, a wearable apparatus, a vehicular device or a vehicle, a wireless communication apparatus or a computing apparatus. For instance, each of apparatus 310 and apparatus 320 may be implemented in a smartphone, a smart watch, a personal digital assistant, an electronic control unit (ECU) in a vehicle, a digital camera, or a computing equipment such as a tablet computer, a laptop computer or a notebook computer. Each of apparatus 310 and apparatus 320 may also be a part of a machine type apparatus, which may be an IoT apparatus such as an immobile or a stationary apparatus, a home apparatus, a roadside unit (RSU), a wire communication apparatus or a computing apparatus. For instance, each of apparatus 310 and apparatus 320 may be implemented in a smart thermostat, a smart fridge, a smart door lock, a wireless speaker or a home control center. When implemented in or as a network apparatus, apparatus 310 and/or apparatus 320 may be implemented in an eNodeB in an LTE, LTE-Advanced or LTE-Advanced Pro network or in a gNB or TRP in a 5G network, an NR network, or an IoT network.
In some implementations, each of apparatus 310 and apparatus 320 may be implemented in the form of one or more integrated-circuit (IC) chips such as, for example and without limitation, one or more single-core processors, one or more multi-core processors, one or more complex-instruction-set-computing (CISC) processors, or one or more reduced-instruction-set-computing (RISC) processors. In the various schemes described above, each of apparatus 310 and apparatus 320 may be implemented in or as a network apparatus or a UE. Each of apparatus 310 and apparatus 320 may include at least some of those components shown in
In one aspect, each of processor 312 and processor 322 may be implemented in the form of one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, even though a singular term “a processor” is used herein to refer to processor 312 and processor 322, each of processor 312 and processor 322 may include multiple processors in some implementations and a single processor in other implementations in accordance with the present disclosure. In another aspect, each of processor 312 and processor 322 may be implemented in the form of hardware (and, optionally, firmware) with electronic components including, for example and without limitation, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors and/or one or more varactors that are configured and arranged to achieve specific purposes in accordance with the present disclosure. In other words, in at least some implementations, each of processor 312 and processor 322 is a special-purpose machine specifically designed, arranged, and configured to perform specific tasks including those pertaining to UE behavior for enhancement of normal call domain conflict resolution during a call to an ECC in accordance with various implementations of the present disclosure.
In some implementations, apparatus 310 may also include a transceiver 316 coupled to processor 312. Transceiver 316 may be capable of wirelessly transmitting and receiving data. In some implementations, transceiver 316 may be capable of wirelessly communicating with different types of wireless networks of different radio access technologies (RATs). In some implementations, transceiver 316 may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, transceiver 316 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communications. In some implementations, apparatus 320 may also include a transceiver 326 coupled to processor 322. Transceiver 326 may include a transceiver capable of wirelessly transmitting and receiving data. In some implementations, transceiver 326 may be capable of wirelessly communicating with different types of UEs/wireless networks of different RATs. In some implementations, transceiver 326 may be equipped with a plurality of antenna ports (not shown) such as, for example, four antenna ports. That is, transceiver 326 may be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communications.
In some implementations, apparatus 310 may further include a memory 314 coupled to processor 312 and capable of being accessed by processor 312 and storing data therein. In some implementations, apparatus 320 may further include a memory 324 coupled to processor 322 and capable of being accessed by processor 322 and storing data therein. Each of memory 314 and memory 324 may include a type of random-access memory (RAM) such as dynamic RAM (DRAM), static RAM (SRAM), thyristor RAM (T-RAM) and/or zero-capacitor RAM (Z-RAM). Alternatively, or additionally, each of memory 314 and memory 324 may include a type of read-only memory (ROM) such as mask ROM, programmable ROM (PROM), erasable programmable ROM (EPROM) and/or electrically erasable programmable ROM (EEPROM). Alternatively, or additionally, each of memory 314 and memory 324 may include a type of non-volatile random-access memory (NVRAM) such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM) and/or phase-change memory.
Each of apparatus 310 and apparatus 320 may be a communication entity capable of communicating with each other using various proposed schemes in accordance with the present disclosure. For illustrative purposes and without limitation, a description of capabilities of apparatus 310, as a UE (e.g., UE 110), and apparatus 320, as a network node (e.g., network node 125) of a network (e.g., wireless network 120 as a 5G/NR mobile network), is provided below in the context of example processes 400 and 500.
At 410, after a first call having been established between apparatus 310 (e.g., as UE 110) and a wireless network (e.g., via apparatus 320 as network node 125 of wireless network 120) on a domain via a first RAT, process 400 may involve processor 312 attempting, via transceiver 316, to establish a second call between apparatus 310 and the wireless network via the first RAT. Process 400 may proceed from 410 to 420.
At 420, in response to a failure in attempting to establish the second call via the first RAT, process 400 may involve processor 312 establishing, via the transceiver 316, the second call via a second RAT different than the first RAT. In establishing the second call via the second RAT, process 400 may involve processor 312 transferring the first call on the domain to the second RAT along with establishing of the second call via the second RAT.
In some implementations, in establishing the second call, process 400 may further involve processor 312 placing the first call in a hold state.
In some implementations, in transferring the first call, process 400 may involve processor 312 performing certain operations. For instance, process 400 may involve processor 312 triggering a scan on the second RAT while the first call is in the hold state. Moreover, process 400 may involve processor 312 performing a context transfer of the first call to another domain corresponding to the second RAT responsive to a successful result of the scan on the second RAT.
In some implementations, process 400 may involve processor 312 performing additional operations. For instance, process 400 may involve processor 312 taking the first call out of the hold state to continue the first call via the second RAT upon completion of the second call.
In some implementations, the first call may have a first priority level, and the second call may have a second priority level higher than the first priority level. For instance, the first call may include a normal call, and the second call may include an emergency call.
In some implementations, the domain may include an IMS domain. Moreover, the first RAT may include NR, and the second RAT may include LTE.
At 510, process 500 may involve processor 312 of apparatus 310 establishing, via transceiver 316, a first call having between apparatus 310 (e.g., as UE 110) and a wireless network (e.g., via apparatus 320 as network node 125 of wireless network 120) on an IMS domain via a NR RAT. Process 500 may proceed from 510 to 520.
At 520, process 500 may involve processor 312 attempting, via transceiver 316, to establish a second call between apparatus 310 and the wireless network via the NR RAT. Process 500 may proceed from 520 to 530.
At 530, process 500 may involve processor 312 establishing, via transceiver 316, the second call via an LTE RAT in response to a failure in attempting to establish the second call via the NR RAT. In establishing the second call, process 500 may involve processor 312 transferring the first call on the IMS domain to the LTE RAT along with establishing of the second call via the LTE RAT.
In some implementations, in establishing the second call, process 500 may further involve processor 312 placing the first call in a hold state.
In some implementations, in transferring the first call, process 500 may involve processor 312 performing certain operations. For instance, process 500 may involve processor 312 triggering a scan on the LTE RAT while the first call is in the hold state. Moreover, process 500 may involve processor 312 performing a context transfer of the first call to an LTE domain corresponding to the LTE RAT responsive to a successful result of the scan on the LTE RAT.
In some implementations, process 500 may involve processor 312 performing additional operations. For instance, process 500 may involve processor 312 taking the first call out of the hold state to continue the first call via the LTE RAT upon completion of the second call.
In some implementations, the first call may have a first priority level, and the second call may have a second priority level higher than the first priority level. For instance, the first call may include a normal call, and the second call may include an emergency call.
The herein-described subject matter sometimes illustrates different components contained within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable”, to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.
Further, with respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.
Moreover, it will be understood by those skilled in the art that, in general, terms used herein, and especially in the appended claims, e.g., bodies of the appended claims, are generally intended as “open” terms, e.g., the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “includes” should be interpreted as “includes but is not limited to,” etc. It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, as an aid to understanding, the following appended claims may contain usage of the introductory phrases “at least one” and “one or more” to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim recitation to implementations containing only one such recitation, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an,” e.g., “a” and/or “an” should be interpreted to mean “at least one” or “one or more;” the same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number, e.g., the bare recitation of “two recitations,” without other modifiers, means at least two recitations, or two or more recitations. Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc. In those instances where a convention analogous to “at least one of A, B, or C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention, e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc. It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase “A or B” will be understood to include the possibilities of “A” or “B” or “A and B.”
From the foregoing, it will be appreciated that various implementations of the present disclosure have been described herein for purposes of illustration, and that various modifications may be made without departing from the scope and spirit of the present disclosure. Accordingly, the various implementations disclosed herein are not intended to be limiting, with the true scope and spirit being indicated by the following claims.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202321033500 | May 2023 | IN | national |
