Requirements

• There is a new RMR Message Type (12001) for Setup Request from RAN (dedicated to E2 Setup)
• Parse it - although E2T will include all the payload in XML (It will decode the ASN.1), we are reading the following:
• The MEID - this is a long string concatenation of - "<Antenna type><MCC ID><MNC-ID>-<Node ID>" where Antenna type is any one of the 

>Macro eNB ID
>Home eNB ID
>Short Macro eNB ID
>Long Macro eNB ID

and <MCC ID>-<MNC-ID> is actualy the PLMN.

Example - Ran name = gnb:310-410-b5c67788

• E2T Instance ID (can be IP or any other Address) take from Adi
• (In the body there will be the XML of the payload, which is again the gNb but as numbers, and the functions, but in this US we will not have any logic on the XML).
• If can't Parse - Log Error
• Send to Routing Manager (Like in R3): associate E2T to this RAN. In this flow we ALWAYS succeed. If fail - Log Error.
• Log the Incoming RMR Message.

See attached mail from Adi

Acceptance

• Simulate Setup from RAN with Node X (PLMN area M,N) sending it to E2T Y.
• See RMR E2 Setup Request arrives
• See associate-ran-to-e2t with the RAN Name is sent to RM
• See the Log contains everything - E2T Address, RAN Name, maybe IP PORT, XML - Functions and RAN ID
  *