The technology relates to signalling connection release indication procedures. More specifically, it relates to methods in Radio Access Networks and in User Equipments for supporting reconfiguration of User Equipments, a device in the Radio Access Network, and a User Equipment UE comprising a module for supporting reconfiguration of a User Equipment.
A signalling connection release indication procedure is used by a User Equipment, UE, to indicate to the Radio Access Network, RAN, that one of its signalling connections has been released or to request the RAN to initiate a state transition to a more battery efficient and less resource consuming Radio Resource Control, RRC, state, see Ref [1].
The Radio Resource Control protocol belongs to the UMTS WCDMA (Universal Mobile Telecommunications System Wideband Code Division Multiple Access) protocol stack and handles the control plane signalling of Layer 3 between the UE and the RAN, e.g. a Universal Terrestrial RAN, UTRAN. The RRC protocol includes:
Further, a typical WCDMA network implementation involves inactivity timers. The configuration of inactivity timers has considerable impact on the battery life of a mobile UE when a packet data connection is open. The RRC idle mode, i.e. no connection, has the lowest energy consumption.
The states in the RRC connected mode, in order of decreasing resource consumption, are CELL_DCH (Dedicated Channel), CELL_FACH (Forward Access Channel), CELL_PCH (Cell Paging Channel) and URA_PCH (URA Paging channel). In the following, CELL_PCH and URA_PCH will be considered as equivalent states, and the notation CELL/URA_PCH could be used hereafter when the CELL_PCH and URA_PCH state is discussed. The power consumption in the CELL_FACH may be roughly 50 percent of that in CELL_DCH, and the PCH states use about 1-2 percent of the power consumption of the CELL_DCH state. The transitions of lower resource consuming states occur when inactivity timers trigger. A timer T1 controls transition from CELL_DCH to CELL_FACH, a timer T2 controls transition from CELL_FACH to CELL/URA_PCH, and a timer T3 controls transition from CELL/URA_PCH to IDLE.
The RRC connection is defined as a point-to-point bi-directional connection between RRC peer entities in the UE and the UTRAN. A UE has either zero or one RRC connection.
The signalling connection is defined as a point to point bi-directional connection between peer entities in the UE and the core network. There can be one signalling connection for each of the Packet Switched and Circuit Switched core networks.
An RRC Signalling Connection Release Indication message is used by the UE to indicate to UTRAN the release of an existing signalling connection. If a data session from the UE is completed, the UE takes a decision that the session is completed and sends an end-of-session message, i.e. a Signalling Connection Release Indication message to the Radio Network Control, RNC, of the UTRAN. The message comprises a cause value, which the UE is configured to set to “UE requested PS Data session end” for indicating to the UTRAN that current data session is completed and that the UE would like to be reconfigured to a dormant state, i.e. a more battery efficient state, see Ref [2].
A Radio Network Control node of the UTRAN may be adapted to reconfigure the RRC state machine from the state CELL_DCH to one of the more battery efficient states, either CELL_FACH, CELL_PCH, URA_PCH or IDLE. There is a resource cost in both radio network and core network for setting up a new connection from IDLE mode, and there is also a resource cost in the radio network for transitions between the different RRC connected mode states. Every change of state incurs a cost. Setting up a new connection also takes a significant time. It is not efficient from a UE battery consumption point of view if a UE is reconfigured from IDLE to connected mode more or less directly after the UE has been released to the IDLE mode state.
It is an object to provide a method that provide better optimization of resource consumption, such as UE battery consumption, radio resource usage and network resource usage, e.g. signalling resources, processing resources, hardware resources, than known methods.
The object is achieved by letting the UE inform the network, e.g., a Radio Network Control node, not only that the current data session is completed, but also of the expected time to next data session and the expected traffic volume for the next data session. In this way the network has better information on which to base resource-related decisions and to select a suitable state for the UE between the data sessions.
Another object is to avoid unnecessary signalling over the air interface between the UE and a RAN as well as between RAN and core network.
Example embodiments for achieving these and other objects are provided. The example embodiments, performed in a Radio Access Network, support reconfiguration of a User Equipment, UE, to a state of a Radio Resource Control state machine. Information concerning the UE's next data session is received in a message indicating the end of a data session performed by the UE. The embodiments may also comprise selecting a state for the UE based on the information concerning the UE's next data session and a selection rule set.
Further, the embodiments comprise generating a message indicating the end of a data session performed by the UE and sending the message to the Radio Access Network where the UE is residing. The generation of the message comprises inserting information concerning the UE's next data session in the message.
Device embodiments comprise a receiver to receive information concerning the UE's next data session in a message for indicating the end of a data session performed by the UE. The device embodiments further comprise a selecting module configured to select a state for the UE based on the information concerning the UE's next data session and a selection rule set.
Additionally, a module for a User Equipment and embodiments thereof are also provided. This module and embodiments are adapted to support reconfiguration to a state of a Radio Resource Control state machine of the UE. The module and its embodiments comprise a message generator to generate a message indicating the end of a data session performed by the UE, and a sender to send the message to a node of the Radio Access Network where the UE is residing. The message generator comprises an insert module configured to insert information concerning the UE's next data session in said message.
A User Equipment comprising the above described module and embodiments thereof is also provided.
One advantage is that the provided methods, devices, modules, user equipment and embodiments thereof provide a possibility to optimize usage of battery power, radio resources, and network resources more efficiently.
The foregoing, and other, objects, features and advantages will be more readily understood upon reading the following detailed description in conjunction with the drawings in which:
a is a diagram schematically illustrating the principle of reconfiguration decisions and state selections according to some example embodiments;
b is a diagram schematically illustrating the principle of a reconfiguration decision and state selection according to an example of a selection rule;
c is a diagram schematically illustrating the principle of a reconfiguration decision and state selection according to an example of a selection rule;
d is a diagram schematically illustrating the principle of a reconfiguration decision and state selection according to an example of a selection rule;
e is a diagram schematically illustrating the principle of a reconfiguration decision and state selection according to an example of a selection rule;
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular circuits, circuit components, techniques, etc. in order to provide a thorough understanding of the provided methods and devices. In other instances, detailed descriptions of well known methods, devices, and circuits are omitted so as not to obscure the description of the present embodiments with unnecessary detail. However, it will be apparent to one skilled in the art how the present described embodiments may be practiced.
Further, the terms reconfigure, reconfiguring, reconfiguration, etc, are used in the description and claims. However, the terms configure, configuring, configuration may as well be used. Said wordings should be considered as mutually equivalent and non-limiting.
In the following detailed description, a message indicating the end of a data session performed by the UE is denoted end-of-session message. Further, a message comprising information about a selected state is denoted a reconfiguration order message.
The drawing illustrates a Radio Access Network, RAN, 10 comprising at least one, in this example three, Radio Network Subsystems, RNSs, 22 comprising a number of Node Bs, or Radio Base Stations, 12 connected to and controlled by a Radio Network Controller, RNC, 16. The RNC 16 is connected to a Core Network, CN, 18 for receiving and transmitting data and telecommunications traffic from other network systems. The RNC controls the Node Bs using the Node B Application Protocol, NBAP. Each Node B 12 is an access node for providing wireless radio communication access for User Equipments, UEs, 20 via an air interface within an area, i.e., cell 14. Different standards may be used, e.g., 2G, 3G, etc. In the drawing, one UE 20 is illustrated. The UE has an ongoing data session over the air interface and via the Node B in the cell where it is for the moment residing.
The figure illustrates that a data session is ongoing between a UE and a RAN to which the UE for the moment is connected. The UE then takes a decision that the session is completed, and it therefore sends an end-of-session message, such as a Signalling Connection Release Indication message to the RAN. According to current standards in the field, the end-of-session message does not comprise any information regarding next data session. The RAN receives the message, and after a certain time period, the RNC of the RAN releases the connection with the UE, the connection being a Dedicated Channel, DCH. Thus, the RNC changes the state of its state machine, which in the following is described with reference to
As the time for setting up a new Radio Access Bearer is considerable, it may not be an energy saving if an UE is reconfigured from Idle to connected mode more or less directly after the UE been released to the IDLE state.
One object is to provide a better energy saving method. The UE informs the network, e.g., the Radio Network Control node, not only that the current data session is completed, but also of the expected time to next data session and the expected traffic volume for the next data session. In this way, the network has better information on which to base resource-related decisions and select a suitable state for the UE between the data sessions.
By introducing two new information elements, “expected time to next session”, abbreviated ttns and “expected data volume for next session”, abbreviated dvns, in an end-of-session message, e.g. the RRC Signalling Connection Release Indication message, the network receives better information to base its decisions on when selecting if the UE shall be hosted in CELL_DCH, CELL_FACH or CELL/URA_PCH or released to IDLE as illustrated in
By introduction of the two new information elements, “expected time to next session” and “expected data volume for next session” in an end-of-session message, better information is provided for selection of which state to host the UE in. For a network decision, some embodiments use a selection rule set comprising a timer rule set and/or a data volume rule set. A timer rule set comprises at least one timer rule, and a data volume rule set comprises at least one data volume rule. The rules may be pre-defined, preferably by the operator of the network. In the following, a few examples of timer rules and data volume rules will be described and discussed in relation to the example illustrated in
a is a diagram schematically illustrating a principle of reconfiguration decisions and states selections according to some example embodiments. This figure shows two things:
(1) The stair of state transitions, see fat dashed line, that take place for an inactive UE not requesting fast dormancy compare with
(2) The principle of reconfiguration decisions and state selections according to the selection rule set.
Further, the time TR is indicating the time for the reception of an end-of-session message. Different values of the parameter ttns, expected time to next session, are indicated as ttns1, ttns2, ttns3.
These rules may be defined as following examples:
If the received ttns value is between T1+T2 and T1+T2+T3, e.g. ttns=ttns2, the network is configured to select one state, e.g. CELL/URA_PCH, for the state machine of the UE. The rule may therefore be defined as follows:
The effect of this rule is illustrated in
If the received ttns value is situated after T1+T2+T3, e.g. ttns=ttns3, the network is configured to select one state, e.g. Idle, for the state machine of the UE. Thus, the UE is released. The rule may therefore be defined as follows:
Further, data volume rules may be defined. Data volume dvns is here the total amount of user data to be transferred during the next data session. A data volume threshold may be defined as dvnst, and if the received dvns value is less or equal to dvnst, the network is configured to select a less resource consuming state, e.g. CELL_FACH, even if the timer rule alone indicates a more resource consuming state, e.g. CELL_DCH, for the state machine of the UE. The selection rule set may therefore be defined as a combination of a timer rule and a data volume rule:
In
b is a diagram schematically illustrating an example of reconfiguration decisions and states selections when the expected time to next session ttns is set to ttns1, wherein T1≦ttns1<T1+T2. The state transition is performed by the UE when it has received a reconfiguration order message comprising the information about the selected state. The time TR is indicating the time for the reception of the end-of-session message. The UE's selected state before and after the state transition is indicated by a continuous fat line. Compared to the state transition according to
c is a diagram schematically illustrating an example of reconfiguration decisions and states selections when the expected time to next session ttns is set to ttns2, wherein T1+T2≦ttns2<T1+T2+T3. The state transition is performed by the UE when it has received a reconfiguration order message comprising the information about the selected state. The time TR is indicating the time for the reception of the end-of-session message. The UE's selected state before and after the state transition is indicated by a continuous fat line. Compared to the state transition according to
d is a diagram schematically illustrating an example of reconfiguration decisions and states selections when the expected time to next session ttns is set to ttns3, wherein T1+T2+T3≦ttns3. The state transition is performed by the UE when it receives a reconfiguration order message comprising the information about the selected state. The time TR is indicating the time for the reception of the end-of-session message. The UE's selected state before and after the state transition is indicated by a continuous fat line. Compared to the state transition according to
e is a diagram schematically illustrating an example of reconfiguration decisions and states selections when the expected time to next session ttns is set to ttns4, wherein ttns4<T1. The selection rule set is defined as a combination of a timer rule and a data volume rule:
The state transition is performed by the UE when it has received a reconfiguration order message comprising the information about the selected state. The time TR is indicating the time for the reception of the end-of-session message. The UE's selected state before and after the state transition is indicated by a continuous fat line. Compared to the state transition according to
In
So far in this description, example embodiments and aspects have been described using four states, i.e., CELL_DCH, CELL_FACH, CELL/URA_PCH, and IDLE states. In the following, example embodiments and aspects are described using generalized states S1, S2, S3 . . . , SN, the states organized in order of decreasing resource consumption.
The method comprises:
States S1, S2 . . . may correspond to CELL_DCH, CELL_FACH or CELL/URA_PCH or IDLE, which states are illustrated in
States S1, S2, . . . , may correspond to CELL_DCH, CELL_FACH or CELL/URA_PCH or IDLE state, which are illustrated in
Other aspects provide a Radio Access Network, comprising one or more nodes supporting reconfiguration of a User Equipment UE to a state S1, S2, . . . .
The device 800 comprises a number of functional blocks of which some are shown in
As stated above in this description, a message indicating the end of a data session performed by the UE is denoted end-of-session message. Further, a message comprising information about the selected state is denoted reconfiguration order message.
The node 16 and its device 800 is configured to receive end-of-session messages 810 comprising information 808 on the next data session. Said information comprises information indicating an expected time to next session, ttns, of the UE, and/or information indicating an expected data volume of next session, duns, of the UE. The end-of-session message 810 may be a Signal Connection Release Indication Message.
The receiver 806 is configured to receive and extract said information 808 concerning the UE's next data session in an end-of-session message 810, and deliver the extracted information to a selecting module 812 configured to select the state S1, S2, . . . , for the UE based on the information 808 on a next data session and in accordance with a selection rule set 814. The selecting module 812 comprises the selection rule set 814 involving a predefined timer rule set 816 for selecting a state S1, S2, . . . , of the RRC state machine 802 based on the information indicating an expected time to next session, ttns, and/or on the information indicating an expected data volume of next session duns for the UE. The decision and selection of states to reconfigure to by means of selection rule sets may be performed as described in
Timer rule: If T1≦ttns<T1+T2, then select state S2.
If the received ttns value is situated between T1+T2 and T1+T2+T3, e.g. ttns=ttns2, the network is configured to select one state, e.g. S3, for the state machine of the UE. The rule may therefore be defined as follows:
Timer rule: If T1+T2≦ttns<T1+T2+T3, then select state S3.
If the received ttns value is situated after T1+T2+T3, e.g. ttns=ttns3, the network is configured to select one state, e.g. IDLE, for the state machine of the UE. Thus, the UE is released. The rule may therefore be defined as follows:
Timer rule: If T1+T2+T3≦ttns, then select state S4.
Further, data volume rules may be defined. A data volume threshold may be defined as dvnst, and if the received dvns value is less or equal to dvnst, the network is configured to select one state, e.g. S2, for the state machine of the UE. If the received dvns value is exceeding dvnst, the network is configured to select one state, e.g. S1.
The sender module 820 is adapted to send a reconfiguration order message 822 comprising information about the selected state 804 if a new state S1, S2, . . . , for the UE is selected, i.e. if a state reconfiguration for the UE is decided. The node may comprise other radio devices, processors and components, which are not shown in the figure. According to some embodiments, some elements or functional blocks of the device 800 may be common and shared by the node and the device 800, such as the sender, receiver and controller.
Further aspects are to provide a User Equipment UE adapted to support reconfiguration to a state (S1, S2 . . . ) of a Radio Resource Control, RRC, state machine.
The module 900 comprises a number of functional blocks of which some are shown in
In the following description of the embodiments, a message indicating the end of a data session performed by the UE is denoted end-of-session message. Further, a message comprising information about the selected state is denoted reconfiguration order message.
The module 900 comprises a message generator 910 to generate an end-of-session message 810, wherein the message generator 910 comprises an insert module 912 configured to insert information 808 concerning the next data session in said end-of-session message 810. The insert module 912 is adapted to handle information 808 concerning the next data session. Said information indicates an expected time to next session, ttns, of the UE and/or information indicating an expected data volume of next session, dvns, of the UE. The values of the parameter ttns and/or parameter dvns are stored in the storage 904 from which the controller is configured to transfer said values to the message generator 910 and the insert module 912. The message generator 910 may be configured to generate a Signal Connection Release Indication Message as an end-of-session message 810 to the Radio Access Network, and the insert module 912 is configured to insert the ttns value and/or dvns value in said message before transmitting the message.
The module 900 further comprises a sender 908 to send said end-of-session message 810 to a node (see 16 in
The receiver block 906 is adapted to receive from the Radio Access Network a reconfiguration order message 822 comprising information about the selected state S1, S2, . . . for reconfiguring the UE.
The controller 902 adapted to reconfigure the state 804 of the RRC state machine 914 the state S1, S2, . . . indicated by the reconfiguration information 804 in the reconfiguration order message 822. The UE may comprise other radio devices, processors and components, which are not shown in the figure. According to some embodiments, some elements or functional blocks of the module 900 may be common and shared by the UE and the module 900, such as the sender, receiver and controller.
The described embodiments of the device 800 and module 900 may be implemented in digital electronically circuitry, or in computer hardware, firmware, software, or in combinations of them. The apparatus may be implemented in a computer program product tangibly embodied in a machine readable storage device for execution by a programmable processor; and method steps may be performed by a programmable processor executing a program of instructions to perform functions by operating on input data and generating output.
The device 800 and module 900 may advantageously be implemented in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device. Each computer program may be implemented in a high-level procedural or object-oriented programming language, or in assembly or machine language if desired; and in any case, the language may be a compiled or interpreted language.
Generally, a processor will receive instructions and data from a read-only memory and/or a random access memory. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such internal hard disks and removable disks; magneto-optical disks; and CD-ROM disks. Any of the foregoing may be supplemented by, or incorporated in, specially designed ASICs (Application Specific Integrated Circuits).
One example beneficial application is to machine-to-machine type of applications, e.g., a UE comprising the module, with a predictable traffic pattern, such as for example meters or sensors—reporting similar type of information, e.g., repetitively every minute, hour, day or month.
A number of non-limiting example embodiments have been described. It will be understood that various modifications may be made without departing from the scope of the claims. Therefore, other implementations are within the scope of the following claims.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/SE11/51276 | 10/27/2011 | WO | 00 | 11/29/2011 |