WO2020033308A1

WO2020033308A1 - Timeout for provisional response ack to reduce voip call setup time

Info

Publication number: WO2020033308A1
Application number: PCT/US2019/045104
Authority: WO
Inventors: Anish T. GEORGE
Original assignee: Intel Corporation
Priority date: 2018-08-10
Filing date: 2019-08-05
Publication date: 2020-02-13

Abstract

Embodiments of a User Equipment (UE) and methods of communication are generally described herein. The UE may receive, from a RAN node, an INVITE message that indicates an incoming VoIP call for the UE. The UE may transmit, to the RAN node, a provisional response message to acknowledge the INVITE message. The UE may monitor for a provisional response acknowledgement (PRACK) message in accordance with a provisional acknowledgement timer. The UE may determine a provisional acknowledgement timeout value used to determine expiration of a provisional acknowledgement timer. The value of the provisional acknowledgement timeout value may be determined to be a value that is less than a default session initiation protocol (SIP) timeout value.

Description

TIMEOUT FOR PROVISIONAL RESPONSE ACK TO REDUCE VOIP

CALL SETUP TIME

PRIORITY CLAIM

[0001] This application claims priority to United States Provisional

Patent Application Serial No. 62/717,312, filed August 10, 2018, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Embodiments pertain to wireless communications. Some embodiments relate to wireless networks including 3 GPP (Third Generation Partnership Project) networks, and 3GPP LTE (Long Term Evolution) networks, Fifth Generation (5G) networks, and/or New Radio (NR) networks. Some embodiments relate to Voice Over Internet Protocol (VoIP), Voice over LTE (VoLTE) and/or other. Some embodiments relate to determination of a timeout value for a provisional response acknowledgement (PRACK) to reduce VoIP call setup time.

BACKGROUND

[0003] Efficient use of the resources of a wireless network is important to provide bandwidth and acceptable response times to the users of the wireless network. However, often there are many devices trying to share the same resources and some devices may be limited by the communication protocol they use or by their hardware bandwidth. Moreover, wireless devices may need to operate with both newer protocols and with legacy device protocols. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] FIG. 1 A is a functional diagram of an example network in accordance with some embodiments;

[0005] FIG. 1B is a functional diagram of another example network in accordance with some embodiments;

[0006] FIG. 2 illustrates a block diagram of an example machine in accordance with some embodiments;

[0007] FIG. 3 illustrates an exemplary communication circuitry according to some aspects;

[0008] FIG. 4 illustrates the operation of a method of communication in accordance with some embodiments;

[0009] FIG. 5 illustrates example operations in accordance with some embodiments; and

[0010] FIG. 6 illustrates example operations in accordance with some embodiments.

DETAILED DESCRIPTION

[0011] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0012] FIG. 1 A is a functional diagram of an example network in accordance with some embodiments. FIG. 1B is a functional diagram of another example network in accordance with some embodiments. In references herein, “FIG. 1” may include FIG. 1A and FIG. 1B. In some embodiments, the network 100 may be a Third Generation Partnership Project (3GPP) network. In some embodiments, the network 150 may be a 3GPP network, a new radio (NR) network and/or Fifth Generation (5G) network. Other networks may be used in some embodiments. In some embodiments, a network may include one or more of: one or more components shown in FIG. 1 A; one or more components shown in FIG. 1B; and one or more additional components. Some embodiments may not necessarily include all components shown in FIG. 1 A and FIG. 1B.

[0013] The network 100 may comprise a radio access network (RAN)

101 and the core network 120 (e.g., shown as an evolved packet core (EPC)) coupled together through an Sl interface 115. For convenience and brevity sake, only a portion of the core network 120, as well as the RAN 101, is shown. In some embodiments, the RAN 101 may include one or more of: one or more components of an evolved universal terrestrial radio access network (E- ETTRAN), one or more components of an NR. network, and/or one or more other components.

[0014] The core network 120 may include a mobility management entity (MME) 122, a serving gateway (serving GW) 124, and packet data network gateway (PDN GW) 126. In some embodiments, the networks 100, 150 may include (and/or support) one or more Evolved Node-B’s (eNBs) 104 and/or one or more Next Generation Node-B’s (gNBs) 105. The eNBs 104 and/or gNBs 105 may operate as base stations for communicating with User Equipment (UE) 102. In some embodiments, one or more eNBs 104 may be configured to operate as gNBs 105. Embodiments are not limited to the number of eNBs 104 shown in FIG. 1 A or to the number of gNBs 105 shown in FIG. 1B.

Embodiments are also not limited to the connectivity of components shown in FIG. 1A.

