本帖最后由 爱卫生 于 2011-3-20 20:50 编辑
5)When resources for the transmission of user data between target RNC and new SGSN have been allocated and the new SGSN is ready for relocation of SRNS, the Forward Relocation Response (Cause, RAN Transparent Container, RANAP Cause, Target-RNC Information) message is sent from the new SGSN to the old SGSN. This message indicates that the target RNC is ready to receive from source SRNC the forwarded downlink PDUs, i.e., the relocation resource allocation procedure is terminated successfully. RAN transparent container and RANAP Cause are information from the target RNC to be forwarded to the source SRNC. The Target RNC Information, one information element for each RAB to be set up, contains the RNC Tunnel Endpoint Identifier and RNC IP address for data forwarding from the source SRNC to the target RNC. The Forward Relocation Response message is applicable only in case of inter-SGSN SRNS relocation. 5)当在目标RNC和new SGSN之间已经为用户数据的传输分配好了资源并且new SGSN已经准备好了SRNS的重选,转发重选响应(原因,RAN传输容器,RANAP原因,目标RNC信息)消息将从new SGSN发给old SGSN。这个消息指示目标RNC已经准备好从源SRNC接收转发的下行PDU,换句话说为重选的资源分配流程已经成功终结。RAN传输容器和RANAP原因是从目标RNC来的信息,转发给源SRNC。目标RNC信息,是对每一个要建立的RAB的信息元素,包含了RNC TEID和从源SRNC到目标RNC的用于数据转发的RNC IP地址。转发重选响应消息只适用于inter-SGSN SRNS重选。
6)The old SGSN continues the relocation of SRNS by sending a Relocation Command message (Target RNC To Source RNC Transparent Container, RABs To Be Released, RABs Subject To Data Forwarding) to the source SRNC. The old SGSN decides the RABs to be subject for data forwarding based on QoS, and those RABs shall be contained in RABs subject to data forwarding. For each RAB subject to data forwarding, the information element shall contain RAB ID, Transport Layer Address, and Iu Transport Association. These are the same Transport Layer Address and Iu Transport Association that the target RNC had sent to new SGSN in Relocation Request Acknowledge message, and these are used for forwarding of downlink N‑DU from the source SRNC to the target RNC. The source SRNC is now ready to forward downlink user data directly to the target RNC over the Iu interface. This forwarding is performed for downlink user data only. 6)old SGSN继续SRNS的重选,发送重选命令消息(目标RNC到源RNC传输容器,需要释放的RAB,需要数据前转的RAB)给源SRNC。old SGSN根据QOS决定需要数据前转的RAB,并且那些RAB应包含在“需要数据前转的RAB"字段里)。对于需要数据前转的每一个RAB,信息元素里应包含RAB ID,传输层地址以及Iu传输关联。这些参数是和目标RNC发送给new SGSN的重选请求确认消息里包含的传输层地址和Iu传输关联是一样的,这些参数用于从源SRNC到目标RNC的下行N-PDU的数据转发。源SRNC现在已经准备好在Iu接口上直接转发下行用户数据给目标RNC。这个转发只针对用户数据。
7)The source SRNC may, according to the QoS profile, begins the forwarding of data for the RABs to be subject for data forwarding. 7)源SRNC可以,根据QOS profile,开始为RAB转发需要前转的数据报文。 NOTE 3:注释3
The order of steps, starting from step 7 onwards, does not necessarily reflect the order of events. For instance, source RNC may start data forwarding (step 7), send the RRC message to MS (step 8) and forward SRNS Context message to the old SGSN (step 9) almost simultaneously. 步骤的顺序,从步骤7往前,并不必须的反应事件的顺序。例如,步骤7的源RNC可以开始数据转发和第8步中的发送RRC消息给MS以及第9步中转发SRNS上下文消息给old SGSN差不多是同时的。
The data forwarding at SRNS relocation shall be carried out through the Iu interface, meaning that the GTP-PDUs exchanged between the source SRNC and the target RNC are duplicated in the source SRNC and routed at the IP layer towards the target RNC. For each radio bearer which uses lossless PDCP the GTP-PDUs related to transmitted but not yet acknowledged PDCP-PDUs are duplicated and routed at IP layer towards the target RNC together with their related downlink PDCP sequence numbers. The source RNC continues transmitting duplicates of downlink data and receiving uplink data. 在SRNS重选发生的数据转发应通过Iu接口承载,意味着在源SRNC和目标RNC之间交换的GTP-PDU,在源SRNC是重复的并且通过IP层路由发给目标RNC。对于每个使用了无损PDCP的无线承载,传输的GTP-PDU但还没有确认的PDCP-PDU是重复的并且和它们相关的下行PDCP序列号一起通过IP层路由发到目标RNC。源RNC继续传输复制的下行数据以及接收的上行数据。
Before the serving RNC role is not yet taken over by target RNC and when downlink user plane data starts to arrive to target RNC, the target RNC may buffer or discard arriving downlink GTP-PDUs according to the related QoS profile.
在服务RNC的角色还没有由目标RNC承担起来之前,并且下行用户平面数据已经开始到达目标RNC,则目标RNC可以根据它们相关的QOS profile缓存或丢弃到达的下行GTP-PDU。
8)Before sending the RRC message the uplink and downlink data transfer shall be suspended in the source SRNC for RABs, which require delivery order. The RRC message is for example Physical Channel Reconfiguration for RNS to RNS relocation, or Intersystem to UTRAN Handover for BSS to RNS relocation, or Handover from UTRAN Command for BSS relocation, or Handover Command for BSS to BSS relocation. When the source SRNC is ready, the source RNC shall trigger the execution of relocation of SRNS by sending to the MS the RRC message provided in the Target RNC to source RNC transparent container, e.g., a Physical Channel Reconfiguration (UE Information Elements, CN Information Elements) message. UE Information Elements include among others new SRNC identity and S‑RNTI. CN Information Elements contain among others Location Area Identification and Routeing Area Identification.8)在发送RRC消息之前,为要求顺序传递的RAB的上下行的数据传输应在SRNC上挂起。RRC消息举例来说是一个物理信道重配置消息,为了RNS到RNS重选的,或系统间改变到UTRAN切换从BSS到RNS重选,或为了BSS重选从UTRAN命令的切换,或为了BSS到BSS重选的切换命令。当服务SRNC准备好后,源RNC应通过发送给MS一个在目标RNC到源RNC透明容器的RRC消息,来触发SRNS重选的执行。例如一个物理信道重配置(UE信息元素,CN信息元素)消息。UE信息元素包括新的SRNC ID和S-RNTI。CN信息元素包含了LAI和RAI。
When the MS has reconfigured itself, it sends an RRC message e.g., a Physical Channel Reconfiguration Complete message to the target SRNC. If the Forward SRNS Context message with the sequence numbers is received, the exchange of packets with the MS may start. If this message is not yet received, the target RNC may start the packet transfer for all RABs, which do not require maintaining the delivery order.
当MS重配置了它自己,它发送一个RRC消息例如物理信道重配置完成消息给目标RNC。如果带有序列号的转发SRNS上下文消息收到,和MS的数据包交换就可以开始。如果消息仍没收到,目标RNC可以开始为所有RAB的数据包转发,并不要求保持分发顺序。
9)The source SRNC continues the execution of relocation of SRNS by sending a Forward SRNS Context (RAB Contexts) message to the target RNC via the old and the new SGSN. The Forward SRNS Context message is acknowledged by a Forward SRNS Context Acknowledge message, from new to old SGSN. The purpose of this procedure is to transfer SRNS contexts from the source RNC to the target RNC, and to move the SRNS role from the source RNC to the target RNC. SRNS contexts are sent for each concerned RAB and contain the sequence numbers of the GTP PDUs next to be transmitted in the uplink and downlink directions and the next PDCP sequence numbers that would have been used to send and receive data from the MS. PDCP sequence numbers are only sent by the source RNC for the radio bearers which used lossless PDCP (see TS 25.323 [57]). The use of lossless PDCP is selected by the RNC when the radio bearer is set up or reconfigured. 9)源SRNC继续SRNS重选的执行,通过old和new SGSN发送转发SRNS上下文(RAB上下文)消息给目标RNC。转发SRNS上下文消息通过转发SRNS上下文确认消息进行确认,从new到old SGSN。这个流程的目的是从源RNC传递SRNS上下文给目标RNC,并且将SRNS的角色从源RNC迁移到目标RNC。SRNS上下文为每个关联的RAB发送并且包含了下一个在上下行方向要传递的GTP PDU的序列号,以及下一个将用于从MS发送和接收数据的PDCP序列号。PDCP序列号仅在使用了无损PDCP的无线承载时,由源RNC发送。无损PDCP的使用,是由RNC在无线承载建立或重配置的时候选择的。
When using Gn/Gp, for PDP context(s) using delivery order not required (QoS profile), the sequence numbers of the GTP-PDUs next to be transmitted are not used by the target RNC.
当使用Gn/Gp,对于根据QOS profile不要求有序分发的PDP上下文,目标RNC不使用下一个将要传输的GTP-PDU的序列号。
When using Gn/Gp, if delivery order is required (QoS profile), consecutive GTP-PDU sequence numbering shall be maintained throughout the lifetime of the PDP context(s). Therefore, during the entire SRNS relocation procedure for the PDP context(s) using delivery order required (QoS profile), the responsible GTP-U entities (RNCs and GGSN) shall assign consecutive GTP-PDU sequence numbers to user packets belonging to the same PDP context uplink and downlink, respectively. 当使用Gn/Gp,对于要求有序分发的PDP上下文,连贯的GTP-PDU序列编号应在PDP上下文的整个生命周期内保持。因此,在有有序分发要求的PDP上下文的整个的SRNS重选流程时,负责GTP-U的实体(RNC和GGSN)应分配连贯的GTP-PDU序列号给属于相同PDP上下文上下行用户数据。
The target RNC establishes and/or restarts the RLC and exchanges the PDCP sequence numbers (PDCP‑SNU, PDCP‑SND) between the target RNC and the MS. PDCP‑SND is the PDCP sequence number for the next expected in-sequence downlink packet to be received by the MS per radio bearer, which used lossless PDCP in the source RNC. PDCP‑SND confirms all mobile terminated packets successfully transferred before the SRNC relocation. If PDCP‑SND confirms reception of packets that were forwarded from the source SRNC, then the target SRNC shall discard these packets. PDCP‑SNU is the PDCP sequence number for the next expected in-sequence uplink packet to be received in the RNC per radio bearer, which used lossless PDCP in the source RNC. PDCP‑SNU confirms all mobile originated packets successfully transferred before the SRNC relocation. If PDCP‑SNU confirms reception of packets that were received in the source SRNC, the MS shall discard these packets. 目标SRNC建立并且/或重启RLC,在目标SRNC和MS之间交换PDCP序列号(PDCP-SNU,PDCP-SND).PDCP-SND是一个用于每一个在源RNC中使用了无损PDCP的无线承载中标识下一个期望从MS接收的序列中的下行数据的序列号。PDCP-SND确认所有终止于手机的包成功的在SRNC重选的时候传递。如果PDCP-SND确认数据包的接收从源SRNC转发过来了,目标SRNC应丢弃这些数据包。PDCP-SNU是一个用于每一个在源RNC中使用了无损PDCP的无线承载中标识下一个期望从MS接收的序列中的上行数据的序列号。PDCP-SNU确认所有手机发起的数据包在SRNC重选之前成功的传递。如果PDCP-SNY确认这些包已经由源SRNC接收,MS应丢弃这些包。
10)The target RNC shall send a Relocation Detect message to the new SGSN when the relocation execution trigger is received. For SRNS relocation type "UE Involved", the relocation execution trigger may be received from the Uu interface; i.e., when target RNC detects the MS on the lower layers. When the Relocation Detect message is sent, the target RNC shall start SRNC operation. 10)目标RNC当收到重选执行触发时,应发送重选检测消息给new SGSN。对于SRNS重选类型为"UE不参与",重选执行触发可以从Uu接口接收,那就是,当目标RNC检测到MS在低层协议栈。当重选检测消息发送后,目标RNC应开始SRNC操作。
11)When the target SRNC receives the appropriate RRC message, e.g. Physical Channel Reconfiguration Complete message or the Radio Bearer Release Complete message in UTRAN case, or the Handover To UTRAN Complete message or Handover Complete message in GERAN case, i.e. the new SRNC‑ID + S‑RNTI are successfully exchanged with the MS by the radio protocols, the target SRNC shall initiate a Relocation Complete procedure by sending the Relocation Complete message to the new SGSN. The purpose of the Relocation Complete procedure is to indicate by the target SRNC the completion of the relocation of the SRNS to the CN. 11)当目标SRNC收到了合适的RRC消息,例如物理通道重配置完成消息或无线承载释放完成消息(在UTRAN的场景里),或切换到UTRAN完成消息或切换完成消息(在GERAN场景里),也就是new SRNC-ID + S-RNTI成功的通过无线协议和MS完成交互,目标SRNC应发起一个重选完成流程,通过发送重选完成消息给new SGSN。重选完成流程的目的是指示目标SRNC,SRNS的重选到核心网已经完成。
12)Upon receipt of Relocation Complete message, if the SRNS Relocation is an inter SGSN SRNS relocation, the new SGSN signals to the old SGSN the completion of the SRNS relocation procedure by sending a Forward Relocation Complete message. 12)一旦接收到重选完成消息,如果SRNS重选是一个inter-SGSN SRNS重选,new SGSN通过发送一个转发重选完成消息,告诉old SGSN关于SRNS重选流程已经完成。
13)Upon receipt of the Relocation Complete message, the CN shall switch the user plane from the source RNC to the target SRNC. If the SRNS Relocation is an inter-SGSN SRNS relocation or if Direct Tunnel was established in intra-SGSN SRNS relocation, the new SGSN sends Update PDP Context Request messages (new SGSN Address, SGSN Tunnel Endpoint Identifier, QoS Negotiated, Negotiated Evolved ARP, serving network identity, CGI/SAI, User CSG Information, RAT type, MS Info Change Reporting support indication, NRSN, DTI) to the GGSNs concerned. The SGSN shall send the serving network identity to the GGSN. If Direct Tunnel is established the SGSN provides to GGSN the RNC's Address for User Plane and TEID for Downlink data and shall include the DTI to instruct the GGSN to apply Direct Tunnel specific error handling procedure as described in clause 13.8. NRSN indicates SGSN support of the network requested bearer control. The inclusion of the Negotiated Evolved ARP IE indicates that the SGSN supports the Evolved ARP feature. If the new SGSN did not receive a Negotiated Evolved ARP IE in the SGSN Forward Relocation Request message from the old SGSN then the new SGSN shall derive this value from the Allocation/Retention Priority of the QoS profile negotiated according to Annex E of TS 23.401 [89].
13)一旦接收到重选完成消息,CN应将用户平面从源RNC切换到目标SRNC。如果SRNS重选是一个inter-SGSN SRNS重选或者直接隧道在一个intra-SGSN SRNS重选流程中建立,new SGSN发送更新PDP上下文请求消息(new SGSN地址,SGSN TEID,协商的QOS,协商的演进ARP,服务网络ID,CGI/SAI,用户CSG信息,RAT类型,MS信息变化报告支持指示,NRSN,DTI)给关联的GGSN.SGSN应发送服务网络ID给GGSN。如果直接隧道建立,SGSN给GGSN提供RNC用户平面地址和TEID用于下行数据并且并包含DTI来指示GGSN应应用直接隧道,错误处理流程在章节13.8描述。NRSN指示SGSN支持网络请求的承载控制.协商的演进ARP IE指示SGSN支持演进的ARP特性.如果new SGSN没有从old SGSN过来的转发重选请求消息中收到协商的演进ARP 信息元素,那么new SGSN应从协商的QOS profile的分配/保持优先级中获取这个值,这在TS23.401的附录E描述。 The GGSNs update their PDP context fields and return an Update PDP Context Response (GGSN Tunnel Endpoint Identifier, Prohibit Payload Compression, APN Restriction, MS Info Change Reporting Action, CSG Information Reporting Action, BCM, Negotiated Evolved ARP) message. The GGSN sets the Negotiated Evolved ARP based on local policy or PCC. The Allocation/Retention Priority of the QoS Profile Negotiated is derived from the Evolved ARP according to the mapping principles of TS 23.401 [89], Annex E. The Prohibit Payload Compression indicates that the SGSN should negotiate no data compression for this PDP context. The SGSN shall apply the Negotiated Evolved ARP if received from the GGSN. GGSN更新它的PDP上下文字段并返回一个更新PDP上下文响应(GGSN TEID,禁止payload压缩,APN限制,MS信息变更报告行动,CSG信息报告行动,BCM,协商的演进ARP)消息。GGSN根据本地策略或PCC来设置协商的演进ARP.从协商的QOS profile的分配/保持优先级中获取这个值,这在TS23.401的附录E描述。禁止payload压缩指示SGSN应为这个PDP上下文协商无数据压缩。SGSN如果从GGSN收到了,则应应用这个协商的演进ARP。
14)Upon receiving the Relocation Complete message or, if it is an inter-SGSN SRNS relocation, the Forward Relocation Complete message, the old SGSN sends an Iu Release Command message to the source RNC. When the RNC data-forwarding timer has expired, the source RNC responds with an Iu Release Complete message. 14)一旦接收到重选完成消息,或,如果这是一个inter-SGSN SRNS重选,转发重选完成消息,old SGSN发送Iu释放命令消息给源RNC。当RNC数据转发计时器超时,源RNC响应一个Iu释放完成消息。
An old S4-SGSN starts a timer to supervise when resources in old Serving GW (in case of Serving GW change or in case of S4 to Gn/Gp SGSN change) shall be released. When this timer expires the old S4-SGSN releases the S‑GW resources. The old S4-SGSN deletes S-GW bearer resources by sending Delete Session Request (Cause, Operation Indication) messages to the SGW. If ISR is activated the Cause indicates that the old S-GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message to the other CN node. The Operation Indication flag is not set by the old S4-SGSN. This indicates to the S-GW that the S‑GW shall not initiate a delete procedure towards the PDN GW. 一个old S4-SGSN启动一个计时器来监管old SGW(例如在SGW变化或S4到Gn/Gp SGSN变化的场景里)的资源应该被释放。当这个计时器超时,old S4-SGSN释放SGW的资源。Old S4-SGSN发送删除会话请求(原因,操作指示)消息给SGW来删除SGW的承载资源。如果ISR激活了,则原因指示old SGW应删除在其他CN节点的承载资源----通过发送删除承载请求消息给其他CN节点。操作指示flag不由old S4-SGSN设置。这将指示SGW,SGW不应发起到PGW的删除流程。
15)After the MS has finished the reconfiguration procedure and if the new Routeing Area Identification is different from the old one, the MS initiates the Routeing Area Update procedure. See clause "Location Management Procedures (Iu mode)". Note that it is only a subset of the RA update procedure that is performed, since the MS is in PMM‑CONNECTED state. 15)在MS完成了重配置流程后,如果new RAI和之前老的不同,MS发起RAU流程。注意,这个RAU流程只是正常RAU流程的一个子集,因为MS已经处于PMM-CONNECTED状态。
The new SGSN shall determine the Maximum APN restriction based on the received APN Restriction of each PDP context/EPS Bearer Context for using S4 from the GGSN/P‑GW or old S4-SGSN for using S4 and then store the new Maximum APN restriction value. new SGSN应根据使用S4的GGSN/PGW或old S4-SGSN收到的每个PDP上下文/EPS承载上下文的APN限制,来决定最大的APN限制,并存储为新的最大APN限制值。
|