RU2575259C2 - Exchange of mobility information in cellular radio communication - Google Patents

Abstract

FIELD: radio engineering, communication.

SUBSTANCE: invention relates to mobile communication. A connection request is received from a remote terminal of a radio communication system at a serving node of the radio communications system. Mobility information is requested based on receiving the connection request. The requested mobility information is received from the remote terminal, and the requested connection is established with the remote terminal.

EFFECT: enabling efficient management of a communication network by obtaining information on the speed of mobile devices.

28 cl, 5 dwg

Description

FIELD OF THE INVENTION

The invention relates to the field of information exchange in cellular radio communications and, in particular, to obtaining information from user equipment regarding the mobility of this user equipment.

State of the art

The management and administration of wireless networks improves when the controllers on the network have more knowledge about users and user equipment (UEs). This knowledge allows the network to adapt its settings for mobile UEs. The speed of movement of the UE equipment, or the speed of movement, is useful for configuring several parameters, such as mobility triggers, for example, to initiate a handover and reselect a cell, transmit paging signals, set intermittent reception (DRX) parameters, deploy new base stations, etc. .d.

In Long Term Evolution (LTE), a mobility state, such as UE speed information, may be available on the network, but only in certain cases. The speed information of the UE is included, for example, in a measurement report message transmitted from the UE. In the measurement report message, the UE reports, along with other parameters, location-info-r10 (location information for version 10). Location-info-r10 contains an area called horizontalVelocity (horizontal speed), which is evaluated by the technical positioning tools defined in 36.331 (3GPP TS 36.331, Technical Specification No. 36.331 of the Third Generation Partnership Project). UE rate information is reported by the UEs when the UE detects a radio link failure or a handover failure.

When the UE detects a radio link failure (RLF) leading to a handover failure, then this reason is indicated by the RRC connection recovery request message sent by the UE to the cell in which the UE finds itself during the RLF recovery procedure. The cell in which the UE finds itself during RLF recovery transmits all the last measurements made by the UE before the RLF was detected. These dimensions include the horizontalVelocity information item. Information is transmitted via an indication of the RLF message exchanged via X2 between the two cells, as defined in 3GPP TS 36.423 (Application Protocol X2). Alternatively, the UE may transmit this information using an RRC message with information about the UE.

The handover request message also has a chronological information element UE, but it is only transmitted during the handover procedure and is sent by the eNB managing the serving cell to the eNB controlling the target cell, as defined in 3GPP TS 36.423. The chronological information element of the UE contains the GCI (Global Cell Identifier) of the last N visited cells along with the time spent in each of these N cells. The maximum number N is 16. Although this information is not a direct measurement of speed or speed, it can be used by the network as a rough estimate.

In each of the messages described above, the network gains knowledge of the speed of the UE for specific purposes and during certain events, such as handover or RLF. The network does not have UE speed information for any UE equipment that does not undergo these events.

Information is also exchanged on the speed of the UEs in the neighboring cell. This occurs when the UE detects the RLF, and the UE is in the neighboring cell. A neighboring cell forwards this information to the last serving cell of the UE in question for use in optimizing mobility stability (MRO). The last serving cell uses this information to update its mobility triggers. Mobility triggers are thresholds used in handover decisions. However, the serving cell no longer serves this particular UE after the RLF.

Even when information is received, it may not be accurate. The accuracy of the horizontalVelocity IE (Information Element) depends on the functionality of the UE. The chronological information of the UE, on the other hand, allows the network to obtain an approximate value of the speed of the UE by estimating the time during which the UE remained in the last N cells. However, the cells may have different sizes, and the UE may cross the entire cell or simply cross a small portion thereof.

SUMMARY OF THE INVENTION

The purpose of the invention is to transmit mobility information from mobile devices to the network. Mobility information can take many different forms, including an information item on mobility status or horizontal speed. Mobility status can be estimated by measuring the number of handovers over a time interval or more directly using location information or location information over time.

In one example, a connection request is received from a user equipment (UE) of a radio communication system in a serving node of a radio communication system. Mobility information is requested from the UE based on the receipt of a connection request. The requested mobility information is received from the UE, and the requested connection with the UE is established.

