Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.316  Word version:  17.3.0

Top   Top   Up   Prev   Next
1…   4…   4.5…   4.7…   5…   6…   7…   7.2.2…   7.2.3…   7.2.4…   7.3…   7.6…   7.7…   8…   9…   10…   A…

 

4  High level featuresp. 10

This clause specifies high level description equivalent to TS 23.501.

4.1  Generalp. 10

The roaming support for W-5GAN access is not specified in this release.
The usage of Trusted or Untrusted access to 5GC by a 5G-RG or by a FN RG is not applicable.

4.2  Network Access Controlp. 11

4.2.0  Generalp. 11

This clause specifies the delta related to network access control defined in TS 23.501, clause 5.2.

4.2.1  Network selectionp. 11

In the case of 5G-RG or FN-RG connected via W-5GAN the PLMN selection specification defined in TS 22.011 and in TS 23.122 is not applicable. The HPLMN is implicitly selected by wired physical connectivity between 5G-RG or FN-RG and W-AGF.
The roaming scenario is not supported in this Release of the specification.
In the case of 5G-RG connected via FWA TS 23.501, clause 5.2.2 applies with the following difference:
Up

4.2.2  Identification and authenticationp. 11

In the case of 5G-RG connected via W-5GAN or FWA, the specification defined in TS 23.501, clause 5.2.3 applies with the following difference:
  • UE is replaced by 5G-RG.
In the case of FN-RG connected via W-5GAN, the specification defined in TS 23.501, clause 5.2.3 applies with the following differences:
  • UE is replaced by FN-RG.
  • The W-AGF provides the NAS signalling connection to the 5GC on behalf of the FN-RG.
  • The W-5GAN may authenticate the FN-BRG per BBF specification BBF TR-456 [9] and WT-457 [10]. The W-5GAN may authenticate the FN-CRG per CableLabs DOCSIS MULPI [8].
Up

4.2.3  Authorisationp. 11

In the case of 5G-RG connected via W-5GAN or FWA, the specification defined in TS 23.501, clause 5.2.4 applies with the following differences:
  • UE is replaced by 5G-RG.
    In the case of FN-RG connected via W-5GAN, the specification defined in TS 23.501, clause 5.2.4 applies with the following differences:
  • UE is replaced by FN-RG.
  • W-AGF performs the UE Registration procedure on behalf of the FN-RG.
Up

4.2.4  Access control and barringp. 11

In the case of 5G-RG or FN-RG connected via W-5GAN the Access Control and Barring defined in TS 23.501, clause 5.2.5 is not applicable.
In the case of 5G-RG connected via FWA the specification defined in TS 23.501, clause 5.2.5 applies with the following difference:
  • UE is replaced by 5G-RG.
Up

4.2.5  Policy controlp. 12

Policy control is specified in clause 9.

4.2.6  Lawful Interceptionp. 12

In the case of 5G-RG connected via FWA the specification defined in TS 23.501, clause 5.2.7 applies with the following difference:
  • UE is replaced by 5G-RG.
In the case of 5G-RG connected via W-5GAN, the definition and functionality of Lawful Interception defined in TS 33.126 applies with the following difference:
  • UE is replaced by 5G-RG.
In the case of FN-RG connected via W-5GAN, the definition and functionality of Lawful Interception defined in TS 33.126 applies with the following difference:
  • UE is replaced by FN-RG, with e.g. the difference that FN-RG may not have a globally unique PEI (as described in clause 4.7.7) and does not hold any 3GPP-based subscriber credentials or subscriber identity information.
Up

4.3  Registration and Connection Managementp. 12

4.3.1  Registration managementp. 12

Registration management when 5G-RG or FN-RG is connected to 5GC via wireline access is described in TS 23.501, clause 5.5.1.
Registration management when 5G-RG is connected to 5GC via NG RAN access is described in TS 23.501, clause 5.3.2.

4.3.2  Connection managementp. 12

Connection management when 5G-RG or FN-RG is connected to 5GC via wireline access is described in clause 5.5.2 of TS 23.501.
Connection management when 5G-RG is connected to 5GC via NG RAN access is described in clause 5.3.3 of TS 23.501.

4.3.3  Mobility Restrictionsp. 12

4.3.3.1  Generalp. 12

Mobility Restrictions restrict service access of an 5G-RG depending on RG location.
For a 5G-RG connecting over NG-RAN, the Mobility Restriction functionality as described in clause 5.3.4.1 of TS 23.501 applies.
For an 5G-RG connecting over wireline access, the Mobility Restriction functionality is described in this clause.
Mobility restrictions do not apply to scenarios with FN-BRG.
Mobility Restrictions for wireline access consists of Forbidden Area and Service Area Restrictions, as described in the following clauses.
Up