[0015] It should be noted that references herein to an eNB 104 or to a gNB 105 are not limiting. In some embodiments, one or more operations, methods and/or techniques (such as those described herein) may be practiced by a base station component (and/or other component), including but not limited to a gNB 105, an eNB 104, a serving cell, a transmit receive point (TRP) and/or other. In some embodiments, the base station component may be configured to operate in accordance with one or more of: a 3 GPP LTE protocol/standard, an NR. protocol/standard, a Fifth Generation (5G) protocol/standard; and/or other protocol/standard, although the scope of embodiments is not limited in this respect.

[0016] Descriptions herein of one or more operations, techniques and/or methods practiced by a component (such as the UE 102, eNB 104, gNB 105 and/or other) are not limiting. In some embodiments, one or more of those operations, techniques and/or methods may be practiced by another component.

[0017] The MME 122 manages mobility aspects in access such as gateway selection and tracking area list management. The serving GW 124 terminates the interface toward the RAN 101, and routes data packets between the RAN 101 and the core network 120. In addition, it may be a local mobility anchor point for inter-eNB handovers and also may provide an anchor for inter- 3GPP mobility. The serving GW 124 and the MME 122 may be implemented in one physical node or separate physical nodes.

[0018] In some embodiments, EEs 102, the eNB 104 and/or gNB 105 may be configured to communicate Orthogonal Frequency Division

Multiplexing (OFDM) communication signals over a multicarrier

communication channel in accordance with an Orthogonal Frequency Division Multiple Access (OFDMA) communication technique.

[0019] In some embodiments, the network 150 may include one or more components configured to operate in accordance with one or more 3 GPP standards, including but not limited to an NR standard. The network 150 shown in FIG. 1B may include a next generation RAN (NG-RAN) 155, which may include one or more gNBs 105. In some embodiments, the network 150 may include the E-UTRAN 160, which may include one or more eNBs. The E- ETTRAN 160 may be similar to the RAN 101 described herein, although the scope of embodiments is not limited in this respect.

[0020] In some embodiments, the network 150 may include the MME

165, which may be similar to the MME 122 described herein, although the scope of embodiments is not limited in this respect. In some embodiments, the network 150 may include the SGW 170, which may be similar to the SGW 124 described herein, although the scope of embodiments is not limited in this respect. [0021] Embodiments are not limited to the number or type of

components shown in FIG. 1B. Embodiments are also not limited to the connectivity of components shown in FIG. 1B.

[0022] As used herein, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware. Embodiments described herein may be implemented into a system using any suitably configured hardware and/or software.

[0023] FIG. 2 illustrates a block diagram of an example machine in accordance with some embodiments. The machine 200 is an example machine upon which any one or more of the techniques and/or methodologies discussed herein may be performed. In alternative embodiments, the machine 200 may operate as a standalone device or may be connected (e.g., networked) to other machines. The machine 200 may be a TIE 102, eNB 104, gNB 105, access point (AP), station (STA), user, device, mobile device, base station, another device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term“machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.

[0024] Examples as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.

[0025] The machine (e.g., computer system) 200 may include a hardware processor 202 (e.g., a central processing unit (CPET), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208. The machine 200 may further include one or more of 210-228.

[0026] The storage device 216 may include a machine readable medium

222 on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, or within the hardware processor 202 during execution thereof by the machine

200. In an example, one or any combination of the hardware processor 202, the main memory 204, the static memory 206, or the storage device 216 may constitute machine readable media. In some embodiments, the machine readable medium may be or may include a non-transitory computer-readable storage medium. In some embodiments, the machine readable medium may be or may include a computer-readable storage medium.

[0027] While the machine readable medium 222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224. The term“machine readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 200 and that cause the machine 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable

Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, machine readable media may include non-transitory machine readable media, computer readable storage media and/or non-transitory computer readable storage media. In some examples, machine readable media may include machine readable media that is not a transitory propagating signal.

[0028] The instructions 224 may further be transmitted or received over a communications network 226 using a transmission medium via the network interface device 220 utilizing any one of a number of transfer protocols. In an example, the network interface device 220 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. In some examples, the network interface device 220 may wirelessly communicate using Multiple User MIMO techniques. The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine 200, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

[0029] FIG. 3 illustrates an exemplary communication circuitry according to some aspects. It should be noted that a device, such as a UE 102, eNB 104, gNB 105, the machine 200 and/or other device may include one or more components of the communication circuitry 300, in some aspects. The communication circuitry 300 may include protocol processing circuitry 305, which may implement one or more of: medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC) and non-access stratum (NAS) functions. The communication circuitry 300 may further include digital baseband circuitry 310, which may implement one or more physical layer (PHY) functions. The communication circuitry 300 may further include transmit circuitry 315, receive circuitry 320 and/or antenna array circuitry 330. The communication circuitry 300 may further include radio frequency (RF) circuitry 325. In an aspect of the disclosure, RF circuitry 325 may include multiple parallel RF chains for one or more of transmit or receive functions, each connected to one or more antennas of the antenna array 330.