In another example, the serving node of the radio communication system has a receiver for receiving a connection request from a user equipment (UE) of the radio communication system, a transmitter for transmitting a mobility information request from the UE based on receiving the connection request. The receiver receives the requested mobility information from the UE, and the controller establishes the requested connection with the UE.

In another example, mobility information is determined in the idle radio system UE. A connection request is sent to the serving node of the radio communication system. The mobility information request is received from the serving node, and the estimated mobility information is sent to the serving node.

In another example, the UE has a controller for determining mobility information in an idle mode. The UE also has a transmitter for sending a connection request to a serving node of the radio communication system and a receiver for receiving a request for mobility information from the serving node. The transmitter sends estimated mobility information to the serving node.

Accurate or current information about the speed of mobile devices on the network provides an advantage, enabling more efficient network management. It includes managing handoffs differently for mobile devices moving at different speeds, and setting various operational parameters for mobile devices.

Brief Description of the Drawings

The presented disclosure can be better understood with reference to the following description and the accompanying drawings.

FIG. 1 is a flowchart of a process for sending mobility information from a UE to an eNB.

FIG. 2 is a flow diagram of a process for receiving mobility information from a UE to an eNB.

FIG. 3 is a simplified diagram of three cells of a radio communication system intersected by a UE and connected in accordance with standards for a UTRAN (Universal Terrestrial Radio Access Network).

FIG. 4 is a simplified block diagram of the hardware of a radio terminal.

FIG. 5 is a signaling diagram illustrating signaling and equipment operations performed to receive mobility information.

Detailed description

In the following description, numerous specific details are formulated, such as logical implementations, operation codes, means for determining the components of operations, implementing separation / sharing / duplication of resources, types and relationships of system components, and logical options for separation / integration. However, it will be understood by those skilled in the art that various implementations may be practiced without such specific details. In other examples, control structures, logic level circuits, and complete sequences of software instructions were not shown in detail so as not to obscure the description.

In the following description and claims, the terms “connected” and “connected” along with their derivatives can be used. It should be understood that these terms should not be construed as synonyms for each other. The term “connected” is used to indicate that two or more elements, which may or may not be in direct physical or electrical contact with each other, are combined or interact with each other. The term “connected” is used to indicate the establishment of communication between two or more elements that are connected to each other.

A user can communicate using a user equipment (UE) through a communication system and receive and send data to other UE equipment in or out of this system. Access to the communication system may be provided by a fixed line or wireless communication interface, or a combination thereof. Examples of wireless access systems providing mobility for UE equipment include cellular access networks, various wireless local area networks (WLANs), wireless personal area networks (WPANs) installed on a satellite communication system, and various combinations thereof. A communication system typically operates in accordance with a standard and / or set of specifications and protocols that establish what the various elements of the system can do and how it should be achieved. For example, this is usually determined if the user, or more precisely, the user device, is provided with communication with circuit switching, or with packet switching, or both. In addition, the way in which information interaction should be implemented between the user device and various elements of information interaction, and their functions and functional responsibilities are usually determined by a predetermined communication protocol. Various functions and features are usually performed in a hierarchical or multi-level structure, the so-called protocol stack, in which higher levels can affect the functioning of lower-level functions.

In cellular communication systems, a network object in the form of a base station provides a node for information interaction with mobile devices in one or more cells or sectors. In some systems, the base station is called 'Node B'. Typically, the operation of the base station devices and other access system devices required for information interaction is controlled by a specific control object, such as a base station controller, a mobile switching center or a packet data support node.

The invention is described in the context of the third generation mobile communication systems (3G) of the universal mobile communication system (UMTS) and, in particular, long-term development (LTE). A specific example of LTE is Enhanced Universal Terrestrial Radio Access (E-UTRA). The Enhanced Universal Terrestrial Radio Access Network (E-UTRAN) includes E-UTRAN Nodes B (eNB), which are configured to provide base station and control functionality. However, the invention is not limited thereto.

