WO2003030568A1 - Cell updates in a umts terrestrial radio access network - Google Patents

Cell updates in a umts terrestrial radio access network Download PDF

Info

Publication number
WO2003030568A1
WO2003030568A1 PCT/EP2002/009005 EP0209005W WO03030568A1 WO 2003030568 A1 WO2003030568 A1 WO 2003030568A1 EP 0209005 W EP0209005 W EP 0209005W WO 03030568 A1 WO03030568 A1 WO 03030568A1
Authority
WO
WIPO (PCT)
Prior art keywords
drnc
srnc
rnsap
transport channel
cell
Prior art date
Application number
PCT/EP2002/009005
Other languages
French (fr)
Inventor
Björn EHRSTEDT
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2003030568A1 publication Critical patent/WO2003030568A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0055Transmission or use of information for re-establishing the radio link
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W92/00Interfaces specially adapted for wireless communication networks
    • H04W92/16Interfaces between hierarchically similar devices
    • H04W92/22Interfaces between hierarchically similar devices between access point controllers

Definitions

  • the present invention relates to the handling of cell updates at the lur interface of a UMTS Terrestrial Radio Access Network (UTRAN), the lur interface being the interface between Radio Network Controllers (RNCs) of the UTRAN.
  • UTRAN UMTS Terrestrial Radio Access Network
  • RNCs Radio Network Controllers
  • the European Telecommunications Standardisation Institute is currently in the process of standardising a new set of protocols for mobile telecommunications systems.
  • the set of protocols is known collectively as the Universal Mobile Telecommunications System (UMTS).
  • UMTS Universal Mobile Telecommunications System
  • the architecture of a UMTS network is based upon a UMTS core network and a UMTS Terrestrial Radio Access Network (UTRAN).
  • the UTRAN comprises a number of Radio Network Controllers (RNCs), each of which is coupled to a set of neighbouring Base Transceiver Stations (BTSs) or Node Bs.
  • BTSs Base Transceiver Stations
  • Each Node B is responsible for a given geographical area or cell, and the controlling RNC is responsible for routing user and signalling data between that Node B and the core network.
  • the interface between an RNC and a Node B is referred to as the Iu interface.
  • a general outline of the UTRAN is given in Technical Specification TS 25.401 (UTRAN overall description
  • User and signalling data may be carried between an RNC and a mobile terminal (referred to in UTRAN as User Equipment (UE)) using Radio Bearers (RBs).
  • a mobile terminal is allocated one or more RBs, each of which is capable of carrying a flow of user or signalling data.
  • RLC Radio Link Control
  • RBs are mapped onto respective logical channels.
  • MAC Media Access Control
  • a set of logical channels is mapped in turn onto a transport channel, of which there are two types: a "common" transport channel which is shared by different mobile terminals and a "dedicated" transport channel which is allocated to a single mobile terminal.
  • FACH Forward Access CHannel
  • Several transport channels (e.g. FACHs) are in turn mapped at the physical layer onto a Secondary Common Control Physical CHannel (S-CCPCH) for transmission over the air interface between a Node B and a mobile terminal.
  • FACH Forward Access CHannel
  • S-CCPCH Secondary Common Control Physical CHannel
  • FIG. 1 illustrates the protocol model for the FACH transport channel when the serving and controlling RNCs are coincident and where Uu indicates the interface between the UTRAN and the mobile terminal (UE), and Iub indicates the interface between the RNC and a Node B.
  • RRC Radio Resource Control
  • the MAC (MAC-c) entity in the RNC transfers MAC-c Packet Data Units (PDUs) to the peer MAC-c entity at the mobile terminal, using the services of the FACH Frame Protocol (FACH FP) entity between the RNC and the Node B.
  • the FACH FP entity adds header information to the MAC-c PDUs to form FACH FP PDUs which are transported to the NodeB over an AAL2 (or other transport mechanism) connection.
  • An interworking function at the Node B interworks the FACH frame received by the FACH FP entity into the PHY entity.
  • the RRC remains terminated at the first RNC whilst the terminal takes advantage of a cell and common transport channel of the second RNC.
  • the first RNC remains as the serving RNC with a connection to the core network whilst the second RNC becomes the controlling RNC.
  • the controlling RNC is in control of the NodeB where the mobile terminal is located and in particular of the logical resources (transport channels) at that Node B.
  • the controlling RNC is referred to as a "drift" RNC (the controlling RNC will also be acting as a serving RNC for mobile terminals registered with that RNC).
  • the protocol model for the FACH transport channel when the serving and controlling RNCs are separate is illustrated in Figure 2. It will be noted that a new interface lur is exposed between the serving and the controlling RNCs. The RNSAP protocol is used for control plane signalling on the lur interface.
  • the mobile terminal When a mobile terminal first moves into the coverage area of the (new) DRNC, the mobile terminal must send an RRC Cell Update message to the SRNC to inform the SRNC of its new location.
  • the RRC Cell Update message (L3 information) is forwarded by the DRNC to the SRNC using the RNSAP UL Signalling Transfer message.
  • the SRNC Upon receipt of a Cell Update, the SRNC must determine the configuration (scheduling priority, MAC-c/sh SDU length(s), and initial window size) of the FACH transport channel used by the DRNC for the cell to which the update relates.
  • the SRNC responds to receipt of a Cell Update by sending a RNSAP Common Transport Channel Resource Request message to the DRNC over the lur interface.
  • the DRNC responds with a RNSAP Common Transport Channel Resource Response message containing the configuration information.
  • the FACH transport channel configuration may be the same for all cells of an RNC. In other network configurations, the configuration may differ from cell to cell.
  • the current standard handles this situation by performing the RNSAP procedure (request and response sequence) each time a Cell Update is received at the SRNC over the lur interface, i.e. for the first and subsequent cell updates.
  • the RNSAP exchange procedure introduces a delay into the cell update procedure. This may cause an interruption in the service provided to a mobile terminal and results in a less than optimal use of radio resources.
  • the procedure increases the signalling load on the lur interface. In communications networks, a greater signalling load often results in higher infrastructure costs.
  • a method of informing a serving RNC, SRNC, of the FACH transport channel configuration allocated by a drift RNC, DRNC, to user equipment, UE comprising: including in a RNSAP message sent from the DRNC to the SRNC, an information element indicating whether FACH flow control information contained in the response is unique to the DRNC cell, or whether the information is common to all of the cells of the DRNC, wherein if said information element indicates that the information is common to all of the cells of the DRNC, the SRNC does not perform the RNSAP Common Transport Channel Resources Initialisation procedure, request/response sequence, for Cell Update messages subsequently received from the DRNC.
  • said RNSAP message is sent as part of a RNSAP Common Transport Channel Resources Initialisation procedure between the SRNC and the DRNC.
  • Embodiments of the present invention both speed up the cell update procedure when a DRNC is involved and reduce the volume of signalling traffic over the lur interface.
  • the RNSAP procedure is performed when the UE first moves into a cell of the DRNC and following the forwarding of an RRC Cell Update message from the DRNC to the SRNC using the RNSAP Uplink Signalling Transfer procedure, the procedure comprising sending a RNSAP Common Transport Channel Resource Request message from the SRNC to the DRNC, and sending a RNSAP Common Transport Channel Resource Response message from the DRNC to the SRNC, one of said Cell Update message and said response containing said information element.
  • Figure 1 illustrates a protocol model for a FACH transport channel when serving and controlling RNCs of the UTRAN are coincident;
  • Figure 2 illustrates a protocol model for a FACH transport channel when serving and controlling RNCs of the UTRAN are separate;
  • Figure 3 illustrates schematically a part of a UMTS network
  • Figure 4 is a flow diagram illustrating a method of handling cell updates via lur in the
  • Figure 5 illustrates the flow of signalling information related to a cell update between a
  • Figure 3 illustrates a part of a UMTS network comprising a core network 1 and a UMTS terrestrial radio access network (UTRAN) 2. Shown in the UTRAN 2 are a pair of Radio Network Controllers (RNCs) 4,5, each of which has control of a set of Node Bs 6. Each Node B 6 provides radio coverage of a particular geographic cell, with the cells of neighbouring Node Bs overlapping.
  • RNCs Radio Network Controllers
  • a UE 7 is shown communicating with one of the Node Bs of a first of the RNCs 4.
  • the UE is assumed to move from the coverage area of the Node B of the first RNC 4 into the coverage area of a Node B of the second RNC 5.
  • the effect of the UE 7 roaming in this way is to cause the UE to take advantage of common transport channels (RACH/FACH) of the second RNC 5, the drift RNC (DRNC).
  • RACH/FACH common transport channels
  • DRNC drift RNC
  • the RRC protocol remains terminated at the first RNC, the serving RNC (SRNC).
  • the UE 7 will send an RRC Cell Update message to the SRNC 4 to inform the SRNC of its new location.
  • the Cell Update message contains the U-RNTI (SRNC Id + RNTI (Radio Network Temporary Identity)) which identifies the UE within UTRAN.
  • the DRNC checks the U-RNTI. As the UE is not registered in the DRNC, the DRNC forwards the Cell Update message, using the RNSAP Uplink Signalling Transfer message, to the SRNC based on the SRNC Id in the U-RNTI.
  • the SRNC 4 When the SRNC 4 receives the first Cell Update message from the DRNC, the SRNC 4 updates its cell location register, and initiates the RNSAP Common Transport Channel Resources Initialisation procedure. This involves the sending of a RNSAP Common Transport Channel Resource Request to the DRNC.
  • This message is a request to establish the user plane towards the DRNC 5 and for the DRNC to return to the SRNC 4 the FACH transport channel configuration for the cell in which the UE 7 is now located.
  • this configuration information includes the scheduling priority, MAC-c/sh SDU length(s), and initial window size.
  • the DRNC 5 responds to receipt of the RNSAP request message by generating and returning to the SRNC 4 a RNSAP Common Transport Channel Resource Response.
  • This message has the following structure:
  • the RNSAP response message includes an additional information element (IE) referred to as "Cell Unique FACH Flow Control Info”.
  • IE additional information element
  • This element contains a flag which can be set to yes to indicate that the FACH transport channel configurations for all of the cells of the DRNC 5 are the same, or no to indicate that the configuration differs from cell to cell.
  • the flag is set by the DRNC 5. It is noted that whilst in the above table, the additional IE is indicated as being mandatory, this need not be so and it may be included as an optional feature.
  • the Cell Unique FACH Flow Control Info IE is analysed. If the IE is set to yes, the SRNC 4 records the fact that it must execute the RNSAP Common Transport Channel Resource Initialisation procedure for every subsequent cell update in the DRNC 5. If the IE is set to no, the SRNC 4 records the fact that the procedure is not needed for subsequent cell updates within the DRNC 5.
  • Figure 4 is a flow diagram further illustrating the method described above.
  • Figure 5 illustrates the flow of signalling information over the lur interface.
  • DRNC may exist prior to the first cell update. If the UE is using dedicated channels
  • the SRNC may decide to perform a channel switch from DCH to FACH (e.g. if the UE has only a best effort packet data RAB and the traffic activity is low). In this case the SRNC may: a) select the target cell for the UE when switching to
  • the SRNC indicates in RRC signalling to the
  • the SRNC will perform the RNSAP Common Transport Channel Resource Initiation procedure without first having received a cell update from the UE via the DRNC.
  • the RNSAP Common Transport Channel Resource Initiation procedure without first having received a cell update from the UE via the DRNC.