[0030] In some embodiments, processing circuitry may perform one or more operations described herein and/or other operation(s). In a non-limiting example, the processing circuitry may include one or more components such as the processor 202, protocol processing circuitry 305, digital baseband circuitry 310, similar component(s) and/or other component(s).

[0031] In some embodiments, a transceiver may transmit one or more elements (including but not limited to those described herein) and/or receive one or more elements (including but not limited to those described herein). In a non limiting example, the transceiver may include one or more components such as transmit circuitry 315, receive circuitry 320, radio frequency circuitry 325, similar component(s) and/or other component(s).

[0032] Although the UE 102, eNB 104, gNB 105, machine 200 and/or other device described herein may each be illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), one or more microprocessors, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements may refer to one or more processes operating on one or more processing elements.

[0033] Embodiments may be implemented in one or a combination of hardware, firmware and software. Embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device may include read only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media. Some embodiments may include one or more processors and may be configured with instructions stored on a computer-readable storage device. [0034] It should be noted that in some embodiments, an apparatus of the

UE 102, eNB 104, gNB 105, machine 200, and/or other device may include various components shown in FIGs. 2-3 and/or other components. Accordingly, techniques and operations described herein that are performed by a device may be performed by an apparatus of the device, in some embodiments.

[0035] In accordance with some embodiments, the UE 102 may receive, from a Radio Access Network (RAN) node of a RAN, control signaling that includes configuration information for Session Initiation Protocol (SIP) for control of voice-over-IP (VoIP) communication between the UE 102 and the RAN. The control signaling may include a T1 parameter, wherein a default SIP timeout value for timers for SIP transactions is defined as a product of 64 and the T1 parameter. The UE 102 may receive, from the RAN node, an INVITE message that indicates an incoming VoIP call for the UE 102. The UE 102 may transmit, to the RAN node, a provisional response message to acknowledge the INVITE message. The UE 102 may determine a provisional acknowledgement timeout value used to determine expiration of a provisional acknowledgement timer, wherein the provisional acknowledgement timeout value is determined to be a value that is less than the default SIP timeout value to over-ride the default SIP timeout value. These embodiments are described in more detail below.

[0036] FIG. 4 illustrates the operation of a method of communication in accordance with some embodiments. Embodiments of the method 400 may include additional or even fewer operations or processes in comparison to what is illustrated in FIG. 4. Embodiments of the method 400 are not necessarily limited to the chronological order that is shown in FIG. 4.

[0037] In some embodiments, a UE 102 may perform one or more operations of the method 400, but embodiments are not limited to performance of the method 400 and/or operations of it by the UE 102. In some embodiments, another device and/or component (including but not limited to the UE 102, gNB 105, eNB 104, a client, a server and/or other component of the network) may perform one or more operations that may be the same as, similar to, reciprocal to and/or related to an operation of the method 400. Discussion of various operations, techniques and/or concepts regarding the method 400 may be applicable to another method (such as another method performed by the UE 102, a method performed by another component and/or other) in some embodiments. One or more of the techniques, operations and/or methods described herein may be performed by a device other than an eNB 104, gNB 105, and UE 102, including but not limited to a Wi-Fi access point (AP), station (STA) and/or other.

[0038] In some embodiments, an apparatus of a device (including but not limited to the UE 102, eNB 104, gNB 105 and/or other) may comprise memory that is configurable to store one or more elements, and the apparatus may use them for performance of one or more operations. The apparatus may include processing circuitry, which may perform one or more operations (including but not limited to operation(s) of the method 400 and/or other methods described herein). The processing circuitry may include a baseband processor. The baseband circuitry and/or the processing circuitry may perform one or more operations described herein. The apparatus may include a transceiver to transmit and/or receive one or more blocks, messages and/or other elements.

[0039] Embodiments are not limited by references herein to

transmission, reception and/or exchanging of elements such as frames, messages, requests, indicators, signals or other elements. In some embodiments, such an element may be generated, encoded or otherwise processed by processing circuitry for transmission by a transceiver or other component cases. In some embodiments, such an element may be received by a transceiver or other component, and may be decoded, detected or otherwise processed by processing circuitry. In some embodiments, the processing circuitry and the transceiver may be included in a same apparatus. In some embodiments, the transceiver may be separate from the apparatus that comprises the processing circuitry, in some embodiments.

