The E1AP Setup Request contained the network configuration (IP address, ports) as well as the actual E1AP Setup Request application data (Supported PLMNs, ...). This has the drawbacks that - The E1AP Setup Request is stored to retrieve IP addresses in the E1AP module, which is confusing as the Setup Request, per standard, has no IP info - The CU-CP received an E1 Setup Request for configuration during start up, but it did not actually receive such Setup Request, but merely the IP configuration to set up the socket This commit splits the E1AP Setup Request into a "real" Setup Request for application data, and creates a new type e1ap_net_config_t to group all IP configuration data. Further, a new ITTI message type E1AP_REGISTER_REQ is introduced to group both types. What happens is - RCconfig_NR_CU_E1() reads both E1AP application-level data and IP configuration, as previously - The data is sent to the CU-CP. It discards the E1AP Setup Request data, and only uses the network configuration to set up the socket - The data is sent to the CU-UP. It uses the network configuration to connect to the CU-CP, and then sends the E1AP Setup Request to the CU-CP. Currently, the CU-CP still stores the Setup Request locally, which will be changed in the next commit to send it to the RRC.
37 lines
1.8 KiB
C
37 lines
1.8 KiB
C
/*
|
|
* Licensed to the OpenAirInterface (OAI) Software Alliance under one or more
|
|
* contributor license agreements. See the NOTICE file distributed with
|
|
* this work for additional information regarding copyright ownership.
|
|
* The OpenAirInterface Software Alliance licenses this file to You under
|
|
* the OAI Public License, Version 1.1 (the "License"); you may not use this file
|
|
* except in compliance with the License.
|
|
* You may obtain a copy of the License at
|
|
*
|
|
* http://www.openairinterface.org/?page_id=698
|
|
*
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
* See the License for the specific language governing permissions and
|
|
* limitations under the License.
|
|
*-------------------------------------------------------------------------------
|
|
* For more information about the OpenAirInterface (OAI) Software Alliance:
|
|
* contact@openairinterface.org
|
|
*/
|
|
|
|
/* gNB_CUUP application layer -> E1AP messages */
|
|
MESSAGE_DEF(E1AP_REGISTER_REQ, MESSAGE_PRIORITY_MED, e1ap_register_req_t, e1ap_register_req)
|
|
|
|
/* E1AP messages -> RRC (CU-CP) */
|
|
MESSAGE_DEF(E1AP_SETUP_REQ , MESSAGE_PRIORITY_MED , e1ap_setup_req_t , e1ap_setup_req)
|
|
|
|
/* E1AP -> eNB_DU or eNB_CU_RRC -> E1AP application layer messages */
|
|
MESSAGE_DEF(E1AP_SETUP_RESP , MESSAGE_PRIORITY_MED, e1ap_setup_resp_t , e1ap_setup_resp)
|
|
|
|
MESSAGE_DEF(E1AP_BEARER_CONTEXT_SETUP_REQ , MESSAGE_PRIORITY_MED , e1ap_bearer_setup_req_t , e1ap_bearer_setup_req)
|
|
|
|
MESSAGE_DEF(E1AP_BEARER_CONTEXT_SETUP_RESP , MESSAGE_PRIORITY_MED , e1ap_bearer_setup_resp_t , e1ap_bearer_setup_resp)
|
|
|
|
MESSAGE_DEF(E1AP_BEARER_CONTEXT_MODIFICATION_REQ , MESSAGE_PRIORITY_MED , e1ap_bearer_setup_req_t , e1ap_bearer_mod_req)
|
|
|