Section: 8.2.2 Handling ASN.1/PER encoded parameters
Content: During the TAU/RAU/HO procedures MME/S4-SGSN GTPv2 entities send some of the RANAP/S1AP/BSSGP parameters to a GTPv2 peer. Copying of the BSSGP parameters into GTPv2 IEs is straightforward. RANAP and S1AP, however, use ASN.1/PER encoding, which is different from GTPv2 specific TLV encoding. Transparent copying of RANAP/S1AP parameters across GTPv2 interfaces: a GTPv2 entity shall transparently copy the respective information into one or more octets of the GTPv2 IE as specified in Annex B and clause 8.48. With this approach, GTPv2 will not be impacted if the contents of such RANAP/S1AP parameter changes over the time. Non-transparent copying of RANAP/S1AP parameters across GTPv2 interfaces: - GTPv2 entity decodes ASN.1/PER parameter and shall encode the value(s) into one or more octets of the GTPv2 IE according to what is specified in the present document.