[0040] One or more of the elements (such as messages, operations and/or other) described herein may be included in a 3 GPP protocol, 3 GPP LTE protocol, 4G protocol, 5G protocol, NR protocol, session initiation protocol (SIP), VoIP protocol, VoLTE protocol and/or other protocol, but embodiments are not limited to usage of those elements. In some embodiments, other elements may be used, including other element(s) in a same standard/protocol, other element(s) in another standard/protocol and/or other. In addition, the scope of embodiments is not limited to usage of elements that are included in standards.

[0041] In some embodiments, the UE 102, eNB 104 and/or gNB 105 may be arranged to operate in accordance with a 3 GPP protocol, NR protocol,

SIP protocol, VoIP protocol, VoLTE protocol and/or other protocol.

[0042] At operation 405, the EE 102 may receive control signaling from a RAN node. At operation 410, the EE 102 may receive an INVITE message. At operation 415, the UE 102 may transmit a provisional response message. At operation 420, the UE 102 may initiate a provisional acknowledgement timer.

At operation 425, the UE 102 may monitor for a provisional response

acknowledgement (PRACK) message. At operation 430, the UE 102 may, if the PRACK message is not received before expiration of the provisional

acknowledgement timer, send a call reject message.

[0043] In some embodiments, the UE 102 may receive, from a Radio

Access Network (RAN) node of a RAN, control signaling that includes configuration information for SIP for control of voice-over-IP (VoIP) communication between the UE 102 and the RAN. The control signaling may include a T1 parameter, wherein a default SIP timeout value for timers for SIP transactions is defined as a product of 64 and the T1 parameter (embodiments are not limited to usage of this default SIP timeout value). The UE 102 may receive, from the RAN node, an INVITE message that indicates an incoming VoIP call for the UE 102. The UE 102 may transmit, to the RAN node, a provisional response message to acknowledge the INVITE message. The UE 102 may determine a provisional acknowledgement timeout value used to determine expiration of a provisional acknowledgement timer, wherein the provisional acknowledgement timeout value is determined to be a value that is less than the default SIP timeout value to over-ride the default SIP timeout value.

[0044] In some embodiments, the UE 102 may initiate the provisional acknowledgement timer. The UE 102 may monitor for a provisional response acknowledgement (PRACK) message that acknowledges the provisional response message. The UE 102 may, if the PRACK message is not received before the expiration of the provisional acknowledgement timer: transmit, to the RAN node, a call rejection message to indicate rejection of the incoming VoIP call by the UE 102.

[0045] In some embodiments, usage of the provisional acknowledgement timeout value may enable a shorter waiting period, in comparison to a waiting period when the default SIP timer is used, for initiation and/or reception of VoIP calls by the UE 102 when the PRACK is not received.

[0046] In some embodiments, if the PRACK message is not received before the expiration of the provisional acknowledgement timer, the UE 102 may be configurable to receive additional incoming VoIP calls (and/or initiate outgoing VoIP calls) during a time window that occurs: after the expiration of the provisional acknowledgement timer, and before a time that is equal to a sum of: an initiation time of the provisional acknowledgement timer, and the default SIP timeout value.

[0047] In some embodiments, the UE 102 may, if the PRACK message is received before the expiration of the provisional acknowledgement timer: transmit, to the RAN node, one or more call setup messages for the incoming VoIP call.

[0048] In some embodiments, the UE 102 may be configured to operate as a client in a client-server arrangement in which a component of the RAN network operates as a server. The control signaling and the INVITE message may be received from the RAN node on behalf of the component that operates as the server. The provisional response message and the call rejection message may be transmitted to the RAN node for forwarding to the component that operates as the server.

[0049] In some embodiments, the UE 102 may transmit, to the RAN node for forwarding to a peer entity, an options request message to query the peer entity regarding capabilities of the peer entity. The UE 102 may monitor for a response message to the options request message in accordance with the SIP default timeout value.

[0050] In some embodiments, the T1 parameter may be based on an estimate of a round trip time (RTT) between a client and a server for a SIP transaction. In a non-limiting example, the T1 parameter may be equal to two seconds based on a 3 GPP LTE protocol, and the default SIP timeout value may be equal to 128 seconds.

[0051] In some embodiments, each SIP transaction may include a request message, zero or more provisional response messages, and a final response message. In some embodiments, the SIP transactions may be in a set that includes initiation of VoIP calls, query for capability, and acknowledgement of VoIP calls.

[0052] In some embodiments, the RAN network may be a 3 GPP LTE network, the RAN node may be an eNB 104, and the VoIP communication may be voice-over-LTE (VoLTE) communication.

