Browse Prior Art Database

Optimized Call Setup for Carrier Sharing

IP.com Disclosure Number: IPCOM000165491D
Original Publication Date: 2008-Jan-10
Included in the Prior Art Database: 2008-Jan-10
Document File: 3 page(s) / 128K

Publishing Venue

Siemens

Related People

Juergen Carstens: CONTACT

Abstract

3GPP is a worldwide cooperation for standardizing the mobile communication through UMTS and GMS technology (acronyms will be explained in the end of this test). There are many technical specification groups such as the "Technical Specification Group Radio Access Network" (TR 25.999). In the specification "TR 25.999 HSPA evolution" (version 2.2.0 and higher) a carrier sharing solution is defined, where the evolved HSPA Node B is connected to the RNC via Iur (see Fig. 1). Iur is an interface located on a UMTS network that can be found between two RNCs. In case of the packet switched service, only RAN supports Iu-CS signaling in a dedicated carrier scenario. In TR 25.999 it is described how the RRC connected terminal is relocated to RNC (using SRNS relocation).

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 51% of the total text.

Page 1 of 3

Optimized Call Setup for Carrier Sharing

Idea: Tuomo Flytström, FI-Espoo; Petri Jäppilä, FI-Espoo

3GPP is a worldwide cooperation for standardizing the mobile communication through UMTS and GMS technology (acronyms will be explained in the end of this test). There are many technical specification groups such as the "Technical Specification Group Radio Access Network" (TR 25.999). In the specification "TR 25.999 HSPA evolution" (version 2.2.0 and higher) a carrier sharing solution is defined, where the evolved HSPA Node B is connected to the RNC via Iur (see Fig. 1). Iur is an interface located on a UMTS network that can be found between two RNCs. In case of the packet switched service, only RAN supports Iu-CS signaling in a dedicated carrier scenario. In TR 25.999 it is described how the RRC connected terminal is relocated to RNC (using SRNS relocation).

The problem is that the current solution creates both SRNS relocation towards the core network and additional messages between different network elements (evolved Node B, RNC, MSC). It is not possible to send a RRC Connection Reject in RRC Connection set up, so the connection has to be created to that same cell (see Fig. 2). To achieve this, the current solution requires that RRC connection is created to the evolved HSPA Node B and SRNS relocation is needed as described in TR 25.999.

In the...