4.3.3.2  Management of Forbidden Area in wireline accessp. 13

In a Forbidden Area, the 5G-RG, based on subscription, is not permitted by the 5GC to initiate any communication with the 5GC for this PLMN.
The UDM stores the Forbidden Area for wireline access in the same way as for 3GPP access, with the following differences:
  • For subscriptions for 5G-BRG, GLI is used to describe the Forbidden Area.
  • For subscriptions for 5G-CRG and FN-CRG, HFC Node IDs are used to describe the Forbidden Area (instead of TA).
  • The Forbidden Area in UDM can be encoded as a "allow list" indicating the non-forbidden area. In this case all GLI or HFC_Node ID values not included in the list are considered forbidden.
Forbidden Area is enforced by AMF, based on subscription data and the location information received from W-AGF. The AMF rejects a Registration Request from a 5G-RG or the W-AGF acting on behalf of a FN-CRG in a Forbidden Area with a suitable cause code. The 5G-RG behaviour depends on the network response (cause code from AMF) that informs the RG that communication is forbidden.
Up

4.3.3.3  Management of Service Area Restrictions in wireline accessp. 13

The subscription data in the UDM for a 5G-BRG includes a Service Area Restriction which may contain either Allowed or Non-Allowed Areas specified by using explicit GLI(s) and/or other geographical information (e.g., longitude/latitude, zip code, etc.).
The subscription data in the UDM for a 5G-CRG and FN-CRG includes a Service Area Restriction which may contain either Allowed or Non-Allowed Areas specified by using explicit HFC Node IDs and/or other geographical information (e.g., longitude/latitude, zip code, etc.).
The geographical information used to specify allowed or non-allowed area is only managed in the network, and the network will map it to a list of GLI(s) or HFC Node IDs before sending Service Area Restriction information to the PCF.
The UDM stores the Service Area Restrictions for the 5G-RG or FN-CRG as part of the subscription data. The PCF in the serving network may (e.g. due to varying conditions such as 5G-RG's location, time and date) further adjust Service Area Restrictions of a 5G-RG, either by expanding an allowed area or by reducing a non-allowed area. The UDM and the PCF may update the Service Area Restrictions of a 5G-RG or a FN-CRG at any time.
During registration, if the Service Area Restrictions of the 5G-RG or FN-CRG is not present in the AMF, the AMF fetches from the UDM the Service Area Restrictions of the 5G-RG or FN-CRG that may be further adjusted by the PCF. The serving AMF shall enforce the Service Area Restrictions of a 5G-RG and a FN-CRG. The AMF receives the location information (GLI, HFC Node IDs) where the RG is connected from the W-AGF via N2.
The network does not send any Allowed Area or Non-Allowed Area to the 5G-RG for wireline access. If the 5G-RG initiates communication in an Allowed Area, the network accepts the communication as allowed by the subscription. If the 5G-RG initiates Service Request or SM signalling in a Non-Allowed Area, the AMF rejects the request with a suitable cause code indicating that the 5G-RG/W-AGF should not retry Service Request and SM signalling while being connected to the same line.
Upon change of serving AMF due to mobility, the old AMF may provide the new AMF with the Service Area Restrictions of the 5G-RG that may be further adjusted by the PCF.
Up

4.4  Session managementp. 14

4.4.0  Generalp. 14

This clause specifies the delta related to session management defined in TS 23.501, clause 5.6.
The LADN service defined in clause 5.6.5 in TS 23.501 does not apply for RG connected to 5GC via wireline access.
When handling DHCP signalling coming from a wireline BBF access, the SMF (as well as an external DHCP server used by SMF) shall support the DHCP signalling as described in in BBF TR-456 [9].
Up

4.4.1  Session management for 5G-RGp. 14

Session management of 5G-RG connected to 5GC via wireline access follows the principle defined in TS 23.501, clause 5.6 with the following difference:
  • UE is replaced by 5G-RG.
  • 5G-RG is connected to 5GC via wireline RAT type instead of 3GPP access.

4.4.2  Session management for FN-RGp. 14

Session management of FN-RG follows the principle defined in TS 23.501, clause 5.6 with the follow difference:
  • UE is replaced by W-AGF
  • FN-RG is connected to 5GC via wireline access instead of 3GPP access.
  • Secondary authentication/authorization by a DN-AAA server during the establishment of a PDU Session is applicable neither to FN-RG nor to N5GC devices.
  • For FN-BRG, only SSC modes 1 or 2 can be used, depending on the type of FN-BRG as described in TR 456 [9] and WT-457 [10].
Up

Up   Top   ToC