[0053] In some embodiments, an eNB 104 of a 3 GPP LTE network may be configured to operate as a relay between the UE 102 and a component of the 3GPP LTE network for VoIP and/or VoLTE communication. The eNB 104 may transmit, to the UE, control signaling that includes configuration information for SIP for control of the VolP/VoLTE communication. The control signaling may include a T1 parameter to be used, by the UE 102, to determine a default SIP timeout value. In some embodiments, the control signaling may further include a value of a provisional acknowledgement timeout value to be used, by the UE 102, to monitor for a PRACK from the eNB 104, although the scope of embodiments is not limited in this respect. In some embodiments, the default SIP timeout value may be defined as a product of 64 and the T1 parameter, wherein the provisional acknowledgement timeout value is less than the default SIP timeout value. The eNB 104 may transmit, to the UE 102, an INVITE message that indicates an incoming VoLTE call for the UE 102. The eNB 104 may monitor for a provisional response message from the UE 102 that acknowledges the INVITE message. The eNB 104 may, if the provisional response message is received, transmit the PRACK message to the UE to acknowledge the provisional response message. The eNB 104 may monitor for a call setup message from the UE 102 or a call rejection message from the UE 102 [0054] In some embodiments, the UE 102 may receive, from an eNB 104 of a 3 GPP LTE network, control signaling that includes configuration information for SIP for control of VoLTE communication between the UE 102 and the 3 GPP LTE network. The control signaling may include a T1 parameter, wherein a default SIP timeout value for timers for SIP transactions is defined as a product of 64 and the T1 parameter. The UE 102 may receive, from the eNB 104, an INVITE message that indicates an incoming VoLTE call for the UE 102. The UE 102 may transmit, to the eNB 104, a provisional response message to acknowledge the INVITE message. The UE 102 may initiate a provisional acknowledgement timer for which a provisional acknowledgement timeout value is less than the default SIP timeout value. The UE 102 may, if a PRACK message is not received before the expiration of the provisional

acknowledgement timer: transmit, to the eNB 104, a call rejection message to indicate rejection of the incoming VoLTE call by the UE 102. The UE 102 may, if the PRACK message is received before the expiration of the provisional acknowledgement timer: transmit, to the eNB 104, one or more call setup messages for the incoming VoLTE call.

[0055] FIGs. 5 and 6 illustrate example operations in accordance with some embodiments. The examples shown in FIGs. 5-6 may illustrate some or all of the concepts and techniques described herein in some cases, but embodiments are not limited by the examples. For instance, embodiments are not limited by the name, number, type, size, ordering, arrangement of elements (such as devices, operations, messages and/or other elements) shown in FIGs. 5-6.

[0056] It should be noted that references to a UE 102, a Mobile

Terminating (MT) UE 102 and/or other device are not limiting. In a non limiting example, in descriptions herein, some techniques, operations and/or methods may be performed by a UE 102. It is understood that one or more of those techniques, operations and/or methods may be performed by an MT UE 102, in some embodiments. In another non-limiting example, in descriptions herein, some techniques, operations and/or methods may be performed by an MT UE 102. It is understood that one or more of those techniques, operations and/or methods may be performed by a UE 102, in some embodiments. [0057] Some embodiments may be related to a call setup procedure on a

UE 102 and/or Mobile Terminating (MT) UE 102. Some embodiments may be related to detecting delay in a Provisional Response Acknowledgement message. Some embodiments may be related to optimizing a call setup procedure on a EE 102 and/or an MT EE 102 by detecting delay in a Provisional Response

Acknowledgement message.

[0058] Some embodiments may be related to VoLTE Calls. VoLTE is a key feature in LTE to provide voice service over the packet-switched (PS) network. VoLTE stands for“Voice over IMS over LTE” and allows an operator to replace circuit-switched services over 2G/3G. VoLTE has been commercially launched by many operators worldwide.

[0059] Some embodiments may be related to general behavior of MT

VoLTE call. In some embodiments, the LE 102 may perform one or more of the following operations. The LE 102 may receive an INVITE with/without an SDP offer. Based on LE 102 and remote capabilities, the LE 102 may choose to send “lxx” response which indicates Reliable Provisional Response, by including “Require” SIP header with tag“lOOrel” as per RFC 3262 and 3 GPP 24.229.

[0060] In some embodiments, the LE 102 may perform one or more of the following. A) Upon successful reception of Reliable Provisional Response Acknowledgement (which may be related to SIP“PRACK”), the LE 102 may proceed with a call setup procedures as per 3 GPP 24.229 standards; B) In case the SIP PRACK request is not received by the LE 102, the LE 102 shall retransmit“lxx” response with an interval starts with Tl (~2sec) and doubles for each retransmission until 64*Tl (-128 sec) elapses. On reaching maximum retransmission limit, the LE 102 shall reject original request with 5xx response.

