Method for renewing sharing network zone information in wireless network controller

Abstract

The method includes steps: (1) based on ITI message cell to construct ITI message; (2) querying whether there is information of sharing network area (SNA) in core network (CN); if no, then information of SNA id, which is in use for denoting that SNA information is not configured in CN or SNA information is already deleted, is carried in ITI message; and the ITI message is sent to radio network controller (RNC); (3) when receiving information of SNA id carried in ITI message, RNC deletes SNA information already existed in local, and does not carry out access control for UE. The method guarantees that: sending ITI message successfully; keeping consistence between SNA information stored in RNC and SNA information stored in CN side; keeping consistence between access control for UE by RNC and requirement of current network.

Description

technical field [0001] The invention relates to user terminal (UE) access technology, especially a method for updating shared network area (SNA) information in a radio network controller (RNC). Background technique [0002] figure 1 It is a schematic diagram of the interconnection and sharing between the core network (CN) and the access network between different operators, from figure 1 It can be seen that the radio access networks of operator 1 and operator 2 have an overlapping area, and this overlapping area is called SNA. An SNA is an area that corresponds to one or more Local Areas (LAs), such as figure 1 As shown in , the SNA includes both a part of the LA of the radio access network 1 (RAN1) and a part of the LA of the RAN2. Then, when the UE is located in the SNA, the UE can access both RAN1 and RAN2. At this time, how to control the access of the UE is a problem. [0003] In order to solve this problem, it is stipulated in the 3rd Generation Alliance Project (3G...

AI Technical Summary

Problems solved by technology

[0018] But, if in step 201, the coding of SNA information has failed, so, ITI message can not be successfully sent to RNC, promptly this message sends and can fail, and this moment, RNC is stored in the local SNA information and can not get updating, The SNA information stored in the RNC is inconsistent with the SNA information stored in the SGSN / MSC, resulting in inconsistent access control of the UE by the RNC and network requirements

[0019] Judging from the methods of updating SNA information in the RNC in the prior art, when sending an ITI message, regardless of whether the SNA information is saved in the SGSN / MSC, the SNA information must be encoded, and if no SNA information is configured or the SNA information has been When deleting, due to the non-existence of the encoding object, the encoding will fail, resulting in the failure of sending the ITI message, thus causing the local SNA information stored by the RNC to not be updated, so that the SNA information stored in the RNC is different from that stored in the SGSN / MSC. The SNA information is inconsistent, which eventually leads to the inconsistency between the RNC's access control to the UE and the current network requirements

Images