WO2016026067A1 - Procédés de retardement d'un domaine de réseau central lors de l'établissement simultané d'appels à commutation de circuits et à commutation de paquets - Google Patents

Procédés de retardement d'un domaine de réseau central lors de l'établissement simultané d'appels à commutation de circuits et à commutation de paquets Download PDF

Info

Publication number
WO2016026067A1
WO2016026067A1 PCT/CN2014/084618 CN2014084618W WO2016026067A1 WO 2016026067 A1 WO2016026067 A1 WO 2016026067A1 CN 2014084618 W CN2014084618 W CN 2014084618W WO 2016026067 A1 WO2016026067 A1 WO 2016026067A1
Authority
WO
WIPO (PCT)
Prior art keywords
call
request
initiating
response
call set
Prior art date
Application number
PCT/CN2014/084618
Other languages
English (en)
Inventor
Yong Xie
Shiau-He Tsai
Xuepan GUAN
Ling Xie
Xiaopeng Li
Huan Xu
Tim Tynghuei Liou
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2014/084618 priority Critical patent/WO2016026067A1/fr
Publication of WO2016026067A1 publication Critical patent/WO2016026067A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/15Setup of multiple wireless link connections
    • H04W76/16Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer

Definitions

  • aspects of the present disclosure relate generally to wireless communication systems, and more particularly, to resolving call set up conflicts between different call set up procedures.
  • Wireless communication networks are widely deployed to provide various communication services such as telephony, video, data, messaging, broadcasts, and so on.
  • Such networks which are usually multiple access networks, support communications for multiple users by sharing the available network resources.
  • UTRAN UMTS Terrestrial Radio Access Network
  • the UTRAN is the radio access network (RAN) defined as a part of the Universal Mobile Telecommunications System (UMTS), a third generation (3G) mobile phone technology supported by the 3rd Generation Partnership Project (3GPP).
  • UMTS Universal Mobile Telecommunications System
  • 3GPP 3rd Generation Partnership Project
  • the UMTS which is the successor to Global System for Mobile Communications (GSM) technologies, currently supports various air interface standards, such as Wideband-Code Division Multiple Access (W-CDMA), Time Division-Code Division Multiple Access (TD-CDMA), and Time Division-Synchronous Code Division Multiple Access (TD- SCDMA).
  • W-CDMA Wideband-Code Division Multiple Access
  • TD-CDMA Time Division-Code Division Multiple Access
  • TD- SCDMA Time Division-Synchronous Code Division Multiple Access
  • the UMTS also supports enhanced 3G data communications protocols, such as High Speed Packet Access (HSPA), which provides higher data transfer speeds and capacity to associated UMTS networks.
  • HSPA High Speed Packet Access
  • a packet-switched (PS) call may be triggered by the OS at almost the same time.
  • a radio bearer (RB) for the PS call is generally set up earlier than another RB for the CS call.
  • NW may send one or more measurement control messages to the UE when the RB for the PS call is set up and a message to set up the RB for the CS call may be accordingly queued (e.g., in a buffer) after the one or more measurement control messages associated with the PS call.
  • the RB for the CS call may not be successfully established before the activation time is up because of delays in handling the set up resulting from the position of the message in the queue. [0004] Therefore, there is a desire for resolving call set up conflicts that may occur between a CS call and a PS call.
  • the present disclosure presents examples of techniques for deferring one core network (CN) domain when CS and PS domain calls are set up simultaneously.
  • these techniques may be used to resolve call set up conflicts between a PS call and a CS call.
  • the present disclosure presents an example method for resolving call set up conflicts, comprising receiving, from a UE, a first request to set up a CS call and a second request to set up a PS call substantially at the same time as the CS call.
  • the example method may include initiating, in response to the first request, a first call set up process for the CS call in response to the first request.
  • the example method may include initiating, in response to the second request, a second call set up process for the PS call, wherein the initiating of the second call set up process is delayed with respect to the initiating of the first call set up process.
  • an apparatus for resolving call set up conflicts between a PS call and a CS call may include means for receiving, from a UE, a first request to set up a CS call and a second request to set up a PS call substantially at the same time as the CS call. Further, the apparatus may include means for initiating, in response to the first request, a first call set up process for the CS call in response to the first request. In addition, the apparatus may include means for initiating, in response to the second request, a second call set up process for the PS call, wherein the initiating of the second call set up process is delayed with respect to the initiating of the first call set up process.
  • a computer readable medium storing computer executable code comprising code for resolving call set up conflicts between a PS call and a CS call.
  • the computer executable code may include code for receiving, from a UE, a first request to set up a CS call and a second request to set up a PS call substantially at the same time as the CS call.
  • the computer-readable medium may include code for initiating, in response to the first request, a first call set up process for the CS call in response to the first request.
  • the computer-readable medium may include code for initiating, in response to the second request, a second call set up process for the PS call, wherein the initiating of the second call set up process is delayed with respect to the initiating of the first call set up process.
  • the apparatus may include a receiver configured to receive, from a user equipment (UE), a first request to set up a circuit-switched (CS) call and a second request to set up a packet- switched (PS) call substantially at the same time as the CS call. Further, the apparatus may include a call set up manager configured to initiate, in response to the first request, a first call set up process for the CS call in response to the first request, wherein the call set up manager is configured to initiate, in response to the second request, a second call set up process for the PS call, wherein the initiation of the second call set up process is delayed with respect to the initiating of the first call set up process.
  • UE user equipment
  • PS packet- switched
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
  • FIG. 1 is a block diagram illustrating an example wireless system in aspects of the present disclosure
  • Fig. 2 is a flow diagram illustrating aspects of a method of resolving call set up conflicts as contemplated by the present disclosure
  • FIG. 3 is a flowchart illustrating aspects of the present disclosure
  • FIG. 4 is a block diagram illustrating aspects of a logical grouping of electrical components as contemplated by the present disclosure
  • FIG. 5 is a block diagram illustrating aspects of a computer device according to the present disclosure
  • Fig. 6 is a conceptual diagram illustrating an example of an access network
  • Fig. 7 is a block diagram conceptually illustrating an example of a NodeB in communication with a UE in a telecommunications system.
  • the present disclosure presents examples of techniques for deferring one core network (CN) domain when CS and PS domain calls are set up simultaneously.
  • Simultaneous set up may refer to set up requests for CS and PS calls being provided or received at substantially the same time (e.g., within a few milliseconds of each other).
  • aspects of these techniques may include an example method and apparatus for resolving call set up conflicts between a PS call and a CS call.
  • a UE may initiate a CS call for voice service.
  • the OS may initiate a PS call for data service at substantially the same time, or within milliseconds, as the CS call. As such, the UE may receive data service for the UE while the UE is conducting a voice call.
  • the NW may transmit one or more measurement control messages and set up the RB for the CS call after the measurement control messages are transmitted. Since the activation time of the RB set up message for the CS call may expire before all the measurement control messages are transmitted, the RB for the CS call may not be successfully established.
  • the present methods and apparatuses may provide an efficient solution, as compared to current solutions, by delaying setting up the PS call so that the RB set up message for the PS call may not conflict with the measurement control messages for the CS call. As a result, both of the PS and CS call may be successfully established.
  • a wireless communication system 100 is illustrated that facilitates resolving call set up conflicts by delaying a call set up procedure of one of the PS and CS calls.
  • system 100 includes UE 102 that may communicate with a network (NW) 104 via one or more over-the-air links.
  • NW 104 may include one or more components, some of which may be network devices.
  • the NW 104 may refer in some instances to a network device, to multiple network devices, or to one or more components within a network device.
  • UE 102 may include an OS 106 that may be configured to transmit a PS call request to NW 104 and a voice call controller 108 that may be configured to transmit a CS call request to NW 104.
  • the PS call request and the CS call request may be transmitted substantially at the same time or within a short time period, e.g., 5 milliseconds.
  • NW 104 may include an authenticator 110 that may authenticate the identity of UE 102 for the CS call, a UE ID verifier 112 that may verify the identity of UE 102 for the PS call, and a call set up manager that may be configured to set up and/or maintain the PS call and the CS call via NAS layer 116 and AS layer 118.
  • NAS layer 116 may refer to a functional layer in the UMTS and LTE wireless telecom protocol stacks between the core network and the UE to manage the establishment of communication sessions and for maintaining continuous communications with the UE as it moves.
  • AS layer 118 may refer to another functional layer in the UMTS and LTE wireless telecom protocol stacks between the core network and the UE to transport data over the wireless connection and managing radio resources.
  • OS 106 may refer to software that manages hardware and software components of UE 102.
  • OS 106 may initiate a PS call for data service by submitting a PS call request to NW 104.
  • OS 106 may be configured to submit the PS call request, which is triggered by voice call controller 108 submitting the CS call request, so that the PS call may be piggy-backed with the CS call.
  • the PS call may not be associated with the CS call. Rather, the PS call may be accidentally initiated substantially at the same time as voice call controller 108 submitting the CS call request.
  • "substantially at the same time” may refer to the CS call request and the PS call request are submitted within a short time period, e.g., 5 milliseconds.
  • voice call controller 108 may refer to a component that may be configured to initiate the CS call by submitting a CS call request to NW 104 to establish a radio connection for voice service.
  • voice call controller 108 may be implemented as hardware, software, firmware, or any combination thereof.
  • NW 104 may be configured to authenticate the identity of UE 102 prior to initiate a first call set up process for the CS call. That is, authenticator 110 may be configured to transmit a request to authenticate the identity of UE 102, e.g., AUTHENTICATION REQUEST, to UE 102 for the CS call. UE 102 may respond with a message that satisfies one or more requirements included in the request, e.g., AUTHENTIC ATION RESPONSE.
  • the authentication process may be implemented in accordance with currently existing authentication methods/algorithms.
  • UE ID verifier 112 may be configured to verify the identity of UE 102 for purpose of the PS call by initiating a verification process.
  • a non-limiting example of the verification process may include UE ID verifier 112 transmitting a "GMM AUTHENTICATION AND CYPHERING REQUEST" to UE 102, receiving a "GMM AUTHENTICATION AND CYPHERING RESPONSE” from UE 102, transmitting a "GMM IDENTITY REQUEST" to UE 102, and/or receiving "GMM IDENTITY RESPONSE” from UE 102.
  • call set up manager 114 may refer to a component that resides on NAS layer 116.
  • Call set up manager 114 be configured to initiate, in response to the CS call request, a first call set up process for the CS call and to delay initiating a second call set up process for the PS call to avoid the conflicts. That is, call set up manager 114 may be configured to instruct components residing on or associated with AS layer 118 to transmit an RB set up message for the CS call to UE 102.
  • the RB for the CS call is established when NW 104 receives a feedback message from UE 102 in response to the RB set up message.
  • call set up manager 114 may then transmit one or more measurement control messages to UE 102 to retrieve one or more measurement quantities with respect to the over-the-air links.
  • the first call set up process for the CS call is considered complete when the measurement control messages are transmitted.
  • the second call set up process for the PS call is delayed by the call set up manager 114 until at least one of one or more conditions is met.
  • the one or more conditions may include, at least, the first call set up process is complete, a percentage ⁇ e.g., 80%) of the first call set up process is complete, a time period ⁇ e.g., 10 milliseconds) has passed since the initiating of the first call set up process, etc.
  • the duration of the time period may be determined based on a duration of the first call set up process.
  • call set up manager 114 may then start the second call set up process for the PS call. That is, call set up manager 114 may be configured to instruct components residing on or associated with AS layer 118 to transmit an RB set up message for the PS call to UE 102. Since the measurement control messages for the CS call have been transmitted to UE 102, the RB set up message will not be queue after the measurement control messages and may be processed within the activation time of the RB set up message. Upon receiving an RB set up response message from UE 102, the RB for the PS call is established.
  • Call set up manager 114 may then transmit one or more measurement control messages for the PS call to UE 102 to retrieve one or more measurement quantities with respect to the over- the-air links.
  • the CS call and the PS call may be respectively established and conflicts therebetween may be avoided.
  • method 200 may resolve call set up conflicts between a PS call and a CS call.
  • Method 200 may operate on a NW, such as NW 104 (Fig. 1), via execution of call set up manager 114. While, for purposes of simplicity of explanation, the method is are shown and described as a series of acts, it is to be understood and appreciated that the method is not limited by the order of acts, as some acts may, in accordance with one or more aspects, occur in different orders and/or concurrently with other acts from that shown and described herein. For example, it is to be appreciated that the method could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a step in accordance with one or more features described herein.
  • method 200 may include receiving, from a UE, a first request to set up a CS call and a second request to set up a PS call substantially at the same time as the CS call.
  • NW 104 may receive the PS call request from OS 106 and the CS call request from voice call controller 108 substantially at the same time or within a short time period, e.g., 5 milliseconds.
  • the NW 104 may include a receiver (see e.g., receiver 735 in Fig. 7), which may be configured to receive the first and second requests.
  • method 200 may include initiating, in response to the first request, a first call set up process for the CS call in response to the first request.
  • NW 104 or call set up manager 114 may be configured to instruct components on AS layer 118 to set up a RB for the CS call and, subsequent to the establishment of the RB, to transmit one or more measurement control messages to UE 102.
  • method 200 may include initiating, in response to the second request, a second call set up process for the PS call, wherein the initiating of the second call set up process is delayed with respect to the initiating of the first call set up process.
  • NW 104 or the call set up manager 114 may delay the second call set up process for the PS call until at least one of one or more conditions is met.
  • the one or more conditions may include, at least, the first call set up process is complete, a percentage (e.g., 80%) of the first call set up process is complete, a time period (e.g., 10 milliseconds) has passed since the initiating of the first call set up process, an event or message associated with the first call set up process has been sent, etc.
  • the duration of the time period may be determined based on a duration of the first call set up process.
  • call set up manager 114 may then start the second call set up process for the PS call. That is, call set up manager 114 may be configured to instruct components residing on or associated with AS layer 118 to transmit an RB set up message for the PS call to UE 102. Since the measurement control messages for the CS call have been transmitted to UE 102, the RB set up message will not be queue after the measurement control messages and may be processed within the activation time of the RB set up message. Upon receiving an RB set up response message from UE 102, the RB for the PS call is established.
  • Call set up manager 114 may then transmit one or more measurement control messages for the PS call to UE 102 to retrieve one or more measurement quantities with respect to the over- the-air links.
  • the CS call and the PS call may be respectively established and conflicts therebetween may be avoided.
  • flowcharts 300 illustrates a method of resolving call set up conflicts between a PS call and a CS call.
  • Method 300 may operate on a NW, such as NW 104 (Fig. 1), via execution of call set up manager 114 (Fig. 1). While, for purposes of simplicity of explanation, the steps herein are shown and described as a series of acts, it is to be understood and appreciated that the steps are not limited by the order of acts, as some acts may, in accordance with one or more aspects, occur in different orders and/or concurrently with other acts from that shown and described herein.
  • NW 104 in Fig. 3 may refer, as noted above, to one or more network entities and/or network entity components configured to handle the specific messages or processes described in connection with Fig. 3.
  • flowchart 300 may be performed by a NW, or one or more components thereof, such as authenticator 110, UE ID verifier 112, and call set up manager 114.
  • voice call controller 108 may transmit a CS call request to NW 104 to establish a CS call and OS 106 may transmit a PS call request to NW 104 to establish a PS call.
  • the PS call request may be triggered by the CS call request such that the PS call may piggy-back with the CS call.
  • UE 102 may receive data service while receiving voice service.
  • the PS call request may be accidentally initiated substantially at the same time as the CS call request.
  • the CS call request and the PS call request may be transmitted to NW 104 within a short time period, e.g., 5 milliseconds.
  • NW 104 may start to establish the CS call for UE 102.
  • authenticator 110 may start an authentication process for the CS call; call set up manager 114 may set up an RB for the CS call and transmit one or more measurement control messages to UE 102.
  • authenticator 110 may be configured to transmit a request to authenticate the identity of UE 102, e.g., AUTHENTICATION JIEQUEST, to UE 102 for the CS call.
  • UE 102 may respond with a message that satisfies one or more requirements included in the request, e.g., AUTHENTICATION RESPONSE.
  • call set up manager 114 may be configured to instruct components residing on AS layer 118 to transmit an RB set up message for the CS call to UE102.
  • the RB for the CS call is established when NW 104 receives a feedback message from UE 102 in response to the RB set up message.
  • call set up manager 114 may then transmit one or more measurement control messages to UE 102 to retrieve one or more measurement quantities with respect to the over-the-air links.
  • the first call set up process for the CS call is considered complete when the measurement control messages are transmitted.
  • NW 104 may start an authentication process for the PS call prior to or subsequent to the completion of the CS call set up.
  • UE ID verifier 112 may be configured to verify the identity of UE 102 for purpose of the PS call by initiating a verification process.
  • a non-limiting example of the verification process may include NW 104 transmitting a "GMM AUTHENTICATION AND CYPHERING REQUEST" to UE 102 and receiving a "GMM AUTHENTICATION AND CYPHERING RESPONSE" from UE 102.
  • the second call set up process for the PS call is delayed by the call set up manager 114 until at least one of one or more conditions is met.
  • the one or more conditions may include, at least, the first call set up process is complete, a percentage (e.g., 80%) of the first call set up process is complete, a time period (e.g., 10 milliseconds) has passed since the initiating of the first call set up process, etc.
  • the duration of the time period may be determined based on a duration of the first call set up process.
  • call set up manager 114 may then start the second call set up process for the PS call.
  • the second call set up process for the PS call may include a UE ID verification process for the PS call, an RB set up process for the PS call, and NW 104 transmitting one or more measurement control messages to UE 102.
  • UE ID verifier 112 may , transmit a "GMM IDENTITY REQUEST" to UE 102, and/or receive "GMM IDENTITY RESPONSE" from UE 102.
  • call set up manager 114 may be configured to instruct components residing on AS layer 118 to transmit an RB set up message for the PS call to UE 102.
  • the RB for the PS call is established when NW 104 receives a feedback message from UE 102 in response to the RB set up message.
  • Call set up manager 114 may then transmit one or more measurement control messages for the PS call to UE 102 to retrieve one or more measurement quantities with respect to the over-the-air links.
  • System 400 is displayed for resolving call set up conflicts between a PS call and a CS call.
  • system 400 can reside at least partially within an NW, for example, NW 104 (Fig. 1) and/or call set up manager 114 (Fig. 1).
  • system 400 is represented as including functional blocks, which can be functional blocks that represent functions implemented by a processor, software, or combination thereof (for example, firmware).
  • System 400 includes a logical grouping 402 of electrical components that can act in conjunction.
  • logical grouping 402 may include an electrical component 404 configured to receive a first request to set up a CS call and a second request to set up a PS call substantially at the same time as the CS call.
  • logical grouping 402 may include an electrical component 406 configured to initiate, in response to the first request, a first call set up process for the CS call in response to the first request.
  • electrical component 406 may comprise call set up manager 114 (Fig. 1).
  • logical grouping 402 may include an electrical component 408 configured to initiate, in response to the second request, a second call set up process for the ps call, wherein the initiating of the second call set up process is delayed with respect to the initiating of the first call set up process.
  • electrical component 408 may comprise call set up manager 114 (Fig. 1).
  • system 400 can include a memory 410 that retains instructions for executing functions associated with the electrical components 404, 406, and 408, stores data used or obtained by the electrical components 404, 406, and 408. While shown as being external to memory 410, it is to be understood that one or more of the electrical components 404, 406, and 408 can exist within memory 410.
  • electrical components 404, 406, and 408 can comprise at least one processor, or each electrical component 404, 406, and 408 can be a corresponding module of at least one processor.
  • electrical components 404, 406, and 408 can be a computer program product including a computer readable medium, where each electrical component 404, 406, and 408 can be corresponding code.
  • authenticator 110, UE ID verifier 112, and/or call set up manager 114 may be represented by a specially programmed or configured NW 104.
  • NW 104 may include authenticator 110, UE ID verifier 112, and/or call set up manager 114 and its components, such as in specially programmed computer readable instructions or code, firmware, hardware, or some combination thereof.
  • the NW 104 may include a receiver and a transmitter to communicate with, for example, a UE.
  • NW 104 includes a processor 502 for carrying out processing functions associated with one or more of components and functions described herein.
  • Processor 502 can include a single or multiple set of processors or multi-core processors.
  • processor 502 can be implemented as an integrated processing system and/or a distributed processing system.
  • call set up manager 114 may be implemented or executed using one or any combination of processor 502, memory 504, communications component 506, and/or data store 508.
  • call set up manager 114 may be defined or otherwise programmed as one or more processor modules of processor 502.
  • call set up manager 114 may be defined as a computer-readable medium stored in memory 504 and/or data store 508 and executed by processor 502.
  • inputs and outputs relating to operations of v call set up manager 114 may be provided or supported by communications component 506, which may provide a bus between the components of NW 104 or an interface to communication with external devices or components.
  • NW 104 further includes a memory 504, such as for storing data used herein and/or local versions of applications being executed by processor 502.
  • Memory 504 can include any type of memory usable by a computer, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof.
  • NW 104 includes a communications component 506 that provides for establishing and maintaining communications with one or more parties utilizing hardware, software, and services as described herein.
  • Communications component 506 may carry communications between components on NW 104, as well as between NW 104 and external devices, such as devices located across a communications network and/or devices serially or locally connected to NW 104.
  • communications component 506 may include one or more buses, and may further include transmit chain components and receive chain components associated with a transmitter and receiver, respectively, or a transceiver, operable for interfacing with external devices.
  • communications component 506 may be configured to receive one or more pages from one or more subscriber networks. In a further aspect, such a page may correspond to the second subscription and may be received via the first technology type communication services.
  • NW 104 may further include a data store 508, which can be any suitable combination of hardware and/or software, that provides for mass storage of information, databases, and programs employed in connection with aspects described herein.
  • data store 508 may be a data repository for applications not currently being executed by processor 502 and/or any threshold values or finger position values.
  • NW 104 may additionally include a user interface component 510 operable to receive inputs from a user of NW 104 and further operable to generate outputs for presentation to the user.
  • User interface component 510 may include one or more input devices, including but not limited to a keyboard, a number pad, a mouse, a touch-sensitive display, a navigation key, a function key, a microphone, a voice recognition component, any other mechanism capable of receiving an input from a user, or any combination thereof. Further, user interface component 510 may include one or more output devices, including but not limited to a display, a speaker, a haptic feedback mechanism, a printer, any other mechanism capable of presenting an output to a user, or any combination thereof.
  • an access network 600 in a UTRAN architecture may include one or more user equipment (UE).
  • the multiple access wireless communication system includes multiple cellular regions (cells), including cells 602, 604, and 606, each of which may include one or more sectors and which may be NW 104 of Fig. 1.
  • the multiple sectors can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell. For example, in cell 602, antenna groups 612, 614, and 616 may each correspond to a different sector. In cell 604, antenna groups 618, 620, and 622 each correspond to a different sector. In cell 606, antenna groups 624, 626, and 628 each correspond to a different sector.
  • the cells 602, 604 and 606 may include several wireless communication devices, e.g., User Equipment or UEs, for example, including UE 102 of Fig. 1, which may be in communication with one or more sectors of each cell 602, 604 or 606.
  • UEs 630 and 632 may be in communication with NodeB 642
  • UEs 634 and 636 may be in communication with NodeB 644, and
  • UEs 636 and 640 can be in communication with NodeB 646.
  • each NodeB 642, 644, 646 is configured to provide an access point for all the UEs 630, 632, 634, 636, 638, 640 in the respective cells 602, 604, and 606.
  • each NodeB 642, 644, 646 may be NW 104 of Fig. 1, and/or each UE 630, 632, 634, 636, 638, 640 may be UE 102 of Fig. 1, and may perform the methods outlined herein.
  • the modulation and multiple access scheme employed by the access network 600 may vary depending on the particular telecommunications standard being deployed.
  • the standard may include Evolution-Data Optimized (EV-DO) or Ultra Mobile Broadband (UMB).
  • EV-DO and UMB are air interface standards promulgated by the 3rd Generation Partnership Project 2 (3GPP2) as part of the CDMA2000 family of standards and employs CDMA to provide broadband Internet access to mobile stations.
  • 3GPP2 3rd Generation Partnership Project 2
  • the standard may alternately be Universal Terrestrial Radio Access (UTRA) employing Wideband-CDMA (W-CDMA) and other variants of CDMA, such as TD-SCDMA; Global System for Mobile Communications (GSM) employing TDMA; and Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash-OFDM employing OFDM A.
  • UTRA, E-UTRA, UMTS, LTE, LTE Advanced, and GSM are described in documents from the 3GPP organization.
  • CDMA2000 and UMB are described in documents from the 3GPP2 organization.
  • the actual wireless communication standard and the multiple access technology employed will depend on the specific application and the overall design constraints imposed on the system.
  • Fig. 7 is a block diagram of a NodeB 710 in communication with UE 750, where the NodeB 710 may be part of the NW 104 that may include call set up manager 114 and where UE 750 may be UE 102 (Fig 1).
  • a transmit processor 720 may receive data from a data source 712 and control signals from a controller/processor 740. The transmit processor 720 provides various signal processing functions for the data and control signals, as well as reference signals (e.g., pilot signals).
  • the transmit processor 720 may provide cyclic redundancy check (CRC) codes for error detection, coding and interleaving to facilitate forward error correction (FEC), mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM), and the like), spreading with orthogonal variable spreading factors (OVSF), and multiplying with scrambling codes to produce a series of symbols.
  • BPSK binary phase-shift keying
  • QPSK quadrature phase-shift keying
  • M-PSK M-phase-shift keying
  • M-QAM M-quadrature amplitude modulation
  • OVSF orthogonal variable spreading factors
  • channel estimates may be derived from a reference signal transmitted by the UE 750 or from feedback from the UE 750.
  • the symbols generated by the transmit processor 720 are provided to a transmit frame processor 730 to create a frame structure.
  • the transmit frame processor 730 creates this frame structure by multiplexing the symbols with information from the controller/processor 740, resulting in a series of frames.
  • the frames are then provided to a transmitter 732, which provides various signal conditioning functions including amplifying, filtering, and modulating the frames onto a carrier for downlink transmission over the wireless medium through antenna 734.
  • the antenna 734 may include one or more antennas, for example, including beam steering bidirectional adaptive antenna arrays or other similar beam technologies.
  • a receiver 754 receives the downlink transmission through an antenna 752 and processes the transmission to recover the information modulated onto the carrier.
  • the information recovered by the receiver 754 is provided to a receive frame processor 760, which parses each frame, and provides information from the frames to a channel processor 784 and the data, control, and reference signals to a receive processor 770.
  • the receive processor 770 then performs the inverse of the processing performed by the transmit processor 720 in the NodeB 710. More specifically, the receive processor 770 descrambles and de-spreads the symbols, and then determines the most likely signal constellation points transmitted by the NodeB 710 based on the modulation scheme. These soft decisions may be based on channel estimates computed by the channel processor 784.
  • the soft decisions are then decoded and de-interleaved to recover the data, control, and reference signals.
  • the CRC codes are then checked to determine whether the frames were successfully decoded.
  • the data carried by the successfully decoded frames will then be provided to a data sink 772, which represents applications running in the UE 750 and/or various user interfaces (e.g., display).
  • Control signals carried by successfully decoded frames will be provided to a controller/processor 780.
  • the controller/processor 780 may also use an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support retransmission requests for those frames.
  • ACK acknowledgement
  • NACK negative acknowledgement
  • a transmit processor 779 In the uplink, data from a data source 778 and control signals from the controller/processor 780 are provided to a transmit processor 779.
  • the data source 778 may represent applications running in the UE 750 and various user interfaces (e.g., keyboard). Similar to the functionality described in connection with the downlink transmission by the NodeB 710, the transmit processor 779 provides various signal processing functions including CRC codes, coding and interleaving to facilitate FEC, mapping to signal constellations, spreading with OVSFs, and scrambling to produce a series of symbols.
  • Channel estimates may be used to select the appropriate coding, modulation, spreading, and/or scrambling schemes.
  • the symbols produced by the transmit processor 779 will be provided to a transmit frame processor 782 to create a frame structure.
  • the transmit frame processor 782 creates this frame structure by multiplexing the symbols with information from the controller/processor 780, resulting in a series of frames.
  • the frames are then provided to a transmitter 756, which provides various signal conditioning functions including amplification, filtering, and modulating the frames onto a carrier for uplink transmission over the wireless medium through the antenna 752.
  • the uplink transmission is processed at the NodeB 710 in a manner similar to that described in connection with the receiver function at the UE 750.
  • a receiver 735 receives the uplink transmission through the antenna 734 and processes the transmission to recover the information modulated onto the carrier.
  • the information recovered by the receiver 735 is provided to a receive frame processor 736, which parses each frame, and provides information from the frames to the channel processor 744 and the data, control, and reference signals to a receive processor 737.
  • the receive processor 737 performs the inverse of the processing performed by the transmit processor 779 in the UE 750.
  • the data and control signals carried by the successfully decoded frames may then be provided to a data sink 738 and the controller/processor, respectively. If some of the frames were unsuccessfully decoded by the receive processor, the controller/processor 780 may also use an acknowledgement (ACK) and/or negative acknowledgement (NACK) protocol to support retransmission requests for those frames.
  • ACK acknowledgement
  • NACK negative acknowledgement
  • the controller/processors 740 and 780 may be used to direct the operation at the NodeB 710 and the UE 750, respectively.
  • the controller/processors 740 and 780 may provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the computer readable media of memories 742 and 762 may store data and software for the NodeB 710 and the UE 750, respectively.
  • a scheduler/processor 746 at the NodeB 710 may be used to allocate resources to the UEs and schedule downlink and/or uplink transmissions for the UEs.
  • TD-SCDMA High Speed Downlink Packet Access
  • HSDPA High Speed Downlink Packet Access
  • HSUPA High Speed Uplink Packet Access
  • HSPA+ High Speed Packet Access Plus
  • LTE Long Term Evolution
  • LTE-A LTE- Advanced
  • EV-DO Evolution-Data Optimized
  • UMB Ultra Mobile Broadband
  • Wi-Fi IEEE 802.11
  • WiMAX IEEE 802.16
  • UWB Ultra- Wideband
  • Bluetooth and/or other suitable systems.
  • LTE Long Term Evolution
  • network architecture and/or communication standard employed will depend on the specific application and the overall design constraints imposed on the system.
  • processors include microprocessors, microcontrollers, digital signal processors (DSPs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • DSPs digital signal processors
  • FPGAs field programmable gate arrays
  • PLDs programmable logic devices
  • state machines gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • One or more processors in the processing system may execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the software may reside on a computer-readable medium.
  • the computer-readable medium may be a non-transitory computer-readable medium.
  • a non-transitory computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip), an optical disk (e.g., compact disk (CD), digital versatile disk (DVD)), a smart card, a flash memory device (e.g., card, stick, key drive), random access memory (RAM), read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), a register, a removable disk, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer.
  • a magnetic storage device e.g., hard disk, floppy disk, magnetic strip
  • an optical disk e.g., compact disk (CD), digital versatile disk (DVD)
  • a smart card e.g., a flash memory device (e.g., card, stick, key drive), random access memory (RAM), read only memory (ROM), programmable ROM
  • the computer-readable medium may also include, by way of example, a carrier wave, a transmission line, and any other suitable medium for transmitting software and/or instructions that may be accessed and read by a computer.
  • the computer-readable medium may be resident in the processing system, external to the processing system, or distributed across multiple entities including the processing system.
  • the computer- readable medium may be embodied in a computer-program product.
  • a computer-program product may include a computer-readable medium in packaging materials.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé et un appareil de résolution de conflits d'établissement d'appel entre un appel à commutation de paquet (PS) et un appel à commutation de circuits (CS). Par exemple, le procédé peut consister à : recevoir, d'un équipement d'utilisateur (UE), une première demande d'établissement d'un appel CS et une seconde demande d'établissement d'un appel PS, sensiblement en même temps (202) ; initier, en réponse à la première demande, un premier processus d'établissement d'appel pour l'appel CS (204) ; initier, en réponse à la seconde demande, un second processus d'établissement d'appel pour l'appel PS, l'initiation du second processus d'établissement d'appel étant retardé par rapport à l'initiation du premier processus d'établissement d'appel (206).
