Section: 4.2.7.1 N2 Configuration
Content: At power up, restart and when modifications are applied, the 5G-AN node and AMF use non-UE related N2 signalling to exchange configuration data. Full details of this configuration data are specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ]  [10], but the following highlights some aspects. The AMF supplies the 5G-AN node with information about: a) the AMF Name and the GUAMI(s) configured on that AMF Name; b) the set of TNL associations to be established between the NG-RAN node and the AMF; c) weight factor associated with each of the TNL association within the AMF; and d) weight factor for each AMF Name within the AMF Set; and e) (optional) for each GUAMI(s) configured on that AMF the corresponding backup AMF Name. The weight factors are used for load distribution of the initial N2 messages. The AMF chooses whether or not to use the same TNL association for the initial N2 message and subsequent messages for that UE. TNL associations configured with a weight factor set to zero are not permitted for the initial N2 message, but can be used for subsequent N2 messages. Deployments that rely solely on 5GC-based load balancing can set the weight factors associated with TNL associations that are permitted for the initial N2 message to the same value. The 5G-AN supplies over N2 the AMF with information about the Tracking Area(s) it serves and the S-NSSAI(s) it supports in each of these Tracking Areas. See clause 5.3.2.3 of TS 23.501[ System architecture for the 5G System (5GS) ]  [2].