Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/10—Connection setup
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
  • H04W4/10—Push-to-Talk [PTT] or Push-On-Call services
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/20—Manipulation of established connections
  • H04W76/27—Transitions between radio resource control [RRC] states
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/40—Connection management for selective distribution or broadcast
  • H04W76/45—Connection management for selective distribution or broadcast for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services

Definitions

• Embodiments relate to assisted state transitions of a user equipment (UE) for delay-sensitive applications within a wireless communications system.
• UE user equipment
• Wireless communication systems have developed through various generations, including a first-generation analog wireless phone service (1G), a second-generation (2G) digital wireless phone service (including interim 2.5G and 2.75G networks) and a third- generation (3G) high speed data / Internet-capable wireless service.
• 1G first-generation analog wireless phone service
• 2G second-generation digital wireless phone service
• 3G third- generation
• technologies including Cellular and Personal Communications Service (PCS) systems.
• Examples of known cellular systems include the cellular Analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), the Global System for Mobile access (GSM) variation of TDMA, and newer hybrid digital communication systems using both TDMA and CDMA technologies.
• CDMA Code Division Multiple Access
• FDMA Frequency Division Multiple Access
• TDMA Time Division Multiple Access
• GSM Global System for Mobile access
• newer hybrid digital communication systems using both TDMA and CDMA technologies
• the method for providing CDMA mobile communications was standardized in the United States by the Telecommunications Industry Association/Electronic Industries Association in TIA/EIA/IS-95-A entitled "Mobile Station-Base Station Compatibility Standard for Dual-Mode Wideband Spread Spectrum Cellular System," referred to herein as IS-95.
• Combined AMPS & CDMA systems are described in TIA/EIA Standard IS-98.
• Other communications systems are described in the IMT-2000/UM, or International Mobile Telecommunications System 2000/Universal Mobile Telecommunications System, standards covering what are referred to as wideband CDMA (W-CDMA), CDMA2000 (such as CDMA2000 lxEV-DO standards, for example) or TD-SCDMA.
• Node Bs also referred to as cell sites or cells
• UEs user equipments
• Node Bs provide entry points to an access network (AN) / radio access network (RAN), which is generally a packet data network using standard Internet Engineering Task Force (IETF) based protocols that support methods for differentiating traffic based on Quality of Service (QoS) requirements.
• AN access network
• RAN radio access network
• IP Internet Protocol
• Push-to-talk (PTT) capabilities are becoming popular with service sectors and consumers.
• PTT can support a "dispatch" voice service that operates over standard commercial wireless infrastructures, such as W-CDMA, CDMA, FDMA, TDMA, GSM, etc.
• endpoints e.g., UEs
• a dispatch call or simply a PTT call.
• a PTT call is an instantiation of a group, which defines the characteristics of a call.
• a group in essence is defined by a member list and associated information, such as group name or group identification.
• an application server receives a call message, from an originating user equipment (UE) that is configured to request initiation of a communication session, to be arbitrated by the application server, between the originating UE and at least one target UE.
• the application server selectively sends, in response to the call message, dummy data to a serving access network of a given UE associated with the communication session in order to facilitate a transition of the given UE to a dedicated-channel state.
• the application server can selectively send the dummy data based on a size of the call message and/or based on a type of the communication session.
• FIG. 1 is a diagram of a wireless network architecture that supports user equipments and radio access networks in accordance with at least one embodiment of the invention.
• FIG. 2A illustrates the core network of FIG. 1 according to an embodiment of the present invention.
• FIG. 2B illustrates an example of the wireless communications system of FIG. 1 in more detail.
• FIG. 3 is an illustration of user equipment in accordance with at least one embodiment of the invention.
• FIG. 4A illustrates a state decision process that is implemented at an application server within a wireless communication system.
• FIG. 4B illustrates an example implementation of a portion of the process of FIG. 4A in accordance with an embodiment of the invention.
• FIG. 4C illustrates an example implementation of a portion of the process of FIG. 4A in accordance with an embodiment of the invention.
• FIG. 4D illustrates an example implementation of another portion of the process of FIG. 4A in accordance with an embodiment of the invention.
• FIG. 4E illustrates an example implementation of another portion of the process of FIG. 4A in accordance with an embodiment of the invention.
• FIG. 4F illustrates an example implementation of a portion of the process of FIG. 4A in accordance with an embodiment of the invention.
• FIG. 4G illustrates an alternative implementation to the process of FIG. 4F in accordance with another embodiment of the invention.
• FIG. 4H illustrates another example implementation of a portion of the process of FIG. 4 A in accordance with an embodiment of the invention.
• a High Data Rate (HDR) subscriber station referred to herein as user equipment (UE), may be mobile or stationary, and may communicate with one or more access points (APs), which may be referred to as Node Bs.
• UE transmits and receives data packets through one or more of the Node Bs to a Radio Network Controller (RNC).
• RNC Radio Network Controller
• the Node Bs and RNC are parts of a network called a radio access network (RAN).
• RAN radio access network
• a radio access network can transport voice and data packets between multiple UEs.
• the radio access network may be further connected to additional networks outside the radio access network, such core network including specific carrier related servers and devices and connectivity to other networks such as a corporate intranet, the Internet, public switched telephone network (PSTN), a Serving General Packet Radio Services (GPRS) Support Node (SGSN), a Gateway GPRS Support Node (GGSN), and may transport voice and data packets between each UE and such networks.
• PSTN public switched telephone network
• GPRS General Packet Radio Services
• SGSN Serving General Packet Radio Services
• GGSN Gateway GPRS Support Node
• a UE that has established an active traffic channel connection with one or more Node Bs may be referred to as an active UE, and can be referred to as being in a traffic state.
• a UE that is in the process of establishing an active traffic channel (TCH) connection with one or more Node Bs can be referred to as being in a connection setup state.
• TCH active traffic channel
• a UE may be any data device that communicates through a wireless channel or through a wired channel.
• a UE may further be any of a number of types of devices including but not limited to PC card, compact flash device, external or internal modem, or wireless or wireline phone.
• the communication link through which the UE sends signals to the Node B(s) is called an uplink channel (e.g., a reverse traffic channel, a control channel, an access channel, etc.).
• the communication link through which Node B(s) send signals to a UE is called a downlink channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc.).
• traffic channel can refer to either an uplink / reverse or downlink/forward traffic channel.
• FIG. 1 illustrates a block diagram of one exemplary embodiment of a wireless communications system 100 in accordance with at least one embodiment of the invention.
• System 100 can contain UEs, such as cellular telephone 102, in communication across an air interface 104 with an access network or radio access network (RAN) 120 that can connect the access terminal 102 to network equipment providing data connectivity between a packet switched data network (e.g., an intranet, the Internet, and/or core network 126) and the UEs 102, 108, 110, 112.
• a packet switched data network e.g., an intranet, the Internet, and/or core network 126)
• the UE can be a cellular telephone 102, a personal digital assistant 108, a pager 110, which is shown here as a two-way text pager, or even a separate computer platform 112 that has a wireless communication portal.
• Embodiments of the invention can thus be realized on any form of access terminal including a wireless communication portal or having wireless communication capabilities, including without limitation, wireless modems, PCMCIA cards, personal computers, telephones, or any combination or sub-combination thereof.
• the term “UE” in other communication protocols may be referred to interchangeably as an "access terminal", “AT”, “wireless device”, “client device”, “mobile terminal”, “mobile station” and variations thereof.
• System 100 is merely exemplary and can include any system that allows remote UEs, such as wireless client computing devices 102, 108, 110, 112 to communicate over-the-air between and among each other and/or between and among components connected via the air interface 104 and RAN 120, including, without limitation, core network 126, the Internet, PSTN, SGSN, GGSN and/or other remote servers.
• remote UEs such as wireless client computing devices 102, 108, 110, 112 to communicate over-the-air between and among each other and/or between and among components connected via the air interface 104 and RAN 120, including, without limitation, core network 126, the Internet, PSTN, SGSN, GGSN and/or other remote servers.
• the RAN 120 controls messages (typically sent as data packets) sent to a RNC 122.
• the RNC 122 is responsible for signaling, establishing, and tearing down bearer channels (i.e., data channels) between a Serving General Packet Radio Services (GPRS) Support Node (SGSN) and the UEs 102/108/110/112. If link layer encryption is enabled, the RNC 122 also encrypts the content before forwarding it over the air interface 104.
• the function of the RNC 122 is well-known in the art and will not be discussed further for the sake of brevity.
• the core network 126 may communicate with the RNC 122 by a network, the Internet and/or a public switched telephone network (PSTN).
• PSTN public switched telephone network
• the RNC 122 may connect directly to the Internet or external network.
• the network or Internet connection between the core network 126 and the RNC 122 transfers data, and the PSTN transfers voice information.
• the RNC 122 can be connected to multiple Node Bs 124.
• the RNC 122 is typically connected to the Node Bs 124 by a network, the Internet and/or PSTN for data transfer and/or voice information.
• the Node Bs 124 can broadcast data messages wirelessly to the UEs, such as cellular telephone 102.
• the Node Bs 124, RNC 122 and other components may form the RAN 120, as is known in the art. However, alternate configurations may also be used and the invention is not limited to the configuration illustrated.
• the functionality of the RNC 122 and one or more of the Node Bs 124 may be collapsed into a single "hybrid" module having the functionality of both the RNC 122 and the Node B(s) 124.
• FIG. 2A illustrates the core network 126 according to an embodiment of the present invention.
• FIG. 2A illustrates components of a General Packet Radio Services (GPRS) core network implemented within a W-CDMA system.
• the core network 126 includes a Serving GPRS Support Node (SGSN) 160, a Gateway GPRS Support Node (GGSN) 165 and an Internet 175.
• SGSN Serving GPRS Support Node
• GGSN Gateway GPRS Support Node
• portions of the Internet 175 and/or other components may be located outside the core network in alternative embodiments.
• GPRS is a protocol used by Global System for Mobile communications (GSM) phones for transmitting Internet Protocol (IP) packets.
• GSM Global System for Mobile communications
• IP Internet Protocol
• the GPRS Core Network e.g., the GGSN 165 and one or more SGSNs 160
• the GPRS core network is an integrated part of the GSM core network, provides mobility management, session management and transport for IP packet services in GSM and W- CDMA networks.
• GTP GPRS Tunneling Protocol
• the GTP is the protocol which allows end users (e.g., access terminals) of a GSM or W-CDMA network to move from place to place while continuing to connect to the internet as if from one location at the GGSN 165. This is achieved transferring the subscriber's data from the subscriber's current SSGN 160 to the GGSN 165, which is handling the subscriber's session.
• GTP-U is used for transfer of user data in separated tunnels for each packet data protocol (PDP) context.
• PDP packet data protocol
• GTP-C is used for control signaling (e.g., setup and deletion of PDP contexts, verification of GSN reach-ability, updates or modifications such as when a subscriber moves from one SGSN to another, etc.).
• GTP' is used for transfer of charging data from GSNs to a charging function.
• the GGSN 165 acts as an interface between the GPRS backbone network (not shown) and the external packet data network 175.
• the GGSN 165 extracts the packet data with associated packet data protocol (PDP) format (e.g., IP or PPP) from the GPRS packets coming from the SGSN 160, and sends the packets out on a corresponding packet data network.
• PDP packet data protocol
• the incoming data packets are directed by the GGSN 165 to the SGSN 160 which manages and controls the Radio Access Bearer (RAB) of the destination UE served by the RAN 120.
• RAB Radio Access Bearer
• the GGSN 165 stores the current SGSN address of the target UE and his/her profile in its location register (e.g., within a PDP context).
• the GGSN is responsible for IP address assignment and is the default router for the connected UE.
• the GGSN also performs authentication and charging functions.
• the SGSN 160 is representative of one of many SGSNs within the core network 126, in an example. Each SGSN is responsible for the delivery of data packets from and to the UEs within an associated geographical service area. The tasks of the SGSN 160 includes packet routing and transfer, mobility management (e.g., attach/detach and location management), logical link management, and authentication and charging functions.
• the location register of the SGSN stores location information (e.g., current cell, current VLR) and user profiles (e.g., IMSI, PDP address(es) used in the packet data network) of all GPRS users registered with the SGSN 160, for example, within one or more PDP contexts for each user or UE.
• location information e.g., current cell, current VLR
• user profiles e.g., IMSI, PDP address(es) used in the packet data network
• SGSNs are responsible for (i) de-tunneling downlink GTP packets from the GGSN 165, (ii) uplink tunnel IP packets toward the GGSN 165, (iii) carrying out mobility management as UEs move between SGSN service areas and (iv) billing mobile subscribers.
• SGSNs configured for GSM/EDGE networks have slightly different functionality as compared to SGSNs configured for W-CDMA networks.
• the RAN 120 communicates with the SGSN 160 via a Iu interface, with a transmission protocol such as Frame Relay or IP.
• the SGSN 160 communicates with the GGSN 165 via a Gn interface, which is an IP-based interface between SGSN 160 and other SGSNs (not shown) and internal GGSNs, and uses the GTP protocol defined above (e.g., GTP-U, GTP-C, GTP', etc.). While not shown in FIG. 2A, the Gn interface is also used by the Domain Name System (DNS).
• the GGSN 165 is connected to a Public Data Network (PDN) (not shown), and in turn to the Internet 175, via a Gi interface with IP protocols either directly or through a Wireless Application Protocol (WAP) gateway.
• PDN Public Data Network
• WAP Wireless Application Protocol
• the PDP context is a data structure present on both the SGSN 160 and the GGSN 165 which contains a particular UE's communication session information when the UE has an active GPRS session.
• the UE When a UE wishes to initiate a GPRS communication session, the UE must first attach to the SGSN 160 and then activate a PDP context with the GGSN 165. This allocates a PDP context data structure in the SGSN 160 that the subscriber is currently visiting and the GGSN 165 serving the UE's access point.
• FIG. 2B illustrates an example of the wireless communications system 100 of FIG. 1 in more detail.
• UEs 1...N are shown as connecting to the RAN 120 at locations serviced by different packet data network end-points.
• the illustration of FIG. 2B is specific to W-CDMA systems and terminology, although it will be appreciated how FIG. 2B could be modified to confirm with a lx EV-DO system.
• UEs 1 and 3 connect to the RAN 120 at a portion served by a first packet data network end-point 162 (e.g., which may correspond to SGSN, GGSN, PDSN, a home agent (HA), a foreign agent (FA), etc.).
• a first packet data network end-point 162 e.g., which may correspond to SGSN, GGSN, PDSN, a home agent (HA), a foreign agent (FA), etc.
• the first packet data network end-point 162 in turn connects, via the routing unit 188, to the Internet 175 and/or to one or more of an authentication, authorization and accounting (AAA) server 182, a provisioning server 184, an Internet Protocol (IP) Multimedia Subsystem (IMS) / Session Initiation Protocol (SIP) Registration Server 186 and/or the application server 170.
• IP Internet Protocol
• IMS Internet Multimedia Subsystem
• SIP Session Initiation Protocol
• UEs 2 and 5...N connect to the RAN 120 at a portion served by a second packet data network end-point 164 (e.g., which may correspond to SGSN, GGSN, PDSN, FA, HA, etc.).
• the second packet data network end-point 164 in turn connects, via the routing unit 188, to the Internet 175 and/or to one or more of the AAA server 182, a provisioning server 184, an IMS / SIP Registration Server 186 and/or the application server 170.
• UE 4 connects directly to the Internet 175, and through the Internet 175 can then connect to any of the system components described above.
• UEs 1, 3 and 5...N are illustrated as wireless cell-phones, UE 2 is illustrated as a wireless tablet-PC and UE 4 is illustrated as a wired desktop station.
• the wireless communication system 100 can connect to any type of UE, and the examples illustrated in FIG. 2B are not intended to limit the types of UEs that may be implemented within the system.
• the AAA 182, the provisioning server 184, the IMS/SIP registration server 186 and the application server 170 are each illustrated as structurally separate servers, one or more of these servers may be consolidated in at least one embodiment of the invention.
• the application server 170 is illustrated as including a plurality of media control complexes (MCCs) 1...N 170B, and a plurality of regional dispatchers 1...N 170A.
• MCCs media control complexes
• the regional dispatchers 170A and MCCs 170B are included within the application server 170, which in at least one embodiment can correspond to a distributed network of servers that collectively functions to arbitrate communication sessions (e.g., half-duplex group communication sessions via IP unicasting and/or IP multicasting protocols) within the wireless communication system 100.
• the communication sessions arbitrated by the application server 170 can theoretically take place between UEs located anywhere within the system 100, multiple regional dispatchers 170A and MCCs are distributed to reduce latency for the arbitrated communication sessions (e.g., so that a MCC in North America is not relaying media back- and-forth between session participants located in China).
• the associated functionality can be enforced by one or more of the regional dispatchers 170A and/or one or more of the MCCs 170B.
• the regional dispatchers 170 A are generally responsible for any functionality related to establishing a communication session (e.g., handling signaling messages between the UEs, scheduling and/or sending announce messages, etc.), whereas the MCCs 170B are responsible for hosting the communication session for the duration of the call instance, including conducting an in-call signaling and an actual exchange of media during an arbitrated communication session.
• a UE 200 (here a wireless device), such as a cellular telephone, has a platform 202 that can receive and execute software applications, data and/or commands transmitted from the RAN 120 that may ultimately come from the core network 126, the Internet and/or other remote servers and networks.
• the platform 202 can include a transceiver 206 operably coupled to an application specific integrated circuit ("ASIC" 208), or other processor, microprocessor, logic circuit, or other data processing device.
• ASIC 208 or other processor executes the application programming interface ("API') 210 layer that interfaces with any resident programs in the memory 212 of the wireless device.
• API' application programming interface
• the memory 212 can be comprised of read-only or random-access memory (RAM and ROM), EEPROM, flash cards, or any memory common to computer platforms.
• the platform 202 also can include a local database 214 that can hold applications not actively used in memory 212.
• the local database 214 is typically a flash memory cell, but can be any secondary storage device as known in the art, such as magnetic media, EEPROM, optical media, tape, soft or hard disk, or the like.
• the internal platform 202 components can also be operably coupled to external devices such as antenna 222, display 224, push-to-talk button 228 and keypad 226 among other components, as is known in the art.
• an embodiment of the invention can include a UE including the ability to perform the functions described herein.
• the various logic elements can be embodied in discrete elements, software modules executed on a processor or any combination of software and hardware to achieve the functionality disclosed herein.
• ASIC 208, memory 212, API 210 and local database 214 may all be used cooperatively to load, store and execute the various functions disclosed herein and thus the logic to perform these functions may be distributed over various elements.
• the functionality could be incorporated into one discrete component. Therefore, the features of the UE 200 in FIG. 3 are to be considered merely illustrative and the invention is not limited to the illustrated features or arrangement.
• the wireless communication between the UE 102 or 200 and the RAN 120 can be based on different technologies, such as code division multiple access (CDMA), W-CDMA, time division multiple access (TDMA), frequency division multiple access (FDMA), Orthogonal Frequency Division Multiplexing (OFDM), the Global System for Mobile Communications (GSM), or other protocols that may be used in a wireless communications network or a data communications network.
• CDMA code division multiple access
• W-CDMA time division multiple access
• FDMA frequency division multiple access
• OFDM Orthogonal Frequency Division Multiplexing
• GSM Global System for Mobile Communications
• the data communication is typically between the client device 102, Node B(s) 124, and the RNC 122.
• the RNC 122 can be connected to multiple data networks such as the core network 126, PSTN, the Internet, a virtual private network, a SGSN, a GGSN and the like, thus allowing the UE 102 or 200 access to a broader communication network.
• voice transmission and/or data can be transmitted to the UEs from the RAN using a variety of networks and configurations. Accordingly, the illustrations provided herein are not intended to limit the embodiments of the invention and are merely to aid in the description of aspects of embodiments of the invention.
• embodiments of the invention are generally described in accordance with W-CDMA protocols and associated terminology (e.g., such as UE instead of mobile station (MS), mobile unit (MU), access terminal (AT), etc., RNC, contrasted with BSC in EV-DO, or Node B, contrasted with BS or MPT/BS in EV-DO, etc.).
• W-CDMA protocols e.g., such as UE instead of mobile station (MS), mobile unit (MU), access terminal (AT), etc., RNC, contrasted with BSC in EV-DO, or Node B, contrasted with BS or MPT/BS in EV-DO, etc.
• a session or call originator sends a request to initiate a communication session to the application server 170, which then forwards a call announcement message to the RAN 120 for transmission to one or more targets of the call.
• a session or call originator sends a request to initiate a communication session to the application server 170, which then forwards a call announcement message to the RAN 120 for transmission to one or more targets of the call.
• UEs User Equipments
• UMTS Universal Mobile Telecommunications Service
• UTRAN Universal Mobile Telecommunications Service
• RRC radio resource control
• the RAN 120 may direct UEs to transition between a number of RRC sub-states; namely, CELL PCH, URA PCH, CELL FACH, and CELL DCH states, which may be characterized as follows:
• a dedicated physical channel is allocated to the UE in uplink and downlink, the UE is known on a cell level according to its current active set, and the UE has been assigned dedicated transport channels, downlink and uplink (TDD) shared transport channels, and a combination of these transport channels can be used by the UE.
• TDD downlink and uplink
• the UE In the CELL FACH state, no dedicated physical channel is allocated to the UE, the UE continuously monitors a forward access channel (FACH), the UE is assigned a default common or shared transport channel in the uplink (e.g., a random access channel (RACH), which is a contention-based channel with a power ramp-up procedure to acquire the channel and to adjust transmit power) that the UE can transmit upon according to the access procedure for that transport channel, the position of the UE is known by RAN 120 on a cell level according to the cell where the UE last made a previous cell update, and, in TDD mode, one or several USCH or DSCH transport channels may have been established.
• FACH forward access channel
• RACH random access channel
• URA PCH State corresponds to a dormant state where the UE periodically wakes up to check a paging indicator channel (PICH) and, if needed, the associated downlink paging channel (PCH), and it may enter CELL FACH state to send a Cell Update message for the following event: cell reselection, periodical cell update, uplink data transmission, paging response, re-entered service area.
• PICH paging indicator channel
• PCH downlink paging channel
• CELL FACH State the UE may send messages on the random access channel (RACH), and may monitor a forward access channel (FACH).
• RACH random access channel
• FACH forward access channel
• the FACH carries downlink communication from the RAN 120, and is mapped to a secondary common control physical channel (S-CCPCH).
• S-CCPCH secondary common control physical channel
• the UE may enter CELL DCH state after a traffic channel (TCH) has been obtained based on messaging in CELL FACH state.
• TCH traffic channel
• R C radio resource control
• Communication sessions arbitrated by the application server 170 may be associated with delay-sensitive or high-priority applications and/or services.
• the application server 170 may correspond to a PTT server in at least one embodiment, and it will be appreciated that an important criterion in PTT sessions is fast session set-up as well as maintaining a given level of Quality of Service (QoS) throughout the session.
• QoS Quality of Service
• a given UE in RRC connected mode, can operate in either CELL DCH or CELL FACH to exchange data with the RAN 120, through which the given UE can reach the application server 170.
• uplink/downlink Radio bearers will consume dedicated physical channel resources (e.g., UL DCH, DL DCH, E-DCH, F-DPCH, HS-DPCCH etc). Some of these resources are even consumed for high speed shared channel (i.e., HSDPA) operations.
• HSDPA high speed shared channel
• uplink/downlink Radio bearers In CELL FACH state, uplink/downlink Radio bearers will be mapped to common transport channels (RACH/FACH). Thereby, in CELL FACH state there is no consumption of dedicated physical channel resources.
• the RAN 120 transitions the given UE between CELL FACH and CELL DCH based substantially on traffic volume, which is either measured at the RAN 120 (e.g., at the serving RNC 122 at the RAN 120) or reported from the given UE itself in one or more measurement reports.
• the RAN 120 can conventionally be configured to transition a particular UE to CELL DCH state from CELL FACH state when the UE's associated traffic volume as measured and/or reported in the uplink or as measured and/or reported in the downlink is higher than the one or more of the Event 4a thresholds used by the RAN 120 for making CELL DCH state transition decisions.
• the originating UE when an originating UE attempts to send a call request message to the application server 170 to initiate a communication session, the originating UE performs a cell update procedure, after which the originating UE transitions to either CELL FACH state or CELL DCH state. If the originating UE transitions to CELL FACH state, the originating UE can transmit the call request message on the RACH to the RAN 120. Otherwise, if the originating UE transitions to CELL DCH state, the originating UE can transmit the call request message on the reverse-link DCH or E-DCH to the RAN 120. Call request messages are generally relatively small in size, and are not typically expected to exceed the Event 4a threshold(s) used by the RAN 120 in determining whether to transition the originating UE to CELL DCH state.
• the originating UE can begin transmission of the call request message more quickly (e.g., because no radio link (RL) need be established between a serving Node B and serving RNC at the RAN 120, no LI synchronization procedure need be performed between the originating UE and the serving Node B, etc.) and no DCH- resources are consumed by the originating UE.
• the RACH is generally associated with lower data rates as compared to the DCH or E-DCH.
• the transmission of the call request message on the RACH may take a longer time to complete as compared to a similar transmission on the DCH or E-DCH in some instances. Accordingly, it is generally more efficient for the originating UE to send higher traffic volumes on the DCH or E-DCH as compared to the RACH, while smaller messages can be sent with relative efficiency on the RACH without incurring overhead from DCH set-up.
• the originating UE's state (e.g., CELL DCH or CELL FACH) is determined based on the amount of uplink data to be sent by the originating UE.
• the standard defines an Event 4a threshold for triggering a Traffic Volume Measurement (TVM) report.
• the Event 4a threshold is specified in the standard, and is used by the UE for triggering Traffic Volume Measurement Report, which summarizes the buffer occupancy of each uplink Radio Bearer.
• an uplink Event 4a threshold for triggering the state transition of a given UE to CELL DCH state
• a downlink Event 4a threshold for triggering the state transition of the given UE to CELL DCH state.
• the uplink and downlink Event 4a thresholds being 'undefined' in the standard means that the respective thresholds can vary from vendor to vendor, or from implementation to implementation at different RANs.
• the RNC 122 moves the UE to CELL DCH. In an example, this decision may be made based on the aggregated buffer occupancy or individual Radio Bearer buffer occupancy. If aggregated buffer occupancy is used for deciding the CELL DCH transition, the same threshold for triggering TVM can be used. Similarly, referring to the downlink Event 4a threshold, in CELL FACH state, if the downlink buffer occupancy of the Radio Bearers of the UE exceeds the downlink Event 4a threshold, the RNC 122 moves the UE to CELL DCH state. In an example, this decision may be done based on the aggregated buffer occupancy or individual Radio Bearer buffer occupancy.
• the size of the call request message can determine whether the originating UE is transitioned to CELL FACH state or CELL DCH state.
• one of the Event 4a thresholds is conventionally used to make the CELL DCH state determination at the RAN 120.
• the RAN 120 triggers the CELL DCH state transition of the UE.
• the processing speed or responsiveness of the RAN 120 itself can also affect whether the CELL DCH state or CELL FACH state is a more efficient option for transmitting the call request message. For example, if the RAN 120 is capable of allocating DCH resources to an originating UE within 10 milliseconds (ms) after receiving a cell update message, the CELL DCH state transition of the originating UE may be relatively fast so that transitions to DCH may be suitable for transmitting delay-sensitive call request messages.
• ms milliseconds
• the RAN 120 is capable of allocating DCH resources to an originating UE only after 100 milliseconds (ms) after receiving a cell update message, the CELL DCH state transition of the originating UE may be relatively slow, so that the transmission of the call request message may actually be completed faster on the RACH.
• the Event 4a threshold(s) are typically set high enough to achieve efficient resource utilization, as lower Event 4a thresholds will cause more frequent DCH resource allocations to UEs that do not necessarily require DCHs to complete their data exchange in a timely manner.
• data transmissions that do not exceed the Event 4a threshold can be transmitted more quickly either in CELL FACH state or CELL DCH state based on the processing speed of the RAN 120 and the amount of data to be transmitted.
• conventional RANs do not evaluate criteria aside from whether measured or reported traffic volume exceeds the Event 4a threshold(s) in making the CELL DCH state transition determination.
• a new feature referred to as a Traffic Volume Indicator is introduced, whereby the originating UE has the option of including the TVI within the cell update message during a cell update procedure.
• the RAN 120 will only transition the originating UE to CELL DCH state upon receipt of a Traffic Volume Measurement Report for Event 4a.
• embodiments of the invention are directed to an application server- assisted state transition, whereby an application server selectively sends a dummy packet to a given UE (e.g., an originating UE, a target UE, etc.).
• a given UE e.g., an originating UE, a target UE, etc.
• the application server 170 sets a size of the dummy packet to be greater than or equal to the downlink Event 4a threshold so that the RAN 120 is prompted to facilitate a CELL DCH state transition for the given UE.
• the application server 170 can control whether the RAN 120 transitions the given UE to CELL DCH based on whether the application server 170 sends the dummy packet thereto.
• FIGS. 4A-4H illustrate application server-assisted UE-state transition processes wherein the system 100 corresponds to a Universal Mobile Telecommunications System (UMTS) that uses Wideband Code Division Multiple Access (W-CDMA) in accordance with embodiments of the invention.
• UMTS Universal Mobile Telecommunications System
• W-CDMA Wideband Code Division Multiple Access
• FIGS. 4A-4H can be directed to communication sessions in accordance with protocols other than W-CDMA.
• certain signaling messages referred to herein are described whereby the application server 170 corresponds to a PTT server.
• other embodiments can be directed to servers providing services other than PTT to UEs of the system 100 (e.g., push-to-transfer (PTX) services, VoIP services, group-text sessions, etc.).
• PTX push-to-transfer
• FIG. 4A illustrates a state decision process that is implemented at the application server 170 within a wireless communication system.
• the application server 170 receives a call request message from a UE that is attempting to originate a communication session (e.g., a PTT communication session, etc.), 400A.
• the application server 170 determines whether to facilitate a transition of the originating UE to CELL DCH state, 405A.
• the determination of 405A can be automatic such that the application server 170 always determines to facilitate a transition of the originating UE to CELL DCH state upon receipt of a call request message.
• the determination of 405 A can be based on whether the application server 170 expects the originating UE to already be in CELL DCH state. For example, the application server 170 can evaluate a size of the call request message, and if the size of the call request message is above the uplink Event 4a threshold, then the application server 170 will assume the RAN 120 already transitioned the originating UE to CELL DCH state based on the uplink traffic volume of the call request message, and thereby determines not to facilitate the CELL DCH transition in 405 A.
• the application server 170 will assume the RAN 120 did not already transition the originating UE to CELL DCH state based on the uplink traffic volume of the call request message, and thereby determines to facilitate the CELL DCH transition in 405A.
• the application server 170 may also consider the roaming status of the UE in determining whether the UE is expected to be in CELL DCH state. For example, if the UE is in a roaming network with message sizes smaller than the threshold (assuming the application server 170 has such knowledge), the application server 170 will assume the UE is not yet transitioned to CELL DCH.
• the determination by the application server 170 regarding whether to transition the originating UE into CELL DCH state can be based upon a 'type' of the communication session (e.g., VoIP, PTX, PTT, etc.).
• the application server 170 can compare the determined type of the communication session with a given list of session types in order to determine whether to transition the originating UE to CELL DCH state in 405 A.
• the given list of session types can be established such that when the comparison indicates that the determined type is present on the given list, the application server 170 determines to facilitate a transition of the originating UE into CELL DCH state.
• the given list of session types may correspond to relatively delay- sensitive communication sessions, such as PTT or PTX sessions.
• the given list of session types can be established such that when the comparison indicates that the determined type is present on the given list, the application server 170 refrains from facilitating a transition of the originating UE into CELL DCH state.
• the given list of session types may correspond to communication sessions that are not particularly delay sensitive, such as conventional calls or VoIP sessions. [0065] Referring to FIG. 4A, if the application server 170 determines to facilitate the transition of the originating UE to CELL DCH state in 405 A, then the application server 170 sends a call request ACK to the originating UE in conjunction with a dummy packet, 41 OA.
• the dummy packet that is sent in 41 OA is configured to have a size at least equal to the downlink Event 4a threshold such that the RAN 120 is prompted to transition the originating UE to CELL DCH state. Otherwise, if the application server 170 determines not to facilitate the transition of the originating UE to CELL DCH state in 405A, then the application server 170 sends a call request ACK to the originating UE without a dummy packet, 415A.
• the application server 170 further determines whether to facilitate a transition of the at least one target UE to CELL DCH state, 420A.
• the determinations of 405A and 420A can be performed concurrently.
• the determination of 420A can be automatic such that the application server 170 always determines to facilitate a transition of the at least one target UE to CELL DCH state during call set-up.
• the determination of 420A can be based on whether the application server 170 expects the at least one target UE to be transitioned into CELL DCH state by the RAN 120 during call set-up based on an associated call announce message even in the absence of a dummy packet.
• the application server 170 can evaluate a size of the call announce message to be sent to the at least one target UE in 420A, and if the size of the call announce message is above the downlink Event 4a threshold used by the RAN to decide the transition to CELL DCH, then the application server 170 will assume the RAN 120 is going to transition the at least one target UE to CELL DCH state based on the downlink traffic volume of the call announce message, and thereby determines not to facilitate the CELL DCH transition in 420A.
• the application server 170 will assume the RAN 120 is not going to transition the at least one target UE to CELL DCH state based on the downlink traffic volume of the call announce message, and thereby determines to facilitate the CELL DCH transition in 420A.
• the determination by the application server 170 regarding whether to transition the at least one target UE into CELL DCH state can be based upon a 'type' of the communication session (e.g., VoIP, PTX, PTT, etc.).
• the application server 170 can compare the determined type of the communication session with a given list of session types in order to determine whether to transition the at least one target UE to CELL DCH state in 420A.
• the given list of session types can be established such that when the comparison indicates that the determined type is present on the given list, the application server 170 determines to facilitate a transition of the at least one target UE into CELL DCH state.
• the given list of session types may correspond to relatively delay-sensitive communication sessions, such as PTT or PTX sessions.
• the given list of session types can be established such that when the comparison indicates that the determined type is present on the given list, the application server 170 refrains from facilitating a transition of the at least one target UE into CELL DCH state.
• the given list of session types may correspond to communication sessions that are not particularly delay sensitive, such as conventional calls or VoIP sessions.
• the application server 170 determines to facilitate the transition of the at least one target UE to CELL DCH state in 420A, then the application server 170 locates the at least one target UE associated with the call request message and sends a call announce message to the at least one target UE in conjunction with a dummy packet, 425 A.
• the dummy packet that is sent in 425A is configured to have a size at least equal to the downlink Event 4a threshold such that the RAN 120 is prompted to transition the at least one target UE to CELL DCH state.
• the application server 170 determines not to facilitate the transition of the originating UE to CELL DCH state in 420A, then the application server 170 locates the at least one target UE associated with the call request message and sends a call announce message to the at least one target UE without a dummy packet, 430A (e.g., if the call announce message itself is already above the downlink Event 4a threshold).
• FIG. 4B illustrates an example implementation of a portion of the process of FIG. 4A in accordance with an embodiment of the invention.
• FIG. 4B illustrates an example of the process of FIG. 4A pertaining to the originating UE whereby the originating UE begins in CELL URA or CELL PCH state.
• a given UE (“originating UE") is operating in either URA PCH or CELL PCH state, 400B, that the originating UE receives a request to initiate a communication session to be arbitrated by the application server 170 (e.g., a user of the given UE pressing a PTT button), 408B, and that the originating UE determines to send a call request message for initiating the communication session on the RACH in CELL FACH state, 412B.
• the application server 170 e.g., a user of the given UE pressing a PTT button
• the originating UE After determining to transmit the call request message from the originating UE on the RACH in CELL FACH state in 412B, the originating UE configures a cell update message without a TVI so that the RAN 120 does not transition the originating UE to CELL DCH state, 416B. Accordingly, the originating UE transmits the cell update message without the TVI on the RACH to the RAN 120, 420B, and the RAN 120 responds to the cell update message by sending a cell update confirm message on the FACH that instructs the originating UE to transition into CELL FACH state, 424B.
• transitions from URA PCH or CELL PCH state into CELL FACH state do not require a radio link (RL) to be set-up between a serving Node B and a serving RNC at the RAN 120, such that the cell update confirm message of 424B can be sent relatively quickly as compared to a cell update message instructing a UE to transition to CELL DCH state).
• RL radio link
• the originating UE receives the cell update confirm message of 424B and transitions to CELL FACH state, 428B.
• the originating UE upon receiving a cell update confirm message from the RAN 120, the originating UE would respond with a cell update confirm response message, after which the originating UE would be permitted to send data on the RACH to the RAN 120.
• the originating UE and RAN 120 are configured to permit the originating UE to transmit data before the cell update confirm response message is sent. Examples of how the originating UE and the RAN 120 can be configured to facilitate this type of 'early' data transmission on the RACH are disclosed in U.S. Provisional Application No.
• the originating UE transmits a given number of call request messages on the RACH to the RAN 120, 432B.
• the RAN 120 receives at least one of these call request messages and forwards the call request message to the application server 170, 436B (e.g., as in 400A of FIG. 4A).
• FIG. 4B focuses on the selective CELL DCH state transition of the originating UE and not the target UE(s), and as such any decision logic related to a selective CELL DCH state transition of the target UE(s) has been omitted from FIG. 4B for the sake of clarity, and is discussed in more detail in other embodiments of the invention.
• the originating UE After sending the call request messages 1...N in 432B, the originating UE sends a cell update confirm response message on the RACH to the RAN 120, 444B.
• the transmission of the cell update confirm response message would conventionally occur prior to transmission of data on the RACH, whereas the originating UE and RAN 120 are specially configured to permit an 'early' transmission of data on the RACH in the embodiment of FIG. 4B.
• the application server 170 after decoding the call request message from 436B, the application server 170 sends a call request ACK to the RAN 120 for transmission to the originating UE, 448B.
• the RAN 120 receives the call request ACK from the application server 170 and transmits the call request ACK to the originating UE on the FACH, 452B. While the call request ACK is shown as occurring after the announce message is sent in 440B, it will be appreciated that the call request ACK can be sent concurrently with or before the announce message in other embodiments of the invention.
• the application server 170 is generally unaware of whether the originating UE is connected to the RAN 120 in CELL FACH state or CELL DCH state. However, to improve performance and reliability during the communication session, the application server 170 will generally desire to maintain the originating UE in CELL DCH state. Therefore, in an embodiment of the invention, the application server 170 determines whether to facilitate a transition of the originating UE of CELL DCH state in 456B (e.g., as in 405A of FIG. 4A).
• the application server 170 can evaluate the size of the call request message received at 436B to infer whether originating UE is expected to already be operating in CELL DCH state, and can determine to transition the originating UE to CELL DCH state if the call request message is not above the threshold.
• the determination of 456B can determine to transition the originating UE to CELL DCH state whenever a call request message is received, irrespective of the size of the call request message.
• the application server 170 may also consider the roaming status of the UE in determining whether the UE is expected to be in CELL DCH state.
• the application server 170 will assume the UE is not yet transitioned to CELL DCH.
• the application server 170 can evaluate a call-type of the communication session to determine whether to facilitate a transition of the originating UE into CELL DCH state in 456B.
• the application server 170 determines to facilitate the transition of the originating UE to CELL DCH state in 456B. Accordingly, the application server 170 sends a dummy packet to the RAN 120 for transmission to the originating UE, with the dummy packet having a size that is greater than or equal to an downlink Event 4a threshold, 460B. Thus, the dummy packet is set to be large enough (e.g., greater than or equal to an downlink Event 4a threshold) to trigger the RAN 120's own CELL DCH state transition mechanism for the originating UE.
• the RAN 120 (specifically, the serving RNC of the RAN 120) receives the dummy packet and determines to transition the originating UE to CELL DCH state based on the dummy packet causing the downlink traffic volume to rise above the downlink Event 4a threshold, 464B. Accordingly, after establishing a radio link (RL) between the serving Node B and the serving RNC at the RAN 120 for the DCH in 468B, the RAN 120 transmits a reconfiguration message to the originating UE over the FACH, 472B.
• RL radio link
• the reconfiguration message can correspond to a Radio Bearer (RB) reconfiguration message, a Transport Channel (TCH) Reconfiguration message or a Physical Channel (PCH) Reconfiguration message, based on whether the Radio Bearer, Transport Channel or Physical Channel is the higher layer of the originating UE to be reconfigured.
• RB Radio Bearer
• TCH Transport Channel
• PCH Physical Channel
• the originating UE receives the reconfiguration message and transitions to CELL DCH state and performs a LI synchronization procedure, 476B, after which the originating UE transmits a reconfiguration complete message on the DCH or E-DCH to the RAN 120, 480B.
• the RAN 120 then transmits the dummy packet to the originating UE on the DCH or HS-DSCH, 484B, and the originating UE decodes and then drops the dummy packet, 488B.
• FIG. 4C illustrates another example implementation of a portion of the process of FIG. 4A in accordance with an embodiment of the invention.
• FIG. 4C illustrates an example of the process of FIG. 4A pertaining to the originating UE whereby the originating UE begins in CELL FACH state.
• a given UE (“originating UE") is operating in CELL FACH state, 400C, and that the originating UE receives a request to initiate a communication session to be arbitrated by the application server 170 (e.g., a user of the given UE pressing a PTT button), 404C, and that the originating UE determines to send a call request message for initiating the communication session on the RACH in CELL FACH state, 408C.
• FIG. 4C omits the steps of exchanging a cell update message, cell update confirm message and cell update confirm response message as in 420B, 424B and 444B of FIG. 4B.
• FIG. 4C substantially corresponds to FIG. 4B and will not be described further for the sake of brevity.
• 412C - 464C of FIG. 4C correspond to 432B - 440B and 448B - 488B of FIG. 4B, respectively.
• FIG. 4D illustrates an example implementation of another portion of the process of FIG. 4A in accordance with an embodiment of the invention.
• FIG. 4D illustrates an example of the process of FIG. 4A pertaining to the target UE whereby the target UE begins in CELL URA or CELL PCH state.
• target UE a given UE
• the application server 170 receives a call request message from an originating UE (not shown), 404D. Accordingly, the application server 170 sends an announce message to the RAN 120 for transmission to the target UE, 408D.
• the application server 170 is generally unaware of whether the target UE is connected to the RAN 120 in CELL FACH state or CELL DCH state. However, to improve performance and reliability during the communication session, the application server 170 will generally desire to maintain the target UE in CELL DCH state. Therefore, in an embodiment of the invention, the application server 170 determines whether to facilitate a transition of the target UE of CELL DCH state in 412D.
• the application server 170 can evaluate the size of the call announce message sent at 408D to infer whether target UE is expected to be transitioned to CELL DCH state by the RAN 120, and can determine to further facilitate the transition of the target UE to CELL DCH state if the call announce message is not above the threshold.
• the determination of 412D can determine to transition the target UE to CELL DCH state whenever a call announce message is transmitted, irrespective of the size of the call announce message.
• the application server 170 may also consider the roaming status of the UE in determining whether the UE is expected to be in CELL DCH state.
• the application server 170 will assume the UE is not yet transitioned to CELL DCH.
• the application server 170 can evaluate a call-type of the communication session to determine whether to facilitate a transition of the at least one target UE into CELL DCH state in 412D.
• the application server 170 determines to facilitate the transition of the target UE to CELL DCH state in 412D. Accordingly, the application server 170 sends a dummy packet to the RAN 120 for transmission to the target UE, with the dummy packet having a size that is greater than or equal to a downlink Event 4a threshold, 416D. Upon receiving the call announce message from 408D, the RAN 120 pages the target UE because the target UE is in URA PCH state or CELL PCH state, 420D.
• the target UE decodes the page from 420D and transitions to CELL FACH state, 424D, and the target UE sends a cell update message to the RAN 120 over the RACH, 428D.
• the RAN 120 determines to transition the target UE to CELL DCH state because the downlink traffic volume is above the downlink Event 4a threshold based at least in part on the dummy packet from 416D. Accordingly, the RAN 120 sets up a RL connection between a serving RNC and serving Node B for the target UE, 436D, and then transmits a cell update confirm message on the FACH to the target UE that instructs the target UE to transition to CELL DCH state, 440D.
• the cell update confirm message can correspond to a radio bearer (RB) reconfiguration message, a Transport Channel (TCH) Reconfiguration message or a Physical Channel (PCH) Reconfiguration message, based on whether the Radio Bearer, Transport Channel or Physical Channel is the higher layer of the target UE to be reconfigured.
• RB radio bearer
• TCH Transport Channel
• PCH Physical Channel
• the target UE receives the cell update confirm message and transitions to CELL DCH state and performs a LI synchronization procedure, 444D, after which the target UE transmits a cell update confirm response message on the DCH or E-DCH to the RAN 120, 448D.
• FIG. 4E illustrates an example implementation of another portion of the process of FIG. 4A in accordance with an embodiment of the invention.
• FIG. 4E illustrates an example of the process of FIG. 4A pertaining to the target UE whereby the target UE begins in CELL_URA or CELL PCH state.
• FIG. 4E shows the application server 170 determining whether to transition the target UE to CELL DCH state after an announce ACK is received from the target UE instead of when the call announce message is sent to the target UE as in FIG. 4D.
• target UE a given UE
• the application server 170 receives a call request message from an originating UE (not shown), 404E. Accordingly, the application server 170 sends an announce message to the RAN 120 for transmission to the target UE, 408E.
• the RAN 120 Upon receiving the call announce message from 408E, the RAN 120 pages the target UE because the target UE is in URA PCH state or CELL PCH state, 412E.
• the target UE decodes the page from 412E and transitions to CELL FACH state, 416E, and the target UE sends a cell update message to the RAN 120 over the RACH, 420E.
• the RAN 120 determines not to transition the target UE to CELL DCH state because the downlink traffic volume is not above the downlink Event 4a threshold.
• the RAN 120 need not set-up a RL connection between a serving RNC and serving Node B for the target UE, and instead transmits N call announce messages on the FACH at a given interval to the target UE, 428E.
• the RAN 120 transmits a cell update confirm message on the FACH to the target UE that instructs the target UE to transition to remain in CELL FACH state, 432E
• the cell update confirm message can correspond to a radio bearer (RB) reconfiguration message, a Transport Channel (TCH) Reconfiguration message or a Physical Channel (PCH) Reconfiguration message, based on whether the Radio Bearer, Transport Channel or Physical Channel is the higher layer of the target UE to be reconfigured.
• RB radio bearer
• TCH Transport Channel
• PCH Physical Channel
• the RAN 120 upon receiving a cell update message from the target UE, the RAN 120 would respond with a cell update confirm message, after which the RAN 120 would be permitted to send data on the FACH to the target UE.
• the target UE and RAN 120 are configured to permit the RAN 120 to transmit data before the cell update confirm message is sent. Examples of how the target UE and the RAN 120 can be configured to facilitate this type of 'early' data transmission on the FACH is disclosed in U.S. Provisional Application No.
• the target UE responds to the cell update confirm message by sending a cell update confirm response message back to the RAN 120 on the RACH, 436E, and the target UE responds to the call announce message from 428E by sending an announce ACK message to the RAN 120 on the RACH, 440E, which is then forwarded by the RAN 120 to the application server 170, 444E.
• the application server 170 receives the announce ACK message and determines whether to facilitate a transition of the target UE of CELL DCH state in 448E. For example, the application server 170 can evaluate the size of the call announce message sent at 408E and/or the announce ACK message received at 448E to infer whether the target UE is expected to be already be operating in CELL DCH state. Then the application server 170 can determine to further facilitate the transition of the target UE to CELL DCH state if each of these messages is not above the threshold. In a further example, in addition to the size of the call request message, the application server 170 may also consider the roaming status of the UE in determining whether the UE is expected to be in CELL DCH state.
• the application server 170 will assume the UE is not yet transitioned to CELL DCH.
• the determination of 448E can determine to transition the target UE to CELL DCH state whenever an announce ACK message is received from a target UE, irrespective of the size of the call announce message or announce ACK message.
• the application server 170 can evaluate a call-type of the communication session to determine whether to facilitate a transition of the at least one target UE into CELL DCH state in 448E.
• the application server 170 determines to facilitate the transition of the target UE to CELL DCH state in 448E. Accordingly, the application server 170 sends a dummy packet to the RAN 120 for transmission to the target UE, with the dummy packet having a size that is greater than or equal to a downlink Event 4a threshold, 452E.
• the RAN 120 receives the dummy packet and determines to transition the target UE to CELL DCH state based on the downlink traffic volume for the target UE being above the downlink Event 4a threshold, 456E.
• the RAN 120 sets up a RL between the serving RNC and serving Node B for the target UE, 460E, and then the RAN 120 sends a reconfiguration message on the FACH to the target UE that instructs the target UE to transition to CELL DCH state, 464E.
• the target UE receives the reconfiguration message and transitions to CELL DCH state and performs a LI synchronization procedure, 468E, after which the target UE transmits a reconfiguration complete message on the DCH or E-DCH to the RAN 120, 472E.
• FIG. 4F illustrates another example implementation of a portion of the process of FIG. 4A in accordance with an embodiment of the invention.
• FIG. 4F is similar to FIG. 4D except that the target UE is assumed to begin in CELL FACH state instead of URA PCH state or CELL PCH state.
• FIG. 4F unlike FIG. 4D, assume that a given UE ("target UE") is operating in either CELL FACH state, 400F.
• 404F through 416F correspond to 404D through 416D of FIG. 4D, respectively, and as such will not be described further for the of brevity.
• the RAN 120 transmits the call announce message to the target UE N times at a given interval on the FACH, 420F.
• a header portion of the call announce message transmissions of 420F can be configured to include a cell identifier for the target UE (e.g., C-RNTI).
• the RAN 120 determines to transition the target UE to CELL DCH state because the downlink traffic volume is above the downlink Event 4a threshold based at least in part on the dummy packet from 416F, 424F. Accordingly, the RAN 120 sets up a RL connection between a serving RNC and serving Node B for the target UE, 428F.
• the target UE After decoding at least one of the call announce messages from 420F, the target UE responds to the call announce message by sending an announce ACK message on the RACH to the RAN 120, 432F, and the RAN 120 forwards the announce ACK message to the application server 170, 436F.
• the RAN 120 sends a reconfiguration message (e.g., a radio bearer (RB) reconfiguration message, a Transport Channel (TCH) Reconfiguration message or a Physical Channel (PCH) Reconfiguration message, based on whether the Radio Bearer, Transport Channel or Physical Channel is the higher layer of the target UE to be reconfigured) to the target UE on the FACH that instructs the target UE to transition to CELL DCH state, 440F.
• a reconfiguration message e.g., a radio bearer (RB) reconfiguration message, a Transport Channel (TCH) Reconfiguration message or a Physical Channel (PCH) Reconfiguration message, based on whether the Radio Bearer, Transport Channel or Physical Channel is the higher layer of the target UE to be reconfigured
• the target UE receives the reconfiguration message and transitions to CELL DCH state and performs a LI synchronization procedure, 444F, after which the target UE transmits a reconfiguration complete message on the DCH or E-DCH to the RAN 120, 448F.
• the dummy- packet decision of CELL DCH state transition decision of 420A of FIG. 4A for the target UE occurs in conjunction in with the transmission of the call announce message.
• FIG. 4F demonstrates an example whereby the announce ACK is sent on the RACH before the reconfiguration complete message is sent by the target UE and while the target UE is still in CELL FACH state 400G.
• FIG. 4G illustrates an alternative implementation to the process of FIG. 4F, whereby the announce ACK is transmitted from the target UE only after the reconfiguration complete message is sent. Accordingly, in FIG. 4G, the announce ACK transmission of 432F and 436F from FIG. 4F is not performed. Instead, after the target UE transmits the reconfiguration complete message in 440G (e.g., as in 448F of FIG. 4F), the announce ACK message is sent in 444G and 448G.
• FIG. 4G is otherwise similar to FIG. 4F and related elements (e.g., 452G and 456G) will not be described further for the sake of brevity.
• FIG. 4H illustrates another example implementation of a portion of the process of FIG. 4A in accordance with an embodiment of the invention.
• FIG. 4H is similar to FIG. 4E except that the target UE is assumed to begin in CELL FACH state instead of URA PCH state or CELL PCH state.
• FIG. 4H unlike FIG. 4E, assume that a given UE ("target UE") is operating in either CELL FACH state, 400H.
• the application server 170 receives a call request message from an originating UE (not shown), 404H. Accordingly, the application server 170 sends an announce message to the RAN 120 for transmission to the target UE, 408H.
• the RAN 120 Upon receiving the call announce message from 408H, the RAN 120 determines not to transition the target UE to CELL DCH state because the downlink traffic volume is not above the downlink Event 4a threshold, 412H. Also, because the target UE is already in CELL FACH state, the RAN 120 transmits N call announce messages on the FACH at a given interval to the target UE, 416H.
• the remainder of FIG. 4H is otherwise similar to FIG. 4E and will not be described further for the sake of brevity.
• 420H through 460H of FIG. 4H correspond to 440E through 480E of FIG. 4E, respectively.
• DSP digital signal processor
• ASIC application specific integrated circuit
• FPGA field programmable gate array
• a general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
• a processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
• a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
• An exemplary storage medium is coupled to the processor such that the processor can read information from, and write information to, the storage medium.
• the storage medium may be integral to the processor.
• the processor and the storage medium may reside in an ASIC.
• the ASIC may reside in a user terminal (e.g., access terminal).
• the processor and the storage medium may reside as discrete components in a user terminal.
• the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
• Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
• a storage media may be any available media that can be accessed by a computer.
• such computer- readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
• any connection is properly termed a computer-readable medium.
• the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
• the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
• Disk and disc includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Landscapes

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

Applications Claiming Priority (3)

Publications (1)

Family

ID=43827843

Family Applications (1)

Country Status (5)

Families Citing this family (2)

Family Cites Families (10)

• 2011
  • 2011-02-09 WO PCT/US2011/024232 patent/WO2011103008A1/en active Application Filing
  • 2011-02-09 CN CN201410710311.7A patent/CN104394517A/zh active Pending
  • 2011-02-09 JP JP2012552961A patent/JP5650764B2/ja not_active Expired - Fee Related
  • 2011-02-09 EP EP11706073A patent/EP2537388A1/de not_active Withdrawn
  • 2011-02-09 CN CN201180008458.6A patent/CN102763483B/zh not_active Expired - Fee Related
  • 2011-02-09 KR KR1020127024284A patent/KR101413772B1/ko not_active IP Right Cessation
  • 2011-02-09 KR KR1020147005791A patent/KR101417724B1/ko not_active IP Right Cessation
• 2014
  • 2014-02-27 JP JP2014036436A patent/JP5784162B2/ja not_active Expired - Fee Related

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events