1. Technical Field
This application relates to mobile telecommunications systems in general, having particular application in UMTS (Universal Mobile Telecommunications System) in general, and in particular relates to an apparatus and method for transmitting messages in mobile telecommunications system user equipment.
2. Description of the Related Art
In a typical cellular radio system, mobile user equipment (UE) communicates via a radio access radio network (RAN) with one or more core networks.
Embodiments will now be described, by way of example only, with reference to the attached drawings, in which:
The method relates to transmitting a sequence of messages from a wireless telecommunications device to a telecommunications network. The sequence of messages comprises a plurality of messages that are to be transmitted at specified times relative to each other. For instance, the sequence of messages may comprise a plurality of messages each of which is to be sent X seconds after the previous one e.g. message 1 at 0 s, message 2 at X seconds, message 3 at 2X seconds etc. The method has particular application to a sequence of messages that are intended to terminate or release a radio connection between the device and the network, particularly in response to a command from the network to terminate the radio connection. The method comprises transmitting a message of the sequence of messages and turning off the transmitter or the receiver or both after transmission of at least one of the messages in the sequence of messages. The method also comprises transmitting a message of the sequence of messages and then turning off at least one of the transmitter and receiver of the device for a set period of time. At the end of the set period of time, the device then turns on whichever of the transmitter and receiver that was previously turned off, in preparation for transmitting a second message at a specified time. The second message is then transmitted and the process repeated, typically at least one of the transmitter and receiver being turned off between transmissions of the messages. This means that the device does not use power powering either the transmitter or the receiver or both during this set period and so battery power may be saved.
The sequence of messages may comprise a first message and one or more messages including a repetition of at least part of the first message.
Typically the device turns on the transmitter or receiver or both at a time relative to the specified time for transmitting the next message e.g. X seconds before the next message is scheduled to be transmitted. That is the transmitter or receiver or both is turned off for a specified time that is defined relative to the specified time for transmitting a next message.
Whether one or both of the transmitter and receiver is turned off during the period will determine the extent of the power savings made. It is believed that turning off the transmitter alone saves more power than turning off the receiver alone. Typical implementations may therefore comprise turning off the transmitter between transmissions and leaving the receiver turned on or turning off both the transmitter and receiver between transmissions. Although, as described above, the transmitter or receiver or both is turned off each time a message is transmitted, power savings (albeit less) may be made by turning off the transmitter or receiver or both in response to the transmission of at least one message in the sequence of messages.
The method is applicable to any wireless telecommunications device in which a sequence of messages is to be transmitted. In typical implementations, no other messages are to be transmitted by the device during the period in which the transmitter or receiver or both is turned off. The method is particularly applicable when the device is to transmit a sequence of messages in an unacknowledged mode i.e. a mode in which the device does not monitor for an acknowledgement from the network of receipt of the message from the device. In addition the method is particularly applicable when the device is in a state such that further messages from the network are not expected during the period in which the sequence of messages is to be transmitted. An example of such a state is when the radio resources of the device are being released, subsequent to a command from the network.
Such a wireless telecommunications device, typically known in the art as user equipment (UE), comprises various types of equipment such as mobile telephones (also known as cellular or cell phones), lap tops with wireless communication capability, personal digital assistants (PDAs) etc. These may be portable, hand held, pocket sized, installed in a vehicle etc and communicate voice or data signals or both with the radio access network.
The idea will now be described further in relation to a third generation wireless telecommunications system known generally as UMTS (Universal Mobile Telecommunications System), and in particular a system that complies with standards as defined by the Third Generation Partnership Project (3GPP). 3GPP has defined many telecommunications standards and reference will now be made to the following one in particular: 3GPP Technical Specification 25.331 which is hereby incorporated by reference in its entirety. Version 3.15.0 Release 99 will be considered. However it is to be appreciated that the method is applicable to other versions and subsequent updates and to any wireless system in which a sequence of messages as discussed above is to be transmitted.
3GPP TS 25.331 v.3.15.0 section 8.1.4 relates to the procedure to release the radio resource control connection between a wireless telecommunications device (known as user equipment or UE) and the network. This is known as Radio Resource Control (abbreviated to RRC) Connection Release. According to section 8.1.4.2, when the UE is in one of two states (CELL_DCH or CELL_FACH) then the UTRAN may at any time initiate a RRC connection release by transmitting a message known as a “RRC CONNECTION RELEASE” message. When the UE receives a “RRC CONNECTION RELEASE” message, and the UE is in one of the above two states, then the UE acts on the message and ultimately sends a message known as a “RRC CONNECTION RELEASE COMPLETE” message to the network to confirm that the RRC connection has been released.
Section 8.1.4.3 sets out how the UE operates in response to the receipt of a “RRC CONNECTION RELEASE” message from the network. Various scenarios are described and we shall now refer to the situation in which the UE receives the first “RRC CONNECTION RELEASE” message and is in the state CELL_DCH (e.g. a speech call is being terminated). In this state, the device operates in an Unacknowledged Mode (UM). Section 8.1.4.6 is also relevant to when the device is in this state and mode. The operation of the device in this state is shown in
Once the timer has expired (action 208 being answered in the affirmative), the counter V308 is incremented by one, action 210. The device then compares the value of the counter with the value of a parameter known as N308, action 212. This parameter N308 is defined in an Information Element sent by the network and, according to TS 25.331 v.3.15.0, is an integer between 1 and 8. If the value of V308 is equal to or smaller than N308, action 212, then the device retransmits (action 204) the “RRC CONNECTION RELEASE COMPLETE” message, albeit with the possibility of carrying out some modifications to information elements in the “RRC CONNECTION RELEASE COMPLETE” message. The process then repeats until at action 212 the value of the counter is greater than the value of the parameter, at which time the device releases its radio resources and enters idle mode, action 214, and the RRC connection release process at the UE ends, action 216.
The UE then turns off the transmitter or receiver or both of the device, action 110. The device then waits for a period, action 112. At the end of this period, the device then turns on the transmitter or receiver or both that had previously been turned off, action 114. The device then undertakes standard actions to carry out power measurements etc. required before further transmissions may be undertaken. The period of action 112 is typically set to be less than the period defined by the timer T308. For example, if T308 is set to be 160 ms then the period set in action 112 is less than this (say 60 ms) so that the device has time (100 ms) to stabilise transmission power before the next transmission of a “RRC CONNECTION RELEASE COMPLETE” message. The period may be defined to be relative to T308, for instance X ms less than T308, where X is sufficient for stabilisation of the transmission power. This allows the device to re-establish the Dedicated Physical Channel (DPCH) in time and preparation for the re-transmission of the next “RRC CONNECTION RELEASE COMPLETE” message (the “RRC CONNECTION RELEASE COMPLETE” messages are transmitted on a Dedicated Control Channel DCCH mapped to DPCH or E-DCH).
Once the timer has expired (action 208 being answered in the affirmative), the counter V308 is incremented by one, action 210. The device then compares the value of the counter with the value of a parameter known as N308, action 212. If the value of V308 is equal to or smaller than N308, action 212, then the device retransmits (action 204) the “RRC CONNECTION RELEASE COMPLETE” message, albeit with the possibility of carrying out some modifications to information elements in the “RRC CONNECTION RELEASE COMPLETE” message. The process then repeats until at action 212 the value of the counter is greater than the value of the parameter, at which time the device releases its radio resources and enters idle mode, action 214, and the RRC connection release process ends at the UE, action 216.
Thus the device transmits a first “RRC CONNECTION RELEASE COMPLETE” message of a sequence of “RRC CONNECTION RELEASE COMPLETE” messages. The device then turns off at least one of the transmitter and receiver of the device for a period of time. The device then turns on at least one of the transmitter and receiver of the device at the end of the period of time in preparation for transmitting a second “RRC CONNECTION RELEASE COMPLETE” message at a specified time. The device then transmits the second “RRC CONNECTION RELEASE COMPLETE” message at the specified time. This repeats until all “RRC CONNECTION RELEASE COMPLETE” messages in the sequence of “RRC CONNECTION RELEASE COMPLETE” messages as defined by the parameter N308 have been transmitted and then the method concerned herein ends.
The method illustrated in
The power savings provided by this method are cumulative: the greater the number of messages in the sequence of messages to be transmitted, the greater the power savings; also the greater the period in action 112, the greater the power savings. This may be illustrated by considering
In
In
In
As can be seen from
The method has been described in relation to 3GPP Technical Specification 25.331 and Version 3.15.0 Release 99 in particular, which are hereby incorporated by reference in their entirety. Subsequent versions of Technical Specification 25.331 refer to a Dedicated Channel known as E-DCH and the method is also applicable to this scenario as well as other versions and subsequent updates and to any wireless system in which a sequence of messages for terminating a radio connection are to be transmitted from the UE.
The radio network controller controls the use and reliability of the radio resources within the RNS 2. Each RNC may also connected to a 3G mobile switching centre 10 (3G MSC) and a 3G serving GPRS support node 12 (3G SGSN).
An RNC 4 controls one or more Node B's. An RNC plus its Node B's together make up an RNS 2. A Node B controls one or more cells. Each cell is uniquely identified by a frequency and a primary scrambling code (primary CPICH in FDD, primary CCPCH in TDD).
Generally in UMTS a cell refers to a radio network object that can be uniquely identified by a UE from a cell identifier that is broadcast over geographical areas from a UTRAN access point. A UTRAN access point is a conceptual point within the UTRAN performing radio transmission and reception. A UTRAN access point is associated with one specific cell i.e., there exists one UTRAN access point for each cell. It is the UTRAN-side end point of a radio link. A single physical Node B 6 may operate as more than one cell since it may operate at multiple frequencies and/or with multiple scrambling codes.
The strategies for an apparatus and method for transmitting messages in mobile telecommunications system user equipment as discussed above with reference to the drawings may be implemented by the RRC block 832.
Turning now to
Where mobile station 900 is enabled for two-way communication, it will incorporate a communication subsystem 911, including both a receiver 912 and a transmitter 914, as well as associated components such as one or more, preferably embedded or internal, antenna elements 916 and 918, local oscillators (LOs) 913, and a processing module such as a digital signal processor (DSP) 920. As will be apparent to those skilled in the field of communications, the particular design of the communication subsystem 911 will be dependent upon the communication network in which the device is intended to operate. For example, mobile station 900 may include a communication subsystem 911 designed to operate within the Mobitex™ mobile communication system, the DataTAC™ mobile communication system, GPRS network, UMTS network, or EDGE network.
Network access requirements will also vary depending upon the type of network 902. For example, in the Mobitex and DataTAC networks, mobile station 900 is registered on the network using a unique identification number associated with each mobile station. In UMTS and GPRS networks, however, network access is associated with a subscriber or user of mobile station 900. A GPRS mobile station therefore requires a subscriber identity module (SIM) card in order to operate on a GPRS network. Without a valid SIM card, a GPRS mobile station will not be fully functional. Local or non-network communication functions, as well as legally required functions (if any) such as “911” emergency calling, may be available, but mobile station 900 will be unable to carry out any other functions involving communications over the network 902. The SIM interface 944 is normally similar to a card-slot into which a SIM card can be inserted and ejected like a diskette or PCMCIA card. The SIM card can have approximately 64K of memory and hold many key configuration 951, and other information 953 such as identification, and subscriber related information.
When required network registration or activation procedures have been completed, mobile station 900 may send and receive communication signals over the network 902. Signals received by antenna 916 through communication network 902 are input to receiver 912, which may perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection and the like, and in the example system shown in
Mobile station 900 preferably includes a microprocessor 938 which controls the overall operation of the device. Communication functions, including at least data and voice communications, are performed through communication subsystem 911. Microprocessor 938 also interacts with further device subsystems such as the display 922, flash memory 924, random access memory (RAM) 926, auxiliary input/output (I/O) subsystems 928, serial port 930, keyboard 932, speaker 934, microphone 936, a short-range communications subsystem 940 and any other device subsystems generally designated as 942.
Some of the subsystems shown in
Operating system software used by the microprocessor 938 is preferably stored in a persistent store such as flash memory 924, which may instead be a read-only memory (ROM) or similar storage element (not shown). Those skilled in the art will appreciate that the operating system, specific device applications, or parts thereof, may be temporarily loaded into a volatile memory such as RAM 926. Received communication signals may also be stored in RAM 926.
As shown, flash memory 924 can be segregated into different areas for both computer programs 958 and program data storage 950, 952, 954 and 956. These different storage types indicate that each program can allocate a portion of flash memory 924 for their own data storage requirements. Microprocessor 938, in addition to its operating system functions, preferably enables execution of software applications on the mobile station. A predetermined set of applications that control basic operations, including at least data and voice communication applications for example, will normally be installed on mobile station 900 during manufacturing. A preferred software application may be a personal information manager (PIM) application having the ability to organize and manage data items relating to the user of the mobile station such as, but not limited to, e-mail, calendar events, voice mails, appointments, and task items. Naturally, one or more memory stores would be available on the mobile station to facilitate storage of PIM data items. Such PIM application would preferably have the ability to send and receive data items, via the wireless network 902. In a preferred embodiment, the PIM data items are seamlessly integrated, synchronized and updated, via the wireless network 902, with the mobile station user's corresponding data items stored or associated with a host computer system. Further applications may also be loaded onto the mobile station 900 through the network 902, an auxiliary I/O subsystem 928, serial port 930, short-range communications subsystem 940 or any other suitable subsystem 942, and installed by a user in the RAM 926 or preferably a non-volatile store (not shown) for execution by the microprocessor 938. Such flexibility in application installation increases the functionality of the device and may provide enhanced on-device functions, communication-related functions, or both. For example, secure communication applications may enable electronic commerce functions and other such financial transactions to be performed using the mobile station 900.
In a data communication mode, a received signal such as a text message or web page download will be processed by the communication subsystem 911 and input to the microprocessor 938, which preferably further processes the received signal for output to the display 922, or alternatively to an auxiliary I/O device 928. A user of mobile station 900 may also compose data items such as email messages for example, using the keyboard 932, which is preferably a complete alphanumeric keyboard or telephone-type keypad, in conjunction with the display 922 and possibly an auxiliary I/O device 928. Such composed items may then be transmitted over a communication network through the communication subsystem 911.
For voice communications, overall operation of mobile station 900 is similar, except that received signals would preferably be output to a speaker 934 and signals for transmission would be generated by a microphone 936. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented on mobile station 900. Although voice or audio signal output is preferably accomplished primarily through the speaker 934, display 922 may also be used to provide an indication of the identity of a calling party, the duration of a voice call, or other voice call related information for example.
Serial port 930 in
Other communications subsystems 940, such as a short-range communications subsystem, is a further optional component which may provide for communication between mobile station 900 and different systems or devices, which need not necessarily be similar devices. For example, the subsystem 940 may include an infrared device and associated circuits and components or a Bluetooth™ communication module to provide for communication with similarly enabled systems and devices.
When mobile device 900 is used as a UE, protocol stacks 946 include apparatus and method for transmitting messages in mobile telecommunications system user equipment.
In the foregoing specification, the invention has been described with reference to specific embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the scope of the technique. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.
It is to be noted that the methods as described have actions being carried out in a particular order. However, it would be clear to a person skilled in the art that the order of any actions performed, where the context permits, can be varied and thus the ordering as described herein is not intended to be limiting.
It is also to be noted that where a method has been described it is also intended that protection is also sought for a device arranged to carry out the method and where features have been claimed independently of each other these may be used together with other claimed features.
Furthermore it will be noted that the apparatus described herein may comprise a single component such as a UE or UTRAN or other user equipment or access network components, a combination of multiple such components for example in communication with one another or a sub-network or full network of such components.
Embodiments have been described herein in relation to 3GPP specifications. However the method and apparatus described are not intended to be limited to the specifications or the versions thereof referred to herein but may be applicable to future versions or other specifications.
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
This application is a continuation of U.S. patent application Ser. No. 12/138,653 filed on Jun. 13, 2008, the entire contents of the application are hereby incorporated by reference herein for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
5241542 | Natarajan et al. | Aug 1993 | A |
5623257 | Bachhuber | Apr 1997 | A |
6246867 | Jakobsson | Jun 2001 | B1 |
6477382 | Mansfield et al. | Nov 2002 | B1 |
7020501 | Elliott | Mar 2006 | B1 |
7672673 | Kojima | Mar 2010 | B2 |
7864720 | Jeyaseelan | Jan 2011 | B2 |
8139599 | Shvodian | Mar 2012 | B2 |
8254925 | Ding | Aug 2012 | B2 |
8312142 | Rinne et al. | Nov 2012 | B2 |
8315194 | Jeong et al. | Nov 2012 | B2 |
8620332 | Laroia et al. | Dec 2013 | B2 |
8755313 | Damnjanovic et al. | Jun 2014 | B2 |
8959368 | Lee | Feb 2015 | B2 |
9144020 | Clevorn | Sep 2015 | B2 |
20020183053 | Gopalakrishna et al. | Dec 2002 | A1 |
20030063658 | Heise | Apr 2003 | A1 |
20030086379 | Terry et al. | May 2003 | A1 |
20030100291 | Krishnarajah | May 2003 | A1 |
20040172566 | Greiger et al. | Sep 2004 | A1 |
20040203400 | Galetti | Oct 2004 | A1 |
20040224688 | Fischer | Nov 2004 | A1 |
20040228491 | Wu | Nov 2004 | A1 |
20050013283 | Yoon et al. | Jan 2005 | A1 |
20060034204 | Lee et al. | Feb 2006 | A1 |
20060040682 | Goertz | Feb 2006 | A1 |
20060098599 | Choi et al. | May 2006 | A1 |
20070058580 | Chae | Mar 2007 | A1 |
20070133479 | Montojo et al. | Jun 2007 | A1 |
20070149257 | Cheresh | Jun 2007 | A1 |
20070274244 | Yoon et al. | Nov 2007 | A1 |
20080014875 | Farnsworth | Jan 2008 | A1 |
20080090573 | Kim et al. | Apr 2008 | A1 |
20080165829 | Lee | Jul 2008 | A1 |
20080207152 | Welborn | Aug 2008 | A1 |
20080232404 | Fischer | Sep 2008 | A1 |
20080253312 | Park | Oct 2008 | A1 |
20080305797 | Somasundaram et al. | Dec 2008 | A1 |
20090068977 | Verstraelen | Mar 2009 | A1 |
20090312004 | Farnsworth et al. | Dec 2009 | A1 |
20100118753 | Mandin et al. | May 2010 | A1 |
20120269122 | Lee | Oct 2012 | A1 |
20120294144 | Niemi et al. | Nov 2012 | A1 |
20130182644 | Kim et al. | Jul 2013 | A1 |
20130203399 | Gupta | Aug 2013 | A1 |
Number | Date | Country |
---|---|---|
2234451 | Sep 2010 | EP |
2007025138 | Mar 2007 | WO |
Entry |
---|
Office Action mailed Nov. 9, 2012, in corresponding Canadian patent application No. 2,668,525. |
Office Action mailed Aug. 26, 2011, in corresponding Canadian patent application No. 2,668,525. |
Examination report mailed Dec. 13, 2010, in corresponding European patent application No. 08158245.4. |
Number | Date | Country | |
---|---|---|---|
20130235775 A1 | Sep 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12138653 | Jun 2008 | US |
Child | 13794280 | US |