Академический Документы
Профессиональный Документы
Культура Документы
A40609VI
(12) INTERNATIONAL APPLICATION PUBLISHED UNDER THE PATENT COOPERATION TREATY (PCT)
9
(l ) World Inl~~~:::~:~~~':~:: O<gan;zation • Illll lllllll II lllll lllll lllll lllll llll III Ill lllll lllll lllll 111111111111111111111111111111111
-- E-DCH SET-UP
SHO INITIATED
202
communication system including at least one
access controller and a plurality of access points,
--
iiiiiiii
SOURCE SCHEDULING NODES
SELECTED AND RUNNING
204
an enhanced dedicated channel, the access
controller comprising: determining means for
determining an access point to be a controlling
access point; and initiating means for initiating
-
i iiiiiii
iiiiiiii N
the control at the controlling access point.
--
PREPARE TO SWITCH 208
COMMUNICATION SYSTEM
In one approach for Node B control scheduling for E-DCH during Inter-
Node B SHO under discussion, it has been discussed that all Node B's,
which are controlling one or more cells in the UE active sets, execute
20 scheduling during the SHO.
In a further approach, it has been discussed that only the Node B which is
controlling the best uplink or downlink cell executes the scheduling during
the SHO. In this approach, a switching between two Node B's is needed for
the execution of the scheduling. That is, there is a need for switching
25 between the Node B which is executing the scheduling, defined to be the
source scheduling Node B, and the Node B that will execute the
scheduling, defined to be the target scheduling Node B, during inter- Node
B SHO. In the event that the E-DCH is setup during inter-Node B SHO,
the Node B which starts to execute the scheduling must know about it,
30 whereas the Node B which does not execute the scheduling should know
WO 2006/018715 PCT/IB2005/002499
3
The step of determining the access point may comprise selecting one
access point from a plurality of access points. The method may further
comprise the step of inhibiting control at any access point other than the
access point selected as the control access point. The step of inhibiting
25 control may comprise notifying the access points of their non-selection.
The step of determining an access point to be a control access point may
include selecting a new access point to replace an existing control access
point, the method further including the step of inhibiting the existing
control access point. The step of determining an access point to be a
30 control access point may be responsive to detection of a more suitable
WO 2006/018715 PCT/IB2005/002499
4
access point for control than an existing control access point. The detection
of a more suitable access point may be made by an access controller.The
step of determining an access point to be a control access point may be
responsive to initiation of an enhanced dedicated channel during soft
5 handover. The method may further comprise the step, responsive to a
scheduling update or change, of transmitting an update notification from
the access point to an access controller.
15 The method may comprise the step of determining an access point more
suitable for scheduling, and selecting such access point as the target
access point. The method may further comprise the step of providing
information from the source scheduling access point to the target
scheduling access point. The method may further include the step of
20 notifying the non·selected access points that they are non·selected. The
step of selecting a target scheduling access point may comprise
determining, at an access controller, the access point having the strongest
uplink or downlink connection with a user equipment. Responsive to
completion of a scheduling change or update, the ta.rget access point may
25 transmit an update message. The update message may be transmitted to
an access controller.
The access controller may further comprise means for inhibiting control at
any access point other than the access point selected as the control access
point.
The means for inhibiting control may comprise means for transmitting to
10 the access points notice of their non·selection. The access controller may
further include means for selecting a new access point to replace an
existing control access point, and further including means for inhibiting
the existing control access point. The means for determining an access
point to be a control access point may be responsive to means for detecting
15 a more suitable access point for control than an existing control access
point. The means for determining an access point to be a control access
point may be responsive to a means for initiating an enhanced dedicated
channel during soft handover. The access controller may further comprise
means, responsive to a scheduling update or change, for receiving an
20 update notification from the access point.
scheduling access point to the target scheduling access point. The access
controller may further include means for notifying the non·selected access
points that they are non-selected. The means for selecting a target
scheduling access point may comprise means for determining the access
5 point having the strongest uplink or downlink connection with a user
equipment. The access controller may include means, responsive to
completion of a scheduling change or update, for receiving an update from
the target access point.
The access point may comprise a Node B of a UMTS system. The access
controller may comprise a radio network controller of a UMTS system.
Signalling to the access point may comprise RNSAP/NBAP messages.
Signalling to the access point may comprise DL FP messages.
The access controller may further comprise means for notifying the others
of the plurality of access points of their non-selection for scheduling.
' The invention will now be described by way of example with reference to
the accompanying figures, in which:
As is known in the art, the at least one user equipment 110 connects with
one of the Node Bs, for example Node B 108a, over a radio interface 112,
20 known in the 3GPP UMTS system as a Uu interface.
Each Node B is connected to at least one RNC via an lub interface. The
RNC 106b connects to the Node Bs 108a and l08b via Iub interfaces 118a
and 118b respectively, and possibly to one or more other Node Bs. The
RNC 106c connects to the Node B 108c via lub interface 122a, and to one or
25 more other Node Bs via one or more other lub interfaces, such as interface
122b. The RNC 106a connects to one or more Node Bs via one or more lub
interfaces, such as interface 120a. Various RNCs may connect to various
Node Bs, as known in the art.
interface 130a, and the RNC 106b is connected to the RNC 106c via an Iur
interface 130b. The RNCs 106a and 106c may similarly be interconnected
via an Iur interface. The various RNCs may be interconnected via Iur
interface.
10 It has been proposed, in 3GPP TSG-RAN, for a new enhanced DCH uplink
transport channel. The DCH uplink transport channel is a channel for
transporting traffic from a user equipment to a Node B in the radio
interface Uu, and for transporting traffic from a Node B to an RNC, and
between RNCs, on the Iub interface or the Iur interface. Embodiments of
15 the invention propose various improvements and enhancements to support
the enhanced DCH.
although the invention is not limited to such. Thus preferably the serving
RNC makes the scheduling decisions for the E· DCH, configures the Node
Bs accordingly, and informs the UE as to the decisions made.
As denoted by step 204, a source scheduling Node B has been selected and
is running. The source scheduling Node B may have been selected in any
10 known way, and the initial selection of a scheduling Node B for E· DCH is
outside the scope of this mode of operation.
20 The serving RNC of the UE is always the RNC in control of all radio links
to the given UE.' Thus even where there is another Node B that is
connected to the serving RNC via another RNC, the serving RNC remains
in control. Relocation of the serving RNC of any given connection, as
known in the art, may occur in combination with other features of this
25 invention, but is in itself outside the scope of the invention. The invention
is relevant to the selection or change of a scheduling Node B, not which
RNC is making the decision to select or change the scheduling Node B.
The change of the scheduling Node B may or may not require for
information to be relayed from the source scheduling Node B to the target
10 scheduling Node B. In such case, the relaying of information allows the
target scheduling Node B to synchronise information related to the
scheduling to information known by the source scheduling Node B. The
need for relaying of information will be dependent upon implementation
requirements. In current implementations, the Node B's are not able to
15 communicate directly with each other, but communicate through the
RNCs they are connected to. If a Node Bis not connected to the serving
RNC of the radio link, then it may communicate any necessary signalling
through the RNC with which it is connected.
setup during an actual SHO. The first mode (described above) relates to a
scenar10 where there is a need to transfer between two scheduling
Node Bs during an SHO and with an existing E-DCH setup. In this
method, as the SHO is taking place the serving RNC becomes aware of
5 an E-DCH setup.
In such a situation a DCH channel may already exist in the SHO. DCH
15 and E·DCH are always connected to the same Node Bs, thus experiencing
the same SHO status.
After the SRNC is notified or made aware of the E·DCH setup during the
SHO, the SRNC determines the scheduling Node B, preferably by
determining the Node B which is controlling the best uplink/downlink
25 cell. However the exact criteria on which the scheduling Node B is selected
is network implementation specific. The serving RNC is thus able to
determine the one of the Node Bs to be the scheduling Node B in
dependence on some implementation criteria, which may be standardised.
The invention is not limited to any specific arrangement. The selection of a
30 particular Node Bas the scheduling Node Bis represented by step 306 of
Figure 3.
WO 2006/018715 PCT/IB2005/002499
14
The invention and embodiments thereof are not limited to any specific
messaging implementation. It is merely sufficient that the Node B which
is to carry out the scheduling is informed of such, and it is ensured that no
other Node Bs carry out scheduling. It may not be necessary to send any
15 message to the other Node Bs. However it may be preferable to notify the
other Node Bs of the Node B which has become the scheduling Node B.
All the messages then sent to the scheduling Node B may have different
contents to the non-scheduling Node B.
After signalling to the Node Bs, the selected scheduling Node B starts
20 scheduling, as denoted by step 308 in Figure 3.
As denoted by step 404, a source scheduling Node B has been selected and
30 is running. The source scheduling Node B may have been selected in any
WO 2006/018715 PCT/IB2005/002499
15
known way, and the initial selection of a scheduling Node B for E-DCH is
outside the scope of this mode of operation.
20 It can be seen from the above descriptions that the first and second mode
of operations share a concept of deciding upon a Node B to be a scheduling
Node B, informing the selected Node B that it is the scheduling Node B,
and informing the other Node Bs participating in the SHO that they are
not the scheduling Node Bs. The third mode of operation represents a
25 refinement to the first and second mode and any common features thereof.
It should also be noted that each of the three modes of operation may,
taken in isolation, offer improved operation during SHO in respect of the
E-DCH. Any aspect of any one mode of operation may be introduced into
another mode of operation.
added and removed in a way such that the user equipment always
maintains at least one radio link with the radio access network. Soft
handover is performed by means of macro diversity, which refers to a
condition where several radio links are active at the same time. The
5 active radio links for a soft handover are generally known as soft handover
branches. Two or more soft handover branches may terminate in the
same radio network controller.
CLAIMS:
12.A method according to claim 11 wherein the method comprises the step
of determining an access point more suitable for scheduling, and
15 selecting such access point as the target access point.
26.A method according to any one preceding claim in which the access
point comprises a Node B of a UMTS system.
1/4
106a
120a
RNC
MSC
lur
· 130a
118a
Node B
x
. 112
uu
. UE
110
RNC 108a
FIG 1
2/4
FIG 2
3/4
1-----------*-----------,
1 STEP 202 ~,,,. 310
1· FIG 2 r ,_
L----------~---~------~
FIG 3
414
I STEP 202 I
I OF FIG 2 I
L-----------------~~---
FIG4
According to International Patenl Classification (IPC) or to both national classification and IPC
B. FIELDS SEARCHED
Minimum documentation searched (classification system followed by classification symbols)
H04Q
Documentation searched other than minimum documentation to the extent that such documents are included in the fields searched
Electronic data base consulled during the international search (name of data base and, where practical, search terms used)
Category• Citation of document, with indication, where appropriate, of the relevant passages Relevant to claini No.
Date of the actual completion of the International search Date ol mailing of the international search report
D are not the proprietor of the IPR(s) disclosed in the attached IPR Information Statement Annex.
~ To the extent that the IPR(s) disclosed in the attached IPR Information Statement Annex are or
become, and remain ESSENTIAL in respect of the ETSI Work Item, STANDARD and/or TECHNICAL
SPECIFICATION identified in the attached IPR Information Statement Annex, the Declarant and/or its
AFFILIATES are prepared to grant irrevocable licences under this/these IPR(s) on terms and
conditions which are in accordance with Clause 6. 1 of the ETSI IPR Policy.
~ This irrevocable undertaking is made subject to the condition that those who seek licences
agree to reciprocate (check box if applicable).
D The Declarant and/or its AFFILIATES are not prepared to make the above IPR Licensing Declaration
(reasons may be explained in writing in the attached IPR Licensing Declaration Annex)
The construction, validity and performance of this IPR information statement and licensing declaration shall
be governed by the laws of France.
Terms in ALL CAPS on this form have the meaning provided in Clause 15 of the ETSI IPR Policy.
SIGNATURE
By signing this IPR Information Statement and Licensing Declaration form, you represent that you have the
authority to bind the Declarant and/or its AFFILIATES to the representations and commitments provided in
this form.
Name of authorized person: Kalle Moilanen
Title of authorized person: IPR Manager
Place, Date: Salo, Finland, 26 1h of March 2009
Method of US 2005270942 AU
controlling 200580031004 .5 CN101049033A CN
communication 05757197 .8 1774804 EP
10/9848 2006003
25 .321 9.2.5.2 74.0 between two PCT/IB2005/002092 W02006 /016212 WO
Nokia 48 1563
UMTS nodes in a 2007 -7005334 KR
Corporation
communication 1217/DELNP/2007 IN
system 2007 -524408 2008-509585 JP
7026570/2008 KR
US 05772926.1 1779697 EP
11/2022 2006003 2007526603 2008-510404 JP
25.433 8.2.17.2 6.b.0 Communication PCTIIB2005/002499 W02006/018715 WO
Nokia 25 4224 system AU
UMTS 2005273609
Corporation
200580027767.2 101006743 CN
2007 -7006069 KR
1569/DELNP/2007 IN I
US PE
Use of the FP 000038/2006/01 N
107554 TH
header to signal TW
the RNC that the 95100133
PCT/IB2005/003916 W02006/072826 WO
node B has not
200704968.7 SG
been able to CN
11/3234 2006014 200580045912 X 101095304
5.12, 6.2.2.2 , determine or
25.427 6.3.0 4 736IDELN P/2007 IN
6.2.4.11 Nokia 67 6889 has not been
UMTS 2007 -549960 2008-527823 JP
Corporation able to
MXla/2007/008193 MX
accurately BR
determine the P10519847.0
2592902 CA
number of RU
retransmissions 2007124793
2007-7015374 07-92261 KR
058265547 1834433 EP
出願番号等
特許出願人 発明の名称 備考(出願国名)
REGISTRATION NO./
PATENT HOLDER NAME OF PATENT REMARKS
APPLICATION NO.
NOKIA Delivering services in a wireless communications system JP 2007-525919 CN, DE, EP, FR, GB, IE, IN, KR,
CORPORATION*7.40 US, WO
NOKIA Data transmission in mobile communication system JP 2008-527819 CN, EP, IN, KR, US, WO
CORPORATION*7.40
NOKIA Use of the FP header to signal the R the node B has not been able to JP 2008-527823 BR, CA, CN, DE, EP, IN, KR, MX,
CORPORATION*7.40 determine or has not been able to accurately determine the number of PE, RU, SG, TH, TW, US, WO
retransmissions
NOKIA Apparatus, method and computer program providing enhanced JP 2008-539634 BR, CN, EP, IN, KE, KR, MX, MY,
CORPORATION*7.40 fractional dedicated physical channel downlink power control during PH, RU, TW, US, VN, WO, ZA
soft handover
NOKIA Enhanced uplink dedicated channel - application protocol over JP 2007-529938 AU, BR, CA, CN, EP, IN, KR, MX,
CORPORATION*7.40 lub/lur RU, SG, US, WO, ZA
NOKIA Frame transmission interval JP 2007-537641 AU, CN, EP, IN, KR, TW, US, WO
CORPORATION*7.40
NOKIA Apparatus, Method and computer program product providing closed JP 2009-500890 BR, CN, EP, IN, KR, MX, NG, PH,
CORPORATION*7.40 loop transmit antenna operation for systems using multiple antennas RU, US, VN, WO, ZA
NOKIA Method, system, apparatus and software product for combination of JP 2008-537399 AP, BR, CN, EP, IN, KR, MX, MY,
CORPORATION*7.40 uplink dedicated physical control channel gating and enhanced PH, RU, TW, US, VN, WO, ZA
uplink dedicated channel to improve capacity
NOKIA Expanded signalling capability for network element, user equipment JP 2008-546268 AP, BR, CN, EP, IN, KR, MX, MY,
CORPORATION*7.40 and system NG, PH, RU, US, VN, WO, ZA
NOKIA Dynamic uplink control channel gating to increase capacity JP 2009-504053 AP, BR, CN, EP, IN, KR, MX, MY,
CORPORATION*7.40 NG, PH, RU, US, VN, WO, ZA
221
22
A40773VI
(19)
I
Europilsches
Patentamt
European 111111111111111111111111111111111111111111111111111111111111111111111111111
Patent Office
Office europeen
des brevets
(11) EP 1 808 029 81
(12) EUROPEAN PATENT SPECIFICATION
T"'"
cc
0)
N
0
co
0
co Note: Within nine months of the publication of the mention of the grant of the European patent in the European Patent
Bulletin, any person may give notice to the European Patent Office of opposition to that patent, in accordance with the
T"'"
Implementing Regulations. Notice of opposition shall not be deemed to have been filed until the opposition fee has been
a. paid. (Art. 99(1) European Patent Convention).
w
Printed by Jouve, 75001 PARIS (FR)
EP 1 808 029 81
Description
[0001] The present invention relates to an inter-system handover between a first radio access network and a second
radio access network. Particularly, the invention relates to a terminal-oriented handover having improved characteristics.
5 [0002] The present invention relates to a method of periorming an inter-system handover of a mobile terminal accessing
a communication network via a radio access network (RAN) of a first type. Particularly, the communication network
comprises radio access networks (RAN) of this first type and one or more radio access networks of second types. The
invention equally relates to a corresponding mobile terminal, to a corresponding communication network, to a corre-
sponding communication system and to network elements of the communication network.
10
BACKGROUND OF THE INVENTION
[0003] It is known from the state of the art in a communication system providing different radio access technologies
(RAT) to support an inter-system handover of a mobile terminal between these technologies. Such a handover may be
15 periormed for instance between a 3G (3rd generation) radio access network and a 2G (2nd generation) radio access
network, or within a 3G system between a UTRAN (universal mobile telecommunication services terrestrial radio access
network) employing WCDMA (wideband code division multiple access) and a GSM (global system for mobile commu-
nications) radio access network (RAN). As a prerequisite for an inter-system handover, the mobile terminal in question
is operable with the communication system via all concerned types of radio access networks (RANs). Such mobile
20 terminals are referred to as multi-mode terminals. One example of a multi-mode terminal is a dual-mode terminal which
is operable in 2G and 3G networks.
[0004] The network signalling employed for periorming an inter-system handover between UMTS (Universal Mobile
Telecommunication Services) and GSM is described for example in the technical specification 3GPP TS 23.009V3.14.0
(2003/06): "Handover procedures" (Release 1999)".
25 [0005] There are several reasons for which a change, i.e. an inter-system handover, of the radio access technology
is enabled.
[0006] The most important reason for an inter-system handover is differences of coverage and connection/service
quality in the communication system. In some situations, a mobile terminal may move out of the coverage area of the
first radio access system. Moreover, the radio connection quality provided by this first radio access system may degrade
30 below a given threshold value. If at the same time, another radio access system still provides coverage and or a better
radio connection quality, an inter-system handover can guarantee a continued and satisfactory supply of the mobile
terminal. The first radio access system is typically a GSM/GPRS system and the second radio access system a WCDMA
system.
[0007] Another essential reason for an inter-system handover is load, i.e. the current amount of traffic in different radio
35 access systems. When the load in a first radio access system exceeds a pre-defined threshold value, an overilow of
mobile terminals can be handed over to another radio access system. In this case, the first radio access system is
typically GSM/GPRS and the second radio access system WCDMA.
[0008] A third reason for an inter-system handover is QoS (Quality of Service) requirements of requested services.
The operator of the communication system defines service based handover criteria according to its preferences. These
40 criteria are then stored in a service priority table in the core network, which initiates the handover. The same table resides
additionally in the Radio Network Controller (RNC) of an UTRAN of the communication system. The table in the RNC
can be used in case the RNC receives no handover information from the core network. In an exemplary assignment of
services to different radio access technologies, GSM may be preferred for speech and WCDMA for packet data, while
circuit switched data has to be transmitted using WCDMA. An additional criterion for a service-based handover is load,
45 load and service based handover thus being a more accurate term than service-based handover.
[0009] As specified for example in the technical specification 3G PP TS 25.413 V3.4.0 (2000-12): 'UTRAN lu lnteriace
RANAP Signalling (Release 1999)", a service based handover from a 3G UTRAN to a 2G GSM radio access network
is implemented by an optional parameter called "Service Handover" in the RANAP (radio access network application
part) messages "RAB Assignment Request" and "Relocation Request" on the lu interiace between the core network
50 and an UTRAN. Three values are defined for this parameter, "HO to GSM should be periormed", "HO to GSM should
not be periormed" and "HO to GSM shall not be periormed". Thus, the core network is not able to force the RNC to carry
out a handover from a 3G to a 2G radio access network, but only to propose a handover. The final decision is taken by
the RNC based on additional criteria like load, coverage and radio connection quality. Furthermore, in load and service
based handovers, an RNC hands mobile terminals over to a base station subsystem (BSS) periodically and in groups,
55 not immediately and on an individual basis.
[0010] All known inter-system handovers are decided by the network, which prevents a communication system to
make use of possible advantages of an inter-system handover in several situations.
[0011] The current 3GPP specifications treat UTRAN, GSM and GERAN radio access cells equally, i.e. there are no
2
EP 1 808 029 81
strong means for the network operator or the user to guide a mobile terminal towards the most suitable radio access
technology. It is known to favour one or another public land mobile network (PLMN), location area (LA), routing area
(RA) or cell based on defined criteria. However, cells of different radio access technologies may be mixed in a single
PLMN, LA or RA, and no method has been proposed so far for forcing the mobile terminal to a specific radio access
5 technology, and not even for favouring a certain radio access technology. Only if a requested service cannot be provided
in the current serving cell, the call may be handed over to another cell by the network, or the call may be cleared.
[0012] In the prior art, various methodologies relating to inter-system handover are known.
[0013] For instance, WO 00 27051 A2 describes a system and method for providing a requested service feature to a
mobile station in a cellular telecommunications system. A request is received at a serving mobile switching center to
10 implement a service feature that is not currently being provided for the mobile station, which determines that an inter-
exchange hand-off request that includes a request for the service feature is necessary. The serving mobile switching
center sends a hand-off request message to a target mobile switching center. This hand-off request includes data that
identifies the requested service. Responsive to the hand-off request message and the service request, the target mobile
switching center determines if it is capable of supporting the requested service for the mobile station and sends a return
15 message to the serving mobile switching center indicating whether the target mobile switching center is capable of
supporting the requested service feature.
[0014] US 6,002,933 describes a method and apparatus for operating a cellular telephone system that supports
performing an inter-system soft handoff. A subscriber unit generates a pilot strength measurement report when the pilot
channel from a base station is detected. When a base station controller receiving the pilot strength measurement report
20 determines that the base station is part of a second cellular telephone system, an inter-system soft handoff request is
generated. An admission control subsystem receives the inter-system soft handoff and either grants or denies the request
base on the traffic level with the second cellular telephone system.
[0015] US 2001/007819A1 describes a mobile communication system that performs a hand-off control process based
on channel station data. One of the mobile switching centers in a home system and a mobile switching center in another
25 system are connected to each other by an inter-system channel. When a mobile station moves from the home system
into the other system and hand-off to the other system is to be performed, the inter-system channel data possessed by
a base station controller which is the master station of the mobile station is searched. If the mobile switching center as
the master station has no inter-system channel, then an inter-mobile-switching-center hard hand-off control process is
performed for hand-off to a base station under the control of a mobile switching center having an inter-system channel.
30 If the mobile switching center as the master station has an inter-system channel, then an inter-system hard hand-off
control process is carried out via the inter-system channel.
[0016] US 2003/186698A1 describes a system and method for providing inter-frequency and inter-system handovers.
In response to a transmission that the terminal is to operate at least one of the radio receiver chains of the terminal in
at least one frequency band not used to receive M encoded data streams during at least one identified data frame therein
35 to measure a radio indicator of the at least one frequency band not used to receive the M encoded data streams, the
terminal controller causes at least one of the radio receiver chains to be turned to the at least one frequency band during
the at least one identified data frame and to make measurements therein and to transmit the measurements with at least
one transmitter of the at least one radio transceiver to a station.
[0017] US 2005/073977 A1 describes schemes for performing inter-system handoff. For a MAHHO scheme, the
40 UTRAN uses measurements obtained by a multi-RAT device to determine suitable cdma2000 cell(s) for handover. The
measurements are obtained by a candidate frequency search procedure, and the handover is accomplished by a handoff
execution procedure. For a MDHHO scheme, the UTRAN relies on location information forthe multi-RAT device to select
suitable cdma2000 cell(s) for handover. For a CRHHO scheme, a new call is established on the cdma2000 RAN and
the pending call on the UTRAN is released in a manner such that the handover appears seamless to the multi-RAT
45 device. The multi-RAT device includes two modem processors that perform processing for the UTRAN and cdma2000
RAN and an application processor that control the modem processors.
50 [0018] There is a need, therefore, for a method, a device and a system for enabling service-based inter-system
handover.
[0019] An aspect of the invention resides in a method to enable a mobile terminal in a communication system to initiate
a service-based, Mobile Originating (MO) inter-system handover to a required type of radio access network during service
establishment.
55 [0020] The envisaged solution in accordance with the present invention and its concept provides a terminal originating
service-based inter-system handover, which does not require any additional communications, signalling or the like in
comparison with existing communications and signalling, respectively, beyond those which are likewise performed.
Beneath the lack of additional communications, the solution implies that mobile terminals are still operable within the
3
EP 1 808 029 81
communication network although those do not support the Mobile Originating (MO) service-based inter-system handover,
which lack of functionality merely results in a conventional operation of those mobile terminals. This means, interoperability
with mobile terminals lacking support and network entities or components lacking support is not compromised.
[0021] According to a first aspect of the present invention, a method of initiation an inter-system handover of a mobile
5 terminal accessing a communication network is provided. The hand-over is service-based and the initiation to perform
the inter-system handover originates from the mobile station, i.e. mobile originating inter-system handover. A commu-
nication network comprises at least two radio access networks of different types, i.e. a radio access network of a first
type and a radio access network of a second type. A mobile terminal designed to be operable with the radio access
networks of the communication network accesses the communication network via the radio access network of the first
10 type. The inter-system handover of the mobile terminal is initiated in response to transmitting by the mobile terminal
information including at least one bearer capability field indicating that a requested service is only operable with the
radio access network of the second type. The bearer capability field is set to indicate that the requested service is only
operable with the radio access network of the second type. In particular, at least one bearer capability field is set to a
parameter value, which serves as an indication for the receiving network and its processing entities, respectively, which
15 receiving network is indicated as the target for the inter-system handover initiated by the mobile terminal.
[0022] The inter-system handover of the present invention may be initiated by the mobile terminal because of a lacking
support of the mobile terminal for the requested service in co-operation with the radio access network of the first type.
This means, the radio access network of the first type may or may not support the requested service. Only the capability
of the mobile terminal, whether it is able to use the requested service in co-operation with the radio access network of
20 the first type or not is decisive. In accordance with the first aspect, the mobile terminal is not capable to operate the
requested service with the radio access network of the first type, which may or may not support the service. The total
capabilities of the radio access network of the first type are not crucial.
[0023] According to an embodiment of the present invention, the transmission including the initiation by the means of
at least one bearer capability field is a transmission in accordance with a call control (CC) level procedure and in particular
25 in accordance with a multimedia telephony call establishment procedure. The multimedia telephony call should comprise
at least video telephony call.
[0024] According to another embodiment of the present invention, the transmission is a call control (CC) message.
The call control message is sent from the mobile terminal to the core network of the first type using currently used radio
access network, and in particular to a call control (CC) entity of the core network of the first type. More particularly, the
30 transmission is a standard transmission in accordance with the call control (CC) protocol, which is applied to establish
a call between the mobile terminal and a calling entity or called entity. The calling or called entity may be any entity
inside or outside the communication system such as another mobile terminal accessing the same or another commu-
nication system, a network terminal connected by wire or wireless to the communication system, a terminal of a public
switched telephone network and the like. Preferably the message I information is then forwarded to the core network of
35 the radio access network of the second type, in particular to a mobile services switching center of the core network of
the second type.
[0025] According to yet another embodiment of the present invention, at least one bearer capability field has an
inapplicable value in view of the radio access network of the first type; i.e. a value, which is inapplicable for being used
in setting up a connection in radio access network of the first type.
40 [0026] According to a further embodiment of the present invention, at least one bearer capability field selected from
the plurality of bearer capability fields is distinguished in that at least one parameter value validity of the at least one
bearer capability field differs in communications with the radio access networks of the first type and the second type.
This means, the radio access networks of the first type and the second type expect value, values or set of values, which
differ depending on the type of radio access network. This means also, that at least one bearercapabilityfield is applicable
45 with one of the types of radio access networkand not applicable with the other one.
[0027] According to yet a further embodiment of the present invention, the transmission is a call control (CC) SETUP
message in accordance with a mobile originating (MO) call establishment procedure. A call control entity of the mobile
terminal encodes the SETUP message with one or more Bearer Capability Information Elements (BC IEs), which includes
at least one bearer capability field. Then the mobile terminal transmits the SETUP message to a call control entity of the
50 radio access networkof the first type to initiate the inter-system handover and after completion of handover, to set up a
connection. The inter-system handover is carried out by the receiving network.
[0028] According to an additional embodiment of the present invention, the transmission is a call control (CC) CALL
CON Fl RM ED message in accordance with a Mobile Terminating (MT) call establishment procedure. A call control entity
of the mobile terminal encodes the CALL CONFIRMED message with one or more Bearer Capability Information Elements
55 (BC IEs), which includes the at least one bearer capability field. The mobile terminal transmits the CALL CONFIRMED
message via a radio frequency interface and a wireless communication connection to a call control entity of the radio
access network of the first type to initiate the inter-system handover and then proceed with the call setup. The inter-
system handover is carried out by the receiving network.
4
EP 1 808 029 81
[0029] According to yet an additional embodiment of the present invention, none of the Bearer Capability (BC) Infor-
mation Elements (IE) includes a channel codings field, the value of which is not set to "not acceptable" in order to indicate
to the receiving network the need for inter-system handover.
[0030] The receiving end of the SETUP message and the CALL CONFIRMED message, respectively, i.e. the call
5 control (CC) entity of the message receiving network, analyses the received message and detects the inapplicable value
of the bearer capability fields selected for indication of the inter-system handover.
[0031] According to one more embodiment of the present invention, the radio access network of the first type and the
radio access network of the second type differ in communication technologies employed for realisation thereof. In
particular, the radio access network of the first type is a 2nd generation technology radio access network. The radio
10 access network of the second type is a 3rd generation technology radio access network. More particularly, the radio
access network of the first type is a GSM I GPRS (Global System for Mobile communications I General Packet Radio
System) radio access network and the radio access network of the second type is a WCDMA (Wideband Code Division
Multiple Access) radio access network such as UMTS (Universal Mobile Telecommunication System).
[0032] According to a second aspect of the present invention, a method of initiation an inter-system handover of a
15 mobile terminal accessing a communication network is provided. The communication network comprises at least a radio
access network of a first type and a radio access network of a second type. The mobile terminal is capable of operating
in at least the radio networks of the first type and the second type, The inter-system handover of the mobile terminal
accessing the communication network via the radio access network of the first type is initiated at a network entity of the
communication network in response to receiving from the mobile terminal information including at least one bearer
20 capability field indicating that a requested service is only operable with the radio access network of the second type.
[0033] According to a third aspect of the present invention, a computer program product is provided, comprising
program code sections storable on a computer-readable medium for carrying out the steps of the aforementioned method
according to an embodiment of the present invention, when the computer program product is run on a processor-based
device, a computer, a terminal, a network device, a mobile terminal, or a mobile communication enabled terminal.
25 [0034] According to a fourth aspect a module is provided, which is provided in a mobile terminal. The mobile terminal
is operable with a communication network comprising at least a radio access network of a first type and a radio access
network of a second type. The module is adapted to access the communication network via the radio access network
of the first type.
[0035] The module is configured to transmit information including at least one bearer capability field from the module
30 to the radio access network of the first type for initiating an inter-system handover. The information serves to indicate
that a requested service is only operable with the radio access network of the second type.
[0036] According to a fifth aspect of the present invention, a mobile terminal for initiation of an inter-system handover
within a communication network is provided. The mobile terminal is operable with the communication network, which
comprises a radio access network of a first type and a radio access network of a second type and the mobile terminal
35 accesses the communication network via the radio access network of the first type. The communication netwok may
further comprise a core network. A information, which includes at least one bearer capability field, is transmitter from
the mobile terminal to radio access network of the first type .. The information serves to indicate that a service requested
by the mobile terminal is only operable with the radio access network of the second type such that the inter-system
handover is required for employing the requested service.
40 [0037] According to one more embodiment of the present invention, the transmission, which includes the initiation, is
a transmission in accordance with a call control level procedure. In particular the transmission is a transmission in
accordance with a multimedia telephony call establishment procedure.
[0038] According to one more embodiment of the present invention, the mobile terminal comprises a call control entity
and a radio frequency interface for communication with the communication network. The call control entity is adapted
45 to encode the transmission and the radio frequency interface is adapted to transmit the transmission to a call control
entity of the radio access network of the first type, which is accessed by the mobile terminal.
[0039] According to a sixth aspect of the present invention, a network entity enabled for triggering an inter-system
handover within a communication network is provided. The network entity is part of the communication network, which
comprises at least a radio access network of a first type and a radio access network of a second type. The communication
50 network may further comprise a core network. Information is received from a mobile terminal, which is operable with the
radio access networks of the communication network, and the received information of the mobile terminal, which accesses
the communication network via the radio access network of the first type, includes at least one bearer capability field,
which indicates that a service requested by the mobile terminal is only operable with the radio access network of the
second type such that the inter-system handover of the mobile terminal to the radio access network of the second type
55 for access by the mobile terminal is triggered.
[0040] According to one more embodiment of the present invention, the transmission including the initiation is a
transmission in accordance with a call control level procedure. In particular the transmission is in accordance with a
multimedia telephony call establishment procedure.
5
EP 1 808 029 81
[0041] According to one more embodiment of the present invention, the network entity comprises an interface, a call
control entity and a triggering entity. The interface is adapted to receive the transmission. The call control entity is adapted
to decode and analyse the transmission in order to detect the indication for the inter-system handover encoded in the
transmission. The triggering entity is adapted to trigger the detected inter-system handover.
5 [0042] According to a seventh aspect of the present invention, communication network enabled for performing an
inter-system handover is provided. The communication network comprises radio access networks of at least a first and
a second type and a network entity for performing the inter-system handover indicated by a mobile terminal, which is
operable with the communication network. The inter-system handover is performed in response to transmission infor-
mation from the mobile terminal, which accesses the communication network via the radio access network of the first
10 type, to the radio access network of the first type. The transmitted information includes at least one bearer capability
field, which indicates that a service requested by the mobile terminal is only operable in the radio access network of the
second type.
[0043] According to one more embodiment of the present invention, the transmission including the initiation is a
transmission in accordance with a call control level procedure. In particular the transmission is a transmission in accord-
15 ance with a multimedia telephony call establishment procedure.
[0044] According to one more embodiment of the present invention, the communication network comprises a radio
frequency interface, a call control entity and a triggering entity. The radio frequency interface is adapted to receive the
transmission from the mobile terminal. The call control entity is adapted to decode and analyse the transmission in order
to detect the indication for the inter-system handover. The triggering entity, which is adapted to trigger the inter-system
20 handover, triggers the inter-system handover upon detection by the call control entity.
[0045] Other objects and features of the present invention will become apparent from the following detailed description
considered in conjunction with the accompanying drawings. It is to be understood, however, that the drawings are
designed solely for purposes of illustration and not as a definition of the scope of the invention, for which reference
should be made to the appended claims. It should be further understood that the drawings are not drawn to scale and
25 that they are merely intended to conceptually illustrate the structure and procedures described therein.
[0046]
30
Fig. 1a shows a schematic flow chart of an inter-system handover from a 2nd generation technology communication
system to a 3rd generation technology communication system;
Fig. 1b shows a schematic flow chart of an inter-system handover from a 3rd generation technology communication
35 system to a 2nd generation technology communication system;
Fig. 2a shows a schematic sequence chart of a mobile originating call establishment procedure;
Fig. 2b shows a schematic sequence chart of a mobile terminating call establishment procedure;
40
Fig. 3 shows schematically the basic structure of a bearer capability information element;
Fig. 4a shows a first communication system, which includes a 2nd generation technology public land mobile network
and a 3rd generation technology public land mobile network and which enables the operation of a dual-mode
45 mobile terminal, according to a first embodiment of the present invention;
Fig. 4b shows a second communication system, which includes a 2nd generation technology public land mobile
network and a 3rd generation technology public land mobile network and which enables the operation of a
dual-mode mobile terminal, according to a second embodiment of the present invention;
50
Fig. 5a shows a schematic sequence chart of a mobile originating call establishment procedure with mobile originating
service-based inter-system handover initiation according to an embodiment of the present invention; and
Fig. 5b shows a schematic sequence chart of a mobile terminating call establishment procedure with mobile originating
55 service-based inter-system handover initiation according to an embodiment of the present invention.
6
EP 1 808 029 81
[0047] An inter-system change from UMTS to GSM or GSM to UMTS takes place when a mobile terminal supporting
both UMTS and GSM changes the radio access technology. A detailed description of call establishment procedures is
5 given in the technical specification 3GPP TS 24.008 V3.19.0 (2004-06): "3rd Generation Partnership Project; Technical
Specification Group Core Network; Mobile radio interface layer 3 specification; Core Network Protocols; Stage 3 (Release
1999)", which is enclosed and incorporated herewith.
[0048] Fig. 1a shows a schematic flow chart of an inter-system handover of a dual-mode mobile terminal from a GSM
access network to a UMTS access network. The mobile terminal, the base station (BS) or the UMTS radio access
10 network (UTRAN) decides to perform an inter-system change, which makes the mobile terminal to switch to a new cell
that supports UMTS radio technology and stops transmission with the previously operated network, here the GSM radio
access network (RAN). Typically but not necessarily, the decision for an inter-system handover is based on a measure-
ment report relating quantities such as signal strength, signal quality, service quality, cell coverage, network data rate
load etc. Also typically, the core network of the radio access network in which the mobile terminal currently operates
15 initiates the inter-system handover including requesting the radio access network addressed by the intended inter-system
handover to reserve of resources for the mobile terminal. The request is acknowledged such that the inter-system
handover can be completed by instructing the mobile terminal to handover to the addressed radio access network. With
reference to Fig. 1a, the core network of the GSM based network requests the handover to the core network of the
UMTS based network, which acknowledges the handover after successful resource reservation. Finally, the mobile
20 terminal is instructed by the core network of the GSM based network to handover.
[0049] Fig. 1b shows a schematic flow chart of an inter-system handover of a dual-mode mobile terminal from a UMTS
access network to a GSM access network. The mobile terminal or base station system (BSS) or UTRAN decides to
perform an inter-system change, which makes the mobile terminal switch to a new cell that supports GSM radio tech-
nology, and stops transmission to the network, i.e. to a new cell that supports UMTS radio technology. The principles
25 explained with reference to Fig. 1a apply hereto likewise. The core network of the UMTS based network requests the
handover to the core network of the GSM based network, which acknowledges the handover after successful resource
reservation. Finally, the mobile terminal is instructed by the core network of the UMTS based network to handover
[0050] It is to be noted that the term handover is meant to include as well cell reselections.
[0051] It should be noted that teaching of inter-system handover procedures is described briefly and not comprehen-
30 sively. The detailed performing of a inter-system handover is out of the scope of the present invention and merely included
into the description for illustrative purposes .. Refer to the cited technical specification for detailed teaching.
[0052] Typical call establishment procedures will be described in the following with reference to Figs. 2a and 2b.
Basically, two different kinds of calls are distinguished in the field of mobile communications, the mobile originating or
mobile originated call and the mobile terminating or mobile terminated call. The term mobile originating call indicates a
35 call initiated by the mobile terminal, whereas the term mobile terminating call indicates a call initiated by the network
and by a calling entity connected to the network, respectively. Establishing procedures of both kinds will be illustrated
exemplarily below. A detailed description of call establishment procedures is given in the technical specification 3GPP
TS 24.008 V3.19.0 (2004-06): "Technical Specification Group Core Network; Mobile radio interface layer 3 specification;
Core Network Protocols; Stage 3 (Release 1999)", which should be enclosed herewith.
40 [0053] With reference to Fig. 2a, a mobile originating (MO) call establishment procedure is illustrated. A call control
(CC) entity of the mobile terminal initiates a call control connection by requesting the mobility management (MM) sublayer
to establish a mobile originating MM connection and entering the "MM connection pending" state. In principle two kinds
of mobile originating calls are distinguished: basic call and emergency call. The kind of call is coded as a parameter in
the request to establish an MM connection. The following description will address the basic call. Having entered the
45 "MM connection pending" state, upon MM connection establishment, the call control entity of the mobile terminal sends
a setup message to its peer entity of the network. In case of a basic call, this setup message is a designated as SETUP
message. Upon transmitting the SETUP message, the call control entity enters the "call initiated" state. The SETUP
message includes all information required by the network to process the call. In particular, the SETUP message includes
the called party address information and one or more bearer capability information elements (BC IE). The one or more
50 bearer capability information elements are illustrated below with reference to Fig. 3.
[0054] The "call initiated" state is supervised by a first timer (T303), which is already started before entering the "MM
connection pending" state. During "call initiated" state, the further proceeding of the call establishment procedure depends
on the kind of response received from the network by the call control (CC) entity of the mobile terminal. Typically the
possible responses comprise a CALL PROCEEDING message, a CONNECT message and a RELEASE COMPLETE
55 message. Upon receipt of the SETUP message, the call control entity of the network enters the "call initiated" state. In
this state, the call information included in the SETUP message is analysed. Based on the call information included in
the SETUP message, the call control entity of the network may determine that the received call information from the
mobile terminal is invalid. Then the call control entity of the network can initiate a call clearing procedure with one of the
7
EP 1 808 029 81
following cause values: "unassigned (unallocated) number"; "no route to destination"; "number changed"; and "invalid
number format (incomplete number)". Likewise, the call control entity of the network may determine that a requested
service is not authorized or is not available. Then the call control entity of the network should initiate a call clearing
procedure with one of the following cause values: "operator determined barring"; "bearer capability not authorized";
5 "bearer capability not presently available"; "service or option not available, unspecified"; or "bearer service not imple-
mented".
[0055] Otherwise, i.e. the call information is valid, the control entity of the network is enabled to either:
send a CALL PROCEEDING message to its peer entity (call control entity of the mobile terminal) to indicate that
10 the call is being processed; (the call control entity of the network enters the "mobile originating call proceeding" state);
send an ALERTING message to its peer entity to indicate that alerting has been started at the called user side; (the
call control entity of the network enters the "call received" state);
or
send a CONNECT message to its peer entity to indicate that the call has been accepted at the called user side; (the
15 call control entity of the network enters the "connect request" state).
[0056] The call control entity of the network may insert bearer capability information element(s) in the CALL PRO-
CEEDING message to select options presented by the mobile terminal in the bearer capability information element(s)
(BC IEs) included in the SETUP message transmitted by the mobile terminal to the network. Upon receipt of the CALL
20 PROCEEDING message, the call entity of the mobile terminal enters the "call initiated" state, stops the first timer (T303),
and starts a second timer (T31 O). The ALERTING message is send by call control entity of the network to its peer entity
at the mobile terminal, when the user alerting has been started at the called address. With receipt of the ALERTING
message, the call control entity of the mobile terminal enters the "call delivered" state, stops the timers (T303 and T31 O),
when running, and may output an altering indication to the user. The altering generation may be generated internally by
25 the mobile terminal or the network may be responsible of the delivery of the altering indication. Upon receiving an
indication that the call has been accepted, the call control entity of the network connects the traffic channel (including
the connection of an interworking function, if required) and sends a CONNECT message to its peer entity at the calling
mobile terminal. A third timer (T313) and the call control entity of the network enters the "connect indication" state. This
CONNECT message indicates to the call control entity of the (calling) mobile terminal that a connection has been
30 established through the network. The call control entity of the mobile terminal, upon receipt of a CONNECT message,
attaches the user connection; returns a CONNECT ACKNOWLEDGE message; stops any locally generated alerting
indication (if applied); stops timers (T303 and T31 O), if running; and enters the "active" state.
[0057] Now the call establishment procedure of a terminal originated call is completed and communications, especially
voice communications, between the (calling) mobile terminal and the called address can commence.
35 [0058] With reference to Fig. 2b, a mobile terminating (MT) call establishment procedure is illustrated. Before the call
establishment in accordance with a mobile terminating call can be initiated in the mobile terminal, the mobility management
(MM) connection has to be established by the network. After the arrival of a call from a remote calling entity, the call
control entity in the network initiates the mobility management (MM) connection establishment enters the "MM connection
pending" state. Upon completion of the MM connection, the call control entity of the network sends a SETUP message
40 to its peer entity at the mobile terminal, starts a first timer (T303), and enters the "call present" state. Upon receipt of a
SETUP message, the mobile terminal performs compatibility checking. If the result of the compatibility checking is
compatibility, the call control entity of the mobile terminal enters the "call present" state. An incompatible mobile terminal
responds with a RELEASE COMPLETE message. If no response to the SETUP message is received by the call control
entity of the network before the expiry of the first timer (T303), the cal failure procedures may be taken. The mobile
45 terminal receiving a SETUP message performs compatibility checking before responding to that SETUP message. The
compatibility checking is based on one or more bearer capability information elements included in the SETUP message.
The basic structure of the bearer capability information elements and valid parameters and values thereof are described
below with reference to Fig. 3.
[0059] Having entered the "call present" state, the call control entity of the mobile terminal acknowledges the SETUP
50 message by a CALL CONFIRMED message, and enters the "mobile terminating call confirmed" state. The call control
entity of the mobile terminal may include in the CALL CONFIRMED message to the network one or two bearer capability
information elements to the network, either pre-selected in the mobile terminal or corresponding to a service dependent
directory number. The mobile terminal may also include one or two bearer capabilities in the CALL CONFIRMED message
to define the radio channel requirements. A busy mobile terminal which satisfies the compatibility requirements indicated
55 in the SETUP message can respond either with a CALL CONFIRMED message if the call setup is allowed to continue
or a RELEASE COMPLETE message if the call setup is not allowed to continue, both with cause "user busy". If the
mobile user wishes to refuse the call, a RELEASE COMPLETE message shall be sent with the cause "call rejected". In
the cases where the mobile terminal responds to a SETUP message with RELEASE COMPLETE message the mobile
8
EP 1 808 029 81
terminal releases the MM connection and enters an idle state after sending the RELEASE COMPLETE message. The
call control entity of the network in the "call present" state, upon receipt of a CALL CONFIRMED message, stops the
first timer (T303), starts a second timer (T310), and enters the "mobile terminating call confirmed" state. The call control
entity of the mobile terminal having entered the "mobile terminating call confirmed" state, if the call is accepted at the
5 called user side, the mobile terminal proceeds with the call establishment. Otherwise, if the signal information element
was present in the SETUP message user alerting is initiated at the mobile terminal side; if the signal information element
was not present in the SETUP message, user alerting is initiated when an appropriate channel is available. Here, initiation
of user alerting means the generation of an appropriate tone or indication at the mobile terminal; and sending of an
ALERTING message by the call control entity of the mobile terminal to its peer entity in the network and entering the
10 "call received" state. The call control entity of the network in the "mobile terminated call confirmed" state, upon receipt
of an ALERTING message, sends a corresponding ALERTING indication to the calling entity; stops the second timer
(T31 O); starts a third timer (T301 ), and enters the "call received" state. In the "mobile terminating call confirmed" state
or the "call received" state, if the user of a mobile terminal is user determined "User Busy" then a DISCONNECT message
shall be sent with cause "user busy". In the "mobile terminating call confirmed" state, if the user of a mobile terminal
15 wishes to reject the call then a DISCONNECT message is sent with cause "call rejected". In the "mobile terminating call
confirmed" state or the "call received" state, the call control entity in the mobile terminal indicates acceptance of a mobile
terminating call by sending a CONNECT message to its peer entity at the network; starting a fourth timer (T313); and
entering the "connect request" state. In the "mobile terminated call confirmed" state or in the "call received" state, the
call control entity of the network, upon receipt of a CONNECT message, through connects the traffic channel (including
20 the connection of an interworking function, if required), stops the second, first or third timers (T31 O, T303 or T301) (if
running); sends a CONNECT ACKNOWLEDGE message to its peer entity at the called mobile terminal; initiates pro-
cedures to send a CONNECT message towards the calling entity and enters the "active" state. In the "connect request"
state, the call control entity of the mobile terminal, upon receipt of a CONNECT ACKNOWLEDGE message: stops the
fourth timer (T313) and enters the "active" state. When the fourth timer (T313) expires prior to the receipt of a CONNECT
25 ACKNOWLEDGE message, the mobile terminal initiates a call clearing procedure.
[0060] Now the call establishment procedure of a terminal originated call is completed and communications, especially
voice communications, between the (calling) mobile terminal and the called address can commence.
[0061] In general, the purpose of the bearer capability information element (BC-IE) is to request a particular bearer
service to be provided by the network. This indication is carried by certain connection control messages which may be
30 categorized into those messages, which are related to the call establishment procedures and which are used during the
established connection. During the call establishment procedure the public land mobile network (PLMN) bearer capability
information element (BC IE) is included in:
the SETUP message, which is generated by the requesting entity (i.e. either the mobile terminal or the mobile
35 services switching center (MSC)) to establish a mobile originating or mobile terminating call, respectively, and in
the CALL CONFIRMED or CALL PROCEEDING messages, respectively, which are generated by the responding
entity (i.e. either the mobile terminal or mobile switching center) in order to negotiate certain parameter values. If
no bearer capability information element (BC IE) is included in the SETUP message, the CALL CONFIRMED
message indicates the complete applicable bearer capability information element (BC IE). Normally, the network
40 may release the call if it does not support the service indicated by the bearer capability information element (BC
IE). Also, if the service does not match with the service requested from the fixed network terminal the mobile services
switching center (MSC) I interworking function (IWF) may release the call. (In the latter case also the fixed network
terminal may release the call.)
45 [0062] During the established connection the public land mobile network (PLMN) bearer capability information element
(BC IE) is included in the MODIFY, MODIFY COMPLETE, and MODIFY REJECT messages in order to change the
service (bearer capability) or to change the maximum number of traffic channels and/or wanted air interface user rate
when a non-transparent multislot data service is in use.
[0063] With reference to Fig. 3 the general structure of the public land mobile network (PLMN) bearer capability
50 information element (BC IE) is illustrated. Some of the shown octets are optional, some are only available or optional,
if the parameter "Information Transfer Capability" does not indicate "Speech"; and some are only available if EDGE is
used. A detailed description is available from the technical specification 3GPP TS 27.001 V3.15.0 (2004-06): "Technical
Specification Group Core Network; General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS) (Release
1999)", which should be enclosed herewith.
55 [0064] With respect to the individual parameter settings at the mobile terminal the following cases may be distinguished
between the mobile originating call establishment and the mobile terminating call establishment.
[0065] The following table illustrates parameters relevant for the mobile originating call set up by a mobile terminal,
i.e. bearer capability parameters included in the SETUP message communicated to the network. A parameter may
9
EP 1 808 029 81
"requested value" indicating a request which cannot be changed by the responding entity;
"offered value" indicating a proposal which may be changed by the responding entity;
5 a particular choice value leaving it up to the responding entity which value ultimately applies;
"as requested" indicating that the requested value applies and is confirmed (by returning it);
"selected value" indicating that a particular value applies either out of the offered set or as a free choice out of the
defined set of values; and
"supported value" indicating a value supported by the responding entity.
10
Message
User Information Layer 2 Protocol (UIL2P) requested value or NAV as requested or NAV
[0066] The following table illustrates parameters relevant for the mobile terminating call set up to a mobile terminal,
i.e. bearer capability parameters included in the CALL CONFIRMED message communicated to the mobile terminal.
35
Message
Number of Data Bits (NOB) offered value selected value (free choice)
40
Parity Information (NPB) offered value selected value (free choice)
Number of Stop Bits (NSB) offered value selected value (free choice)
Connection Element (CE) requested value (TINT) as requested or selected value (TINT)
(free choice)
45
"both" with the preferred value selected value (TINT)
Indicated (e.g. both NT)
10
EP 1 808 029 81
(continued)
Message
10
[0067] The validity of a bearer capacity (BC) parameter value, either in the SETUP or CALL CONFIRMED message,
may differ from A/Gb mode to GERAN (GSM/EDG E radio access network) lu mode to UTRAN lu mode. Certain param-
eters are irrelevant in UTRAN or GERAN lu mode and any value given is valid and ignored. These parameters may be
available in the bearer capability information element (BC IE). For those parameters that are relevant in UTRAN lu mode,
15
GERAN lu mode and A/Gb mode, certain values may be invalid in one of the systems.
[0068] Invalid parameter values may cause rejection of the bearer capability (BC) and subsequent release of the call.
Parameters that are ignored in UTRAN or GERAN lu mode may be set to default values, or to specific values in view
of an eventual handover to A/Gb mode. Parameter values that are invalid in one system may result in unsuccessful
handover from the other system. The following table shows lists of parameters that are ignored in UTRAN and parameter
20
values which validity is different in A/Gb mode and UTRAN lu mode.
Modem type I
55
[0069] Those skilled in the art will appreciate the inventive concept on the basis of the teaching given above. Dual-
mode mobile terminals exist, which are capable to operate with different network technologies as described above. In
particular, dual-mode mobile terminals are operable with a 2nd generation PLMN, such as GSM, GSM with GPRS and/or
GSM with EDGE enhancement, and a 3rd generation PLMN, especially WCDMA, UMTS and the like. Such dual-mode
11
EP 1 808 029 81
mobile terminals are allowed to inter-system handover between the 2nd generation network technology and the 3rd
generation network technology. As described above, such inter-system handovers, also between system of differing
technologies, are conventionally operated on the basis of network measurements, such as coverage, signal quality
parameters (signal strength, signal error rate etc.), connection quality parameters (block error rate, etc.), load, service
5 quality parameters and quality of service and the like. Although there is also possibility for service-based handover,
where handover is done based on services supported only by one of the network, there exists currently no means
(specification) defined for indication of the need for service-based handover. This means that service-based handovers
are more like only a word without any actual implementation.
[0070] Currently the common way mobile terminals and networks operate is that they support multimedia telephony
10 only in PLMNs operating 3rd generation technology, not in 2nd generation technology PLMNs. In accordance with the
current specifications, mobile terminals may request multimedia calls only when operating in a 3rd generation PLMN.
Moreover, based on the network measurements, the network may order a dual-mode mobile terminal to operate in 2nd
generation technology PLMN at any time. If the user now wishes to do a multimedia video telephony call, there exists
up to now no way for the mobile terminal to request such a multimedia call. In fact, dual-mode mobile terminal can not
15 do anything else, except notifying the user that the desired multimedia call can not be done.
[0071] With reference to Fig. 4a a communications system according to a first embodiment of the present invention
is illustrated, which includes a 3rd generation technology PLMN and a 2nd generation technology PLMN, in particular a
UTRAN 1 (Universal Mobile Telecommunication Services Terrestrial Radio Access Network) employing WCDMA (wide-
band code division multiple access) and a GSM (Global System for Mobile communication) radio access network 2. The
20 OUTRAN 1 includes a Base Station (BS) which is connected to a Radio Network Controller (RNC). The Radio Network
cCntroller (RNC) of the UTRAN 1 is in turn connected to a home location register (HLR) and the mobile services switching
center (MSC). The GSM radio access network (RAN) includes a base station (BTS), which is connected to a base station
controller (BSC). The base station controller (BSC) of the GSM RAN 2 is in turn connected to the home location register
(HLR), to the mobile services switching center (MSC). Further network entities such as the visited location register (VLR),
25 interworking function (IWF), serving GPRS support node (SGSN), gateway GPRS support node (GGSN) belong to the
core network of the communication system. The core network servers for Switching communications in-between the
PLMN, to other PLMNs, to external communication networks such as telephony networks and data networks (packet
switched networks, Internet).
[0072] The illustrated communication system includes also a dual-mode mobile terminal, which supports GSM as well
30 as WCDMA network technology for wireless communication. The dual-mode mobile terminal is operable with either the
UTRAN or the GSM RAN for communication services. It shall be assumed that the dual-mode mobile terminal is currently
operating in the GSM RAN, which embodies a 2nd generation technology network. Video telephony calls, which represent
a specific class of multimedia calls, are requested with call control (CC) level messages, described above in detail with
reference to Figs. 2a and 2b. Nevertheless, multimedia telephony calls and especially video telephony calls usually
35 require a mobile terminal operating in a 3rd generation technology network supporting multimedia telephony services;
i.e. here the UTRAN.
[0073] With reference to Fig. 4b a communications system according to a second embodiment of the present invention
is illustrated, which includes a 3rd generation technology PLMN and a 2nd generation technology PLMN, in particular a
UTRAN 1 (UMTS universal mobile telecommunication services terrestrial radio access network) employing WCDMA
40 (wideband code division multiple access) and a GSM (Global System for Mobile communication) radio access network
2. The first and second embodiments of communication systems illustrated in Figs. 4a and 4b differ merely slightly. In
particular, the second embodiment includes in contrast to the first embodiment different mobile services switching centers
MSC-A and MSC-B associated with the GSM RAN 1 and the UTRAN 2, respectively.
[0074] With reference to Figs. Sa and Sb, the inventive concept will be described in accordance with the mobile
45 originating call establishment procedure as well as the mobile terminating call establishment procedure.
[0075] In case of a mobile originating video (multimedia) telephony call as illustrated in Fig. Sa, the mobile terminal
requests the call with SETUP message. As described above, the SETUP message contains one or more bearer capability
information elements (BC IEs), which indicates the bearer requirements for the call to be established. Before coding
and sending of the SETUP message, the current subscription of the mobile terminal is checked to determine whether
50 the mobile terminal is currently subscribed to either the GSM RAN (or GERAN BSS) or the UTRAN. Here, the dual-
mode mobile terminal operates in the GSM RAN (or GERAN BSS). Consequently, the desired video (multimedia)
telephony call may not be allowed, but may be enabled after an inter-system handover of the dual-mode mobile terminal
to the UTRAN. Consequently, the SETUP message to be transmitted is encoded with an indication that the required
bearer service(s) is/are not available.
55 [0076] With reference back to Fig. 3 and the description thereto, the skilled persons are thought that validity of a bearer
capacity (BC) parameter value, in the SETUP message, may differ from (GSM RAN, GERAN BSS) A/Gb mode to UTRAN
lu mode; i.e. there exists 2nd generation specific fields and 3rd generation specific fields. To inform the network, i.e. the
call control entity of the network, about the lacking support for the requested multimedia call, one or more 2nd generation
12
EP 1 808 029 81
specific bearer capability fields, for instance the channel coding fields, may be set to "not acceptable". The parameter
value "not acceptable" may be coded in accordance with a numeral or binary representation, i.e. in particular, the
parameter value "not acceptable" may be coded as numeral, decimal and binary "O", respectively. It should be noted
that any other representation is likewise applicable. Alternatively, there exists 2nd generation specific fields and 3rd
5 generation specific fields having differing valid parameter values, such as the fixed network user rate (FNUR), where
the rate value 33.6 kbit/s is a valid value as the dual mode mobile terminal is subscribed to a WCDMA (UMTS) PLMN.
Moreover, the fixed network user rate (FNUR) may contain also another date rate value, which is not applicable with
the 2nd generation technology network but applicable with the 3rd generation technology network, to which the handover
is intended. In UMTS, the video telephony call is operable at a 64 kBits/s transparent data communication connection.
10 [0077] The network, i.e. the call control entity thereof, which may be implemented in MSC, receives the SETUP
message, which contains one or more bearer capability information elements (BC IEs) with one or more bearer capability
fields values modified in the manner as described above. This means, the one or more channel coding fields may contain
"not acceptable" (value "O") and/or the FNUR field may contain a rate parameter value not applicable with GSM RAN
mode (e.g. 33.6 kbit/s, 64 kbit/s etc.).
15 [0078] The call control entity of the network analyses the one or more received bearer capability information elements
(BC I Es) and detects the modifications. This detection indicates to the call control entity of the network that the dual-
mode mobile terminals requests for a service, here the video (multimedia) telephony call, which is not supported by the
access network, in which the dual-mode mobile terminal is currently subscribed. Hence, the network initiates an inter-
system handover of the dual-mode mobile terminal. Such inter-system handover procedures are described above with
20 reference to Figs. 1a and 1b. After completion of the inter-system handover, the dual-mode mobile terminal is now
operating in the 3rd generation PLMN (WCDMA, UMTS), which supports the requested communication service, here
the multimedia (video) telephony service. Thus, the call establishment procedure can be continued with a CALL PRO-
CEEDING message sent by the call control (CC) entity of the network to the call control entity of the dual-mode mobile
terminal. The call establishment procedure follows now substantially the call setup procedure described above with
25 reference to Fig. 2a.
[0079] In case of a mobile terminating video (multimedia) telephony call as illustrated in Fig. 5b, the call control entity
of the network, in which the mobile terminal is currently subscribed, notifies also the call control entity of the mobile
terminal of an incoming call with a SETUP message. This SETUP message indicates to the mobile terminal that the
calling entity wishes to establish a multimedia call. The mobile terminal answers to this SETUP message with CALL
30 CONFIRMED message, which also contains one or more bearer capability information elements (BC IEs) defining
information about the capabilities of the mobile terminal for this multimedia call. With reference to the conventional case,
the CALL CON Fl RM ED message should contain a rejection indication due to the lacking support of the video (multimedia)
telephony call requested by the SETUP message. In contrast to the conventional case, the CALL CON Fl RM ED message,
which contains one or more bearer capability information elements (BC IEs) to inform the network about the bearer
35 capabilities of the mobile terminal, includes bearer capability fields with parameter value modified in the way as described
above. This means, the call control (CC) entity of the mobile terminal encodes a bearer capability information element
(BC IE) with one or more 2nd generation specific bearer capability fields, for instance the channel coding fields, set to
"not acceptable" (or any representation thereof such as value "O"). Alternatively, the call control (CC) entity encodes one
or more 2nd generation specific fields with a parameter value only applicable as the mobile terminal operates in a 3rd
40 generation technology network, such as the fixed network user rate (FNUR), where the rate value 33.6 kbit/s (or 64
kbit/s or any other applicable value) is a valid field parameter value as the dual mode mobile terminal is operating in a
WCDMA (UMTS) PLMN. This CALL CONFIRMED message containing the one or more bearer capability information
elements (BC I Es) with one or more bearer capability fields values modified in the manner as described above is sent
by the call control (CC) entity of the mobile terminal to the peer call control (CC) entity of the network.
45 [0080] The network, i.e. the call control entity thereof, which may be implemented in MSC, receives the CALL CON-
Fl RM ED message, which contains one or more bearer capability information elements (BC IEs) with one or more bearer
capability fields values modified in the manner as described above. This means, the one or more channel coding fields
may contain "not acceptable" and/or the FNUR field may contain a rate parameter value not applicable with GSM RAN
mode (e.g. 33.6 kbit/s, 64 kbit/s etc.).
50 [0081] The call control (CC) entity of the network analyses the one or more received bearer capability information
elements (BC I Es) and detects the modifications. This detection indicates to the call control (CC) entity of the network
that the dual-mode mobile terminals requests to establish a service, here the video (multimedia) telephony call, which
is not supported by the access network, in which the dual-mode mobile terminal is currently subscribed. Hence, the
network initiates an inter-system handover of the dual-mode mobile terminal Such inter-system handover procedures
55 are described above with reference to Figs. 1a and 1b. In particular, the MSC informs the GERAN BSS, in which the
mobile terminal is currently subscribed about the handover to the UTRAN After completion of the inter-system handover,
the dual-mode mobile terminal is now operating in the 3rd generation PLMN (WCDMA, UMTS), which supports the
requested communication service, here the multimedia (video) telephony service. Thus, the call establishment procedure
13
EP 1 808 029 81
can be continued with an ALERTING message sent by the call control (CC) entity of the mobile terminal to the call control
entity of the network and the calling entity, respectively. The call establishment procedure follows now substantially the
call setup procedure described above with reference to Fig. 2b.
[0082] In principle, the inventive concept is based on the fact that the bearer capability information element has differing
5 fields and or differing field parameter values applicable with 2nd generation technology networks and 3rd generation
technology networks. For example, there are no channel codings in 3rd generation technology systems, such as WCDMA
and UMTS, so channel coding fields are valid only for 2nd generation technology systems, such as GSM. In the same
way, some parameter value of fields may be applicable for one system only, for example, data rate 33.6 (64 kbit/s) in
fixed network user rate (FNUR) field is applicable only for 3rd generation technology systems.
10 [0083] The inventive concept includes several advantages. There are no new messages or information elements
needed in signalling between mobile terminal and the network and its entities to enable the (service-base terminal
originating) inter-system handover indication to the network. The interoperability with mobile terminals supporting older
standard specifications and network entities and components supporting older standard specifications is not compro-
mised such that operability of those terminals, entities, and components is guaranteed. The only reasonable way for a
15 network entity/component being realised on the basis of an older standard is to handle situations where no channel
codings are supported, which results in a disconnection of the call. Form user side, this is a similar behaviour compared
to the behaviour of the mobile terminal, which does not implement the functionality presented here. The communication
from the Mobile Services Switching Center (MSC) to the mobile terminal is substantially not affected; i.e. the mobile
terminating SETUP message remains actually exactly the same, as channel codings are not filled in the SETUP message
20 sent in this (downlink) direction to the mobile terminal.
[0084] Those skilled in the art will appreciate that the term RAN is used in its general understanding which may differ
from that of the standard description. The conjunction with a 2nd generation technology network and especially a GSM
network, the radio access network (RAN) thereof may also be understood as GERAN BSS (Base Station Subsystem).
To specify a 3rd generation radio access network, the term UTRAN is used in the description.
25 [0085] It should be noted that the CALL PROCEEDING message (shown in Fig. 5a) may be also sent to the mobile
terminal before the inter-system handover for the mobile terminal is initiated.
[0086] It should be also noted thatthe communication network receives this mobile originating service-based indication
for inter-system handover (either coded in the SETUP message in case of mobile originating call establishment or coded
in the CALL CONFIRMED message in case of mobile terminating call establishment) via the radio access network, to
30 which the mobile terminal is currently connected, and in case this radio access network does not employ the requested
radio access technology, the communication network checks whether the terminal can be handed over to a cell using
the requested technology. The final decision is thus taken by the communication network and depends in addition on
other related factors of which the mobile terminal has no knowledge, like the network configuration and the current load
situation. If it is possible, the communication network will hand the mobile terminal over to a cell using the preferred
35 radio access technology. Thus, the communication network is able to allocate a cell using the best suited radio access
technology as early as possible. Afterwards, the communication network maintains the provided knowledge about the
preferred radio access technology in order to enable the mobile terminal to use this technology for the duration of the
connection.
[0087] It should be noted that the above teaching with reference to Figs. 5a and 5b is applicable in a communication
40 system illustrated in Fig. 4a, which may be distinguished by a mobile services switching center (MSC) associated with
both the core network of the 2nd generation technology network system as well as the 3rd generation technology network
system. Alternatively to a common MSC, different MSC may be operable with the respective network system. Such an
embodiment is illustrated in Fig. 5b, where a first MSC-A is associated with the GSM RAN 1 (i.e. the 2nd generation
technology network) and the UTRAN 2 (i.e. 3rd generation technology network), respectively. The handling and signalling
45 relating to the inter-system handover is in principle out of the scope of the present invention, but a brief teaching about
possible signalling for inter-MSC handover should be given.
[0088] To make this solution according to the present invention also applicable for signalling between core network
(CN) and radio access network (RAN) and in case of an required inter-MSC handover, a signalling similar to the signalling
described above may be applied at A-interface base station subsystem application port (BSSAP) signalling. The A-
50 interface is a signalling interface between Mobile Services Switching Center (MSC) and Base Station Controller (BSC).
This means in case of multimedia or video telephony call ( requiring a 64kbit/s transparent data rate communication
connection between access network and mobile terminal), the MSC should be able to set the allowed radio interface
data rate values in the Channel Type Information Element (CT IE) of an Assignment Request message. In particular,
the octet 5a of the Channel Type Information Element to values 0, in particular together with indication that service
55 handover to UMTS should be performed by Base Station Controller (BSC). The same BSSAP signalling as used at the
A-interface may be applicable also with the E-interface, which represents the interface the MSC-A and the MSC-B in
inter-MSC inter-system handovers. During such inter-MSC inter-system handovers, the Channel Type IE (CT IE) of the
BSSAP is sent from MSC-A to MSC-B. MSC-B will have to create the Radio Access Network Application Port (RANAP)
14
EP 1 808 029 81
Radio Access Bearer (RAB) parameters that are used at lu interface towards the Radio Network Controller (RNC). In
particular to enable this, the MSC-B will have to get at least a Channel Type indicating FNUR 64kbit/s, which corresponds
to the requiring a 64kbit/s transparent data rate communication connection for video telephony calls.
[0089] In addition, when indicating the allowed radio interface data rate values as 0 in Channel Type Information
5 Element (CT IE), the MSC-B would also know that it's not possible to make a subsequent inter-system handover back
to GSM for a once established connection after above described handover, since the mobile station does not support
this service (radio interface data rate 0 kbit/s) in GSM mode.
10 Claims
1. Method of initiation an inter-system handover of a mobile terminal accessing a communication network, wherein
said communication network comprises at least a radio access network of a first type and a radio access network
of a second type, wherein said mobile terminal is capable of operating in at least said radio networks of said first
15 type and said second type, wherein said method is characterized by initiating said inter-system handover of said
mobile terminal accessing said communication network via said radio access network of said first type in response
to said mobile terminal transmitting information including at least one bearer capability field indicating that a requested
service is only operable with said radio access network of said second type.
20 2. Method according to claim 1, wherein said information transmitted for initiation is a transmission in accordance with
a call control level procedure.
3. Method according to claim 2, wherein said information is transmitted in accordance with a multimedia telephony call
establishment procedure.
25
4. Method according to anyone of the preceding claims, wherein said information is a call control message, said method
comprising transmitting said message from said mobile terminal to a core network using said radio access network
of said first type.
30 5. Method according to anyone of the preceding claims, wherein said at least one bearer capability field has an
inapplicable parameter value in view of said radio access network of said first type.
6. Method according to anyone of the preceding claims, wherein said at least one bearer capability field selected from
said plurality of bearer capability fields is distinguished in that at least one parameter value validity of said at least
35 one bearer capability field differs in communications with said radio access networks of said first type and said
second type.
7. Method according to anyone of the preceding claims, wherein said transmission is a call control SETUP message
in accordance with a mobile originating call establishment procedure,
40 said method comprising:
encoding said SETUP message with one or more bearer capability information elements including said at least
one bearer capability field in a call control entity of said mobile terminal; and
transmitting, by said mobile terminal, said SETUP message to a call control entity of said core network using
45 said radio access network of said first type to initiate said inter-system handover.
8. Method according to anyone of claims 1to6, wherein said transmission is a call control CALL CONFIRMED message
in accordance with a mobile terminating call establishment procedure,
said method comprising:
50
encoding, in a call control entity of said mobile terminal, said CALL CONFIRMED message with one or more
bearer capability information elements including said at least one bearer capability field; and
transmitting, by said mobile terminal, said CALL CONFIRMED message to a call control entity of said core
network using said radio access network of said first type to initiate said inter-system handover.
55
9. Method according to anyone of the preceding claims, wherein said at least one bearer capability information element
includes all channel codings fields being set to "not acceptable".
15
EP 1 808 029 81
10. Method according to anyone of the preceding claims, wherein said at least one bearer capability field includes a
fixed network user rate field being set to a data rate value only applicable with said radio access network of said
second type.
5 11. Method according to claim 10, wherein said fixed network user rate field is set to a data rate value of 33.6 kbit/s.
12. Method according to anyone of the preceding claims, wherein said radio access network of said first type is a 2nd
generation technology radio access network and said radio access network of said second type is a 3rd generation
technology radio access network.
10
13. Method according to anyone of the preceding claims, wherein said radio access network of said first type is a GSM
I GPRS, global system for mobile communications I general packet radio system, radio access network and said
radio access network of said second type is a WCDMA, wideband code division multiple access, radio access
network.
15
14. Method of initiation an inter-system handover of a mobile terminal accessing a communication network, wherein
said communication network comprises at least a radio access network of a first type and a radio access network
of a second type, wherein said mobile terminal is capable of operating in at least said radio networks of said first
type and said second type, wherein said method is characterized by initiating at a network entity of said commu-
20 nication network said inter-system handover of said mobile terminal accessing said communication network via said
radio access network of said first type in response to receiving from said mobile terminal information including at
least one bearer capability field indicating that a requested service is only operable with said radio access network
of said second type.
25 15. Method according to claim 14, wherein said information transmitted for initiation is a transmission in accordance
with a call control level procedure.
16. Method according to claim 14 or 15, wherein said information is a call control message, said method comprising
receiving said message from said mobile terminal at a core network using said radio access network of said first type.
30
17. Computer program product comprising program code sections stored on a computer-readable medium for carrying
out the respective steps of the corresponding method according to anyone of claims 1 to 16, when said program
code sections are run on a processor-based device associated either with the mobile terminal enabled for commu-
nication with said communication network, or with the network entity, respectively.
35
18. Module provided in a mobile terminal, which is operable with a communication network comprising at least a radio
access network of a first type and a radio access network of a second type, wherein said module is adapted to
access said communication network via said radio access network of said first type; characterized in that said
module is configured to transmit information including at least one bearer capability field from said module to said
40 radio access network of said first type for initiating an inter-system handover, wherein said information serves to
indicate that a requested service is only operable with said radio access network of said second type.
19. Mobile terminal enabled for initiation of an inter-system handover within a communication network, wherein said
mobile terminal is operable with said communication network comprising at least a radio access network of a first
45 type and a radio access network of a second type, wherein said mobile terminal is adapted to access said commu-
nication network via said radio access network of said first type; characterized in that said mobile terminal is
configured to transmit information including at least one bearer capability field from said mobile terminal to said
radio access network of said first type, wherein said information serves to indicate that a requested service is only
operable with said radio access network of said second type.
50
20. Mobile terminal according to claim 19, wherein said transmission including said initiation is a transmission in ac-
cordance with a call control level procedure.
21. Mobile terminal according to claim 20, wherein said transmission is in accordance with a multimedia telephony call
55 establishment procedure.
22. Mobile terminal according to anyone of claims 19 to 21, comprising a call control entity, which is adapted to encode
said transmission, and a radio frequency interface, which is adapted to transmit said transmission to a call control
16
EP 1 808 029 81
23. Network entity enabled for triggering an inter-system handover within a communication network, of which said
network entity is a part, wherein a transmission is received from a mobile terminal operable with at least a radio
5 access network of a first type and a radio access network of a second type forming said communication network,
characterized in that said network entity is adapted to trigger said inter-system handover to said radio access
network of said second type, in response to said transmission from said mobile terminal accessing said communi-
cation network via said radio access network of said fist type, wherein said transmission includes information including
at least one bearer capability field, which indicates that a requested service is only operable with said radio access
10 network of said second type.
24. Network entity according to claim 23, wherein said transmission including said initiation is a transmission in accord-
ance with a call control level procedure.
15 25. Network entity according to claim 24, wherein said transmission is in accordance with a multimedia telephony call
establishment procedure.
26. Network entity according to any of claims 23 to 25, comprising an interface, which is adapted to receive said
transmission, a call control entity, which is adapted to decode and analyse said transmission, in order to detect said
20 indication for said inter-system handover, and a triggering entity, which is adapted to trigger said inter-system
handover.
27. Communication network enabled for performing an inter-system handover, wherein said communication network
comprises radio access networks of at least a first and a second type and a network entity for triggering said inter-
25 system handover of a mobile terminal operable with said radio access networks of said first and said second type,
characterized in that said communication network is adapted to perform said inter-system handover to said access
network of said second type, in response to a transmission from said mobile terminal accessing said communication
network via said radio access network of said first type, wherein said transmission includes information including at
least one bearer capability field indicating that a service requested by said mobile terminal is only operable with said
30 radio access network of said second type.
28. Communication network according to claim 27, wherein said transmission including said initiation is a transmission
in accordance with a call control level procedure.
35 29. Communication network according to claim 28, wherein said transmission is in accordance with a multimedia te-
lephony call establishment procedure.
30. Communication network according to any of claims 27to 29, comprising a radio frequency interface, which is adapted
to receive said transmission from said mobile terminal, and a call control entity, which is adapted to decode and
40 analyse said transmission, in order to detect said indication for said inter-system handover, wherein a triggering
entity, which is adapted to trigger said inter-system handover, triggers said inter-system handover upon detection.
Patentanspruche
45
1. Verfahren zum Einleiten eines Inter-System Handovers eines Mobilendgerats, das auf ein Kommunikationsnetz
zugreift, wobei das Kommunikationsnetz mindestens ein Funkzugangsnetz eines ersten Typs und ein Funkzugangs-
netz eines zweiten Typs umfasst, wobei das Mobilendgerat in der Lage ist, in mindestens den Funknetzen des
ersten Typs und des zweiten Typs zu arbeiten, wobei das Verfahren gekennzeichnet ist durch:
50
Einleiten des Inter-System Handovers des Mobilendgerats, das auf das Kommunikationsnetz Ober das Funk-
zugangsnetz des ersten Typs zugreift, in Reaktion auf Ubertragen einer Information durch das Mobilendgerat,
die mindestens ein Tragerdienst-Fahigkeits-Feld beinhaltet, das anzeigt, dass ein angeforderter Dienst nur mit
dem Funkzugangsnetz des zweiten Typs betreibbar ist.
55
2. Verfahren gemaB Anspruch 1, wobei die Information, die zum Einleiten ubertragen wird, eine Obertragung gemaB
einer Verbindungssteuerungs-Schicht-Prozedur ist.
17
EP 1 808 029 81
3. Veriahren gemaB Anspruch 2, wobei die Information gemaB einer Verbindungsaufbau-Prozedur fOr Multimedia-
Telefonie ubertragen wird.
4. Veriahren gemaB einem der vorhergehenden Anspruche, wobei die Information eine Verbindungssteuerungs-Mel-
5 dung ist, wobei das Veriahren eine Obertragung der Meldung von dem Mobilendgerat an ein Kernnetz unter Ver-
wendung des Funkzugangsnetzes des ersten Typs umfasst.
5. Veriahren gemaB einem der vorhergehenden Anspruche, wobei das mindestens eine Tragerdienst-Fahigkeits-Feld
einen unanwendbaren Parameterwert hinsichtlich des ersten Funkzugangsnetzes des ersten Typs aufweist.
10
6. Veriahren gemaB einem dervorhergehenden Anspruche, wobei das mindestens eine Tragerdienst-Fahigkeits-Feld,
das aus der Mehrzahl von Tragerdienst-Fahigkeits-Feldern ausgewahlt wird, darin ausgezeichnet ist, dass sich
mindestens eine Parameterwert-Gultigkeit des mindesten einen Tragerdienst-Fahigkeits-Feldes bei der Kommuni-
kation mit dem Funkzugangsnetz des ersten Typs und des zweiten Typs unterscheidet.
15
7. Veriahren gemaB einem der vorhergehenden Anspruche, wobei die Obertragung eine Verbindungssteuerungs-
SETUP-Meldung gemaB einer Verbindungsaufbau-Prozedur, ausgehend von dem anrufenden Mobilendgerat, ist,
wobei das Veriahren umfasst:
9. Veriahren gemaB einem der vorhergehenden Anspruche, wobei das mindestens eine Tragerdienst-Fahigkeits-
lnformationselement alle Kanalkodierungsfelder beinhaltet, die auf "nicht akzeptabel" festgelegt wurden.
40
1O. Veriahren gemaB einem der vorhergehenden Anspruche, wobei das mindestens eine Tragerdienst-Fahigkeits-Feld
ein Festnetz-Benutzerdatenraten-Feld beinhaltet, das auf einen Datenratenwert festgelegt wurde, der nur mit dem
Funkzugangsnetz des zweiten Typs anwendbar ist.
45 11. Veriahren gemaB Anspruch 1O, wobei das Festnetz-Benutzerdatenraten-Feld auf einen Datenratenwert von 33,6
Kbit/s festgelegt wird.
12. Veriahren gemaB einem der vorhergehenden Anspruche, wobei das Funkzugangsnetz des ersten Typs ein Funk-
zugangsnetz der 2. Generationstechnologie und das Funkzugangsnetz des zweiten Typs ein Funkzugangsnetz der
50 3. Generationstechnologie ist.
13. Veriahren gemaB einem der vorhergehenden Anspruche, wobei das Funkzugangsnetz des ersten Typs ein GSM/
GPRS, Global System for Mobile Communications I General Packet Radio System -Funkzugangsnetz ist und wobei
das Funkzugangsnetz des zweiten Typs ein WCDMA, Wideband Code Division Multiple Access - Funkzugangsnetz
55 ist.
14. Veriahren zum Einleiten eines Inter-System Handovers eines Mobilendgerats, das auf ein Kommunikationsnetz
zugreift, wobei das Kommunikationsnetz mindestens ein Funkzugangsnetz eines ersten Typs und ein Funkzugangs-
18
EP 1 808 029 81
netz eines zweiten Typs umfasst, wobei das Mobilendgerat in der Lage ist, in mindestens den Funkzugangsnetzen
des ersten Typs und des zweiten Typ zu arbeiten, wobei das Verfahren gekennzeichnet ist durch:
Einleiten auf einer Netzeinheit des Kommunikationsnetzes des Inter-System Handovers des Mobilendgerats,
5 das auf das Kommunikationsnetz Ober das Funkzugangsnetz des ersten Typs zugreift, in Reaktion auf Emp-
fangen einer Information von dem Mobilendgerat, die mindestens ein Tragerdienst-Fahigkeits-Feld beinhaltet,
das anzeigt, dass ein angeforderter Dienst nur mit dem Funkzugangsnetz des zweiten Typs betreibbar ist.
15. Verfahren gemaB Anspruch 14, wobei die Information, die zum Einleiten Obertragen wird, eine Ubertragung gemaB
10 einer Verbindungssteuerungs-Schicht-Prozedur ist.
16. Verfahren gemaB Anspruch 14oder15, wobei die Information eine Verbindungssteuerungs-Meldung ist, wobei das
Verfahren Empfangen der Meldung von dem Mobilendgerat in einem Kernnetz unter Verwendung des Funkzu-
gangsnetzes des ersten Typs umfasst.
15
17. Computerprogrammprodukt, umfassend Programmcodeabschnitte, die auf einem computerlesbaren Medium ge-
speichert werden, um die jeweiligen Schritte des entsprechenden Verfahrens gemaB einem der AnsprOche 1 bis
16 auszufOhren, wenn die Programmcodeabschnitte auf einer Prozessor-basierten Vorrichtung ausgefOhrt werden,
die jeweils entweder einem Mobilendgerat, das zur Kommunikation mit dem Kommunikationsnetz geeignet ist, oder
20 der Netzeinheit zugeornet ist.
18. Modul, das in einem Mobilendgerat bereitgestellt ist, das mit einem Kommunikationsnetz betreibbar ist, das minde-
stens ein Funkzugangsnetz eines ersten Typs und ein Funkzugangsnetz eines zweiten Typs umfasst, wobei das
Modul angepasst ist, um auf das Kommunikationsnetz Ober das Funkzugangsnetz des ersten Typs zuzugreifen;
25 dadurch gekennzeichnet, dass das Modul eingerichtet ist, um eine Information, die mindestens ein Tragerdienst-
Fahigkeits-Feld beinhaltet, von dem Modul an das Funkzugangsnetz des ersten Typs zu Obertragen, um ein Inter-
System Handover einzuleiten, wobei die Information zum Anzeigen dient, dass ein angeforderter Dienst nur mit
dem Funkzugangsnetz des zweiten Typs betreibbar ist.
30 19. Mobilendgerat, das zum Einleiten eines Inter-System Handovers innerhalb eines Kommunikationsnetzes geeignet
ist, wobei das Mobilendgerat mit dem Kommunikationsnetz betreibbar ist, das mindestens ein Funkzugangsnetz
eines ersten Typs und ein Funkzugangsnetz eines zweiten Typs umfasst, wobei das Mobilendgerat angepasst ist,
um auf das Kommunikationsnetz Ober das Funkzugangsnetz des ersten Typs zuzugreifen; dadurch gekennzeich-
net, dass das Mobilendgerat eingerichtet ist, um eine Information, die mindestens ein Tragerdienst-Fahigkeits-Feld
35 beinhaltet, von dem Mobilendgerat an das Funkzugangsnetz des ersten Typs zu Obertragen, wobei die Information
zum Anzeigen dient, dass ein angeforderter Dienst nur mit dem Funkzugangsnetz des zweiten Typs betreibbar ist.
20. Mobilendgerat gemaB Anspruch 19, wobei die Ubertragung, die die Einleitung beinhaltet, eine Ubertragung gemaB
einer Verbindungssteuerungs-Schicht-Prozedur ist.
40
21. Mobilendgerat gemaB Anspruch 20, wobei die Ubertragung gemaB einer Verbindungsaufbau-Prozedur tor Multi-
media-Telefonie ist.
22. Mobilendgerat gemaB einem der AnsprOche 19 bis 21, umfassend eine Verbindungssteuerungs-Einheit, die ange-
45 passt ist, um die Ubertragung zu kodieren, und eine Funkfrequenzschnittstelle, die angepasst ist, um die Ubertragung
an eine Verbindungssteuerungs-Einheit des Funkzugangsnetzes des ersten Typs zu Obertragen.
23. Netzeinheit, die geeignet ist, um ein Inter-System Handover innerhalb eines Kommunikationsnetzes auszulosen,
wobei die Netzeinheit ein Teil davon ist, wobei eine Ubertragung aus einem Mobilendgerat empfangen wird, das
50 mindestens mit einem Funkzugangsnetz eines ersten Typs und einem Funkzugangsnetz eines zweiten Typs be-
treibbar ist, die das Kommunikationsnetz bilden, dadurch gekennzeichnet, dass die Netzeinheit angepasst ist,
um das Inter-System Handover zum Funkzugangsnetz des zweiten Typs auszulosen, in Reaktion auf die Ubertra-
gung von dem Mobilendgerat, das auf das Kommunikationsnetz Oberdas Funkzugangsnetz des ersten Typs zugreift,
wobei die Ubertragung eine Information beinhaltet, die mindestens ein Tragerdienst-Fahigkeits-Feld beinhaltet, das
55 anzeigt, dass ein angeforderter Dienst nur mit dem Funkzugangsnetz des zweiten Typs betreibbar ist.
24. Netzeinheit gemaB Anspruch 23, wobei die Ubertragung, die die Einleitung beinhaltet, eine Ubertragung gemaB
einer Verbindungssteuerungs-Schicht-Prozedur ist.
19
EP 1 808 029 81
25. Netzeinheit gemaB Anspruch 24, wobei die Ubertragung gemaB einerVerbindungsaufbau-Prozedurtor Multimedia-
Telefonie ist.
26. Netzeinheit gemaB einem der Anspruche 23 bis 25, umfassend eine Schnittstelle, die angepasst ist, um die Uber-
5 tragung zu empfangen, eine Verbindungssteuerungs-Einheit, die angepasst ist, um die Obertragung zu dekodieren
und zu analysieren, um die Anzeige tor das Inter-System Handover zu erfassen, und eine Ausloseeinheit, die
angepasst ist, um das Inter-System Handover auszulosen.
27. Kommunikationsnetz, das geeignet ist, ein Inter-System Handover auszutohren, wobei das Kommunikationsnetz
10 Funkzugangsnetze mindestens eines ersten und eines zweiten Typs und eine Netzeinheit zum Auslosen des Inter-
System Handovers eines Mobilendgerats umfasst, das mit den Funkzugangsnetzen des ersten und des zweiten
Typs betreibbar ist, dadurch gekennzeichnet, dass das Kommunikationsnetz angepasst ist, um das Inter-System
Handover zu dem Zugangsnetz des zweiten Typs auszutohren, in Reaktion auf eine Obertragung von dem Mobi-
lendgerat, das auf das Kommunikationsnetz Ober das Funkzugangsnetz des ersten Typs zugreift, wobei die Uber-
15 tragung eine Information beinhaltet, die mindestens ein Tragerdienst-Fahigkeits-Feld beinhaltet, das anzeigt, dass
ein durch das Mobilendgerat angeforderter Dienst nur mit dem Funkzugangsnetz des zweiten Typs betreibbar ist.
28. Kommunikationsnetz gemaB Anspruch 27, wobei die Obertragung, die die Einleitung beinhaltet, eine Obertragung
gemaB einer Verbindungssteuerungs-Schicht-Prozedur ist.
20
29. Kommunikationsnetz gemaB Anspruch 28, wobei die Obertragung gemaB einer Verbindungsaufbau-Prozedur tor
Multimedia-Telefonie ist.
30. Kommunikationsnetz gemaB einem der Anspruche 27 bis 29, umfassend eine Funkfrequenzschnittstelle, die an-
25 gepasst ist, um die Ubertragung von dem Mobilendgerat zu empfangen, und eine Verbindungssteuerungs-Einheit,
die angepasst ist, um die Obertragung zu dekodieren und zu analysieren, um die Anzeige tor das Inter-System
Handover zu eriassen, wobei eine Ausloseeinheit, die angepasst ist, um das Inter-System Handover auszulosen,
das Inter-System Handover auf eine Erfassung auslost.
30
Revendications
1. a a
Precede destine initier un transfert intercellulaire inter-systeme d'un terminal mobile accedant un reseau de
communication, dans lequel ledit reseau de communication comprend au moins un reseau d'acces radio d'un
35 a
premier type et un reseau d'acces radio d'un second type, dans lequel ledit terminal mobile est apte etre exploite
dans au mo ins lesdits reseaux radio dudit premier type et duditsecond type, dans lequel ledit precede estcaracterise
a
par l'etape consistant initier ledit transfert intercellulaire inter-systeme dudit terminal mobile accedant audit reseau
a
de communication via ledit reseau d'acces radio dudit premier type en reponse la transmission, par le biais dudit
terminal mobile, d'une information comportant au moins un champ de capacite de porteuse indiquant qu'un service
40 requis est uniquement exploitable avec ledit reseau d'acces radio dudit second type.
2. Precede selon la revendication 1, dans lequel ladite information transmise pour !'initiation est une transmission selon
une procedure de niveau de commande d'appel.
45 3. Precede selon la revendication 2, dans lequel ladite information est transmise selon une procedure d'etablissement
d'appel de telephonie multimedia.
4. Precede selon l'une quelconque des revendications precedentes, dans lequel ladite information est un message
a
de commande d'appel, ledit precede comportant l'etape consistant transmettre ledit message dudit terminal mobile
5o a un reseau federateur en faisant appel audit reseau d'acces radio dudit premier type.
5. Precede selon l'une quelconque des revendications precedentes, dans lequel ledit au moins un champ de capacite
de porteuse presente une valeur de parametre inapplicable pour ledit reseau d'acces radio dudit premier type.
55 6. Precede selon l'une quelconque des revendications precedentes, dans lequel ledit au moins un champ de capacite
a
de porteuse choisi partir de ladite pluralite de champs de capacite de porteuse se distingue en ce qu'au moins
unevalidite devaleurde parametre dudit au moins un champ de capacite de po rte use differe dans les communications
avec lesdits reseaux d'acces radio dudit premier type et dudit second type.
20
EP 1 808 029 81
7. Precede selon l'une quelconque des revendications precedentes, dans lequel ladite transmission est un message
de reglage « SETUP,, de commande d'appel selon une procedure d'etablissement d'appel en provenance d'un
mobile,
ledit precede comportant les etapes ci-dessous consistant a:
5
coder ledit message de reglage « SETUP ,, avec un ou plusieurs elements d'information de capacite de porteuse
co mportant ledit au moins un champ de capacite de porteuse dans une entite de commande d'appel dudit
terminal mobile ; et
a
transmettre, par le biais dudit terminal mobile, ledit message de reglage « SETUP,, une entite de commande
10 d'appel, en faisant appel audit reseau federateur dudit reseau d'acces radio dudit premier type pour initier ledit
transfert intercellulaire inter-systeme.
8. a
Precede selon l'une quelconque des revendications 1 6, dans lequel ladite transmission est un message d'appel
confirme" CALL CONFIRMED ,, de comm an de d'appel selon une procedure d'etablissement d'appel determinaison
15 d'un mobile,
ledit precede comportant les etapes ci-dessous consistant a:
coder, dans une entite de commande d'appel dudit terminal mobile, ledit message d'appel confirme « CALL
CONFIRMED,, avec un ou plusieurs elements d'information de capacite de porteuse comportant ledit au moins
20 un champ de capacite de porteuse ; et
transmettre, par le biais dudit terminal mobile, ledit message d'appel confirme «CALL CONFIRMED,, une a
entite de commande d'appel dudit reseau federateur en utilisant ledit reseau d'acces radio dudit premier type
pour initier ledit transfert intercellulaire inter-systeme.
25 9. Precede selon l'une quelconque des revendications precedentes, dans lequel ledit au mo ins un element d'information
de capacite de porteuse comprend tous les champs de codages de canal qui sont definis en tant que « non
acceptables "·
10. Precede selon l'une quelconque des revendications precedentes, dans lequel ledit au moins un champ de capacite
30 de porteuse comprend un champ de debit d'utilisateur de reseau fixe qui est defini a une valeur de debit de donnees
applicable uniquement avec ledit reseau d'acces radio dudit second type.
11. Precede selon la revendication 10, dans lequel ledit champ de debit d'utilisateur de reseau fixe est defini a une
valeur de debit de donnees de 33,6 kbit/s.
35
12. Precede selon l'une quelconque des revendications precedentes, dans lequel ledit reseau d'acces radio dudit
premier type est un reseau d'acces radio de technologie de 28 generation et Iedit reseau d'acces radio dudit second
type est un reseau d'acces radio de technologie de 38 generation.
40 13. Precede selon l'une quelconque des revendications precedentes, dans lequel ledit reseau d'acces radio dudit
premier type est un reseau d'acces radio de systeme mondial de communication avec les mobiles I service general
de radiocommunication par paquets, GSM/GPRS, et ledit reseau d'acces radio dudit seconde type est un reseau
a
d'acces radio, d'acces multiple par repartition en code large bande, WCDMA.
45 a a
14. Precede destine initier un transfert intercellulaire inter-systeme d'un terminal mobile accedant un reseau de
communication, dans lequel ledit reseau de communication comprend au moins un reseau d'acces radio d'un
a
premier type et un reseau d'acces radio d'un second type, dans lequel ledit terminal mobile est apte fonctionner
dans au moins lesdits reseaux d'acces radio dudit premier type et dudit second type, dans lequel ledit precede est
a
caracterise par l'etape ci-dessous consistant initier, au niveau d'une entite de reseau dudit reseau de commu-
50 nication, ledit transfert intercellulaire inter-systeme dudit terminal mobile accedant audit reseau de communication
a
via Iedit reseau d'acces radio dudit premiertype, en reponse la reception, par leditterminal mobile, d'une information
comportant au moins un champ de capacite de porteuse indiquant qu'un service requis est uniquement exploitable
avec ledit reseau d'acces radio dudit second type.
55 15. Precede selon la revendication 14, dans lequel ladite information transmise pour !'initiation est une transmission
selon une procedure de niveau de commande d'appel.
16. Precede selon la revendication 14 ou 15, dans lequel ladite information est un message de commande d'appel,
21
EP 1 808 029 81
ledit precede comportant l'etape consistant a recevoir ledit message dudit terminal mobile au niveau d'un reseau
federateur en faisant appel audit reseau d'acces radio dudit premier type.
17. Produit-programme informatique comportant des sections de code de programme stockees sur un support lisible
5 par ordinateur pour mettre en oeuvre les etapes respectives du precede correspondant selon l'une quelconque des
a
revendications 1 16, lorsque lesdites sections de code de programme sont executees sur un dispositif base de a
processeur associe au terminal mobile active pour la communication avec ledit reseau de communication, ou a
l'entite de reseau, respectivement.
10 18. Module fourni dans un terminal mobile, qui est exploitable avec un reseau de communication comportant au moins
un reseau d'acces radio d'un premier type et un reseau d'acces radio d'un second type, dans lequel ledit module
est apte a acceder audit reseau de communication via ledit reseau d'acces radio dudit premier type ; caracterise
en ce que ledit module est configure pour transmettre une information comportant au moins un champ de capacite
de porteuse dudit module audit reseau d'acces radio dudit premier type en vue d'initier un transfert intercellulaire
15 inter-systeme, dans lequel ladite information sert a indiquer qu'un service requis est uniquement exploitable avec
ledit reseau d'acces radio dudit second type.
19. Terminal mobile active pour !'initiation d'un transfert intercellulaire inter-systeme au sein d'un reseau de communi-
cation, dans lequel ledit terminal mobile est exploitable avec ledit reseau de communication comportant au moins
20 un reseau d'acces radio d'un premier type et un reseau d'acces radio d'un second type, dans lequel ledit terminal
a
mobile est apte acceder audit reseau de communication via ledit reseau d'acces radio dudit premier type ; carac-
terise en ce que ledit terminal mobile est configure pour transmettre une information comportant au moins un
champ de capacite de porteuse, dudit terminal mobile audit reseau d'acces radio dudit premier type, dans lequel
a
ladite information sert indiquer qu'un service requis est uniquement exploitable avec ledit reseau d'acces radio
25 dudit second type.
20. Terminal mobile selon la revendication 19, dans lequel ladite transmission comportant ladite initiation est une trans-
mission selon une procedure de niveau de commande d'appel.
30 21. Terminal mobile selon la revendication 20, dans lequel ladite transmission s'effectue selon une procedure d'eta-
blissement d'appel de telephonie multimedia.
22. Terminal mobile selon l'une quelconque des revendications 19 a 21, comportant une entite de commande d'appel,
qui est apte a coder ladite transmission, et une interface de frequence radio, qui est apte a transmettre ladite
35 transmission a une entite de commande d'appel dudit reseau d'acces radio dudit premier type.
23. Entite de reseau activee en vue de declencher un transfert intercellulaire inter-systeme au sein d'un reseau de
communication, dont ladite entite de reseau fait partie, dans laquelle une transmission est rec;:ue d'un terminal mobile
exploitable avec au moins un reseau d'acces radio d'un premier type et un reseau d'acces radio d'un second type
40 a
formant ledit reseau de communication, caracterisee en ce que ladite entite de reseau est apte declencher ledit
transfert intercellulaire inter-systeme audit reseau d'acces radio dudit second type, en reponse au fait que ladite
transmission en provenance dudit terminal mobile accede audit reseau de communication via ledit reseau d'acces
radio dudit premier type, dans laquelle ladite transmission comporte une information incluant au moins un champ
de capacite de porteuse, lequel indique qu'un service requis est exploitable uniquement avec ledit reseau d'acces
45 radio dudit second type.
24. Entite de reseau selon la revendication 23, dans lequel ladite transmission comportant ladite initiation est une
transmission selon une procedure de niveau de commande d'appel.
50 25. Entite de reseau selon la revendication 24, dans lequel ladite transmission s'effectue selon une procedure d'eta-
blissement d'appel de telephonie multimedia.
26. Entite de reseau selon l'une quelconque des revendications 23 a25, comportant une interface, qui est apte a recevoir
a a
ladite transmission, une entite de commande d'appel, qui est apte decoder et analyser ladite transmission en
55 vue de detecter ladite indication pour ledit transfert intercellulaire inter-systeme, et une entite de declenchement,
a
qui est apte declencher ledit transfert intercellulaire inter-systeme.
27. Reseau de communication apte amettre en oeuvre un transfert intercellulaire inter-systeme, dans lequel ledit reseau
22
EP 1 808 029 81
de communication comp rend des reseaux d'acces radio d'au mo ins un premier type et un second type et une entite
de reseau pour declencher ledit transfert intercellulaire inter-systeme d'un terminal mobile exploitable avec les
reseaux d'acces radio dudit premier type et dudit second type, caracterise en ce que ledit reseau de communication
a
est apte mettre en oeuvre ledit transfert intercellulaire inter-systeme audit reseau d'acces radio dudit second type,
5 en reponse au fait qu'une transmission dudit terminal mobile accede audit reseau de communication via ledit reseau
d'acces radio dudit premier type, dans lequel ladite transmission comprend une information incluant au moins un
champ de capacite de porteuse indiquant qu'un service requis par ledit terminal mobile est uniquement exploitable
avec ledit reseau d'acces radio dudit second type.
10 28. Reseau de communication selon la revendication 27, dans lequel ladite transmission comportant ladite initiation est
une transmission selon une procedure de niveau de commande d'appel.
29. Reseau de communication selon la revendication 28, dans lequel ladite transmission s'effectue selon une procedure
d'etablissement d'appel de telephonie multimedia.
15
30. Reseau de communication selon l'une quelconque des revendications 27 a29, comportant une interface afrequence
a
radio, qui est apte recevoir ladite transmission en provenance dudit terminal mobile, et une entite de commande
a a
d'appel, qui est apte decoder et analyser ladite transmission, en vue de detecter ladite indication pour ledit
a
transfert intercellulaire inter-systeme, dans lequel une entite de declenchement, qui est apte declencher ledit
20 a
transfert intercellulaire inter-systeme, declenche ledit transfert intercellulaire inter-systeme suite une detection.
25
30
35
40
45
50
55
23
EP 1 808 029 81
Mobile GSMBSS
Tenninal (RAN).
MSC UTRAN
System Infonnation
Measurement Report
Fig. la
Mobile GSMBSS
Terminal
UTRAN MSC (RAN)
l l l l
( Mobile Terminal operates in 3G (UMTS) n.etwork
Measurement Report ..
,,,
Resource.! 1-eservation _..,
Resource Reservati< n Acknowledge and
Inter-System Handover
.....
-~ Handover Con:nnand
-
~ Command
Handover Access
.
..
""."
Fig. lb
24
EP 1 808 029 81
SETUP message
CONNECT messqe
....
Fig. 2a
25
EP 1 808 029 81
SETUP messa e
____ !9-----~~-~Q~l?~!~a.1.e_____ _
____ !~l----~~~§.!f~~~~~.!!i! __ _
CONNECT message ..
CONNECT ACKNOWLEDGE message
Fig. 2b
26
EP 1 808 029 81
8 7 6 5 4 3 2 1
Bearer capability IEI octet 1
Lel}Qth of the bearer c~abillli' contents octet2
0/1 radio co- trans Information
channel ding fer transfer octet3
ext
r~uirement std mode c~abi~
0/1
0 0
co- speech version
ext
dl1!9.
CTM spare
indication
octet 3a*
0/1 0 0 0
ext co- spare spare
speech version octet 3b etc*
di1!9. Indication
1 comp
structure
dupl. confi
NIRR esta-
ext -ress. mode _g_ur. bll.
0/1 0 0 rate signalling
octets-
ext access Id. adaption access protocol
0/1 Other rate 0 0 0 octet'Sa*
ext Other ITC ada_J)_tlon S_p_are
1 Hdr/ Multi Ass lg lnb. 0
Mode LLI octet'Sb*
ext noHdr frame nor/e neg Spare
0/1 0 1 User information sync/
octet'6*
ext lay_er 1 Id. l~er 1_Q_rotocol async
numb. nego- numb.
0/1 stop tia- user rate octet ea•
data
ext
bits tlon bits
0/1 intermed. NIC NIC Parity octet Sb*
ext rate on TX on RX
0/1 connection
modem type octet 6c*
ext element
0/1 Other
Fixed network user rate octet Gd*
ext modemtvDe
Acceptable
0/1 Maximum number of
octet6e*
channel
ext traffic channels
codin_g_s
0/1 Wanted air interface
UIMI octet 6f9
ext user rate
Acceptable Asymmetry 0 0
1 channel codings octet6g*
ext
extended Indication s~are
1 1 0 User infonnatlon
octet.,.
ext lay~r2 Id. l!!Y_er 2..Q..rotocol
Fig. 3
27
EP 1 808 029 81
GGSN
HLR
BS (NodeB) BTS
dual-mode
mobile terminal,
Fig. 4a
GGSN
HLR
VLR
RNC BSC
'EJ .
BS(NodeB) BTS
dual-mode
. mobile tennina1
Fig.4b
28
EP 1 808 029 81
Inter-System Handover
Handover co lete
CALLPROCE
Fig. Sa
l l l
Dual.Mode Mobile Terminal operates in 20 {OSM) network
...
.....
SETUP message
CALL CONFm.MED messa e with modified BC IE fields
....
Inter.;system Handover
Handover complete .....r
ALERTIN Gmessage ..
,,.
t .. · ,; ..... •. .-:. :.: J t::·. ;: •.. ·'···: ·"!:-:. ·.;.] (Ii"'·'"'.'...!'~ .. ; ,;;!J',:,.' j : 1ti
·Fig. Sb
29
EP 1 808 029 81
This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European
patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be
excluded and the EPO disclaims all liability in this regard.
30
Page 1
ETSI Rules of Procedure, 26 November 2008
D are not the proprietor of the IPR(s) disclosed in the attached IPR Information Statement Annex.
SIGNATURE
By signing this IPR Information Statement and Licensing Declaration form, you represent that you have the
authority to bind the Declarant and/or its AFFILIATES to the representations and commitments provided in
this form.
Name of authorized person: Kalle Moilanen
Title of authorized person: IPR Manager
Place, Date: Salo, Finland, 21st of June 2010
Signature:
200480044232 .1 101044771 CN
04798766.4 1808029 DE
EP
04798766.4 1808029 OK
Inter-system
04798766.4 1808029 GB
hand over of a
2238/DELNP/2007 IN
0479876 mobile terminal
5.3 .6.2.1, 1808029 2007 -539641 2008-519520 JP I
24.008 6.9.0 Nokia 6.4 operable with a
GSM 5.3.6.2.2 2007-7010154 2007-61577 KR
Corporation first and a
PI20055102 MY
second radio
783/2005 PK
access network
04798766.4 1808029 RO
94137753 TW
11 /666578 20090156215 US
PCT1IB2004/003590 W02006 /048697 WO
I
Unlicensed
44.318 :6.2.2. 44.318: mobile access 200680021168.4 101199163 I CN
1,6.1,6.2.2.2, 8.7.0 , 11 /2883 20060286 support in US 06744959 .5 1891774 EP
44.318, Nokia
GSM 11 .2.7, 43.318: 41 981 mobile networks PCT/IB2006/051554 W02006 /134504 WO
43.318 Corporation
43 .318 :3.1, 8.4.0 of the third
4.2 generation
!
System and I
method for
secure US
33.259 4.1, B.1 , 4.4.1 9.0.0 Nokia 10/8813 20060005 communications
GSM 14 033 between at
Corporation
least one user I
device and a I
network entity
Mod ified dual
US
20070286 symbol rate for 200780013791 .X 101427508 CN
45.004 4.1, 5.1 7.2.0 Nokia 11 /7299
GSM 300 uplink mobile 8241 /DELNP/2008 IN
Corporation 56
com m u nications PCT /IB2007 /000815 W02007 /119135 WO
I
Page 1
ETSI Rules of Procedure, 26 November 2008
SIGNATURE
By signing this IPR Information Statement and Licensing Declaration form, you represent that you have the
authority to bind the Declarant and/or its AFFILIATES to the representations and commitments provided in
this form.
Name of authorized person: Kalle Moilanen
Title of authorized person: IPR Manager
Place, Date: Salo, Finland, 21st of June 2010
~ f&VJc')-=
t
nature:
200480044232 .1 101044771 CN
EP 04798766.4
04798766.4
1808029
1808029
DE
OK
Inter-system
04798766.4 1808029 GB
hand over of a 1
2238/DELNP/2007 IN
0479876 mobile terminal I JP
5.3.6.2 .1, 1808029 2007-539641 2008-519520
24.008 6.9.0 Nokia 6.4 operable with a
UMTS 5.3.6.2.2 2007-7010154 2007-61577 KR
Corporation first and a
PI20055102 MY
second radio
783/2005 PK
access network
04798766.4 1808029 I RO
94137753 I TW
11 /666578 20090156215 US
PCT/IB2004/003590 W02006/048697 WO
System and
method for
secure US
I
33 .259 4.1, B.1 , 4.4.1 9.0.0 Nokia 10/8813 20060005 communications
UMTS
Corporation 14 033 between at I I
SIGNATURE
By signing thfs IPR Information Statement and Licensing Declaration form, you represent that you have the
authority to bind the Declarant and/or its AFFILIATES to the representations and commitments provided in
this form.
Name of authorized person : u ~v 1,0 L ( oi..lf.N
Title of authorized person :
Place, Date : ,vm
Signature: /lltJ.L l oJ.tN
Please return this form duly signed to: ETSI Director-Genera/
ETSI - 650, route des Lucio/es - F-06921 Sophia AntipoUs Cedex - France I Fax. +33 (0) 4 93 65 47 16
IPR Information Statement Annex
STANDARD, TECHNICAL SPECIFICATION or
FURTHER INFORMATION
ETSI Work Item
Other members of this PATENT FAMILY, if any *
Illustrative
Application Publication Patent/Application Country of
Work Specific Proprietor
Project or No. No. Title registration
item or part of the Version Country of
Standard Application No. Publication No.
Standard standard (V.X.X.X) registration
name
No. (e.g.
Section)
LTE$ 123.272$ 4.1,$4.2,$ V8.12.0$ Vringo$ 04798766.4$ 1808029$ Inter>system$ EP$ 200480044232.1$ 602004021646.1$ DE$
4.3.1,$ Infrastructure,$ hand>over$of$a$ 04798766.4$ 101044771$ CN$
6.2,$7.3$ Inc.$ mobile$ 04798766.4$ 1808029$ DK$
terminal$ 04798766.4$ 1808029$ GB$
operable$with$a$ 2238/DELNP/2007$ $ IN$
first$and$a$
2007>539641$ 4612050$ JP$
second$radio$
2007>7010154$ 912629$ KR$
access$network$
PI20055102$ 142706>A$ MY$
783/2005$ 141924$ PK$
047998766.4$ 1808029$ RO$
94137753$ I393462$ TW$
11/666578$ 20090156215$ US$
PCT/IB2004/003590$ WO2006/048697$ WO$
LTE$ 124.301$ 8.2.15.1,$ V.8.10.0$ Vringo$ 04798766.4$ 1808029$ Inter>system$ EP$ 200480044232.1$ 602004021646.1$ DE$
9.9.3.27$ Infrastructure,$ hand>over$of$a$ 04798766.4$ 101044771$ CN$
Inc.$ mobile$ 04798766.4$ 1808029$ DK$
terminal$ 04798766.4$ 1808029$ GB$
operable$with$a$ 2238/DELNP/2007$ $ IN$
first$and$a$
2007>539641$ 4612050$ JP$
second$radio$
access$network$ 2007>7010154$ 912629$ KR$
PI20055102$ 142706>A$ MY$
783/2005$ 141924$ PK$
047998766.4$ 1808029$ RO$
94137753$ I393462$ TW$
11/666578$ 20090156215$ US$
PCT/IB2004/003590$ WO2006/048697$ WO$
LTE$ 124.008$ 10.5.4.5$ V.9.2.0$ Vringo$ 04798766.4$ 1808029$ Inter>system$ EP$ 200480044232.1$ 602004021646.1$ DE$
Infrastructure,$ hand>over$of$a$ 04798766.4$ 101044771$ CN$
Inc.$ mobile$ 04798766.4$ 1808029$ DK$
terminal$ 04798766.4$ 1808029$ GB$
operable$with$a$ 2238/DELNP/2007$ $ IN$
! 1!
first$and$a$ 2007>539641$ 4612050$ JP$
second$radio$ 2007>7010154$ 912629$ KR$
access$network$ PI20055102$ 142706>A$ MY$
783/2005$ 141924$ PK$
047998766.4$ 1808029$ RO$
94137753$ I393462$ TW$
11/666578$ 20090156215$ US$
PCT/IB2004/003590$ WO2006/048697$ WO$
UMTS/GSM$ 24.008$ 5.3.6.2.1,$ V.6.9.0$ Vringo$ 04798766.4$ 1808029$ Inter>system$ EP$ 200480044232.1$ 602004021646.1$ DE$
5.3.6.2.2$ Infrastructure,$ hand>over$of$a$ 04798766.4$ 101044771$ CN$
Inc.$ mobile$ 04798766.4$ 1808029$ DK$
terminal$ 04798766.4$ 1808029$ GB$
operable$with$a$ 2238/DELNP/2007$ $ IN$
first$and$a$
2007>539641$ 4612050$ JP$
second$radio$
2007>7010154$ 912629$ KR$
access$network$
PI20055102$ 142706>A$ MY$
783/2005$ 141924$ PK$
047998766.4$ 1808029$ RO$
94137753$ I393462$ TW$
11/666578$ 20090156215$ US$
PCT/IB2004/003590$ WO2006/048697$ WO$
* Information on other members of a PATENT FAMILY is provided voluntarily (Clause 4.3 of the ETSI IPR Policy).
!
!
! 2!
特許出願人 発明の名称 出願番号等 備考(出願国名)( 2)
(PATENT HOLDER) (NAME OF PATENT) (REGISTRATION NO. / REMARKS
APPLICATION NO.)
NOKIA Method and apparatus for detecting hangover periods in a TDMA JP9-504848, 3826185 Other countries:
CORPORATION *8.20 wireless communication system using discontinuous transmission AT, AU, BR, CA, CN, DE, ES, FI,
FR, GB, IT, MX, RU, SE, US, WO
NOKIA Upgrading of resources in a telecommunications network JP2000-527040, AU, CN, DE, EP, ES, FI, FR, GB, IT,
CORPORATION *8.20 2002500467 NL, RO, US, WO
NOKIA Multi-mode radio telephone which executes handover between JP7-333841, 3182068 DE, EP, FR, GB, SE, US
CORPORATION *8.20 different system
NOKIA Method and device for carrying out security procedures involving JP2001-540555, 3830388 CA, CN, DE, EP, FI, FR, GB, IT, NL,
CORPORATION *8.20 mobile stations in hybrid cellular telecommunication systems US, WO
NOKIA Authentication in heterogeneous IP networks JP2006-530754, 4475596 AU, CN, EP, IN, KR, US, WO
CORPORATION *8.20
NOKIA Method and apparatus for performing inter-technology handoff JP2005-505658, 4251500 US, WO
CORPORATION *8.20 from WLAN to cellular network
NOKIA Method and apparatus enabling reauthentication in a cellular JP2005-500071, CN, EP, KR, MY, NO, RU, TW, US,
CORPORATION *8.20 communication system 2006-515486 VN, WO
NOKIA Inter-system hand-over of a mobile terminal operable with a first JP2007-539641, CN, DE, DK, EP, GB, IN, KR, MY,
CORPORATION *8.20 and a second radio access network 2008-519520 MY, PK, RO, TW, US, WO
NOKIA Apparatus, method and computer program product providing JP2008-526565, BR, CN, EP, IN, KE, KR, MX, MY,
CORPORATION *8.20 inclusion of local area information in broadcast messages and 2009-505547 NG, PH, RU, TH, TW, US, VN, WO,
maintenance of radio access network black list ZA
NOKIA Adaptive preamble length for continuous connectivity transmission JP2008-553842, AP, CN, EP, IN, KR, NG, PH, TH,
CORPORATION *8.20 2009-527140 US, WO
286
23
A40985VI
(19) Europ:.iisches
Patentamt
European 111111111111111111111111111111111111111111111111111111111111111111111111111
Patent Office
Office europt!en
des brevets
(11) EP 1 842 386 81
(12) EUROPEAN PATENT SPECIFICATION
Note: Within nine months of the publication of the mention of the grant of the European patent in the European Patent
Bulletin, any person may give notice to the European Patent Office of opposition to that patent, in accordance with the
Implementing Regulations. Notice of opposition shall not be deemed to have been filed until the opposition fee has been
a.. paid. (Art. 99(1) European Patent Convention).
w
Printed by Jouve, 75001 PARIS (FR) (Cont. next page)
EP 1 842 386 B1
2
EP 1 842 386 B1 2
3
3 EP 1 842 386 B1 4
4
5 EP 1 842 386 B1 6
can be minimized as well. In the prior art a dummy LLC by the target cell triggers downlink data forwarding and
(logical link control) frame was frequently used to perform releasing of the source side radio resources by the BSS
a cell update, thus minimizing the downlink transmission 12).
gap because the SGSN could start the downlink trans- [0034] According to the present invention, for the non-
mission sooner when a short LLC frame (e.g., the dummy 5 optimized intra-BSS case and the inter-BSS case the
LLC frame) was used for the cell update with faster han- source side radio resources are still released by the SG-
dling of that short LLC frame. According to the present SN, but the downlink data transmission gap is reduced
invention, sending the dummy LLC cell is not necessary by the omission of the cell update procedure as described
any more and the mobile station 10 can send the LLC above. The PS Handover Performed message (refer to
frame with a payload data right away after the PS hando- 10 step 50) shall therefore contain element information such
ver is performed, thus minimizing the uplink transmission as a TLLI (temporary logical link identity), a Cell Identifier
gap (e.g., in principle after step 38). (including RAC, i.e., routing area code), a Flush Action
[0028] Thus, according to the present invention, the and a Number of Octets Affected. A new information el-
mobile station (MS) can be informed about said cell ement (for the target cell) "new BVCI" (BSSGP virtual
change in step 34 which allows starting immediately said 15 connection identifier) is needed as well, if for the opti-
uplink data transfer as discussed above, thus further re- mized intra-BSS case the message is not sent on the p-
ducing said service interruption caused by said packet t-p (point-to-point) BVCI, but instead on the signalling
switched handover. BVCI.
[0029] The radio interface packet switched (PS) [0035] It is to be understood that the above-described
Handover Command message 34 shall contain an indi- 20 arrangements are only illustrative of the application of
cation that a cell update is handled by the BSS 12, such the principles of the present invention. Numerous modi-
that the MS 10 can omit the procedure and start the actual fications and alternative arrangements may be devised
uplink data transmission right after access on the target by those skilled in the art without departing from the scope
cell. of the present invention, and the appended claims are
[0030] For the optimized intra-BSS case a target BSC 25 intended to cover such modifications and arrangements.
is the same as a source BSC so it knows based on the
source and target cells whether the RA (routing area)
stays the same or changes during the packet switched Claims
handover. For the optimized intra-BSS case the source
and target cells are associated with the same network 30 1. A method for improving the performance of a down-
service entity (NSE) and the same routing area (RA). link data transfer during a packet switched handover,
[0031] For the non-optimized intra-BSS case and inter- wherein said packet switched handover corresponds
BSS case the target BSC knows based on information to an optimized intra-BSS handover procedure, com-
elements a Source Cell Identifier and a Target Cell Iden- prising:
tifier (inside a PS Handover Request from the SGSN 14 35
to the target BSS 12) whether the RA stays the same or changing a source cell to a target cell in a context
changes during the packet switched handover. If the RA of said packet switched handover; and
stays the same, the target BSC (e.g., the BSS 12, 20 or informing a serving general packet radio service
24) shall handle the cell update towards the correspond- support node (14) about said cell change after
ing SGSN (e.g., the SGSN 14 or 22) and the MS 10 is 40 said change as the only required signalling with
informed. If the RA changes, it is up to the MS 10 to the serving general packet radio service support
perform an RA update towards the SGSN 14 as currently node to allow said downlink data transfer to re-
defined in the standardization. start immediately, for reducing a service inter-
[0032] CS (circuit switched) type of Handover Per- ruption caused by said packet switched hando-
formed message (per 3GPP TS 48.008 V6.7.0 45 ver, wherein said informing is performed by a
(2004-11)) which is also called a PS Handover Performed base station subsystem (12) and does not com-
message (as in the step 34 of Figures 2 and 3) could be prise sending a message from a mobile station
used for to reducing the gap for a downlink data trans- (10) to said serving general packet radio service
mission. support node.
[0033] For the optimized intra-BSS case, according to 50
the present invention, with a message indicating the 2. A method according to claim 1 further comprising:
same as the BSSGP (base station subsystem GPRS pro-
tocol) Flush-LL-Ack message, data could be forwarded informing said mobile station (10) about said cell
to the target cell and the source side radio resources change after said change, which allows an up-
could be released by the BSS 12 upon reception of the 55 link data transfer to restart immediately, thus fur-
first correct uplink RLC/MAC (radio link control/medium ther reducing said service interruption caused
access control) block (sent in a normal burst format) from by said packet switched handover.
the MS 10 (i.e., the uplink data reception from the MS 10
5
7 EP 1 842 386 B1 8
3. A method according to claim 1, wherein said chang- radio resources in said source cell right after said
ing said source cell to said target cell is performed cell change, which allows restarting immediately
by said base station subsystem (12) communicating said downlink data transfer, thus reducing said
with said mobile station ( 10). service interruption caused by said packet
5 switched handover.
4. A method according to claim 1, wherein said packet
switched handover is performed within a
GSM/EDGE radio access network. PatentansprUche
5. A computer program product comprising: a compu- 10 1. Verfahren zur Verbesserung der Leistung einer
ter readable storage structure embodying computer Downlink-DatenObertragung wahrend einer paket-
program code thereon for execution by a computer vermittelten Obergabe, wobei die paketvermittelte
processor, wherein said computer program code Obergabe einem optimierten lntra-BSS-Obergabe-
comprises instructions for performing the method of vorgang entspricht, wobei das Verfahren umfasst:
claim 3. 15
6
9 EP 1 842 386 B1 10
link-DatenObertragung wahrend einer paketvermit- le fa it de changer une cellule source en une cel-
telten Obergabe, wobei die paketvermittelte Ober- a
lule cible dans un contexte dud it transfert com-
gabe einem optim ierten lntra-BSS-0 bergabevor- mutation de paquets ; et
gang entspricht, wobei das System umfasst: le fa it d'informer un noeud de support de service
5 general radio par paquets (14) dudit change-
Mittel ( 12) zum Andern einer Quellzelle in eine ment de cellule apres led it changement en tant
Zielzelle in einem Kontext einer paketvermittel- que seule signalisation requise avec le noeud
ten Obergabe; und de support de service general radio par paquets
Mittel ( 12) zum lnformieren eines Serving Ge- pour permettre audit transfert de donnees de
neral Packet Radio Service Support Node (14) 10 liaison descendante de recommencer immedia-
Ober die Zellanderung nach der Anderung als tement, pour reduire une interruption de service
einzig erforderliche Signalisierung an den Ser- a
entraTnee par ledit transfert commutation de
ving General Packet Radio Service Support No- paquets, dans lequel Iedit fa it d'informer est rea-
de, um einen unverzOglichen Neustart einer lisee par un sous-systeme de station de base
Downlink-DatenObertragung zu ermoglichen, 15 (12) et ne comprend pas le fait d'envoyer un
um eine durch die paketvermittelte Obergabe message d'une station mobile (10) audit noeud
hervorgerufene Betriebsunterbrechung zu ver- de support de service general radio par paquets.
kOrzen, wobei das Mittel zum lnformieren ein
Basisstationsubsystem umfasst und wobei das 2. Precede selon la revendication 1, comprenant en
lnformieren kein Senden einer Nachricht van ei- 20 outre :
ner mobilen Station ( 10) an den Serving General
Packet Radio Service Support Node umfasst. le fait d'informer ladite station mobile (10) dudit
changement de cellule a pres led it changement,
7. System nach Anspruch 6, wobei das Mittel (12) zum ce qui permet a un transfert de donnees de
Andern der Quellzelle in die Zielzelle derart konfigu- 25 liaison montante de recommencer immediate-
riert ist, dass es mit der mobilen Station (10) kom- ment, reduisant ainsi davantage ladite interrup-
muniziert. tion de service entraTnee par ledit transfert a
commutation de paquets.
8. System nach Anspruch 7, wobei das Mittel (12) zum
lnformieren des Serving General Packet Radio Ser- 30 3. Precede selon la revendication 1, dans lequel ledit
vice Support Node Ober die Zellanderung dazu kon- fait de changer ladite cellule source en dite cellule
figuriert ist, nach dem lnformieren keinen Zellaktua- cible est realise par led it sous-systeme de station de
lisierungsvorgang durchzufUhren. base (12) communiquant avec ladite station mobile
(10).
9. System nach Anspruch 6, wobei die paketvermittelte 35
Obergabe innerhalb eines GSM/EDGE-Funkzu- 4. Precede selon la revendication 1, dans lequel ledit
gangsnetzes durchgefUhrt wird. a
transfert commutation de paquets est realise l'in-a
terieur d'un reseau d'acces radio GSM/EDGE.
10. System nach Anspruch 6, welches ferner umfasst:
40 5. Produit programme d'ordinateur, comprenant:
Mittel zum weiteren Weiterleiten der Downlink-
Daten van der Quellzelle zur Zielzelle und zur une structure de stockage lisible par ordinateur
Freigabe van Funkressourcen in der Quellzelle incorporant un code de programme d'ordinateur
direkt nach der Zellanderung, was den unver- sur celle-ci pour !'execution par un processeur
zOglichen Neustart der Downlink-DatenObertra- 45 d'ordinateur, dans lequel led it code de program-
gung ermoglicht, wodurch die durch die paket- me d'ordinateur comprend des instructions pour
vermittelte Obergabe hervorgerufene Betriebs- realiser le precede selon la revendication 3.
unterbrechung verkOrzt wird.
6. Systeme pour ameliorer les performances d'un
50 transfert de donnees de liaison descendante durant
Revendications a
un transfert commutation de paquets, dans lequel
a
ledit transfert commutation de paquets correspond
1. Precede pour ameliorer les performances d'un a une procedure de transfert intra-BSS optimisee,
transfert de donnees de liaison descendante durant comprenant :
a
un transfert commutation de paquets, dans lequel 55
a
led it transfert commutation de paquets correspond des moyens (12) pour le fait de changer une
a une procedure de transfert intra-BSS optimisee, cellule source en une cellule cible dans un con-
comprenant: a
texte d'un transfert commutation de paquets ;
7
11 EP 1 842 386 B1 12
et
des moyens (12) pour le fa it d'informer un noeud
de support de service general radio par paquets
(14) dudit changement de cellule apres ledit
changement en tant que seule signalisation re- 5
quise avec le noeud de support de service ge-
neral radio par paquets pour permettre de re-
commencer immediatement un transfertde don-
nees de liaison descendante, pour reduire une
interruption de service entraTnee par led it trans- 10
a
fert commutation de paquets, dans lequel les-
dits moyens pour le fa it d'informer comprennent
un sous-systeme de station de base et dans le-
quel led it fait d'informer ne comprend pas le fa it
d'envoyer un message d'une station mobile (10) 15
audit noeud de support de service general radio
par paquets.
50
55
8
EP 1 842 386 B1
Core network
j__24 L22
Further base
station subsystem """"'"-----+~.-i Further SGSN
(BSS) r--
12
\ Base station
subsystem 1~Gb SGSN ~
(BSS) •:11'''
A
A
Um Mobile
switching
.. center
Gb
Mobile station
107
Additional base
20
~ station
subsystem
(BSS)
Figure 1
9
EP 1 842 386 B1
MS BSS SGSN
PS Handover Command
...
PS Handover Access
~
-r----. 42a
Flush-LL_Ack
42b
!""'-----------
10
EP 1 842 386 B1
10 14
12
MS BSS SGSN
38
,. ___ -------- DL LLC PDU (new BVCI)
-------- -
44
Figure 3
11
EP 1 842 386 B1
This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European
patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be
excluded and the EPO disclaims al/ liability in this regard.
WO 2004021582 A1 [0004]
Packet-Switched Handover for GERAN A/Gb mode. 3GPP TS 43.129 V6.1.0, November 2004 [0017]
3GPP TS 43.129 V6.0.0, November 2004 [0002] [0023]
3GPP TS 48.008 V6. 7.0, November 2004 [0032]
12
European Telecommunication Standards Institute
IPR information statement and licensing declaration forms
Page 1 of B (version 5)
IPR Holder/Organisation
Signatory
Department: IPR _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __
E-mail: kalle.moilanen@nokia.com _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ __
In accordance with the ETSI IPR Policy, Clause 4.1, I hereby inform ETSI that,
it is my belief that the IPRs listed in the attached IPR information statement annex are, or are likely to
become, Essential I PRs in relation to that Standard.
The SIGNATORY has notified ETSI that it is the proprietor of the IPRs listed in the attached IPR
information statement annex and has informed ETSI that it believes that the I PRs may be considered
ESSENTIAL to the Standards listed above.
The SIGNATORY and/or its AFFILIATES hereby declare that they are prepared to grant irrevocable
licences under the IPRs on terms and conditions which are in accordance with Clause 6.1 of the ETSI
IPR Policy, in respect of the STANDARD, to the extent that the IPRs remain ESSENTIAL.
This undertaking is made subject to the condition that those who seek licences agree to reciprocate same
in respect of the STANDARD in accordance with Clause 6.1 of the ETSI IPR Policy (delete this paragraph
if this condition is not required).
The construction, validity and performance of this DECLARATION shall be governed by the laws of
France.
handover
10.4.33
GSM v.7.4.0 PI20061395 Malaysia
TS 43.055 TS 43.055 Nokia US200603909 Utilizing a United
95111130 Taiwan
TS 48.008 v.7.7.0 Corpora 93 same target States
6.3.3 W02006/103517 International
tion cell during
TS 48.018 v.7.7.0 Procedure
circuit-
switched
TS 48.008 and packet
3.1.5.1 switched
handover
3.2.1.8
24
A46841VI
(12) INTERNATIONAL APPLICATION PUBLISHED UNDER THE PATENT COOPERATION TREATY (PCT)
--
iiiiiiii
(54) Title: METHOD, DEVICE, SYSTEM AND SOFTWARE PRODUCT FOR PROVIDING SYSTEM INFORMATION TO
ENABLE PACKET SWITCHED HANDOVER
-
-
i iiiiiii
iiiiiiii
850 Target BSS Indication Whether SI/PSI is
Requested
-- handover signalling
SI/PSI
SI/PSI 860
870
before the expiration of the time limit for amending the For two-letter codes and other abbreviations, refer to the "Guid-
claims and to be republished in the event of receipt of ance Notes on Codes and Abbreviations" appearing at the begin-
amendments ning of each regular issue of the PCT Gazette.
WO 2007/036796 PCT/IB2006/002711
CONFIRMATION COPY
WO 2007/036796 PCT/IB2006/002711
2
WO 2007/036796 PCT/IB2006/002711
3
WO 2007/036796 PCT/IB2006/002711
It is important to ensure that the SRNC will get all the necessary information for PS
handover from the target BSS in case ofUTRAN to GERAN PS handover. With the present
invention, the SRNC will receive PSI/SI blocks in addition to a PS handover command
message, in the target BSS to source BSS transparent container.
One drawback of adding PSI/SI blocks in the target BSS to source BSS transparent
container may be in case the SRNC is the same as the CRNC, and the CRNC implements a
RJM/NACC procedure. As mentioned, it would be a waste to transfer PSI/SI blocks in the
transparent container, because the SRNC would have these blocks. To avoid this situation,
the present invention includes a way for the SRNC to indicate whether it needs PSI/SI blocks
fo the source BSS to target BSS transparent container. With this indication, it becomes
possible to avoid unnecessary delivery of PSI/SI blocks from the target BSS to the source
RNC.
This present invention can be used not only for inter-RAT PS handover, but also for
inter-BSS PS handover as well. This is because the RJM/NACC procedure is optional in the
GSM network as well.
Fig. 5 shows a change to 3GPP TS 25.413, section 9.2.l, describing a target BSS to
source BSS transparent container, according to a second version of an embodiment of the
present invention.
Fig. 6 shows another change to 3GPP TS 48.018, Table 11.3.80.a, describing a target
BSS to source BSS transparent container coding, according to the second solution of the
present invention.
FIG. 7 is a flow chart showing a method according to an embodiment of the present
invention.
FIG. 8 is a block diagram showing a system according to an embodiment of the
present invention.
5
WO 2007/036796 PCT/IB2006/002711
solution. An optimization for this transparent container solution can be to include a PSI/SI
Indicator IE in a source BSS to target BSS transparent container. If the SRNC and the CRNC
are the same RNC, and the CRNC implemented RIM/NACC, the SRNC will not need to
receive PSI/SI blocks again via a target BSS to source BSS transparent container. So, if the
SRNC has PSI/SI blocks for the target GSM cell, the SRNC will not include the PSI/SI
Indicator IE. If the SRNC needs to receive PSI/SI blocks via target BSS to source BSS
transparent container, it will include the PSI/SI Indicator with the value "True". If the
target BSS receives this indicator, it includes the PSI/Sis blocks in the target to source BSS
transparent container.
One illustrative implementation of the PSI/SI Indicator is shown in FIG 1. If the
PSI_SI Indicator IE is missing, it means the SRNC does not need to receive PSI/SI blocks.
But the meaning of existence of IE can be the other way around; i.e., a missing PSI/SI
Indicator IE can mean that the SRNC needs PSI/SI blocks.
Another illustrative implementation of the PSI/SI Indicator is to make the PSI/SI
Indicator a mandatory IE. Thus, this PSI/SI Indicator will always be included in the source
BSS to target BSS transparent container, and the source RNC/BSS must indicate clearly
whether it needs PSI/SI blocks or not. The implementation details can vary to realize PSI/SI
Indicator. The importance is that there should be a means for the source RNC/BSS to indicate
whether it needs to receive PSI/SI blocks or not from target BSS via transparent container.
A first version of this embodiment of the present invention involves having two parts
in a target BSS to source BSS transparent container. The first part of the container includes
PS HO COMMAND message in CSN.1 code in an octet string. The second part of the
container includes the number of PSI/Sis, type and PSIs or Sls in BSSGP code in an octet
string. According to this version, an approved RRC message (HANDOVER FROM UTRAN
COMMAND) can be used. Also, no RIM/NA CC is needed. The SRNC will always get
PSI/Sis in time during PS HO. The SRNC has to interpret the BSSGP command, because
only "Number of SI/PSI," "Type" and "SI/PSI" are needed in RRC message.
6
WO 2007/036796 PCT/IB2006/002711
7
WO 2007/036796 PCT/IB2006/002711
includes PS HO COMMAND message in CSN. l code, in an octet string. The third part to
the nth part of the container include the PSis or Sis, in BSSGP code in an octet string; i.e.,
one of these n parts contains one PSI or SI. No R.IM/NACC is needed. The SRNC will
always get PSI/Sis in time during PS HO. Blocks are transparent to the SRNC, and the
SRNC only needs to read the number of blocks. Then it just copies the content into a GSM
message list IE in HANDOVER FROM UTRAN COMMAND in the RRC.
To accommodate this version of the invention, a GSM message list must be extended
to cover a maximum of eleven (11) GSM messages, and the UE must distinguish whether
PSis or Sis are included. Thus, a RRC change request (CR) is needed, in order to remove
PSI/SI choice IE in HANDOVER FROM UTRAN COMMAND message, in addition to a
RANAP change request and a BSSGP change request.
FIG 5 shows a change to 3GPP TS 25.413, section 9.2.1, describing a target BSS to
source BSS transparent container, according to a second version of an embodiment of the
present invention.
FIG 6 shows another change to 3GPP TS 48.018, Table 11.3.80.a, describing a target
BSS to source BSS transparent container coding, according to the second solution of the
present invention. This information element contains the information needed in the Source
BSS to execute a PS handover, and the element coding is as shown in FIG 6. The SI/PSI
field contains a list of either system information or packet system information messages valid
for the reporting cell. The number of (packet) system information messages is indicated in the
Number of SI/PSI field specified above. Furthermore, if the Type field indicates that "SI
messages as specified for BCCH (3GPP TS 44.018) follow" then the SI/PSI field contains
System Information message instances encoded for BCCH as specified in 3GPP TS 44.018.
Each System Information message contains the Message type octet followed by all the IEs
composing the message payload. Each message is 21 octets long. If the Type field indicates
that "PSI messages as specified for PBCCH (3GPP TS 44.060) follow" then the SI/PSI field
contains Packet System Information message instances encoded for PBCCH as specified in
3GPP TS 44.060. Each Packet System Information message then contains the
MESSAGE_TYPE field followed by the PSI message content. Each message is 22 octets
long.
Turning now to FIG 7, a method 700 is shown according to an embodiment of the
8
WO 2007/036796 PCT/IB2006/002711
invention. An indication is provided 705 indicating whether or not SI/PSI is requested from a
PS handover target via transparent container. No such request is made ifthe SRNC is a
CRNC that implements RJM/NACC. lfthe indication requested the PSI/SI, then that is
received 720 in a target to source transparent container. A relocation command is received
725 with the SI/PSI. Then at least part of the contents of the target to source transparent
container is sent 730 to a user equipment (e.g. mobile device).
A system for implementing this type of method is shown in FIG 8. A source RNC
860 (e.g. an SRNC) includes a network element 845 which includes a transmitting module
870 and a receiving module 880. The source RNC sends an indication to a target BSS 850 as
to whether SI/PSI is requested. If so, the SI/PSI is provided from the target BSS 850 to the
source RNC 860. The source RNC then provides SI/PSI to a mobile device 800, which is
received by a receiving module 810 of the mobile device, and is stored in a memory 820.
Then a processor 840 can access that SI/PSI in order to have a transmitting device 830
perform handover signalling.
The embodiments described above can be implemented using a general purpose or
specific-use computer system, with standard operating system software conforming to the
method described herein. The software is designed to drive the operation of the particular
hardware of the system, and will be compatible with other system components and I/O
controllers. The computer system of this mobile device embodiment includes the CPU
. processor 840, comprising a single processing unit, multiple processing units capable of
parallel operation, or the CPU can be distributed across one or more processing units in one
or more locations, e.g., on a client and server. Memory 820 may comprise any known type of
data storage and/or transmission media, including magnetic media, optical media, random
access memory (RAM), read-only memory (ROM), a data cache, a data object, etc. Moreover,
similar to the CPU, the memory may reside at a single physical location, comprising one or
more types of data storage, or be distributed across a plurality of physical systems in various
forms. The computer system for the network element 845 has a similar description, as a
person skilled in the art will understand.
It is to be understood that the present figures, an~ the accompanying narrative
discussions of best mode embodiments, do not purport to be completely rigorous treatments
of the method, system, mobile device, and software product under consideration. A person
9
WO 2007/036796 PCT/IB2006/00271 l
skilled in the art will understand that the steps and signals of the present application represent
general cause-and-effect relationships that do not exclude intermediate interactions of various
types, and will further understand that the various steps and structures described in this
application can be implemented by a variety of different sequences and configurations, using
various different combinations of hardware and software which need not be further detailed
herein.
10
WO 2007/036796 PCT/IB2006/002711
1. A method comprising:
providing an indication whether a source radio network controller requests to
receive system information from a handover target; and
receiving the system information in a target to source transparent container, if
the indication requests to receive the system information.
4. The method of claim 1, wherein the target to source transparent container is sent
from a target radio network controller with a relocation command.
7. The method of claim 1, wherein the indication indicates that the source radio
network controller requests to not receive the system information from the handover
target, ifthe source radio network controller is a controlling radio network controller
that implements a radio access network information management procedure with
network assisted cell change.
11
WO 2007/036796 PCT/IB2006/002711
11. The software product of claim 10, wherein the system information includes
information required by a mobile station for a packet switched handover.
12. The software product of claim 10, wherein the indication is included in a source to
target transparent container.
13. The software product of claim 10, wherein the target to source transparent
container is sent from a target radio network controller with a relocation command.
14. The software product of claim 10, further comprising the function of sending to a
user equipment at least a part of what is received in the target to source transparent
container.
12
WO 2007/036796 PCT/IB2006/00271 l
16. The apparatus of claim 15, wherein the system information includes information
required by a mobile station for a packet switched handover.
17. The apparatus of claim 15, wherein the indication is included in a source to target
transparent container.
18. The apparatus of claim 15, wherein the target to source transparent container is
sent from a target radio network controller with a relocation command.
19. The apparatus of claim 15, further comprising means for sending to a user
equipment at least a part of what is received in the target to source transparent
container.
21. The network element of claim 20, wherein the system information includes
information required by a mobile station for a packet switched handover.
22. The network element of claim 20, wherein the indication is included in a source to
target transparent container.
13
WO 2007/036796 PCT/IB2006/00271 l
23. The network element of claim 20, wherein the target to source transparent
container from a target radio network controller conveys a relocation command.
24. The network element of claim 20, wherein the transmitting module is further
configured to send to a user equipment at least a part of what is received in the target
to source transparent container.
26. The system of claim 25, wherein the system information includes information
required by a mobile station for a packet switched handover.
28. The mobile device of claim 27, wherein the packet switched handover is a
handover to a different radio access technology.
14
WO 2007/036796 PCT/IB2006/002711
1/8
FIG.1
WO 2007/036796 PCT/IB2006/002711
2/8
FIG. 2
WO 2007/036796 PCT/IB2006/002711
3/8
8 I 7 l 6 J 5 l 4 ] 3l 2 l 1
Octet 1 !El
Octet2 2a Length Indicator
Octet 3-? Rest of element coded as a complete PS Handover Command
radio interface message as defined in 3GPP TS 44.060 (carrying
the PS Handover to A!Gb Mode Payloasfl
Octet ?+1- RAN-INFORMATION Application Container for the NACC
?? Application/11.3.63.2.1
FIG. 3
WO 2007/036796 PCT/IB2006/002711
4/8
8 I 7 l 6 I 5 I 4 1 3 l 2 l 1
Octet 1 IEI
Octet 2, 2a LeQg_th Indicator
Octet 3-10 ReportiQg_ Cell Identifier
Octet 11 Number of SI/PSI l ~e
Octet 12-n SI/PSI
FIG. 4a
Coding Semantic
0 SI messages as ~ecified for BCCHJ3GPP TS 44.01 ~follow
1 PSI mess~es as specified for PBCCHJ..3GPP TS 44.06Ql follow
FIG. 4b
Coding Semantic
000 0000 O "SI/PSI" follows
000 0001 1 "SI/PSI" follow
• "
1111111 127 "SI/PSI" follow
FIG. 4c
WO 2007/036796 PCT/IB2006/002711
5/8
FIG. 5
WO 2007/036796 PCT/IB2006/002711
6/8
8 1 7 1 6 l 5 1 4 l 3 1 2 J 1
Octet 1 IEI
Octet 2 2a Le1!9!h Indicator
Octet 3 Number of Containers
Octet 4-? Rest of element coded as a complete PS Handover Command
radio interface message as defined in 3GPP TS 44.060 (carrying
the PS Handover to NGb Mode PaJ!!.oad)
Octet ?+1- SI/PSI
??
FIG. 6
WO 2007/036796 PCT/IB2006/002711
7/8
70 5
•
Receiving SI/PSI in a target to source transparent container if indication
( requests it.
720
•
Receiving a relocation command with the SJJPSI.
(
725
FIG. 7 700
850 Target SSS Indication Whether SI/PSI is
Requested
Transparent Contains
870 -
QC)
QC)
Transmitting
Transmitting device Receiving module Having SI/PSI
810 800 Module
880
330 820
Receiving
Module
Processor Memory
"'C1
Network Element n
840 Mobile Device 845 Source RNC
-=
~
~
-
0
0
0-,
0
0
N
FIG 8
-.....l
i-
i-
INTERNATIONAL SEARCH REPORT International application No.
PCT/IBZ006/00Z711
A. CLASSIFICATION OF SUBJECT MATIER
Category* Citation of document, with indication, where appropriate, of the relevant passages Relevant to claim No.
--
A WO 0079808 AZ (TELEFONAKTIEBOLAGET LM ERICSSON 1-28
(PUBL)), 28 December 2000 (28.12.ZOOO),
abstract
--
-------- [jg
D Further documents are listed in the continuation of Box C. See patent family annex.
* Special categories of cited documents: "T" later document published after the international filing elate or priority
"A" document defining the general state of the art which is not considered elate and not in conflict with the application but cited to understand
to be of particUlar relevance the principle or theory underlying the invention
"E" earlier application or patent but published on or after the international
filing elate
·x· document of particular relevance: the claimed invention cannot be
considered novel or cannot be considered to involve an inventive
"L" document which may throw doubts on priority claim(s) or which is step when the document is taken alone
cited to establish the publication date of another citation or other
special reason (as specified) "Y" document of particular relevance: the claimed invention cannot be
·o· document referring to an oral disclosure, use, exhibition or other considered to involve an inventive step when the document is
combined with one or more other such documents, such combination
means
being obvious to a person skilled in the art
·p· document published prior to the international filing elate but later than
the priority elate claimed "&" document member of the same patent family
Date of the actual completion of the international search Date of mailing of the international search report
O IPR(s) contained within technical contributions made by the Declarant and/or its AFFILIATES, or
[gj any lPRs
the Declarant hereby irrevocably declares that (1) it and its AFFILIATES are prepared to grant irrevocable
licenses under its/their IPR(s) on terms and conditions which are in accordance with Clause 6. 1 of the ETSI
IPR Policy, in respect of the STANDARD(S), TECHNICAL SPECIFICATION(S), or the ETSI Project(s), as
identified above, to the extent that the IPR(s) are or become, and remain ESSENTIAL to practice that/those
STANDARD(S) or TECHNICAL SPECIFICATION(S) or, as applicable, any STANDARD or TECHNICAL
SPECIFICATION resulting from proposals or Work Items within the current scope of the above identified
ETSI Project(s), for the field of use of practice of such STANDARD or TECHNICAL SPECIFICATION ; and
(2) it will comply with Clause 6. 1bis of the ETSI IPR Policy with respect to such ESSENTIAL IPR (s) .
~ This irrevocable undertaking is made subject to the condition that those who seek licences agree to
reciprocate (check box if applicable) .
The construction, validity and performance of this General IPR licensing declaration shall be governed by the
laws of France.
Terms in ALL CAPS on this form have the meaning provided in Clause 15 of the ETSI IPR Policy.
SIGNATURE
By signing this General IPR Licensing Declaration form , you represent that you have the authority to bind the
Declarant and/or its AFFILIATES to the representations and commitments provided in this form .
Name of authorized person: David L. Cohen
Title of authorized person: Chief Legal and IP Officer
Place, Date: ~ew York USA, 20 August 2015
Signature:
SIGNATURE
By signing this IPR Information Statement and Licensing Declaration form, you represent that you have the
authority to bind the Declarant and/or its AFFILIATES to the representations and commitments provided in
this form.
Name of authorized person: David L. Cohen
Title of authorized person: Chief Legal and IP Officer
Place, Date: New York, N,.ew York USA; 20 August 2015
Signature:
fil-
Please return this form duly signed to: ETSI Director-Genera/
ETSI - 650, route des Lucio/es - F-06921 Sophia Antipolis Cedex - France I Fax. +33 (0) 4 93 65 47 16
Page 3 (version 9)
k. .
I STANDARD, TECHNICAL SPECIFICATION or
~ork
ETSI Wo'k ll•m
I lll~strative--1
1
Proprietor
I'
Application
No.
Publication
No.
PatenUApplication
Title
I
Country of
registration
FURTHER INFORMATION
Software 08
Product for JP 571 7820 i japan
3GPP KR 10- Korea
providing
LTE TS 10.2.2 VB.5.0 AP 2390 ARIPO 09992075
system 1286/ 2006 Pakistan
36.3 31
information to 9 5136469 Taiwan
enable packet us United St ates
switched 20070070949
hand over
us United States
20130003705
I
AP 2390 I ARIPO
3GPP Method , Device, CN 1012 78589 China P_R
LTE 8.10 , 11 .2.4 3 VB .3.0 AP 2390 ARIPO
TS System and EP1938648 EPO
-- ·--~---~ ..a.""""'" ~-- · ':'"~~--'IE»t;.'et~-------------'!!!"!11-------
Page 4 (version 9)
JP 5717820 I japan
providing KR 10· 1 Korea
system 1286/2006 09992075
information to 95136469 Pakistan
enable packet Taiwan l
switched us United States I
I
20070070949
handover us United States I
20130003705 I
---- J
I I
*Information on other members of a PATENT FAMILY is provided voluntarily (Clause 4.3 of the ETSI IPR Policy).
Please retum this form together with the "IPR Information Statement and Licensing Declaration form" to.
ETSI Director-General - ETSI - 650, route des Lucio/es - F-06921 Sophia Antipolis Cedex - France I Fax. +33 (0) 4 93 65 47 16
IPR online declaration service Page 1 of7
In accordance with the ETSI IPR Policy, Clause 4.1, I hereby inform ETSI that,
it is my belief that the IP Rs listed in the attached IPR information statement annex are, or are likely to become, Essential JPRs in relation to that Standard.
The SIGNATORY has notified ETSI that it is the proprietor of the IPRs listed in the attached JPR information statement annex and has informed ETSI that it believes that the IPRs may be
considered ESSENTIAL to the Standards listed above.
The SIGNATORY and/or its AFFILIATES hereby declare that they are prepared to grant irrevocable licences under the IPRs on terms and conditions which are in accordance with Clause 6.1 of
the ETSI IPR Policy, in respect of the STANDARD, to the extent that the IPRs remain ESSENTIAL.
This undertaking is made subject to the condition that those who seek licences agree to reciprocate same in respect of the STANDARD in accordance with Clause 6.1 of the ETSI IPR Policy
(delete this paragraph if this condition is not required).
The construction, validity and performance of this DECLARATION shall be governed by the Jaws of France.
Additional infonr-.ations:
00 1 f\ "'.IAAO
IPR online declaration service Page 2 of7
I. I ;UI
I
:.f'S
.Iv
2006139789
,l
281981
, Ire
PCT/IB04/001579
IpCT
16 I SOUTH AFRICA . ZA
I
I
or
2006139426
..
1273806
PCT/FI200S/000215 I Ire
47 I AFRICA ·ZA
25.413. 48.018:8a.5, 25.413:7.7.0,
48.018 11.3.80, 48.018:6.19.7
1 06808913.5
11.;J.::1oa IEPO
I
()O 1 {\ r"J(\()Q
IPR online declaration service Page 7 of7
TS 26.114 r -I
9.2.1 7.1.0 INokia - -- -- -- I
PCT/182007/0536
- -·
SYSTEM AND Patent 11/661216 IUNITED STATES - us
Corporation METHOD FOR Cooperation
I- I
I
PROVIDING Treaty
'_J
REDUNDANCY I
I MANAGEMENT I
I
I
UMTS 8.1.1.1.1,
I
f Nokia PCT/IB2008/0000 [ METHOD,
'
I
Patent
lj P080100082 ARGENTINA - AR
6.4.3.1, I Corporation SYSTEM, USER Cooperation l 0801000062 THAILAND - TH
8.6.7.19.7, ! EQUIPMENT, Treaty
l 96150300 TAIWAN, PROVINCE C
25.331 B.1.1.6.15.1a, 7.6.0 NETWORK CHINA-TW
8.1.1.6.15.3a,
6.6.7.19.7,
I I
ELEMENT AND
SOFTWARE
! 12/008703 UNITED STATES - US
10 ' PRODUCT FOR
I I GENERIC
I I
II BROADCASTED
I
I
I I
POSITIONING
ASSISTANCE
~DATA
i
I I
i
I , I I
--- ____,
I
-8.1.1.1.1, --- ~
s i Nokia PCT/EP2007/061
'I I PROVIDING IPatent 196140333
TAIWAN, PROVINCE C
25.331 10.2.48.8.18.0, 7.6.0 ICorporation AND USING Cooperation CHINA-TW
10.3.7.960 I MESSAGES
INCLUDING
Treaty ! 11/978212
i
UNITED STATES - US
I
II ' TIME RELATED
INFORMATION
I
I
I
= - ---
I
!
'
---- ! Enhanced
- I
I UNITED
JI - P080101076 ARGENTINA -AR
i· Quality I STATES 0801001280 THAILAND - TH
Reporting for 97109060 TAIWAN, PROVINCE C
I
Transmission
Sessions
I I PCT/EP 20081052702
CHINA-TW
Patent Cooperation Tre
I,~~~~~~~~~~P~C~T~~~~~-
NOKIA FIXED HS-DSCH OR E-DCH ALLOCATION FOR VOIP (OR WO06/114689 MY,TW,US,WO,BR,CN,EP,IN,
CORPORATION*7.10 HS-DSCH WITHOUT HS-SCCH/E-DCH WITHOUT E-DPCCH) JP,MX,PH,RU,ZA,KR,VN,AP
NOKIA METHOD, DEVICE, SYSTEM AND SOFTWARE PRODUCT FOR WO2007/0036796 PK,TW,US,WO,AP,CN,EP,IN,
CORPORATION*7.10 PROVIDING SYSTEM INFORMATION TO ENABLE PACKET JP,KR
SWITCHED HANDOVER
198