In the following description and claims, the terms “UE” and “User Equipment” are used to refer to remote terminals, mobile devices or radio stations, subscriber equipment and any other type of mobile device that can connect to more than one cell and complete a handover. The term “handover” also includes “handover”. The term "eNB" or "cell" is used generally to refer to a base station, access point, fixed terminal, and the like, and refers to the field of radio communications for a base station, cell, or sector. The description is presented in the context of LTE for purposes of illustration, but the invention is not limited thereto.

In LTE, the term “mobility” is used to refer to handoffs and handover protocols in general, as in mobility resiliency optimization (MRO). It is also used to indicate an information element that indicates the speed at which a UE moves through cells. An information element can have one of three values: high, medium, and low. This term "mobility" refers to the speed at which the UE moves on the ground, and to the LTE parameter called horizontal speed. In the following description and claims, the term "mobility" is used to denote and transfer service in the general sense and to the speed with which the UE moves. The rate at which the UE sends and receives data will be referred to in other terms, such as data rate, high or low information flow rate, etc.

The present invention provides a method by which UEs report their mobility state upon transitioning to an RRC connected mode. Mobility status is evaluated in RRC idle mode. UE equipments are aware of their mobility state when they are idle, as defined in 3GPP TS 36.304. As described herein, when connecting an RRC, the network may ask the UE to report its estimated mobility state, for example, its speed, among other information. The UEs may report this information using a message such as a measurement report message. In addition, during a handover, mobility status information may be included in a handover request message exchanged between a serving and a target cell.

Using these exchanges, the network can have a complete picture of the user's speed on the network. This information can be used for various purposes, such as identifying paging signaling areas, establishing DRX, establishing mobility triggers, defining network deployment strategies, etc. So, for example, when the network is aware of the UE speeds in the system, it can optimize paging signaling. If users within the area move very quickly, then the paging area can be set large. Similarly, a DRX cycle of a given UE with no data or very little data in buffers can be set in accordance with its average speed. Fast moving UEs can be installed on longer DRX cycles than slow moving UEs.

In one typical process for collecting UE speed information, equipment UEs report their speed or mobility status when they switch from idle mode to connected mode. FIG. 1 is a simplified flowchart from a UE perspective. In FIG. 1, in step 100, the UE is in RRC idle mode. Although RRC modes and commands are described in this document, the invention is not limited thereto, and any of a wide range of different protocols and standards may benefit from the described techniques, processes, and systems.

At step 110, the UE performs an estimate of the speed of the moving object, such as assessing the state of mobility in idle mode. The mobility state assessment compares the number of cells crossed (up to 16) with the time taken to obtain a value indicative of the speed of the UE. Mobility status is high, medium, or low. The number of handoffs for a given period is used to determine the mobility state as high if there are many handoffs, average if there is an average number of handoffs, and low if there are a small number of handoffs within a given time window.

Alternatively, the UE may use other rate estimates. LTE defines the horizontalVelocity of an information element as defined in 3GPP TS 36.331. Typically, it is included in the chronological information element of the UE of the handover request message exchanged between cells through X2, as defined in 3GPP TS 36.423. Other measurement results and reporting forms may be used. The UE may directly measure its speed based on received communication signals, or location signals, or based on other factors.

At step 120, the UE decides whether to switch the UE from the idle RRC mode to the connected RRC mode. The decision is usually triggered by a user request to send or receive data, but can also be triggered by a paging signal from a serving eNB or administrative functions. If the UE does not transition from idle mode, then the process returns to step 100, and the UE remains in idle mode.

At step 130, the UE sends either a paging signal response or an RRC connection request to the serving eNB to establish a connection. The eNB responds differently, depending on which message was sent by the UE. In the event that the eNB is able to establish a connection, at step 140, it sends a message that the connection is established. This message may include uplink channel allocation, training mode data, synchronization data, and other information.

At step 150, the UE receives a request from the serving eNB to transmit mobility information back to the eNB. This request may be combined with a connection establishment message, or it may be sent as a separate message. In one example, the request is presented in the form of a measurement control message. The request may determine the specific requested information, such as mobility status, horizontal speed, or other or additional parameters.

