mirror of https://gerrit.osmocom.org/libosmocore
Pau Espin
3278f0fb3c
Once the IuUP FSM moved away from Init state, it stopped handling Initialization messages received from peers and simply ignored them starting from that point. As a result, if the first IuUP Init ACK it sent to the peer was lost, the peer would keep retrying with more IuUP Init and getting no answer. In any case, it seems possible and desirable that a peer may send an IuUP Init at a later point, as pointed out vaguely in 3GPP TS 25.415. sec 6.5.2.1: """ Upon reception of a frame indicating that an Initialisation procedure is active in the peer Iu UP entity, the Iu UP protocol layer forwards the whole protocol information contained in the INITIALISATION control frame to the upper layers. It also stores the RAB sub-Flow Combination set (and thus replaces a possible previous set) in order to control during the transfer of user data, that the Iu UP payload is correctly formatted (e.g. RFCI matches the expected Iu UP frame payload total length). The peer Iu UP entity receiving the INITIALISATION control frame shall choose a version that it supports among the proposed versions indicated by the sender for which it has enough initialisation information. """ sec B.2.2 "Initialisation State": """ After sending a positive acknowledgement of the last INITIALISATION control frame, the Iu UP instance enters SMpSDU data transfer ready state. Note that CN does not know if the initialisation ACK was correctly received by the RNC (and Initialisation procedure successfully completed) until it receives RAB assignment response, or use data from the RNC. The CN must therefore be able to continue receiving INITIALISATION control frames by re-entering the Initialisation state (from Support Mode Data Transfer Ready State), if the CN has started to send user data before receiving the indication that Initialisation was successfully completed """ sec B.2.3 "Support Mode Data Transfer Ready State": """ In case of handover or relocation, Initialisation procedures may have to be performed and Iu UP instance may have to enter the initialisation state. """ Related: SYS#5995 Change-Id: I5cb740702805693cc7f0a550e2e093f9bfdd507c |
||
|---|---|---|
| .. | ||
| kdf | ||
| milenage | ||
| Makefile.am | ||
| a5.c | ||
| abis_nm.c | ||
| apn.c | ||
| auth_comp128v1.c | ||
| auth_comp128v23.c | ||
| auth_core.c | ||
| auth_milenage.c | ||
| auth_xor.c | ||
| bsslap.c | ||
| bssmap_le.c | ||
| bts_features.c | ||
| cbsp.c | ||
| comp128.c | ||
| comp128v23.c | ||
| gad.c | ||
| gan.c | ||
| gea.c | ||
| gprs_cipher_core.c | ||
| gprs_gea.c | ||
| gprs_rlc.c | ||
| gsm48.c | ||
| gsm48_arfcn_range_encode.c | ||
| gsm48_ie.c | ||
| gsm48_rest_octets.c | ||
| gsm0341.c | ||
| gsm0411_smc.c | ||
| gsm0411_smr.c | ||
| gsm0411_utils.c | ||
| gsm0414.c | ||
| gsm0480.c | ||
| gsm0502.c | ||
| gsm0808.c | ||
| gsm0808_utils.c | ||
| gsm23003.c | ||
| gsm23236.c | ||
| gsm29118.c | ||
| gsm29205.c | ||
| gsm48049.c | ||
| gsm_04_08_gprs.c | ||
| gsm_utils.c | ||
| gsup.c | ||
| gsup_sms.c | ||
| i460_mux.c | ||
| ipa.c | ||
| iuup.c | ||
| kasumi.c | ||
| kdf.c | ||
| lapd_core.c | ||
| lapdm.c | ||
| libosmogsm.map | ||
| mncc.c | ||
| oap.c | ||
| oap_client.c | ||
| rsl.c | ||
| rxlev_stat.c | ||
| sysinfo.c | ||
| tlv_parser.c | ||