Landscapes

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

Abstract

In a UMTS radio access network, a method of informing a serving RNC, SRNC, of the FACH transport channel configuration allocated by a drift RNC (DRNC) 5 to user equipment (UE) 7. When the UE 7 first moves into a cell of the DRNC 5, forwarding an RRC Cell Update message from the DRNC 5 to the SRNC 4, sending a RNSAP Common Transport Channel Resource Request message from the SRNC 4 to the DRNC 5, and sending a RNSAP Common Transport Channel Resource Response message from the DRNC 5 to the SRNC 4, said response containing an information element indicating whether FACH flow control information contained in the response is unique to the DRNC cell to which the procedure relates, or whether the information is common to all of the cells of the DRNC. If said information element indicates that the information is common to all of the cells of the DRNC 5, the SRNC 4 does not perform the RNSAP Common Transport Channel Resources Initialisation procedure for subsequent Cell Update messages received from the DRNC 5.

Description

Cell Updates in a UMTS Terrestrial Radio Access Network
Field of the Invention
The present invention relates to the handling of cell updates at the lur interface of a UMTS Terrestrial Radio Access Network (UTRAN), the lur interface being the interface between Radio Network Controllers (RNCs) of the UTRAN.
Background to the Invention
The European Telecommunications Standardisation Institute (ETSI) is currently in the process of standardising a new set of protocols for mobile telecommunications systems. The set of protocols is known collectively as the Universal Mobile Telecommunications System (UMTS). The architecture of a UMTS network is based upon a UMTS core network and a UMTS Terrestrial Radio Access Network (UTRAN). The UTRAN comprises a number of Radio Network Controllers (RNCs), each of which is coupled to a set of neighbouring Base Transceiver Stations (BTSs) or Node Bs. Each Node B is responsible for a given geographical area or cell, and the controlling RNC is responsible for routing user and signalling data between that Node B and the core network. The interface between an RNC and a Node B is referred to as the Iu interface. A general outline of the UTRAN is given in Technical Specification TS 25.401 (UTRAN overall description) of the 3rd Generation Partnership Project, 3 GPP.
User and signalling data may be carried between an RNC and a mobile terminal (referred to in UTRAN as User Equipment (UE)) using Radio Bearers (RBs). Typically, a mobile terminal is allocated one or more RBs, each of which is capable of carrying a flow of user or signalling data. At a Radio Link Control (RLC) entity, RBs are mapped onto respective logical channels. At a Media Access Control (MAC) entity, a set of logical channels is mapped in turn onto a transport channel, of which there are two types: a "common" transport channel which is shared by different mobile terminals and a "dedicated" transport channel which is allocated to a single mobile terminal. One type of common channel is a Forward Access CHannel (FACH). Several transport channels (e.g. FACHs) are in turn mapped at the physical layer onto a Secondary Common Control Physical CHannel (S-CCPCH) for transmission over the air interface between a Node B and a mobile terminal.
When a mobile terminal registers with an RNC, via a Node B, that RNC acts at least initially as both the serving and controlling RNC for the mobile terminal. The RNC both controls the air interface radio resources and terminates the layer 3 intelligence (Radio Resource Control (RRC) protocol), routing data associated with the mobile terminal directly to and from the core network. Figure 1 illustrates the protocol model for the FACH transport channel when the serving and controlling RNCs are coincident and where Uu indicates the interface between the UTRAN and the mobile terminal (UE), and Iub indicates the interface between the RNC and a Node B. It will be appreciated that the MAC (MAC-c) entity in the RNC transfers MAC-c Packet Data Units (PDUs) to the peer MAC-c entity at the mobile terminal, using the services of the FACH Frame Protocol (FACH FP) entity between the RNC and the Node B. The FACH FP entity adds header information to the MAC-c PDUs to form FACH FP PDUs which are transported to the NodeB over an AAL2 (or other transport mechanism) connection. An interworking function at the Node B interworks the FACH frame received by the FACH FP entity into the PHY entity.
Consider now the situation which arises when a mobile terminal leaves the area covered by a RNC with which the terminal is registered, and enters the area covered by a second RNC. Under the UTRAN protocols, the RRC remains terminated at the first RNC whilst the terminal takes advantage of a cell and common transport channel of the second RNC. Thus, the first RNC remains as the serving RNC with a connection to the core network whilst the second RNC becomes the controlling RNC. The controlling RNC is in control of the NodeB where the mobile terminal is located and in particular of the logical resources (transport channels) at that Node B. In this scenario the controlling RNC is referred to as a "drift" RNC (the controlling RNC will also be acting as a serving RNC for mobile terminals registered with that RNC). The protocol model for the FACH transport channel when the serving and controlling RNCs are separate is illustrated in Figure 2. It will be noted that a new interface lur is exposed between the serving and the controlling RNCs. The RNSAP protocol is used for control plane signalling on the lur interface. When a mobile terminal first moves into the coverage area of the (new) DRNC, the mobile terminal must send an RRC Cell Update message to the SRNC to inform the SRNC of its new location. The RRC Cell Update message (L3 information) is forwarded by the DRNC to the SRNC using the RNSAP UL Signalling Transfer message. Upon receipt of a Cell Update, the SRNC must determine the configuration (scheduling priority, MAC-c/sh SDU length(s), and initial window size) of the FACH transport channel used by the DRNC for the cell to which the update relates. According to the current standard, the SRNC responds to receipt of a Cell Update by sending a RNSAP Common Transport Channel Resource Request message to the DRNC over the lur interface. The DRNC responds with a RNSAP Common Transport Channel Resource Response message containing the configuration information.
In some network configurations, the FACH transport channel configuration may be the same for all cells of an RNC. In other network configurations, the configuration may differ from cell to cell. The current standard handles this situation by performing the RNSAP procedure (request and response sequence) each time a Cell Update is received at the SRNC over the lur interface, i.e. for the first and subsequent cell updates.
Summary of the Invention
The approach adopted by the current standard has two main disadvantages. Firstly, the RNSAP exchange procedure introduces a delay into the cell update procedure. This may cause an interruption in the service provided to a mobile terminal and results in a less than optimal use of radio resources. Secondly, the procedure increases the signalling load on the lur interface. In communications networks, a greater signalling load often results in higher infrastructure costs.
According to a first aspect of the present invention there is provided, in a UMTS radio access network, a method of informing a serving RNC, SRNC, of the FACH transport channel configuration allocated by a drift RNC, DRNC, to user equipment, UE, the method comprising: including in a RNSAP message sent from the DRNC to the SRNC, an information element indicating whether FACH flow control information contained in the response is unique to the DRNC cell, or whether the information is common to all of the cells of the DRNC, wherein if said information element indicates that the information is common to all of the cells of the DRNC, the SRNC does not perform the RNSAP Common Transport Channel Resources Initialisation procedure, request/response sequence, for Cell Update messages subsequently received from the DRNC.
In one embodiment of the invention, said RNSAP message is sent as part of a RNSAP Common Transport Channel Resources Initialisation procedure between the SRNC and the DRNC.
Only in the event that the RNSAP Common Transport Channel Resource Response message indicates that the FACH flow control information is not common to all cells will the RNSAP Common Transport Channel Resources Initialisation procedure be , repeated for subsequent cell updates corresponding to movement of the UE between two cells of the DRNC. Embodiments of the present invention both speed up the cell update procedure when a DRNC is involved and reduce the volume of signalling traffic over the lur interface.
In one embodiment of the present invention, the RNSAP procedure is performed when the UE first moves into a cell of the DRNC and following the forwarding of an RRC Cell Update message from the DRNC to the SRNC using the RNSAP Uplink Signalling Transfer procedure, the procedure comprising sending a RNSAP Common Transport Channel Resource Request message from the SRNC to the DRNC, and sending a RNSAP Common Transport Channel Resource Response message from the DRNC to the SRNC, one of said Cell Update message and said response containing said information element.
Brief Description of the Drawings Figure 1 illustrates a protocol model for a FACH transport channel when serving and controlling RNCs of the UTRAN are coincident;
Figure 2 illustrates a protocol model for a FACH transport channel when serving and controlling RNCs of the UTRAN are separate;
Figure 3 illustrates schematically a part of a UMTS network;
Figure 4 is a flow diagram illustrating a method of handling cell updates via lur in the
UMTS network of Figure 3; and
Figure 5 illustrates the flow of signalling information related to a cell update between a
DRNC and a SRNC.
Detailed Description of a Preferred Embodiment
Protocol models for the FACH transport channel of a UMTS network have been described with reference to Figures 1 and 2 for the cases where the serving RNC and controlling RNC are both coincident and separate. Figure 3 illustrates a part of a UMTS network comprising a core network 1 and a UMTS terrestrial radio access network (UTRAN) 2. Shown in the UTRAN 2 are a pair of Radio Network Controllers (RNCs) 4,5, each of which has control of a set of Node Bs 6. Each Node B 6 provides radio coverage of a particular geographic cell, with the cells of neighbouring Node Bs overlapping.
In the scenario illustrated in Figure 3, a UE 7 is shown communicating with one of the Node Bs of a first of the RNCs 4. The UE is assumed to move from the coverage area of the Node B of the first RNC 4 into the coverage area of a Node B of the second RNC 5. The effect of the UE 7 roaming in this way is to cause the UE to take advantage of common transport channels (RACH/FACH) of the second RNC 5, the drift RNC (DRNC). As described above, the RRC protocol remains terminated at the first RNC, the serving RNC (SRNC). The UE 7 will send an RRC Cell Update message to the SRNC 4 to inform the SRNC of its new location. This message is sent via the DRNC 5 across the lub and lur interfaces (and is the first connection between the UE and the DRNC). The Cell Update message contains the U-RNTI (SRNC Id + RNTI (Radio Network Temporary Identity)) which identifies the UE within UTRAN. At reception of the Cell Update message, the DRNC checks the U-RNTI. As the UE is not registered in the DRNC, the DRNC forwards the Cell Update message, using the RNSAP Uplink Signalling Transfer message, to the SRNC based on the SRNC Id in the U-RNTI.
When the SRNC 4 receives the first Cell Update message from the DRNC, the SRNC 4 updates its cell location register, and initiates the RNSAP Common Transport Channel Resources Initialisation procedure. This involves the sending of a RNSAP Common Transport Channel Resource Request to the DRNC. This message is a request to establish the user plane towards the DRNC 5 and for the DRNC to return to the SRNC 4 the FACH transport channel configuration for the cell in which the UE 7 is now located. As already stated above this configuration information includes the scheduling priority, MAC-c/sh SDU length(s), and initial window size.
The DRNC 5 responds to receipt of the RNSAP request message by generating and returning to the SRNC 4 a RNSAP Common Transport Channel Resource Response. This message has the following structure:
Figure imgf000007_0001
where the presence field indicates whether or not the information elements of the message are mandatory (M) or optional (O). The RNSAP response message includes an additional information element (IE) referred to as "Cell Unique FACH Flow Control Info". This element contains a flag which can be set to yes to indicate that the FACH transport channel configurations for all of the cells of the DRNC 5 are the same, or no to indicate that the configuration differs from cell to cell. The flag is set by the DRNC 5. It is noted that whilst in the above table, the additional IE is indicated as being mandatory, this need not be so and it may be included as an optional feature.
When the RNSAP response is received by the SRNC 4, the Cell Unique FACH Flow Control Info IE is analysed. If the IE is set to yes, the SRNC 4 records the fact that it must execute the RNSAP Common Transport Channel Resource Initialisation procedure for every subsequent cell update in the DRNC 5. If the IE is set to no, the SRNC 4 records the fact that the procedure is not needed for subsequent cell updates within the DRNC 5.
Figure 4 is a flow diagram further illustrating the method described above. Figure 5 illustrates the flow of signalling information over the lur interface.
It will be appreciated by the person of skill in the art that various modifications may be made to the above described embodiments without departing from the scope of the present invention. For example, it is possible that a connection between the UE and the
DRNC may exist prior to the first cell update. If the UE is using dedicated channels
(DCHs) via the DRNC, the SRNC may decide to perform a channel switch from DCH to FACH (e.g. if the UE has only a best effort packet data RAB and the traffic activity is low). In this case the SRNC may: a) select the target cell for the UE when switching to
FACH; or b) force the UE to perform a cell update (in this case the target cell is selected by the UE) before switching to FACH. The SRNC indicates in RRC signalling to the
UE whether the UE shall use a cell selected by the SRNC (alternative a) or perform a cell update (alternative b). In alternative a, the SRNC will perform the RNSAP Common Transport Channel Resource Initiation procedure without first having received a cell update from the UE via the DRNC. In alternative b, the RNSAP Common
Transport Channel Resource Initialisation procedure follows a cell update.

