hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.4.2 Ppinserver_ASRegistration_Request operation
| API operation name: Ppinserver_ASRegistration_Request
Description: The consumer requests to register the AS on the PIN server.
Inputs: See clause 8.8.3.4.
Outputs: See clause 8.8.3.5.
See clause 8.8.2.3 for details of usage of this operation.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.4.3 Ppinserver_ASRegistration_Update operation
| API operation name: Ppinserver_ASRegistration_Update
Description: The consumer requests to update the registered information of the AS on the PIN server.
Inputs: See clause 8.8.3.6.
Outputs: See clause 8.8.3.7.
See clause 8.8.2.4 for details of usage of this operation.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.4.4.4 Ppinserver_ASRegistration_Deregister operation
| API operation name: Ppinserver_ASRegistration_Deregister
Description: The consumer requests to deregister the AS from the PIN server.
Inputs: See clause 8.8.3.8.
Outputs: See clause 8.8.3.9.
See clause 8.8.2.5 for details of usage of this operation.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9 Service Continuity
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.1 General
| PIN service continuity procedures enable an Application Client participating in a PIN to maintain service when PIN Elements enter or leave the PIN. The following examples illustrate scenarios where PIN service continuity is needed.
In a first scenario, a first PIN Element (e.g. a UE) receives data from a second PIN E... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.2 Procedure
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.2.1 Service continuity in PEGC relocation scenario
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.2.1.1 General
| Following procedures are supported for service continuity in a PEGC relocation scenario:
- PIN Management PEGC Service Continuity procedure;
- PIN Management PEGC Configuration procedure;
- PIN Configuration Service Continuity Update procedure;
- PIN Management PEGC Discovery procedure;
- PIN Service Continuity s... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.2.1.2 PIN Management PEGC Service Continuity procedure
| Pre-conditions:
1. PIN Element has an application session that goes through a PIN Gateway Client; and
2. PIN Gateway Client needs to be replaced (e.g., PEGC will become unavailable or PEGC is unreachable).
Figure 8.9.2.1.2-1: PIN PEGC Service Continuity procedure
1. The PIN Gateway Client or the PIN Client sends ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 2 Upon receiving the request, the PIN Management Client validates the request and checks if the request is authorized for the given PIN Client(s), PIN Gateway Client and service. If the request is authorized and valid, the PIN Management Client determines if a target PIN Gateway Client meets the requirements for handli... | If the PIN Management Client identifes a target PIN Gateway Client that meets the requirements, the PIN Management Client sends PIN Management PEGC Configuration request to the target PIN Gateway Client to configure the target PIN Gateway for handling service traffic from the PIN Client(s) as in clause 8.9.2.1.3. If th... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.2.1.3 PIN Management PEGC Configuration procedure
| Pre-conditions:
1. The PIN Management Client has received a PIN Management PEGC Service Continuity request; and
2. The PIN Management client has identified a target PIN Gateway Client.
Figure 8.9.2.1.3-1: PIN Management PEGC Configuration procedure
1. The PIN Management Client sends a PIN Management PEGC Configur... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.2.1.4 PIN Configuration Service Continuity Update procedure
| The PIN Configuration Service Continuity Update procedure allows the PEMC to inform the PIN Server about a service continuity request received at the PEMC for a PINE, and it allows the PIN Server to inform the related AS of the same if such functionality is supported by the AS.
The PIN Server may provide, in the resp... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.2.1.5 PIN Management PEGC Discovery procedure
| PEMC performs PIN Management PEGC discovery procedure to discover which PEGC are available at the PINE when the PEMC does not have that information; for example, the PEMC may ignore if a PEGC is available at the PINE or PEGC information may not have been provided to the PEMC in the service provisioning request.
Pre-co... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.2.1.6 PIN Service Continuity subscription
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.2.1.6.1 General
| The PIN service continuity subscription is used by the Application Server to be notified of PIN service continuity events by the PIN Server.
The PIN service continuity notification includes PIN service continuity information.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.2.1.6.2 Procedure
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.2.1.6.2.1 PIN service continuity subscribe
| Figure 8.9.2.1.6.2.1-1 illustrates the PIN service continuity subscribe procedure.
Pre-conditions:
1. The application server has already received the address of the PIN server;
2. The application server is authorized to communicate with PIN server;
Figure 8.9.2.1.6.2.1-1: PIN service continuity subscribe
1. The... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.2.1.6.2.2 PIN service continuity notify
| Figure 8.9.2.1.6.2.2-1 illustrates the PIN service continuity notify procedure.
Pre-conditions:
1. The application server has subscribed with the PIN server as specified in clause 8.9.2.1.6.2.1.
Figure 8.9.2.1.6.2.2-1: PIN service continuity notify procedure
1. When a service continuity event occurs at the PIN s... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.2.1.6.2.3 PIN service continuity update
| Figure 8.9.2.1.6.2.3-1 illustrates the PIN service continuity update procedure.
Pre-conditions:
1. The application server has subscribed with the PIN server as specified in clause 8.9.2.1.6.2.1.
Figure 8.9.2.1.6.2.3-1: PIN service continuity update
1. The application server sends a PIN service continuity update r... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.2.1.6.2.4 PIN service continuity unsubscribe
| Figure 8.9.2.1.6.2.4-1 illustrates the PIN service continuity unsubscribe procedure.
Pre-conditions:
1. The application server has subscribed with the PIN server as specified in clause 8.9.2.1.6.2.1.
Figure 8.9.2.1.6.2.4-1: PIN service continuity unsubscribe
1. The application server sends a PIN service continuit... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.2.2 Service continuity in changing access to 5GS
| This procedure solves the situation, that PINE 1 has application layer communication with PINE 2 via PEGC 1. But when the communication via PEGC 1 is not viable, for example, the PINE 2 moves out of the coverage of PEGC 1, only PINE 2 triggers to establish the 5GS communication to connect to PINE 1 via PEGC 2is the pot... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3 Information flows
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3.1 General
| The following information flows are specified for Service Continuity:
- PIN Management PEGC Service Continuity request and response
- PIN Management PEGC Configuration request and response
- PIN Configuration Service Continuity Update request and response
- PIN Management PEGC Discovery request and response
- PIN ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3.2 PIN Management PEGC Service Continuity request
| Table 8.9.3.2-1 describes information elements for the PIN Management PEGC Service Continuity request that is sent from the PIN Gateway client to the PIN Management client.
Table 8.9.3.2-1: PIN Management PEGC Service Continuity request
Information element
Status
Description
Requestor identifier
M
Requestor iden... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3.3 PIN Management PEGC Service Continuity response
| Table 8.9.3.3-1 describes information elements for the PIN Management PEGC Service Continuity response.
Table 8.9.3.3-1: PIN Management PEGC Service Continuity response
Information element
Status
Description
Successful response (see NOTE)
O
Indicates that the request was successful.
> Target PEGC identifier
O
... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3.4 PIN Management PEGC Configuration request
| Table 8.9.3.4-1 describes information elements for the PIN Management PEGC Configuration request that is sent from the PEMC to the PEGC.
Table 8.9.3.4-1: PIN Management PEGC Configuration request
Information element
Status
Description
Requestor identifier
M
Requestor identifier.
Security credentials
M
Securit... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3.5 PIN Management PEGC Configuration response
| Table 8.9.3.5-1 describes information elements for the PIN Management PEGC Configuration response.
Table 8.9.3.5-1: PIN Management PEGC Configuration response
Information element
Status
Description
Successful response (see NOTE)
O
Indicates that the request was successful.
> PEGC connectivity information
O
In... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3.6 PIN Configuration Service Continuity Update request
| Table 8.9.3.6-1 describes information elements for the PIN Configuration Service Continuity Update request that is sent from the PEMC to the PIN Server.
Table 8.9.3.6-1: PIN Configuration Service Continuity Update request
Information element
Status
Description
Requestor identifier
M
Requestor identifier.
Securi... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3.7 PIN Configuration Service Continuity Update response
| Table 8.9.3.7-1 describes information elements for the PIN Configuration Service Continuity Update response.
Table 8.9.3.7-1: PIN Configuration Service Continuity Update response
Information element
Status
Description
Successful response (see NOTE)
O
Indicates that the request was successful.
> Service continui... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3.9 PIN Management PEGC discovery response
| Table 8.9.3.9-1 describes information elements for the PIN Management PEGC discovery response.
Table 8.9.3.3-1: PIN Management PEGC discovery response
Information element
Status
Description
Successful response (see NOTE)
O
Indicates that the request was successful.
> List of PEGC identifiers
O
List of PEGC id... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3.10 PIN service continuity subscribe request
| Table 8.9.3.10-1: PIN service continuity subscribe request
Information element
Status
Description
Application server ID
M
Unique identifier of the application server.
Security credentials
M
Security credentials resulting from a successful authorization for the PIN service.
PIN ID
M
The identifier of PIN.
... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3.11 PIN service continuity subscribe response
| Table 8.9.3.11-1: PIN service continuity subscribe response
Information element
Status
Description
Successful response
(see NOTE)
O
Indicates that the subscription request was successful.
> Subscription ID
M
Subscription identifier corresponding to the subscription.
> Expiration time
O
Indicates the expi... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3.12 PIN service continuity notify
| Table 8.9.3.12-1 describes information elements in the PIN service continuity notification from the PIN server to application server.
Table 8.7.3.12-1: PIN service continuity notification
Information element
Status
Description
PIN subscription identifier
M
Identifier of the subscription
Subscribed event
M
Id... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3.13 PIN service continuity update request
| Table 8.9.3.13-1: PIN service continuity update request
Information element
Status
Description
Subscription ID
M
Subscription identifier corresponding to the subscription.
Security credentials
M
Security credentials resulting from a successful authorization for the PIN service.
PIN ID
O
PIN identifier
Sub... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3.14 PIN service continuity update response
| Table 8.9.3.14-1: PIN service continuity update response
Information element
Status
Description
Successful response (see NOTE)
O
Indicates that the subscription update request was successful.
> Expiration time
O
Indicates the expiration time of the subscription. To maintain an active subscription, a subscripti... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3.15 PIN service continuity unsubscribe request
| Table 8.9.3.15-1: PIN service continuity unsubscribe request
Information element
Status
Description
Subscription ID
M
Subscription identifier corresponding to the subscription.
Security credentials
M
Security credentials resulting from a successful authorization for the PIN service.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.3.16 PIN service continuity unsubscribe response
| Table 8.7.3.16-1: PIN service continuity unsubscribe response
Information element
Status
Description
Successful response (see NOTE)
O
Indicates that the unsubscribe request was successful.
Failure response (see NOTE)
O
Indicates that the unsubscribe request failed.
> Cause
M
Indicates the cause of unsubscri... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.4 APIs
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.4.1 General
| Table 8.9.4.1-1 illustrates the API for AS service continuity subscription.
Table 8.9.4.1-1: Ppinserver_ASServiceContinuitySubscription API
API Name
API Operations
Operation
Semantics
Consumer(s)
Ppinserver_ASServiceContinuity
Subscribe
Subscribe/Notify
AS
Notify
Update
Unsubscribe
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.4.2 Ppinserver_ ASServiceContinuity_Subscribe operation
| API operation name: Ppinserver_ASServiceContinuity_Subscribe
Description: The consumer subscribes for service continuity information.
Inputs: See clause 8.9.3.10.
Outputs: See clause 8.9.3.11.
See clause 8.9.2.1.6.2.1 for details of usage of this operation.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.4.3 Ppinserver_ ASServiceContinuity_Notify operation
| API operation name: Ppinserver_ASServiceContinuity_Notify
Description: The consumer is notified with service continuity information.
Inputs: See clause 8.9.3.12.
Outputs: None.
See clause 8.9.2.1.6.2.2 for details of usage of this operation.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.4.4 Ppinserver_ ASServiceContinuity_ Update operation
| API operation name: Ppinserver_ASServiceContinuity_Update
Description: The consumer updates an existing subscription for service continuity information.
Inputs: See clause 8.9.3.13.
Outputs: See clause 8.9.3.14.
See clause 8.9.2.1.6.2.3 for details of usage of this operation.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.9.4.5 Ppinserver_ ASServiceContinuity_ Unsubscribe operation
| API operation name: Ppinserver_ASServiceContinuity_Unsubscribe
Description: The consumer cancels an existing subscription for service continuity information.
Inputs: See clause 8.9.3.15.
Outputs: See clause 8.9.3.16.
See clause 8.9.2.1.6.2.4 for details of usage of this operation.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.10 PIN Authorization
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.10.1 General
| The PIN authorization procedure is used by a PINE, PEGC or PEMC to acquire security information needed to perform procedures with other functional entities (e.g., PIN Server, PEMC, PEGC) of the PIN. The security information is used by a PINE, PEGC or PEMC (e.g., a requestor) when performing procedures of clause 8 that ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.10.2 Procedure
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.10.2.1 General
| PIN authorization procedure is either performed directly with the PIN server or indirectly via the PEGC for PINE(s) that require support of the PEGC to access the PIN server; the PEGC can deliver the PIN authorization request of the PINE to the PIN server when needed.
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.10.2.2 PIN authorization with PIN server
| Figure 8.10.2.2-1 illustrates PIN authorization procedure based on request/response model.
Pre-conditions:
1. The PINE/PEGC/PEMC has been pre-configured or has discovered the address (e.g., IP address, FQDN, URI) of the PIN server;
2. The PINE/PEGC/PEMC has been pre-configured with the PIN identifier;
3. The PIN se... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.10.3 Information flows
| |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.10.3.1 General
| The following information flows are specified for PIN authorization:
- PIN authorization request and response;
|
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.10.3.2 PIN authorization request
| Table 8.10.3.2-1 describes information elements in the PIN authorization request sent from the PINE or AS to the PIN server.
Table 8.10.3.2-1: PIN authorization request
Information element
Status
Description
Requestor identifiers
M
The identifiers of the requestor (i.e., GPSI of the PINE, and PINE identifier or ... |
f08903a2acbf9cb7accfe1b012f0a8bc | 23.542 | 8.10.3.3 PIN authorization response
| Table 8.10.3.3-1 describes information elements in the PIN authorization response sent to the PINE.
Table 8.10.3.3-1: PIN authorization response
Information element
Status
Description
Successful response
O
(see NOTE)
Indicates that the PIN authorization request was successful.
> Security information
M
The s... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 1 Scope
| The present document defines the Stage 2 specifications for enhancements of 5G System to support Edge Computing.
|
127ec4ebaf75180a017c55376a75e41a | 23.548 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 3 Definitions of terms, symbols and abbreviations
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 3.1 Terms
| For the purposes of the present document, the terms given in TR 21.905 [1], TS 23.501 [2] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1] and TS 23.501 [2].
Central DNS resolver/server: A DNS resolver/server centrally deplo... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 3.2 Abbreviations
| For the purposes of the present document, the abbreviations given in TR 21.905 [1], TS 23.501 [2] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1] and TS 23.501 [2].
C-DNS Central DNS
C-NEF Central NEF
C-P... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 4 Reference Architecture and Connectivity Models
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 4.1 General
| Edge Computing enables operator and 3rd party services to be hosted close to the UE's access point of attachment, so as to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network.
5GS supports Edge Hosting Environment (EHE) deployed in the DN beyond the PSA UPF. A... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 4.2 Reference Architecture for Supporting Edge Computing
| The reference architectures for supporting Edge Computing are based on the reference architectures specified in clause 4.2 of TS 23.501 [2]. The following reference architectures for non-roaming, LBO roaming and HR with Session Breakout (HR-SBO) roaming scenarios further depict the relationship between the 5GS and a DN... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 4.3 Connectivity Models
| 5GC supports the following connectivity models to enable Edge Computing:
- Distributed Anchor Point: For a PDU Session, the PSA UPF is in a local site, i.e. close to the UE location. The PSA UPF may be changed e.g. due to UE mobility and using SSC mode 2 or 3.
- Session Breakout: A PDU Session has a PSA UPF in a cent... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 5 Functional Description for Supporting Edge Computing
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 5.1 EASDF
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 5.1.1 Functional Description
| The Edge Application Server Discovery Function (EASDF) includes one or more of the following functionalities:
- Registering to NRF for EASDF discovery and selection.
- Providing DNS security information to SMF.
- Handling the DNS messages according to the instruction from the SMF, including:
- Receiving DNS message... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 5.1.2 EASDF Discovery and Selection
| The EASDF discovery and selection is defined in clause 6.3 in TS 23.501 [2].
|
127ec4ebaf75180a017c55376a75e41a | 23.548 | 5.2 Edge DNS Client (EDC) Functionality
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 5.2.1 Functional Description
| The Edge DNS Client (EDC) functionality is a 3GPP functionality in the UE that ensures that DNS requests from applications are sent to the DNS Server's (e.g. EASDF/DNS resolver) IP address received from the SMF in the ePCO. The EDC functionality in the UE is a UE capability that ensures the usage of the EAS discovery a... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6 Procedures for Supporting Edge Computing
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.1 General
| Edge Computing enables operator and 3rd party services to be hosted in EAS close to the UE's point of attachment. The traffic to EAS can be routed based on the UE position and EAS availability "near to" that position.
The subsequent clauses describe the procedures for supporting Edge Computing in 5G System considering... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2 EAS Discovery and Re-discovery
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.1 General
| In Edge Computing deployment, an application service may be served by multiple Edge Application Servers typically deployed in different sites. These multiple Edge Application Servers that host service may use a single IP address (anycast address) or different IP addresses. To start such a service, the UE needs to know ... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.2 EAS (Re-)discovery over Distributed Anchor Connectivity Model
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.2.1 General
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.2.2 EAS Discovery Procedure
| For the Distributed Anchor connectivity model, in PDU Session Establishment procedure, the SMF selects a DNS Server for the PDU Session. The DNS Server is configured to UE via PCO, and may also be configured via DHCP and/or IPv6 RA. The SMF determines the DNS server address for the PDU Session based on local configurat... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.2.3 EAS Re-discovery Procedure at Edge Relocation
| In order to change the PDU Session Anchor serving a PDU Session of SSC mode 2/3 for a UE, SMF triggers session continuity, service continuity and UP path management procedures as indicated in clause 4.3.5.1, 4.3.5.2 and 4.3.5.3 of TS 23.502 [3]. During these procedures, for SSC mode 2/3, it is recommended that the UE a... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.2.4 Procedure for EAS Discovery with Dynamic PSA Distribution
| 5GC supports an EAS discovery procedure that allows that at PDU Session Establishment the SMF selects a Central PSA, regardless if a Local PSA is available to the SMF and then, it allows to dynamically re-anchor the PDU Session and transition to a Distributed Anchor Point connectivity model when needed. This is applica... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3 EAS (Re-)discovery over Session Breakout Connectivity Model
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3.1 General
| This clause describes the EAS discovery and re-discovery procedures for PDU Session with Session Breakout connectivity model.
The following Session breakout models are defined:
- Dynamic Session Breakout: ULCL/BP/Local PSA (and their associated traffic filters and forwarding rules) are inserted based on DNS Response ... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3.2 EAS Discovery Procedure
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3.2.1 General
| For PDU Session with Session Breakout connectivity model, based on UE subscription (e.g. DNN) and/or the operator's configuration, the DNS Query sent by UE may be handled by an EASDF (see clause 6.2.3.2.2), or by a local or central DNS resolver/server (see clause 6.2.3.2.3). N6 delay measurement may be performed for L-... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3.2.2 EAS Discovery Procedure with EASDF
| For the case that the UE DNS Query is to be handled by EASDF, the following applies.
- The AF may provide EAS Deployment Information to NEF which may store it in UDR, as defined in clause 6.2.3.4. SMF may retrieve EAS Deployment Information from NEF as described in clause 6.2.3.4 or has locally preconfigured informati... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3.2.3 EAS Discovery Procedure with Local DNS Server/Resolver
| For the case that the DNS message is to be handled by Local DNS resolver/server, the DNS Query is routed to the Local DNS resolver/server corresponding to the DNAI where the L-PSA connects. The SMF selects the Local DNS server address based on the DNAI corresponding to the inserted local PSA, local configuration and ba... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3.2.4 Select common DNAI with Local DNS Server/Resolver for a set of UEs
| The following procedure is for selecting common DNAI with Local DNS Server/Resolver for set of UEs.
NOTE: In this Release, when an operator deploys the Local DNS server option defined in clause 6.2.3.2.3, the operator needs to be ensured that a UE cannot be involved in more than one UE set for a DNN and S-NSSAI.
Fi... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3.2.5 Common EAS discovery with EASDF for a set of UEs
| The following is the procedure for common EAS discovery for a set of UEs accessing the same application. Different UEs can be served by different SMFs.
The common EAS IP address for the set of UEs may either be provided by AF or determined by 5GC. AF may provide the common EAS IP via AF Traffic influence procedure as ... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3.2.6 EAS discovery corresponding to Common DNAI with EASDF for a set of UEs
| The common DNAI for the set of UEs can be provided either by AF or determined by 5GC. When the AF determines the common DNAI, the AF provides the common DNAI for the set of UEs via AF Traffic influence procedure as defined in clause 4.3.6.2 of TS 23.502 [3]. The AF may determine the common DNAI based on candidate DNAI(... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3.2.7 Coordination among SMFs for Common EAS/DNAI determination
|
Figure 6.2.3.2.7-1: Handling of Common EAS, Common/DNAI for set of UEs
1. SMF sends Nsmf_TrafficCorrelation_Notify to the NEF with Notification Endpoint received in the PCC rule as described in clauses 6.2.3.2.5 and 6.2.3.2.6 and provides: EAS IP address(es) based on EASDF procedure and/or list of candidate DNAI(s),... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3.3 EAS Re-discovery Procedure at Edge Relocation
| The support for EAS rediscovery indication procedure enables the UE to refresh stale EAS information stored locally so that the UE can trigger EAS discovery procedure to discover new EAS information.
For PDU Session with Session Breakout connectivity, the UE may indicate its support for refreshing stale EAS informatio... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3.4 EAS Deployment Information Management
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3.4.1 General
| EAS Deployment Information management refers to the capability to create, update or remove EAS Deployment Information from AF and the distribution to the SMF or to the I-SMF in case I-SMF based Local Offloading Management applies. The NEF is in charge of the management of EAS Deployment Information which may be stored ... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3.4.2 EAS Deployment Information Provision from AF via NEF
| The AF provides non-PDU Session specific EAS Deployment information to 5GC via the procedure defined in this clause.
Figure 6.2.3.4.2-1 EAS Deployment Information management in the AF procedure
1. The AF invokes the Nnef_EASDeployment_Create/Update/Delete service operation.
2. NEF checks whether the AF is authoriz... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3.4.3 EAS Deployment Information Management in the SMF or I-SMF
| The SMF may receive the EAS Deployment Information from NEF via Subscribe /Notify procedure defined in this clause. NEF may have stored the information in UDR.
When I-SMF based Local Offloading Management applies, the I-SMF may receive the EAS Deployment Information from NEF as described in this clause.
NOTE: When I-... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.3.4.4 BaselineDNSPattern Management in the EASDF
| The SMF receives EAS Deployment Information as described in clause 6.2.3.4.1, and derives BaselineDNSPattern from the EAS Deployment Information. The BaselineDNSPattern is not dedicated to a specific PDU Session.
SMF may create/update/delete the BaselineDNSPattern in the EASDF.
For EAS Deployment Information manageme... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.2.4 EDC Functionality based DNS Query to reach EASDF/DNS Resolver/DNS Server indicated by the SMF
| In order to guarantee that the FQDN requested by the Application that intends to use EAS is resolved by the DNS Server (e.g. EASDF/DNS resolver) indicated by the SMF, the consumer in the UE uses the related EDC functionality to either:
1) Send a DNS Query to the DNS Server (e.g., EASDF/DNS resolver) indicated by the S... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.3 Edge Relocation
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.3.1 General
| Edge Relocation refers to the procedures supporting EAS changes and/or PSA UPF relocation.
Edge Relocation may be triggered by an AF request (e.g. due to the load balance between EAS instances in the EHE) or by the network (e.g. due to the UE mobility).
With Edge Relocation, the user plane path may be re-configured t... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.3.2 Edge Relocation Involving AF Change
| This clause is related to scenarios where distributed Edge Application Server (EAS) deployed in local part of a Data Network or a central AS are relocated, and where the (E)AS relocation also implies AF relocation i.e. AF instance change.
Application Function influence on traffic routing mechanism as described in clau... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.3.3 Edge Relocation Using EAS IP Replacement
| EAS IP replacement enables the Local PSA UPF to replace the source/old Target EAS IP address and port number with the target/new target EAS IP address and port number for the Destination IP address and Destination Port number field of the uplink traffic and replace the target/new target EAS IP address and port number w... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.3.3.1 EAS IP Replacement Procedures
| |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.3.3.1.1 Enabling EAS IP Replacement Procedure by AF
|
Figure 6.3.3.1.1-1: Enabling EAS IP replacement procedure by AF
NOTE 1: This procedure covers the scenarios that the UE moves from non-EC to EC or the AF decides to enable the EAS IP replacement in the middle of a session.
1. UE requests to establish a PDU Session.
2. UE is preconfigured with the Source EAS IP add... |
127ec4ebaf75180a017c55376a75e41a | 23.548 | 6.3.3.1.2 EAS IP Replacement Update upon DNAI and EAS IP Change
|
Figure 6.3.3.1.2-1: EAS IP replacement update upon DNAI and EAS IP change
1. For UL traffic, the destination IP address is replaced with the old Target EAS IP address at Local PSA; for DL traffic, the source IP address is replaced back with the Source EAS IP address at Local PSA.
2. SMF configures Target UL CL with... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.