At step 160, the UE meets the requirements of the request and sends the requested information. The serving eNB can use this information for its own purposes or provide this network information through S1 or to other nodes through X2. Some examples of use are mentioned above, but the invention is not limited to this.

At step 170, the UE exchange packet data with the serving eNB. The established connection requested in step 130 is used to complete the data call for which it was established. At step 180, if the data buffers are empty or the time limit is exceeded, the data call will be completed and the UE may return to idle mode.

The process flowchart is simplified to show how to obtain mobility information from the UE immediately after the UE transitions from the idle mode. Before or after any of the above operations, there may be intermediate steps. Data exchange may continue, for example, despite various handovers and other interruptions. In addition, mobility information may be sent on a dedicated uplink channel or using a random access channel or a control channel, depending on the particular implementation.

FIG. 2 is a simplified flowchart from the perspective of a serving eNB. At step 200, the eNB receives a connection request or a response to transmitting the paging signal from the UE. If the UE is not active, then the eNB will not have the latest information about its location and movement.

In one example, after receiving, for example, an RRC connection request message from a given UE, the serving eNB in step 230 requests that the UE report its estimated mobility state. Since the UE has just transitioned from idle mode, the latest mobility state is likely to be the mobility state evaluated by the UE, while the UE was in idle mode. The network may ask the UE about this using, for example, measurement control messages or in other forms. Alternatively, other messages may also be used, for example, an information message to the UE. The E-UTRAN defines a UECapabilityInformation message (UE functionality information) that indicates the UE’s radio access capability for various classes of radio frequency bands. As mentioned above, the request may be combined with a connection establishment and channel allocation message, or it may be a separate message. The mobility information request at step 230 may take the form of a request for the most recent assessment of the mobility state of the UE, however, as an alternative or in addition to the mobility state, the eNB may request other information regarding the speed at which the UE moves. It includes horizontalVelocity and other speed measurement results, as mentioned above.

Intermediate operations may be performed between the connection request and the mobility status request. These operations may be related to the provision or refusal to establish a connection or other operational problems. In the example shown in FIG. 2, the network first checks the quality of the communication line in step 210. If, for example, the SINR (signal to interference to noise ratio) of the RRC connection request message is above a threshold, then the quality of the communication line is considered to be good and the eNB will satisfy the request to connect and ask for mobility status. Otherwise, the eNB will not be able to respond or send a rejection of the connection request. Alternatively, as shown, if the quality of the communication line is not good enough, then the network is waiting. After delaying or waiting, at step 220, upon receiving another connection request at step 200, or upon receiving packet data from the just connected UE, and if the quality becomes better than the quality threshold, the eNB transmits a mobility status request. A link quality control operation 210 is optional. It allows the network to increase the likelihood of correctly receiving mobility information. The quality threshold can be selected so as to interfere with the connections of the equipment of the UE, which cannot maintain a reliable connection. In accordance with a specific implementation, a specific threshold value may be selected.

At step 240, a response with mobility status data and any necessary responses to any other aspects of the message from the eNB is received from the UE. The UE may respond using any of a variety of different types of mobility information. The response may include horizontalVelocity of the information element and / or mobilityState (mobility state) of the information element, as defined in 3GPP TS 36.331 & 36.304, or any other type of estimation of speed or speed of movement made internally in the UE, in particular one that the network was no longer communicated. They are typically included in the chronological information element of the UE of the handover request message exchanged via X2, as defined in 3GPP TS 36.423, but otherwise they will not be transmitted. In addition, if the network has estimated the speed of the UE moving based on, for example, measuring uplink transmissions, then this information may already be known to the network. The network can combine all this information and make average, instantaneous speed estimates.

At step 250, the serving eNB exchanges packet data with the UE. The established connection requested in step 200 is used to complete the data call for which it was established. The connection may occur with a request for mobility information at step 230, or it may occur using another messaging (not shown). At step 260, if the data buffers are empty or the time limit is exceeded, data access will be completed and the UE may return to idle mode. Additional operations may occur in connection with the exchange of packet data or as auxiliary operations, including handoffs, reconfiguration, parameter assignment, etc.