Claims

Claims
1. In a UMTS radio access network, a method of informing a serving RNC, SRNC, of the FACH transport channel configuration allocated by a drift RNC, DRNC, to user equipment, UE, the method comprising: including in a RNSAP message sent from the DRNC to the SRNC, an information element indicating whether FACH flow control information contained in the response is unique to the DRNC cell, or whether the information is common to all of the cells of the DRNC, wherein if said information element indicates that the information is common to all of the cells of the DRNC, the SRNC does not perform the RNSAP Common Transport Channel Resources Initialisation procedure, request/response sequence, for Cell Update messages subsequently received from the DRNC.
2. A method according to claim 1, wherein said RNSAP message is sent as part of a RNSAP Common Transport Channel Resources Initialisation procedure between the SRNC and the DRNC.
3. A method according to claim 2 and comprising performing the RNSAP procedure when the UE first moves into a cell of the DRNC and following the forwarding of an RRC Cell Update message from the DRNC to the SRNC using the RNSAP Uplink Signalling Transfer procedure, the procedure comprising sending a RNSAP Common Transport Channel Resource Request message from the SRNC to the DRNC, and sending a RNSAP Common Transport Channel Resource Response message from the DRNC to the SRNC, one of said Cell Update message and said response containing said information element.
4. A method according to claim 1, wherein said RNSAP procedure is carried out as part of a channel switch, from a DCH to a FACH.
5. A method according to claim 1, wherein said RNSAP procedure follows receipt of a cell update message from the UE at the SRNC.
6. A Radio Network Controller for use in a UTRAN and comprising processing means for implementing the method of any one of the preceding claims.
PCT/EP2002/009005 2001-09-28 2002-08-12 Cell updates in a umts terrestrial radio access network WO2003030568A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB0123308A GB2371179B (en) 2001-09-28 2001-09-28 Cell updates in a UMTS terrestrial radio access network
GB0123308.9 2001-09-28

