A2.2.2 Rules for Configuration

25.4013GPPRelease 17TSUTRAN overall description

There are some limitations for configuring network when the extended RNC-ID scheme is used. The network configuration shall follow all four rules as stated below together.

Explanation of terms

Legacy RNC/CN: RNC/CN do not comprehend/support the extended RNC-ID IE/Scheme, e.g. Pre-Rel7 RNC/CN.

Upgraded RNC/CN: RNC/CN comprehend/support the extended RNC-ID IE/Scheme and can distinguish which RNC-ID scheme are used in the received message or sending message based on the stored configuration data.

Rule1):

In case relocation needs to be supported to/from an RNC using the extended RNC-ID, it is recommended to connect the source and target RNCs to the same upgraded CN to reduce the number of upgraded CN. In case CN cannot be upgraded, it is recommended to use legacy RNC-ID under that CN. (Example in Figure A2.2.2.1).

Rule2):

Not configure the Iur interface connection between legacy RNC and upgraded RNC using the extended RNC-ID.

Rule3):

In case RNCs with legacy RNC-ID and RNCs with extended RNC-ID co-exist in the network, configure the legacy RNC-ID so that legacy RNC-ID will not be the same as the 12 bit of MSB of any of extended RNC-ID to which the legacy RNC may have Iur connection. (See the Figure A2.2.2.3 and A2.2.2.4).

Rule4):

In case a URA spanned over multiple RNCs with extended RNC-ID and the RNCs have different capability on HS-DSCH reception in URA_PCH state, the RNCs capable of HS-DSCH reception in URA_PCH state shall not have the same 12bit MSB in their extended RNC-ID compared to the RNCs not capable of HS-DSCH reception in URA_PCH. (See Figures A2.2.2.5 and A2.2.2.6).

Depiction of Configuration Rules

Figure A2.2.2.1: Configuration example for Rule 1 and 2

Figure A2.2.2.2: Configuration example for Rule 1 and 2.

Figure A2.2.2.3: Problematic configuration example
(does not follow Rule3)

Figure A2.2.2.4: Configuration example for Rule3

Figure A2.2.2.5 Problematic configuration example (does not follow Rule4)

Figure A2.2.2.6 Configuration example for Rule4