Skip to content

Commit

Permalink
Merge pull request #161 from ruiqizhu-ricky/main
Browse files Browse the repository at this point in the history
fixed links in design docs of AUSF and SMF
  • Loading branch information
ianchen0119 authored Sep 18, 2024
2 parents fe79c4c + 7afd553 commit 360f423
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions docs/doc/Ausf/design.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ When the AUSF (Authentication Server Function) is initiated within a 5G network,
![Alt text](EAP-AKA.png)
> Authentication procedure for EAP-AKA, described in *3GPP TS 33.501 clause 6.1.3.1*
The EAP-AKA' authentication sequence unfolds as follows, correlating with the sequence diagram above which is depicted in [TS33.501](6.1.3.1)
The EAP-AKA' authentication sequence unfolds as follows, correlating with the sequence diagram above which is depicted in [TS33.501](https://www.tech-invite.com/3m33/toc/tinv-3gpp-33-501_h.html#e-6-1-3-1)

- **Authentication Vector (AV) Creation:** Initiated by the UDM/ARPF generating a tailored AV.
- **AV Transmission to AUSF:** The AV is sent to the AUSF, signaling readiness for authentication.
Expand All @@ -39,7 +39,7 @@ When the AUSF (Authentication Server Function) is initiated within a 5G network,
![Alt text](5GAKA_Authentication_Procedure.png)
> Authentication procedure for 5G AKA , described in *3GPP TS 33.501 clause 6.1.3.2*
The authentication procedure unfolds as follows, aligned with the flow above which is depicted in [TS33.501](6.1.3.2)
The authentication procedure unfolds as follows, aligned with the flow above which is depicted in [TS33.501](https://www.tech-invite.com/3m33/toc/tinv-3gpp-33-501_h.html#e-6-1-3-2)

- **Authentication Vector (AV) Creation:** The UDM/ARPF generates a 5G AV, initiating the process.
- **AV Transmission to AUSF:** The AV is dispatched to the AUSF to begin the authentication challenge.
Expand Down
4 changes: 2 additions & 2 deletions docs/doc/Smf/design.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,9 +34,9 @@ When SMF is started, several software functionalities related to PFCP are activa
2. [3-2] ***PDU Session :***
- (1) **Release** : When the Service Management Function (SMF) receives a PDU Session Release SMContext Request from the Access and Mobility Management Function (Possible scenarios include: AMF changes, an invalid SUPI from the UE, or the UE registering repetitively with the same AMF, etc.), The SMF will send an PFCP Session Deletion Request towards the User Plane Function (UPF) to release resources associated with this session.

- (2) **Update** : When the Service Management Function (SMF) receives a PDU Session Update SMContext Request from the Access and Mobility Management Function for updating N3 tunnel information (Possible scenarios include: EPS to 5GS handover [TS23.502](4.11.1.2.2.2), etc.), The SMF will send an PFCP Session Modification Request towards the User Plane Function (UPF) to update resources associated with this session.
- (2) **Update** : When the Service Management Function (SMF) receives a PDU Session Update SMContext Request from the Access and Mobility Management Function for updating N3 tunnel information (Possible scenarios include: EPS to 5GS handover [TS23.502](https://www.tech-invite.com/3m23/toc/tinv-3gpp-23-502_zf.html#e-4-11-1-2-2-2), etc.), The SMF will send an PFCP Session Modification Request towards the User Plane Function (UPF) to update resources associated with this session.

- (3) **Post** : When the Service Management Function (SMF) receives a PDU Session Create SMContext Request from the Access and Mobility Management Function (Possible scenarios include: UE Requested PDU Session Establishment), The SMF will send an PFCP Session Establishment Request towards the User Plane Function (UPF). If the SMF received Nsmf_PDUSession_CreateSMContext Request and the SMF is able to process the PDU Session establishment request, the SMF creates an SM context and responds to the AMF by providing an SM Context Identifier. [TS23.502](4.3.2.2)
- (3) **Post** : When the Service Management Function (SMF) receives a PDU Session Create SMContext Request from the Access and Mobility Management Function (Possible scenarios include: UE Requested PDU Session Establishment), The SMF will send an PFCP Session Establishment Request towards the User Plane Function (UPF). If the SMF received Nsmf_PDUSession_CreateSMContext Request and the SMF is able to process the PDU Session establishment request, the SMF creates an SM context and responds to the AMF by providing an SM Context Identifier. [TS23.502](https://www.tech-invite.com/3m23/toc/tinv-3gpp-23-502_m.html#e-4-3-2-2)

3. [3-3] ***ULCL Procedure*** :
- The insertion of ULCL (Uplink Control Channel) in 5G networks serves the purpose of facilitating the transmission of control information during uplink data transfer. ULCL enables the network to transmit control signals and indications during uplink transmission, effectively managing and controlling the allocation and scheduling of wireless resources. This includes transmitting scheduling information, establishing and releasing connections, modulation and coding information, among others, to ensure efficient control and management of uplink data transmission from user equipment.
Expand Down

0 comments on commit 360f423

Please sign in to comment.