[0061] Reference for Reliable Provisional Response and Provisional

Response Acknowledgement is defined in RFC 3262. Relevant reference related to this document are mentioned below. Referring to RFC 3262 Section-3, the reliable provisional response is passed to the transaction layer periodically with an interval that starts at Tl seconds and doubles for each retransmission.

Referring to RFC 3262 Section-3, retransmissions of the reliable provisional response cease when a matching PRACK is received by the UA core. Referring to RFC 3262 Section-3, if a reliable provisional response is retransmitted for 64*Tl seconds without reception of a corresponding PRACK, the UAS

SHOULD reject the original request with a 5xx response. Referring to 3GPP 24.229, section 7.7, the following table may be applicable, although the scope of embodiments is not limited in this respect.

[0062] In embodiments may be related to the issue indicated as“B” above, wherein there is no PRACK received by the UE 102, and the UE 102 will be blocked to process any new MT call or originate an MO call till 64*Tl

(~l28sec). The mentioned situation can happen even before a user (and/or UE 102) is alerted regarding incoming call which is usually“Ringing” state. In some cases, since the user (and/or UE 102) is unaware of such a call being processed, it may be unfair to block the user (and/or UE 102) from originating or receiving further calls. In some cases, the network may also choose not to forward any new calls to the UE 102, since one call is already in progress, usually with a busy tone. In some cases, 64*Tl (-128 sec) may be a relatively large duration. For instance, such a duration may result in a bad user experience. In addition, signaling on advanced technologies (e.g. Voice over LTE -VoLTE, Voice over 5G -Vo5G and/or other) may be able to transport signals in a much faster and dedicated manner, in some embodiments.

[0063] In some cases, in a Multi-SIM device, a situation may arise in which an incoming call is being processed and the UE 102 waits for a

Provisional Acknowledgement message. The UE 102 may choose not to entertain further calls on either or both SIMs.

[0064] In some cases, a root cause of the UE 102 not receiving a SIP

PRACK request could be a failure of any entity involved in signaling (MO UE, MT UE, Proxies, B2B UA, any User Agents or any entities). The impact of not processing PRACK is described herein.

[0065] In some embodiments, a mechanism for releasing MT call may be used. Such a mechanism may address one or more of the issues described herein.

[0066] A non-limiting example 1000 in FIG. 10 illustrates messages that may be exchanged between the UE 102 and the network 1010, and also illustrates potential impacts (labeled as“Impact 1,”“Impact 2,” and“Impact 3” for clarity). In some embodiments, the network 1010 may include one or more of: one or more components of the network 100 in FIG. 1 A; one or more components of the network 150 in FIG. 1B; and/or other components.

[0067] In some cases, the UE 102 may wait for a period (such as 64*Tl, approximately 128 seconds) until a timer expires before release of an MT call.

As a result, the UE 102 may be blocked from making and/or receiving further calls (at least for a period of time).

[0068] In some embodiments, a configurable parameter may be defined.

In some embodiments, the configurable parameter may be defined in seconds, although the scope of embodiments is not limited in this respect. In some embodiments, the configurable parameter may be related to a“Provisional Acknowledgement timer,” although the scope of embodiments is not limited in this respect. In some embodiments, the configurable parameter may define a timer which is less than 64*Tl.

[0069] In some embodiments, the UE 102 shall wait for a provisional

Acknowledgement“PRACK” from any peer entity to be received. A timer (including but not limited to the“Provisional Acknowledgement timer”) may be started when the UE 102 sends reliable provisional responses (including but not limited to responses defined in RFC 3262). The UE 102 shall terminate/reject calls in cases in which the“Provisional Acknowledgement timer” expires before the Provisional Acknowledgement is received. In some embodiments, a value of the timer may be less than a“lxx” retransmission max duration (which may be approximately 64*Tl, although the scope of embodiments is not limited in this respect).

[0070] In some cases, one or more of the techniques, operations and/or methods described herein may result in one or more of: a better user-experience with respect to shorter call setup time if the user wishes to make a new call within in Provisional Acknowledgement wait time; a better user-experience with respect to a Multi-SIM device, wherein resources might get blocked for a longer duration (one or more of the techniques, operations and/or methods described herein may reduce wait time and/or may optimize user experience, in some cases); better management of the Network Resources such as dedicated bearer (QoS), wherein a dedicated bearer may have been already setup but is unused since call signaling requires a longer duration; a better user-experience and Network service wherein a new MT call can be setup by network and UE 102, which otherwise may have blocked by Provisional Acknowledgement wait time in some cases; and/or other.

