- 23 May, 2024 18 commits
-
-
Guido Casati authored
Bugfix issue with copy F1 network config to SCTP introduced in 76ea8181
-
Guido Casati authored
-
Guido Casati authored
-
Guido Casati authored
-
Guido Casati authored
-
Guido Casati authored
-
Guido Casati authored
* moved F1AP related docs to a separate folder in docs
-
Guido Casati authored
-
Guido Casati authored
-
Guido Casati authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
Add a new target f1ap_lib that groups F1AP ASN.1 encoding&decoding for messages defined f1ap_messages_types.h. The objective is to, for each F1AP message, - add encoder&decoder (similar to what already exists, but without mandatory message sending afterwards) - eq_X() function that checks two messages for equality (to be used mostly in tests) - cp_X() function that deep-copies a message, e.g., to be used when sending ITTI messages, instead of manual copying done currently - free_X() function that frees the memory associated to a memory, to avoid memory leaks. Each message will be tested, notably that encoding&decoding as well as copying yield identical messages. The actual message encoding & decoding, tests, and their use will be done in the forthcoming commits.
-
Robert Schmidt authored
-
Robert Schmidt authored
The currently used type does not cover all possibilities. While we don't encode&decode them, it might still be good to be able to express it, so introduce the new type.
-
Robert Schmidt authored
-
Robert Schmidt authored
teid_t is defined in platfrom_types.h, which defines a bunch of 4G-specific things. In an attempt to decouple from 4G types, do not use it.
-
Robert Schmidt authored
The previously used net_ip_address_t type is limited to some bytes, but the CU name might be longer. Use char * to allow longer DNS names. Also, this type separates IPv4/v6, which is not necessary, as it is now handled by the same C API (getaddrinfo()), since !2635.
-
- 22 May, 2024 5 commits
-
-
Robert Schmidt authored
Integration: `2024.w21` See merge request oai/openairinterface5g!2746 * !2717 Additional check on pucch_Config and srs_Config * !2730 Fix for SSB index in function get_nr_prach_info_from_ssb_index * !2734 add a function to reset the transmission timestamps chain * !2741 Fix several potential segfaults in UE PUCCH tx power determination.
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
- 21 May, 2024 2 commits
-
-
Raphael Defosseux authored
Signed-off-by:
Raphael Defosseux <raphael.defosseux@eurecom.fr>
-
Jaroslava Fiedlerova authored
-
- 20 May, 2024 1 commit
-
-
Bartosz Podrygajlo authored
-
- 16 May, 2024 2 commits
-
-
francescomani authored
-
Robert Schmidt authored
uper_encode_to_buffer() of asn1c returns the number of BITS that have been encoded; if we use this, we need to calculate the resulting number of bytes (rounding up) to get the right buffer size. Note that do_NR_ULInformationTransfer() uses uper_encode_to_new_buffer() which returns the number of BYTES, hence, in this similar function, we should not modify the return value.
-
- 15 May, 2024 1 commit
-
-
laurent authored
add a function to reset the transmission timestamps chain, and use it in context of UE resynchronization
-
- 07 May, 2024 1 commit
-
-
Robert Schmidt authored
Integration `2024.w18` See merge request oai/openairinterface5g!2713 * !2705 Fix CRC check in UE DCI detection * !2708 Adding few more NR bands to the list of supported ones * !2701 gNB archi fixes * !2203 DL-MMSE * !2684 remove asserts on min RX/TX, set the RX/TX shift as 2 in the UE * !2594 F1AP refactoring to align with O-RAN.WG5.C.1-v11
-
- 06 May, 2024 10 commits
-
-
Guido Casati authored
-
Jaroslava Fiedlerova authored
-
Jaroslava Fiedlerova authored
-
Robert Schmidt authored
Taking the example of the AMF Set ID, the previous version of the macro used another macro to encode the number, then marked the last 6 bits in the bit string (of length 16/2 bytes) as unused. This is wrong, because, assuming AMF Set ID=3, it basically truncates the number by encoding all 16 bits and cutting off the last 6, like this: ------------------- encode 16 bits 0000 0000 0000 0011 ------------ take these 10 bits So what remains is these bit positions of the number: (16,15,14,13,12,11,10,9,8,7) -- the last 6 bits are cut (and the first 6 are either 0 or garbage, because they don't exist). Instead, manually encode bits (10,9,8,7,6,5,4,3) in the first byte, and (2,1) in the second byte of the bit string, like so: ------------ encode 10 bits 0000 0000 1100 0000 ------------ take these 10 bits Do the same with the pointer. The AMF Region ID above is correct, as it is exactly 8 bits.
-
Robert Schmidt authored
We can optionally indicate the PDU session IDs. At least with OAI 5GC, that should help it clean up.
-
Robert Schmidt authored
In the case of PDU sessions in the NG UE context setup request, we first have to set up security. Hence, in this commit, implement the "delayed" set up of theses PDU sessions, and acknowledge the setup request after reconfiguration, as requested by O-RAN.WG5.C.1-v11.
-
Robert Schmidt authored
Trigger UE ctxt setup response for the case of "registration request" (no PDU sessions in UE Context setup response), as mandated by O-RAN.WG5.C.1-v11.
-
Robert Schmidt authored
As of this commit, since we now send the UE security command as a DL NAS message, there is no F1 UE Context setup request. Hence, instead of sending a UE context modif request, send the UE context setup request after the E1 bearer setup response (which logically also makes more sense, as the E1 setup procedure comes before the F1 setup procedure).
-
Robert Schmidt authored
This reverts commit 0f100a6e, which introduced a hack to possibly wait with a PDU session setup at the RRC in case a RRC UE capability transaction (requesting UE capabilities from a UE) was ongoing. This happened, as we delayed the UE capabilities to after the first RRC reconfiguration; in that case, certain UEs were requesting the next PDU session, and if RRC did not delay the new PDU session (as requested from the core), this procedure might occur while UE capability enquiry was ongoing, leading to failures in these transactions.
-
Robert Schmidt authored
The default RRC reconfiguration was previously sent after the security mode command as a "first" RRC reconfiguration. However, it is simply not needed, as it will be triggered through a subsequent reconfiguration that also sets up DRBs. Move the Measurement Config to the "other/dedicated" RRC reconfiguration. This reconfiguration would have forwarded a NAS PDU (typically a registration accept). This is now done by a dedicated forwarding of NAS.
-