PCT/CN2014/084618 2014-08-18 2014-08-18 Procédés de retardement d'un domaine de réseau central lors de l'établissement simultané d'appels à commutation de circuits et à commutation de paquets WO2016026067A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/084618 WO2016026067A1 (fr) 2014-08-18 2014-08-18 Procédés de retardement d'un domaine de réseau central lors de l'établissement simultané d'appels à commutation de circuits et à commutation de paquets

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/084618 WO2016026067A1 (fr) 2014-08-18 2014-08-18 Procédés de retardement d'un domaine de réseau central lors de l'établissement simultané d'appels à commutation de circuits et à commutation de paquets

Publications (1)

Publication Number Publication Date
WO2016026067A1 true WO2016026067A1 (fr) 2016-02-25

Family

ID=55350060

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/084618 WO2016026067A1 (fr) 2014-08-18 2014-08-18 Procédés de retardement d'un domaine de réseau central lors de l'établissement simultané d'appels à commutation de circuits et à commutation de paquets

Country Status (1)

Country Link
WO (1) WO2016026067A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030232629A1 (en) * 2002-03-01 2003-12-18 Nortel Networks Limited System and method for providing a voice call waiting during an active data call
US20110021204A1 (en) * 2003-09-22 2011-01-27 Research In Motion Limited Methods And Apparatus For Prioritizing Voice Call Requests During Data Communication Sessions With A Mobile Device
CN103202089A (zh) * 2010-09-16 2013-07-10 苹果公司 用于控制无线设备中的多个无线电接入承载的重新配置的方法
US20130208628A1 (en) * 2012-02-15 2013-08-15 Apple Inc. Managing a packet service call during circuit service call setup within mobile communications user equipment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030232629A1 (en) * 2002-03-01 2003-12-18 Nortel Networks Limited System and method for providing a voice call waiting during an active data call
US20110021204A1 (en) * 2003-09-22 2011-01-27 Research In Motion Limited Methods And Apparatus For Prioritizing Voice Call Requests During Data Communication Sessions With A Mobile Device
CN103202089A (zh) * 2010-09-16 2013-07-10 苹果公司 用于控制无线设备中的多个无线电接入承载的重新配置的方法
US20130208628A1 (en) * 2012-02-15 2013-08-15 Apple Inc. Managing a packet service call during circuit service call setup within mobile communications user equipment