[0071] In some embodiments, a configurable parameter in seconds

(which may be related to a“Provisional Acknowledgement timer”) may be used. This parameter may define a timer which is less that 64*Tl, wherein the UE 102 shall wait for Provisional Acknowledgement request to be received. On the timer expiry, if the Provisional Acknowledgement“PRACK” is not received, the UE 102 shall terminate the call.

[0072] In FIG. 6, a non-limiting example call flow 600 is illustrated. As indicated by 622, the Provisional Acknowledgement timer is started after sending a reliable Provisional Response (as indicated by 615). After the

Provisional Acknowledgement timer is started, if the Provisional Response Acknowledgement (PRACK) is not received when the Provisional

Acknowledgement timer expires, the UE 102 may perform one or more of: drop the call, release the UE 102, release network resources and/or other. In some embodiments, the UE 102 may then accept or dial further calls at this point of time (as indicated by 630).

[0073] In some cases, when the Provisional Acknowledgement is delayed, by some standard (3GPP 24.229, RFC 3262 and/or other), the UE 102 may be expected to retransmit“lxx” reliable provisional response with an interval that starts with Tl (~2sec) and doubles for each retransmission until 64*Tl (-128 sec) elapses. In some embodiments described herein, the UE 102 may retransmit a“lxx” reliable provisional responses for a shorter duration before terminating call. [0074] In some embodiments, the UE 102 may be capable of receiving

Acknowledgement (ACK) within a certain time of a Provisional

Acknowledgement Timer after a reliable Provisional response (lxx) is sent for a Mobile Terminating (MT) call. In some embodiments, the UE 102 may be capable of rejecting MT call on expiry of the Provisional Acknowledgement Timer. In some embodiments, the UE 102 may be capable of originating a new call after a period of time has elapsed, which may be shorter than a comparable period of time in current standards, in some cases. In some embodiments, the UE 102 may be capable of accepting a new call after a period of time has elapsed, which may be shorter than a comparable period of time in current standards, in some cases. In some embodiments, the UE 102 may be capable of releasing network resources reserved after a period of time has elapsed.

Otherwise, those resources would otherwise be unnecessarily blocked by uncertain signaling conditions in some cases.

[0075] The Abstract is provided to comply with 37 C.F.R. Section

1.72(b) requiring an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims. The following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.

Claims

CLAIMS What is claimed is:

1. An apparatus of a User Equipment (UE), the apparatus comprising: memory; and processing circuitry, configured to:

decode, from a Radio Access Network (RAN) node of a RAN, control signaling that includes configuration information for Session Initiation Protocol (SIP) for control of voice-over-IP (VoIP) communication between the UE and the RAN, wherein the control signaling includes a T1 parameter, wherein a default SIP timeout value for timers for SIP transactions is defined as a product of 64 and the T1 parameter;

decode, from the RAN node, an INVITE message that indicates an incoming VoIP call for the UE;

encode, for transmission to the RAN node, a provisional response message to acknowledge the INVITE message;

determine a provisional acknowledgement timeout value used to determine expiration of a provisional acknowledgement timer, wherein the provisional acknowledgement timeout value is determined to be a value that is less than the default SIP timeout value to over-ride the default SIP timeout value, wherein the memory is configured to store the provisional

acknowledgement timeout value.

2. The apparatus according to claim 1, the processing circuitry further configured to:

initiate the provisional acknowledgement timer;

monitor for a provisional response acknowledgement (PRACK) message that acknowledges the provisional response message;

if the PRACK message is not received before the expiration of the provisional acknowledgement timer:

encode, for transmission to the RAN node, a call rejection message to indicate rejection of the incoming VoIP call by the UE.

3. The apparatus according to claim 2, wherein usage of the provisional acknowledgement timeout value enables a shorter waiting period, in comparison to a waiting period when the default SIP timer is used, for initiation and/or reception of VoIP calls by the UE when the PRACK is not received.

4. The apparatus according to claim 2, wherein if the PRACK message is not received before the expiration of the provisional acknowledgement timer, the UE is configurable to receive additional incoming VoIP calls during a time window that occurs:

after the expiration of the provisional acknowledgement timer, and before a time that is equal to a sum of:

an initiation time of the provisional acknowledgement timer, and the default SIP timeout value.

5. The apparatus according to claim 2, wherein if the PRACK message is not received before the expiration of the provisional acknowledgement timer, the UE is configurable to initiate outgoing VoIP calls during a time window that occurs:

6. The apparatus according to claim 2, the processing circuitry further configured to:

if the PRACK message is received before the expiration of the provisional acknowledgement timer:

encode, for transmission to the RAN node, one or more call setup messages for the incoming VoIP call.

