7 Commits
Author SHA1 Message Date
Robert Schmidt 4c2bfe7a1f F1AP: send() functions take assoc_id
To allow to send F1 messages to multiple DUs from the CU, we need to
send these messages via different assoc_id (SCTP association ID,
basically akin to a file descriptor). Currently, the assoc_id is stored
in a context at the F1 module and retrieved in
f1ap_itti_send_sctp_data_req().

To facilitate a later change towards indicating (from the RRC) to which
assoc_id (hence, DU) to send a message, we refactor all
CU_send_*()/DU_send_*() functions to take the assoc_id as a parameter to
which to send messages. In this commit, we then pass the assoc_id from
the context. A later commit changes this (at the CU) to pass the
assoc_id from the message to be sent.
2023-11-08 10:18:52 +01:00
Robert Schmidt 3f46a71157 SCTP assoc_id: Make it sctp_assoc_t, project-wide 2023-09-22 08:22:15 +02:00
Laurent THOMAS 6ce958f7ed Coarse grain cleanup: a lot of errors fixed 2021-07-03 16:32:20 +02:00
Navid Nikaein 942d92cf7c send msg 4 in F1 DL RRC message transfer 2018-09-16 16:36:45 +02:00
Robert Schmidt f4633ba260 Correctly add headers for RRC message transfer, remove warnings 2018-09-14 17:16:04 +02:00
Bing-Kai Hong ef1627fac7 INITIAL_UL_RRC_MESSAGE at DU and CU respectively is developped 2018-09-13 19:55:01 +02:00
Bing-Kai Hong f736213d09 Update F1AP new code structure to closer implementing all the procedures 2018-09-13 16:25:51 +02:00