WCDMA RAN Protocols and Procedures  Chapter 8  Iu Interface - RANAP Protocol

WCDMA RAN Protocols and Procedures Chapter 8 Iu Interface - RANAP Protocol PowerPoint PPT Presentation


  • 1089 Views
  • Uploaded on
  • Presentation posted in: General

Objectives of Chapter 8, Iu Interface - RANAP Protocol. RADIO ACCESS NETWORK APPLICATION PART (RANAP)PROTOCOL---INTRODUCTION---. The Iu interface connects WCDMA RAN to the Core Network. The Radio Access Network Application Part (RANAP) protocol is used over the Iu interface RANAP carries Non-Access Stratum (NAS) messages, which are relayed between the CN nodes and the Ues. The Iu interface is divided into two instances: * the Iu Circuit Switched (CS) to connect WCDM33533

Download Presentation

WCDMA RAN Protocols and Procedures Chapter 8 Iu Interface - RANAP Protocol

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


1. WCDMA RAN Protocols and Procedures Chapter 8 Iu Interface - RANAP Protocol In this chapter we will look at the considerations that must be taken into account when planning a CDMA network.In this chapter we will look at the considerations that must be taken into account when planning a CDMA network.

2. Objectives of Chapter 8, Iu Interface - RANAP Protocol

7. RANAP signaling over the lu interface (figure 8-3)

19. Iu Connections between RNC and the Core Network (figure 8-10)

27. Class 1 EPs with response (table 8-1)

28. Class 2 EPs without response (figure 8-2)

29. Class 3 EPs with possibility of multiple responses (figure 8-3)

32. RANAP Procedures for Mobile Terminated call

33. Paging

34. Paging Paging is used by the CN to page a UE This procedure uses connectionless signaling The PAGING message includes: Permanent NAS UE Identity (i.e. IMSI) for calculation of paging group and also for WCDMA RAN paging co-ordination. * paging coordination means that if a Radio Resource Control (RRC) connection already exists for this UE, the radio-interface paging-message will be sent via this RRC connection instead of via the broadcast paging channel. The DRX Cycle Length Coefficient (if available) may be included in the Paging message, which used for calculating the paging occasions for the UE. Temporary UE ID (that is, the TMSI). Used over the paging channel. If TMSI is not included the RNC shall use the Permanent NAS UE Identity instead, Paging Cause shall indicate the reason for sending the paging message. Non Searching Indication. If set to non-searching, the RNC does not need to do WCDMA RAN paging co-ordination. Paging Area. Can be the LAI, RAI and (if omitted) the whole RNC area.

35. Initial UE Message (figure 8-11)

36. Initial UE Message The Initial UE Message procedure is used to establish an Iu signaling connection between a CN domain and the RNC. This procedure uses connection oriented signaling. The SRNC sends a SSCP Connect Request (CR) message to the CN. The SCCP Connection Request message carries the RANAP Initial UE message. The Initial UE Message carries the NAS messages with the establishment cause, the UE identity and the current location, on cell level of the UE. The SRNC receives confirmation that the signaling connection has been setup by a SCCP Connection Confirm (CC) message. The SCCP CC message may include a RANAP message, for example “Common Id”

37. Common ID (figure 8-11)

38. Common ID The Common ID procedure informs the RNC about the permanent NAS UE Identity (i.e. IMSI). This procedure uses connection oriented signaling. The permanent NAS UE Identity is tied to the RRC connection and is used at Paging to check if an RRC connection already exists for this UE; That is WCDMA RAN paging co-ordination. The WCDMA RAN also needs the permanent NAS UE Identity from this message in order to be able to calculate the paging group in case of WCDMA RAN initiated paging.

39. Direct Transfer (figure 8-11)

40. Direct Transfer The Direct Transfer procedure is used to transfer NAS information between the CN and the RNC or vice versa. This procedure uses connection oriented signaling. Besides NAS-PDU for the NAS information, this message also includes SAPI for indicating the priority of the message. SAPI 0 for high priority and SAPI 3 for low priority (SMS). Only used downlink. LAI + RAC. Needed in connection with Routing Area Update. Only used towards the PS domain. In this specific case Direct Transfer is used for Authentication and Ciphering Request and Response.

41. Security Mode Control (figure 8-11)

42. Security Mode Control The Security Mode Control procedure is used by the CN to pass cipher and integrity protection information to the WCDMA RAN. This procedure uses connection oriented signaling. Messages If WCDMA RAN can support the requested ciphering and integrity protection, the message SECURITY MODE COMPLETE is returned. Otherwise the message SECURITY MODE REJECT with an appropriate cause value is returned.

43. Security Mode Control continued In case a UE has RABs towards both the PS and CS CNs (not supported), the following is valid: User data for RABs towards CS are ciphered with the ciphering key received from the CS domain. User data for RABs towards PS are ciphered with the ciphering key received from the PS domain. Signaling data is ciphered and integrity protected with the latest received keys.

44. RAB Assignment (figure 8-11)

45. RAB Assignment The RAB Assignment procedure is used to establish one or more new RABs for a given UE and/or to modify or release already existing RABs. This procedure uses connection oriented signaling. The RAB Establishment consists of two parts: Iu bearer setup between the CN and the SRNC. Radio Bearer Setup between the UE and the SRNC. The RAB ASSIGNMENT REQUEST message contains: list of RABs to establish with their bearer characteristics list of RABs to modify with their bearer characteristics list of RABs to release

46. RAB Assignment continued Upon reception of RAB ASSIGNMENT REQUEST, the WCDMA RAN executes the requested configuration. The result is reported to CN in one or more RAB(s) ASSIGNMENT RESPONSE messages. The first of these messages contains: successfully established RABs successfully modified RABs released RABs RABs failed to establish, modify or release queued RABs

47. RAB Assignment continued The subsequent messages are used for reporting the outcome of the queued RABs. (The procedure is not completed until all RABs have been reported.) The following outcomes are possible: successfully established or modified failed to establish or modify failed to establish due to timer expiry

48. Some information elements (IEs) included in RAB Assignment Request For RABs to be setup or modified:

49. Some information elements (IEs) included in RAB Assignment Request For RABs to be released:

50. Some information elements (IEs) included in RAB Assignment Response For RABs to be setup or modified: For RABs failed to setup or modified:

51. Some information elements (IEs) included in RAB Assignment Response For RABs released: For RABs failed to release:

52. Some information elements (IEs) included in RAB Assignment Response For RABs queued:

53. Iu Release (figure 8-11)

54. Iu Release (figure 8-12) The Iu Release procedure is used to release an Iu connection and all WCDMA RAN resources related to that Iu connection. This procedure uses connection oriented signaling. Any RABs still existing for the UE will also be released.

55. Iu Release Request This procedure is used by WCDMA RAN to ask the CN to initiate the release of an Iu connection. This procedure uses connection oriented signalling. The CN can follow the request and initiate the Iu Release procedure. It can, however, also choose to take some other action, including ignoring the request.

  • Login