7. The apparatus according to claim 1, wherein: the UE is configured to operate as a client in a client-server arrangement in which a component of the RAN network operates as a server,

the control signaling and the INVITE message are received from the RAN node on behalf of the component that operates as the server, and

the provisional response message and the call rejection message are transmitted to the RAN node for forwarding to the component that operates as the server.

8. The apparatus according to claim 1, the processing circuitry further configured to:

encode, for transmission to the RAN node for forwarding to a peer entity, an options request message to query the peer entity regarding capabilities of the peer entity;

monitor for a response message to the options request message in accordance with the SIP default timeout value.

9. The apparatus according to claim 1, wherein the T1 parameter is based on an estimate of a round trip time (RTT) between a client and a server for a SIP transaction.

10. The apparatus according to claim 1, wherein each SIP transaction includes a request message, zero or more provisional response messages, and a final response message.

11. The apparatus according to claim 1, wherein:

the RAN network is a Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) network,

the RAN node is an Evolved Node-B (eNB),

the VoIP communication is voice-over-LTE (VoLTE) communication.

12. The apparatus according to claim 11, wherein:

the T1 parameter is equal to two seconds based on a 3GPP LTE protocol, and

the default SIP timeout value is equal to 128 seconds.

13. The apparatus according to claim 1, wherein the SIP transactions are in a set that includes initiation of VoIP calls, query for capability, and acknowledgement of VoIP calls.

14. The apparatus according to claim 1, wherein:

the apparatus includes a transceiver to receive the control signaling, and the processing circuitry includes a baseband processor to decode the control signaling.

15. A computer-readable storage medium that stores instructions for execution by processing circuitry of an Evolved Node-B (eNB) of a Third Generation Partnership Project (3 GPP) Long Term Evolution (LTE) network, the eNB configured to operate as a relay between a User Equipment (UE) and a component of the 3GPP LTE network for voice-over-LTE (VoLTE)

communication, the operations to configure the processing circuitry to:

encode, for transmission to the UE, control signaling that includes configuration information for Session Initiation Protocol (SIP) for control of the VoLTE communication,

wherein the control signaling includes:

a provisional acknowledgement timeout value to be used, by the UE, to monitor for a provisional response acknowledgement (PRACK) from the eNB, and

a T1 parameter to be used, by the UE, to determine a default SIP timeout value for timers for other SIP transactions, wherein the default SIP timeout value is defined as a product of 64 and the T1 parameter, wherein the provisional acknowledgement timeout value is less than the default SIP timeout value;

encode, for transmission to the UE, an INVITE message that indicates an incoming VoLTE call for the UE; monitor for a provisional response message from the UE that acknowledges the INVITE message;

if the provisional response message is received, encode the PRACK message for transmission to the UE to acknowledge the provisional response message; and

monitor for a call setup message from the UE or a call rejection message from the UE.

16. The computer-readable storage medium according to claim 15, wherein the T1 parameter is based on an estimate of a round trip time (RTT) between a client and a server for a SIP transaction.

17. An apparatus of a User Equipment (UE) of a Third Generation Partnership Project (3 GPP) Long Term Evolution (LTE) network, the apparatus comprising: memory; and processing circuitry, configured to:

decode, from an Evolved Node-B (eNB) of the 3 GPP LTE network, control signaling that includes configuration information for Session Initiation Protocol (SIP) for control of voice-over-LTE (VoLTE) communication between the UE and the 3 GPP LTE network, wherein the control signaling includes a T1 parameter, wherein a default SIP timeout value for timers for SIP transactions is defined as a product of 64 and the T1 parameter;

decode, from the eNB, an INVITE message that indicates an incoming VoLTE call for the UE;

encode, for transmission to the eNB, a provisional response message to acknowledge the INVITE message;

initiate a provisional acknowledgement timer for which a provisional acknowledgement timeout value is less than the default SIP timeout value; if a provisional response acknowledgement (PRACK) message is not received before the expiration of the provisional acknowledgement timer:

encode, for transmission to the eNB, a call rejection message to indicate rejection of the incoming VoLTE call by the UE; and

encode, for transmission to the eNB, one or more call setup messages for the incoming VoLTE call

wherein the memory is configured to store the provisional

acknowledgement timeout value.

18. The apparatus according to claim 17, wherein usage of the provisional acknowledgement timeout value enables a shorter waiting period, in comparison to a waiting period when the default SIP timer is used, for initiation and/or reception of VoLTE calls by the UE when the PRACK is not received.

19. The apparatus according to claim 18, wherein the T1 parameter is based on an estimate of a round trip time (RTT) between a client and a server for a SIP transaction.