Similar Documents

Publication Publication Date Title
EP2885889B1 (fr) Procédés et appareils permettant d'économiser l'énergie pendant le décodage de blocs de transport dans les systèmes umts
US8761788B2 (en) Methods and apparatuses for data throughput optimization in DSDS scenarios
US9036548B2 (en) Apparatuses and methods for controlling access to a radio access network
EP2719112B1 (fr) Procédés et appareils pour des perfectionnements basés sur un équipement utilisateur d'une commande de liaison radio pour des transmissions sans fil multipoint
US20130260761A1 (en) Method and apparatus for supporting tune away in dual-sim dual standby mobile devices
KR102140051B1 (ko) VoLTE 호에서 UMTS PS 기반 음성 호로의 핸드오버
JP5619329B1 (ja) Cell_fachにおけるセル内のhs−dpcchでのdlトリガーcqiフィードバックのサポート
EP3039936B1 (fr) Procede et appareil pour ameliorer la performance de liaison montante à un équipement utilisateur
KR20160146708A (ko) 향상된 타이머 핸들링 메커니즘
US20130195027A1 (en) Method and Apparatus for Channel Fallback in Enhanced Cell Forward Access Channel Dedicated Channel
US20220030556A1 (en) Processing method and device
US9554360B2 (en) Apparatus and method for improving data throughput of a tune-away operation in a wireless communication system
CN112398585A (zh) 码本的生成方法及装置
WO2016026067A1 (fr) Procédés de retardement d'un domaine de réseau central lors de l'établissement simultané d'appels à commutation de circuits et à commutation de paquets
WO2020228631A1 (fr) Procédé et dispositif de traitement pour planification inter-créneaux
US9585064B2 (en) Method and apparatus for network cognizant uplink transmissions during IRAT handovers
WO2015168895A1 (fr) Appareil et procédés de validation d'un message de reconfiguration
WO2016029427A1 (fr) Techniques de réduction du temps d'établissement d'appel à commutation de circuits (cs) durant un processus de resélection ou de redirection de cellule
EP4178249A1 (fr) Procédé de transmission de données, procédé d'indication et dispositif
WO2016023165A1 (fr) Traitement d'une requête de configuration d'appel durant une procédure de changement d'emplacement
WO2015192350A1 (fr) Procédé et appareil pour réduire des échecs d'établissement d'appel durant une relocalisation d'un sous-système de réseau radio de desserte (srns)

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14900058

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14900058

Country of ref document: EP

Kind code of ref document: A1