Publications (1)

Publication Number Publication Date
WO2003030568A1 true WO2003030568A1 (en) 2003-04-10

Family

ID=9922845

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2002/009005 WO2003030568A1 (en) 2001-09-28 2002-08-12 Cell updates in a umts terrestrial radio access network

Country Status (2)

Country Link
GB (1) GB2371179B (en)
WO (1) WO2003030568A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005020476A1 (en) * 2003-08-22 2005-03-03 Samsung Electronics Co., Ltd. Method for srnc inquiring of channel type
WO2008037217A1 (en) * 2006-09-25 2008-04-03 Huawei Technologies Co., Ltd. Method, apparatus and system for preventing periodical cross-cell update from failure
WO2011022960A1 (en) * 2009-08-28 2011-03-03 中兴通讯股份有限公司 Method and apparatus for notifying multimedia broadcast multicast service capability

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2387294B (en) * 2002-04-03 2004-02-18 Lucent Technologies Inc A method in a third generation or higher telecommunications network
JP4411842B2 (en) 2003-01-10 2010-02-10 日本電気株式会社 Mobile communication system, radio control apparatus used therefor, and operation control method thereof
US7423993B2 (en) * 2003-02-10 2008-09-09 Nokia Corporation Connection release in communication network
US8923236B2 (en) 2006-11-01 2014-12-30 Lg Electronics Inc. Method of transmitting and receiving paging messages in a wireless communication system
TWI446807B (en) 2006-11-01 2014-07-21 Lg Electronics Inc Method of transmitting and receiving paging messages in a wireless communication system
WO2008054158A2 (en) 2006-11-01 2008-05-08 Lg Electronics Inc. Methods of transmitting and receiving downlink data in wireless communication system
TW201538014A (en) 2007-02-05 2015-10-01 Interdigital Tech Corp Paging over a high-speed downlink shared channel
KR101193478B1 (en) 2007-09-28 2012-10-24 인터디지탈 패튼 홀딩스, 인크 Method and apparatus for terminating transmission of a message in an enhanced random access channel
KR20100089883A (en) 2007-10-25 2010-08-12 인터디지탈 패튼 홀딩스, 인크 Methods and apparatuses for management and setup of enhanced mac-e/es resources in cell-fach state
US8325684B2 (en) 2008-01-02 2012-12-04 Interdigital Patent Holdings, Inc. Method and apparatus for cell reselection

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998032303A2 (en) * 1997-01-20 1998-07-23 Nokia Telecommunications Oy Routing area updating in packet radio network
US20010018345A1 (en) * 1999-06-07 2001-08-30 Fabio Longoni Cell update in a cellular communications system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6829482B2 (en) * 2000-05-16 2004-12-07 Telefonaktiebolaget Lm Ericsson (Publ) Switching from dedicated to common channels when radio resources are controlled by drift radio network

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1998032303A2 (en) * 1997-01-20 1998-07-23 Nokia Telecommunications Oy Routing area updating in packet radio network
US20010018345A1 (en) * 1999-06-07 2001-08-30 Fabio Longoni Cell update in a cellular communications system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
BRASCHE G ET AL: "CONCEPTS, SERVICES, AND PROTOCOLS OF THE NEW GSM PHASE 2+ GEBERAKL PACKET RADIO SERVICE", IEEE COMMUNICATIONS MAGAZINE, IEEE SERVICE CENTER. PISCATAWAY, N.J, US, vol. 35, no. 8, 1 August 1997 (1997-08-01), pages 94 - 104, XP000704443, ISSN: 0163-6804 *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005020476A1 (en) * 2003-08-22 2005-03-03 Samsung Electronics Co., Ltd. Method for srnc inquiring of channel type
WO2008037217A1 (en) * 2006-09-25 2008-04-03 Huawei Technologies Co., Ltd. Method, apparatus and system for preventing periodical cross-cell update from failure
DE112007000077B4 (en) * 2006-09-25 2013-07-18 Huawei Technologies Co., Ltd. A method, apparatus and system for avoiding the absence of periodic radio cell update
WO2011022960A1 (en) * 2009-08-28 2011-03-03 中兴通讯股份有限公司 Method and apparatus for notifying multimedia broadcast multicast service capability