FIG. 3 is a diagram of an overall configuration of a radio communication system. In FIG. 3, the UE moves from cell A to cell B and then to cell C, as indicated by arrows pointing to the right in the drawing. Each cell has a base station illustrated in the form of a tower, such as an eNB, or similar structure, near the center of each of these three cells. Although the base stations are shown as being near the center of each cell, as an alternative, they can determine the sides of each cell using sectorized antennas, or have any other desired configuration. In an E-UTRAN, various user equipment (UE) terminals are connected to base stations (commonly referred to as Enhanced Node B (eNBs)) wirelessly and perform handover to various eNBs as they move from cell to cell, as shown. In the E-UTRAN, the base stations are directly connected to the core network (CN) via the S1 interface, which controls the eNBs connected to it. The eNBs are also connected to each other via the X2 interface. The Functioning and Support System (OSS) is logically connected to all base stations, as well as to the CN, through the OSS interface.

Figure 4 shows an example of a hardware architecture design diagram suitable for a UE and an eNB. Hardware 400 includes one or more antenna elements 401. There may be separate transmit and receive antenna arrays, sectorized or spaced antennas, or a single omnidirectional antenna element. For transmission, data is collected in a transmission queue 403 from which it is sent to a baseband modulator 405 for character conversion, modulation, and upconversion. Transmitter 407 further modulates and amplifies the signal for transmission through the antenna.

On the receive side, received symbols in the receive channel 409 are demodulated and downconverted to the base frequency band. A communication system for transmitting data over a single unmodulated frequency band extracts the bit pattern from the received signal and generates any error detection codes that may be required. The bitstream is stored in a receive buffer or in a queue 413 for use by the system.

Controller 415 controls the operation of the transmit and receive channels, applies data to the outgoing queue, and receives data from the incoming queue. It also generates messages to support the wireless and wired communication protocols over which it communicates. The controller is associated with one or more storage systems 417, which may include software, intermediate cached values, configuration parameters, user data, and system data. The controller may also include internal storage, in which one or more of these types of information and data can be stored instead of or in addition to being stored in an external storage system. The controller is connected to a system interface 419 data input / output, which provides the possibility of information interaction with external devices and user interface 421 data input / output, which provides the user with the ability to control, use, administer and operate the system.

In the case of an eNB, the system interface 419 can provide access through the S1, OSS, and X2 interfaces to the rest of the network equipment to send and receive data, messages, and administrative information. However, one or more of these interfaces may also use a radio interface 401 or another interface (not shown). In the case of the UE, the system interface can be connected to other components in the device, such as sensors, microphones, and video cameras, as well as to other devices, such as personal computers or other types of wireless networks, via wireless or wired interfaces.

FIG. 5 is a signaling diagram illustrating aspects of the disclosed techniques. As with the flowcharts, additional and alternative operations can be added or subtracted from the illustrated signaling. At the top of the circuit, reference designation 1, the UE performs idle mode operations, which include an assessment of mobility status. The UE may also perform other operations, such as cell selection, broadcast synchronization, etc. During idle mode, a connection event occurs, 2. This may be a reception of a paging signal from an eNB (not shown), a timer awakening, detection or input of data for transmission, or any other event.

Then, the UE sends a connection request, 3, to the serving eNB or eNB selected during the idle mode; The eNB performs a validation check, 4, which may include measuring the signal strength or SINR of the received signal. This may also include determining whether the channels are available to allocate them for the requested connection, and if so, determining which channels. If the UE is to be allowed, the eNB sends connection configuration information, 5, and a request for mobility information, such as mobility status information, 6. As mentioned above, although the mobility status is an easily accessible information item in LTE that can be easily requested, instead of, or in addition to, a mobility state, other data may be requested.

The UE issues a response with mobility status information, 7, and packet data exchange is established. The network may use mobility information, 9, for any of a variety of different purposes, as mentioned above, including system control and channel allocation between different eNBs. After some time, the connection between the UE and the eNB disconnects, 10. Then, the UE returns to the idle mode or to the normal operation mode without an active connection, and other processes may be performed.

The operations of the flowcharts and signal transmissions are described with reference to exemplary embodiments. However, it should be understood that the operations of the flowcharts may be performed in ways different from those discussed with respect to these other flowcharts, and the changes discussed with respect to these other flowcharts may carry out operations that are different from those discussed with respect to the flowcharts.

As described herein, instructions may relate to specific hardware configurations, such as application oriented integrated circuits (ASICs) configured to perform certain operations or having predetermined functionality, or to software instructions stored in a storage device embodied in a short-term machine-readable medium. Thus, the techniques shown in the drawings can be implemented using code and data stored and executed on one or more electronic devices (e.g., UE, eNB, etc.). Such electronic devices store and exchange (internally and / or with other electronic devices via the network) code and data using computer-readable media such as short-term machine-readable media (e.g. magnetic disks; optical disks; random access memory; read-only memory; devices flash memory; phase-transition memory) and short-term computer-readable communication media (e.g., electrical, optical, acoustic or other form of propagating signals) alov - such as carrier waves, infrared signals, digital signals, etc.). In addition, such electronic devices typically include a set of one or more processors associated with one or more other components, such as one or more storage devices (short-term machine-readable storage media), user input / output devices (e.g., keyboard, touch screen and / or display device) and network connections. Communication between a set of processors and other components is typically done through one or more buses and bridges (also called bus controllers). Thus, a data storage device for a given electronic device typically stores code and / or data for execution on a set of one or more processors of this electronic device. Of course, one or more parts of an embodiment of the invention may be implemented using various combinations of software, firmware, and / or hardware.

The operations of the flowcharts are described with reference to examples of embodiments of other circuits. However, it should be understood that these operations of the flowcharts may be performed by means of embodiments of the invention other than those discussed with respect to these other schemes, and the embodiments of the invention discussed with respect to these other patterns may perform operations other than those discussed with respect to the flowcharts stages.

Although the flowcharts in the drawings show a certain order of operations performed by certain embodiments of the invention, it should be understood that such an order is exemplary (for example, alternative embodiments may perform operations in a different order, combine some operations, combine some operations, etc. )

Although the invention has been described with respect to several embodiments, those skilled in the art will understand that the invention is not limited to the described embodiments, but can be practiced with modification and alteration. Thus, the description should be considered as illustrative and not restrictive.

Claims (28)

1. A method for receiving mobility information from a remote terminal implemented in a serving node of a radio communication system, the serving node being configured to connect to a plurality of remote terminals via radio links, the method comprising:
receiving (200) a connection request from a remote terminal,
a request (230) for mobility information from a remote terminal in response to receiving a connection request,
receiving (240) the requested mobility information from the remote terminal, and
Establishing (250) the requested connection to the remote terminal. 2. The method of claim 1, wherein receiving the connection request comprises receiving an RRC connection request message. 3. The method of claim 1, wherein the mobility information request comprises a request for an estimated mobility status. 4. The method of claim 2, wherein the mobility information request comprises a request for an estimated mobility status. 5. The method of claim 3, wherein the assessed mobility state is a mobility state evaluated by the remote terminal when the remote terminal is in an idle state. 6. The method of claim 4, wherein the assessed mobility state is a mobility state estimated by the remote terminal when the remote terminal is in an idle state. 7. The method of claim 3, wherein the request for an estimated mobility state comprises sending a measurement control message to a remote terminal. 8. The method of claim 4, wherein the request for an estimated mobility state comprises sending a measurement control message to a remote terminal. 9. The method of claim 3, wherein the request for an estimated mobility state comprises a message request with information about the UE (user equipment), which includes remote terminal radio access capabilities for different classes of radio frequency bands. 10. The method of claim 4, wherein the request for an estimated mobility state comprises a request message with information about the UE (user equipment), which includes remote terminal radio access capabilities for different classes of radio frequency bands. 11. The method according to one of the preceding paragraphs, in which the request for mobility information comprises a request for an information element UE (user equipment) horizontalVelocity (horizontal speed) from a remote terminal. 12. The method according to one of paragraphs. 1-10, wherein receiving the requested mobility information comprises receiving an estimate of the moving speed of the remote terminal made by the remote terminal. 13. The method of claim 11, wherein receiving the requested mobility information comprises receiving an estimate of the speed of movement of the remote terminal made by the remote terminal. 14. The method according to one of paragraphs. 1-10, 13, in which the receipt of the connection request comprises restoring via a radio link, the method further comprising:
measuring (210) the quality of the radio link with the remote terminal based on the received connection request,
determining whether the availability of the radio link is good by comparing the signal-to-noise ratio of the received connection request with a threshold value, and
wherein the mobility information request (230) contains a mobility information request only if the radio link is of satisfactory quality. 15. The method according to p. 11, in which the receipt of the connection request comprises restoring via a radio link, the method further comprising:
measuring (210) the quality of the radio link with the remote terminal based on the received connection request,
determining whether the availability of the radio link is good by comparing the signal-to-noise ratio of the received connection request with a threshold value, and
wherein the mobility information request (230) contains a mobility information request only if the radio link is of satisfactory quality. 16. The method according to p. 12, in which the receipt of the connection request comprises restoring via a radio link, the method further comprising:
measuring (210) the quality of the radio link with the remote terminal based on the received connection request,
determining whether the availability of the radio link is good by comparing the signal-to-noise ratio of the received connection request with a threshold value, and
wherein the mobility information request (230) contains a mobility information request only if the radio link is of satisfactory quality. 17. The method of claim 1, further comprising:
receiving mobility information from a variety of other remote terminals, and
combining received mobility information from a remote terminal with received mobility information from a variety of other remote terminals. 18. A service node (400) of a radio communication system configured to exchange packet data with a plurality of remote terminals and obtain mobility information from a remote terminal, the service node comprising
a receiver (409) configured to receive (200) a connection request from a remote terminal,
a transmitter (407) configured to transmit (230) a request for mobility information from a remote terminal in response to receiving a connection request,
moreover, the receiver is further configured to receive (240) the requested mobility information from a remote terminal, and
a controller (415) to establish (250) the requested
connections to a remote terminal. 19. The serving node of claim 18, wherein the requested mobility information comprises an estimate of the speed of movement of the remote terminal made by the remote terminal. 20. The service node of claim 18, wherein the receiver is further adapted to receive requested mobility information from other remote terminals, and in which the controller combines the received mobility information received from other remote terminals. 21. A method for sending mobility information to a serving node, the method being implemented in a remote terminal of a radio communication system, the remote terminal being configured to request a connection to one of the plurality of serving nodes via radio links, the method comprising:
determining (110) information about mobility in idle mode in the remote terminal,
sending (130) a connection request to the serving node,
receiving (150) a request for mobility information from a serving node in response to sending a connection request, and
sending (160) mobility information to a serving node in response to a request for mobility information. 22. The method of claim 21, wherein sending the mobility information comprises sending the estimated mobility state. 23. The method of claim 21, wherein sending the mobility information comprises sending a horizontalVelocity UE (user equipment) information element determined by the remote terminal. 24. The method of claim 22, wherein sending the mobility information comprises sending a horizontalVelocity UE (user equipment) information element determined by the remote terminal. 25. The method according to one of paragraphs. 21-24, wherein sending the connection request comprises sending an RRC connection request message. 26. The method according to one of paragraphs. 21-24, further comprising establishing (170) a connection with the serving node. 27. The method according to p. 25, further comprising establishing (170) a connection with the serving node. 28. The remote terminal (400) of the radio communication system, configured to function to exchange packet data with one of the plurality of serving nodes and send mobility information to the serving node, wherein the user equipment comprises:
a controller (415), configured to determine (110) idle mobility information in a remote terminal,
a transmitter (407) configured to send (130) a connection request to a serving node, and
a receiver (409), configured to receive (150) a request for mobility information from a serving node in response to sending a connection request,
wherein the transmitter is further configured to send (160) estimated mobility information to a serving node in response to a request for mobility information.

Images