An error occurred fetching the project authors.
  1. 30 Jan, 2025 6 commits
    • Guido Casati's avatar
      Limit scope of NAS functions (static) · f73579ea
      Guido Casati authored
      f73579ea
    • Guido Casati's avatar
      Refactor includes in nr_nas_msg (.c/.h) · ddad26ef
      Guido Casati authored
      ddad26ef
    • Guido Casati's avatar
      Refactor NAS 5GS message type definitions · 27ed2373
      Guido Casati authored
      * move defines to openair3/NAS/NR_UE/nr_nas_msg.h as they are
        only used in nr_nas_msg.c
      * made naming of all message types consistent, using the same
        prefix for all
      27ed2373
    • Guido Casati's avatar
      Remove NAS/COMMON/nr_common.c and move servingNetworkName to nr_nas_msg.c · fb85ba7d
      Guido Casati authored
      * the only function used from nr_common.c is servingNetworkName which is
        used in nr_nas_msg.c, so it was moved to the latter file and its scope
        was reduced
      fb85ba7d
    • Guido Casati's avatar
      Refactor NAS 5GS (5GMM & 5GSM) structs definitions and their use · 03a4d8ef
      Guido Casati authored
      Every NAS 5GS message can have 3 different headers: (1) security protected
      (2) 5GMM plain (3) 5GS plain;
      
      According to 3GPP TS 24.501:
      > 4.2 Coordination between the protocols for 5GS mobility management and 5GS session management
      > A 5GS session management (5GSM) message is piggybacked in specific 5GS mobility management (5GMM) transport
      > messages. To this purpose, the 5GSM messages can be transmitted in an information element in the 5GMM transport
      > messages.
      
      A PDU Session Establishment accept is a 5GSM message and as such it is contained in a 5GMM
      transport message. The code in capture_pdu_session_establishment_accept_msg is reflecting this.
      The message is thus expected to have: (1) Security protected 5GMM header (2) Plain 5GMM message
      (3) 5GSM Payload Container (4) Plain 5GSM message.
      
      5.4.5 of 3GPP TS 24.501: also says:
      
      > The type of the payload is identified by the Payload container type IE and includes one of the following: a) a single 5GSM message;
      
      Thus, a 5GSM is not the only possible payload of a NAS transport message.
      
      This commit is focusing on the refactoring of the structs definitions and adaptation of the CMakeLists.
      
      Based on the above:
      
      * Move NR_NAS_defs.h to 5GS subfolder in NR_UE
      * Move NAS FGS structs and definitions to NR_NAS_defs.h
      * Rename mm_msg_header_t to fgmm_msg_header_t
      * Remove duplicated NAS struct definitions
        (1) kept fgs_nas_message_security_header_t over security_protected_nas_5gs_msg_t
        (2) Kept fgsm_msg_header_t over fgs_sm_nas_msg_header_t
      * Remove unused definitions, structs, functions in the process
      03a4d8ef
    • Guido Casati's avatar
      Migrated NAS 5GS (5GMM & 5GSM) to NR folders and refactor CMakeLists.txt files · c0583be2
      Guido Casati authored
      This commit is introducing the following macro changes:
      
      (1) Migrate NAS 5GS lib files to a new 5GS subfolder in NR_UE
          and organize NAS 5GS lib messages into 5GMM and 5GSM subfolders.
          A nested CMake structure was implemented and CMakeLists.txt were
          added whenever necessary. This is effectively separating 5GS
          libraries from LTE libraries.
      
      (2) In order to simplify the separation of 5GS libs from LTE libs,
          remaining dependencies from NAS LTE (e.g. nas_ue_task.c, ue-idx-standalone)
          were removed in the process
      
      (3) ExtendedProtocolDiscriminator.c/.h and SpareHalfOctet.c/.h were deleted
          and affected types were replaced with simple integer types
      
      (4) Cleanup: unused definitions and libs (e.g. LIB_5GNAS_GNB)
          were removed
      
      (5) Update doc/Doxyfile
      
      (6) clang-formatted the migrated files in the process
      
      (7) Update includes of headers in affected files
      c0583be2
  2. 08 Jan, 2025 7 commits
  3. 10 Dec, 2024 4 commits
  4. 09 Dec, 2024 1 commit
  5. 08 Dec, 2024 1 commit
    • Robert Schmidt's avatar
      Merge remote-tracking branch 'origin/fhi-f-release' into integration_2024_w49 (!3147) · 0b3d0986
      Robert Schmidt authored
      Fronthaul xran library update to F release (2. and final step towards M-plane integration)
      
      - xran library support -> both E and F releases
      - RU delay profile removed -> not used in neither of the releases
      - DU delay profile updated
      - one-way delay measurements support is improved/fixed in the F release.
        However, not implemented here as it depends on the RU capabilities
      0b3d0986
  6. 06 Dec, 2024 5 commits
  7. 05 Dec, 2024 16 commits