Also Published As

Publication number Publication date
GB0123308D0 (en) 2001-11-21
GB2371179B (en) 2004-01-07
GB2371179A (en) 2002-07-17

Similar Documents

Publication Publication Date Title
EP1222830B1 (en) Method of scheduling packets for transmission over a umts network
US7471957B2 (en) Paging method and system for a radio access network
US6721566B2 (en) Cell update in a cellular communications system
US7254392B2 (en) Intersystem handover with modified parameters
EP2053899B1 (en) Transfer of optimization algorithm parameters during handover of a mobile station between radio network subsystems
EP1269773B1 (en) Relocation of serving radio network controller with signaling of linking of transport channels
US7215958B2 (en) Relocation method, system and network element
KR100531144B1 (en) Relocation in a communication system
JP2003533926A (en) Connections in communication systems
EP1792445A1 (en) Data transmission method and network elements
JP2007520901A (en) Data transmission optimization in packet data networks
WO2003030568A1 (en) Cell updates in a umts terrestrial radio access network
EP1260112B1 (en) Intersystem handover with modified parameters
US7292839B2 (en) Macrodiversity system with signal combining in the base station
WO2003045088A1 (en) Method for recovering from an abnormal release in a umts network
WO2002084952A1 (en) Flow control in radio access networks
GB2368243A (en) Error handling in the Iur interface of a UMTS terrestrial radio access network
WO2003047299A1 (en) Mobile communication paging

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BY BZ CA CH CN CO CR CU CZ DE DM DZ EC EE ES FI GB GD GE GH HR HU ID IL IN IS JP KE KG KP KR LC LK LR LS LT LU LV MA MD MG MN MW MX MZ NO NZ OM PH PL PT RU SD SE SG SI SK SL TJ TM TN TR TZ UA UG US UZ VC VN YU ZA ZM

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ UG ZM ZW AM AZ BY KG KZ RU TJ TM AT BE BG CH CY CZ DK EE ES FI FR GB GR IE IT LU MC PT SE SK TR BF BJ CF CG CI GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP