2 * Retained (E2M->E2T issue) - retrying when is_Ready flag in socket handle is false
5 * Restart/Start of RM, fetch E2T data from E2manager - implementation in RM for v1/e2t/list API handling
8 * Corrected route table syntax in case of broadcast message
11 * Added debug API to request route and configuration details in routing manager
14 * Added code for subscription merge and added RMR from xapp-framework
17 * Temporary Fix for R3 (E2M->E2T issue) - retrying when is_Ready flag in socket handle is false
20 * Entry in meid map will only contain the delta change
23 * Check DNS lookup for E2T address, RED Button and KEEP alive message routes added for new E2T Address
26 * Static platform routes can be configured via configuration file
29 * Multiple E2T instance Feature: Introduced APIs Delete E2T Instance, associate RANs to E2T and disassociate RANs from E2T Instance.
32 * Create E2T Instance API introduced for Multiple E2T Feature
35 * Included RMR changes that has MEID implementation
38 * Added Routes when AC-xApp is deployed
39 * included xapp-framework. Using only config and Logger module for now.
42 * Fixed integration and subscription routes related issues for R3
45 * Added RSM platform component routes for message types RAN_CONNECTED, RAN_RESTARTED, RAN_RECONFIGURED, RIC_RES_STATUS_REQ,RIC_RES_STATUS_RESP and RIC_RES_STATUS_FAILURE
46 * xApp manager interface changes for Subscription Request API
49 * Adding docs and updating release notes for routing manager
52 * Fix routes for RIC_ENDC_X2_SETUP_REQ, RIC_ENDC_X2_SETUP_RESP and RIC_ENDC_X2_SETUP_FAILURE
55 * Routing Manager is more resilient to missing components
56 * Put in order the message types
59 * Added platform route to send RIC_SCTP_CLEAR_ALL message to implement big red button.
60 * Added E2_TERM_INIT and RIC_SCTP_CONNECTION_FAILURE message type routes.
63 * The following tools made available in the final docker image: iputils-ping, net-tools, curl and tcpdump
66 * Introduced delete API over REST interface for subscriptions.
69 * Minor code changes due to appmgr/rtmgr api differences
74 * Removed "rte" route types and made all routes to construct of "mse" literal.
77 * Introduced platform-specific routes: basic components (e2term, ueman, subman, e2man) are stored in a json file (example in manifests/rtmgr/rtmgr-cfg.yaml)
78 * Introduced subscription add functionality: /ric/v1/xapp-subscriptions endpoint is active, on a POST method it generates endpoint specific mse routing table entries
81 * Introduced http rest functionality
82 * A way to get intial xapp data from xapp manager while booting the routing manager
83 * A way to create a sinple webhook registration in the xapp-manager to listen on updates abpout changes in xapps
86 * Changes in swagger API definition
87 * UTs for SBI, SDL and RPE modules
88 * New message types according to RMR
91 * Introduces NNGPush SBI module
92 * Bugfixes in argument handling
93 * different RMR policy generator for Push and Pub communication
96 * RMR Policy Engine has been refactored to handle receiving groups properly
97 * Debugging feature has been added
99 * A complex JSON file has been added to xApp Manager to test new behavior
102 * RTMGR (Routing Manager) implementation in Golang
103 * Updated project folder structure
104 * Integration manifests
107 * Initial version of Routing Manager for CI/CD pipeline
108 * Dummy solution: still has no real routing capability
109 * Container is based on the _**tx**_ version of [admin xApp] which already implements [RMR library]