5G Core 21.1 Session Management ISSUE 1.0

5GC Session Management Data
Configuration
www.huawei.com
Copyright © Huawei Technologies Co., Ltd. All rights reserved.

Objectives
 After completing this course, you will be able to:

 Master the background of 5GC session management: session management, APN/DNN function, and the principle
of UE IP address assignment.
 Master basic data configuration for the 5GC SMF and UPF.
 Master data configuration for UE IP address assignment.
Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 3

Contents
1. Basic Concepts and Background

2. 5GC Session Management Data Configuration

Contents
1.1 Background of Session Management
1.2 Overview of UE IP Addresses Assignment
1.3 Static Address User Routing Redundancy Feature

APN Structure
internet. mnc<MNC>.mcc<MCC>.gprs
APN
APNNetwork
Network APN
APNOperator
Operator
Identifier
Identifier Identifier
Identifier
 APN-NI defines the external networks or services that mobile subscribers access through the gateway.
 APN-OI defines the GPRS/UMTS/EPC where the gateway is located.
 On the EPC network, you need to insert "apn.epc" between the APN-NI and APN-OI and replace "gprs" with
"3gppnetwork.org" for the APN official domain name APNFQDN.
 For example, on the EPC network, the official domain name of the APN internet.mnc015.mcc234.gprs is
internet.apn.epc.mnc015.mcc234.3gppnetwork.org.

5GC Session Management Feature Description
 The 5G core network supports a packet data unit (PDU) connectivity service, that is, a service that exchanges PDUs between a UE
and a DN identified by a data network name (DNN).
 The 5GC Session Management feature involves the following procedures:
 PDU session establishment: This procedure involves UE IP address assignment, UPF selection, PCC policy acquisition, and
permission check for a UE to access an external network.
 PDU session modification: A UE or the network initiates this procedure to update QoS parameter when one or more QoS
parameters exchanged between the UE and network are modified or the UE capability changes.
 PDU session release: A UE or the network initiates this procedure to release session resources when the UE does not require
related services, and the PCF or the SMF locally configures the release policy.

Access Point Name (APN)
DNS server on the
Internet
Domain name: www.yahoo.com www.yahoo.com=211

.*.*.*
APN: web
Traffic
eNodeB Signaling
MS
SAEGW
APN->PGW IP IP address=
MME 211.*.*.*
DNS core network of

www.yahoo.com
the GPRS system

Data Network Name (DNN)
DNS server on the
Internet
Domain name: www.yahoo.com Internet DNS

DNN: web
Traffic
gNodeB
MS UPF
Signaling
IP address=
211.*.*.*
AMF
DNN,Snssai->SMF IP
SMF
DNN/TAI->UPF IP
www.yahoo.com
NRF

Data Network Name (DNN) (Continued)
 A DNN defined in 3GPP TS 23.501 R15 is equivalent to an APN. Both identifiers have an equivalent
meaning and carry the same information. In addition, in R15, a DNN is equivalent to an APN.
 A DNN may be used to:
 Select an SMF and a UPF for a PDU session.
 Select an N6 interface (DN) for a PDU session.
 Determine policies to apply to this PDU session.

Contents

1.1 Introductions to APN and DNN
1.2 Overview of UE IP Address Assignment

Concepts
 UE IP address
 A UE IP address uniquely identifies a UE on a network. Only UEs assigned IP addresses can be addressed or communicate with
each other. Multiple network entities, such as the SMF, AAA server, and HSS/UDM, can assign IP addresses to UEs. During
user plane address assignment, the UDG assigns IP addresses to UEs from its local address pool.
 Address assignment
 The UDG supports two address assignment methods to provide IPv4, IPv6, or IPv4v6 addresses for UEs:
 External address assignment
The PGW-C/SMF, AAA server, or HSS/UDM assigns an IP address to a UE and notifies the UDG of the IP address. The UDG
then advertises the route.
 User plane address assignment
The UDG assigns an IP address to a UE from its local address pool and then advertises the route. The UDG is a user-plane
gateway that exchanges data between a PS core network and an external data network (DN). When the UDG assigns IP
addresses to UEs, it can also generate downlink routes to transmit downlink packets.

Address Assignment Overview
 The following figure shows how the UDG works with the UNC and UDM to assign IP addresses to UEs. A UE requests the UNC for
an IP address. The UNC notifies the UDG of an address assignment method based on the UE's subscription data and the local policy.
The UDG either assigns a user-plane IP address or forwards a received IP address to the UE through a session response message.
After obtaining the IP address, the UE initiates a data service request.

Overall Address Assignment Procedure
 The UNC proactively sends a PFCP Association Setup Request message to the
UDG. The UDG responds to the UNC with a PFCP Association Setup
Response message that contains user plane address assignment capabilities.
 During PDU session establishment, the UNC sends the UDG a session
establishment request message to notify the UDG of a specific address
assignment method. The UE IP Address IE in this message contains the
address type and IP address required for a UE to access an external data
network.
 The UDG determines to use external or user plane address assignment based
on the parameters in the UE IP Address IE in the session establishment request
message.
 The UDG then assigns an address or forwards a received address to the UE,
advertises a route, and detects the address whitelist or conflict.
 If user plane address assignment is used, the UDG assigns an IP address to the
UE and sends the assigned IP address to the UNC through a PDU session
establishment response message.

5GC UPF Is Recommended to Allocate UE IP Addresses
Protocols and standards
 Address assignment by the SMF: applicable to simple networking using one SMF and multiple UPFs
 Address assignment by the UPF: applicable to complex networking using multiple SMFs and UPFs
Commercial deployment
 Address assignment by the SMF: complex planning and low address pool usage
 Address assignment by the UPF: simple planning and high address pool usage
O&M scenarios
 Address assignment by the SMF: SMF/UPF capacity expansion is complex and requires peripheral cooperation.
 Address assignment by the UPF: SMF/UPF capacity expansion is simple and does not require peripheral cooperation.
Smooth evolution
 Address assignment by the SMF: The address pools need to be replanned on the entire network for the evolved SMF set.
 Address assignment by the UPF: The IP address planning does not need to be modified for the evolved SMF set.

Reporting of User Plane Address Assignment Capabilities
 The PGW-U/UPF reports its user plane address assignment capabilities to the PGW-C/SMF when they
exchange association messages, such as PFCP Association Setup Request/PFCP Association Setup
Response or PFCP Association Update Request/PFCP Association Update Response. The PGW-U/UPF
always includes a UP Function Flag IE in such a message. The ADUP bit in this IE is used to inform the
PGW-C/SMF of whether the UDG is capable of assigning user-plane addresses. This bit is set to 1 by
default, indicating that the UDG is capable of assigning user-plane addresses.

Address Assignment Method Selection
 The PGW-C/SMF uses the UE IP Address IE in a PFCP Session Establishment Request message to notify the PGW-
U/UPF of a specific address assignment method. The PGW-U/UPF then selects the external or user plane address
assignment based on the extension UPA, V4, and V6 bits in the UE IP Address IE. The following figure shows the UE
IP Address IE.
IE Description
Create PDR
---PDI The information in the left column shows the
------UE IP Address structure of the UE IP Address IE in a PFCP
Session Establishment Request message. The
Huawei solution specifies that user plane address
assignment is used if both the UPA bit and the V4
Create Traffic Endpoint or V6 bit are set to 1. If the UPA bit is set to 0, IP
---UE IP Address addresses are assigned by the control plane.

User Plane Address Assignment Overview
 The UDG uses a proprietary extension field in an association establishment request or response message over the N4
interface to inform the control plane of its local address assignment capabilities. The control plane then obtains the
capabilities.
 A subscriber initiates a session establishment request to the control plane during the activation procedure, applying
for an IP address. The control plane then determines whether the user plane or control plane assigns an IP address of
the specified type (IPv4, IPv6, or IPv4v6). If the control plane determines that the user plane assigns an IP address, it
uses a PFCP Session Establishment Request message over the N4 interface to instruct the UDG to assign an IP
address. The UDG then assigns an IP address as instructed by the control plane, and sends a PFCP Session
Establishment Response message with the assigned IP address to the UE. After the UE obtains the IP address, it can
initiate an uplink or downlink data service request.

User Plane Address Assignment Procedure
1. After NFs are deployed and interwork with each other at the data link layer, configure local information on
the user plane (UPF/PGW-U) to establish a connection towards the control plane (SMF/GW-C).
2. The user plane (UPF/PGW-U) reports its local address assignment capability in an association
establishment response message.
3. The user plane initiates a session establishment request message to the control plane for subscriber
activation. The Requested PDU Session Type IE in this message indicates the PDU session type (IPv4,
IPv6, or IPv4v6) requested by the UE.
4. The control plane determines whether the control plane or user plane assigns the requested IPv4, IPv6, or
IPv4v6 address of the specified PDU type to the UE based on its locally configured address assignment
capabilities.
5. The control plane sends a PFCP Session Establishment Request message to the user plane. This message
contains the UE IP Address sub-IE, which is delivered with either the PDI or Create Traffic Endpoint IE in
the Create PDR IE. In the UE IP Address sub-IE, the extension UPA bit, V4 bit, and V6 bit jointly indicate
whether the UDG assigns IP addresses and what types of IP address it assigns.
6. The user plane assigns a specified type of IP addresses to UEs from its local address pool as instructed by
the control plane.
7. The user plane returns a PFCP Session Establishment Response message to the control plane, with the
assigned IP address included in the UE IP Address sub-IE in the Created PDR or Created Traffic Endpoint
IE in this message. If address assignment fails due to insufficient IP addresses in the address pool, the UDG
responds to the control plane with a cause value "75 (No resources available)".
8. After obtaining the UE IP address, the control plane responds with a subscriber activation response message
to the (R)AN, and sends the assigned IP address to the UE.

IPv6 Address Assignment on the User Plane
UE AMF SMF UPF
1. The SMF includes the IPv6 Extended Filter IE in a PFCP Session
PDU Session Establishment Establishment Request message to match RS packets.
Request
Nsmf_PDUSession_Creat 2. The UPF includes the assigned IPv6 address in a PFCP Session
eSMContext Request
Establishment Response message.
Nsmf_PDUSession_CreateS
MContext Response 3. The SMF includes an interface ID in the N1 SM container IE in the
PFCP Session Establishment Request
(IPv6 Extended Filter) response message.
PFCP Session Establishment Response
(UE IP Address=IPv6 address) 4. The UE sends an RS message through the data plane based on the
Namf_Communication_N1N interface ID. The UPF matches the RS message sent by the UE and
2MessageTransfer
(N1 SM container: interface
sends a PFCP Session Report Request message carrying the RS
identifier) message to the SMF.
PDU Session
Establishment Accept 5. The SMF includes an RA message in a PFCP Session Report
Router Solicitation Response message and sends the message to the UPF. The UPF
PFCP Session Report Request then forwards the message to the UE.
(UP Signalling Message Information:
Router Solicitation) 6. If the SMF does not receive an RS message from the UE, the SMF
PFCP Session Report Response
(UP Signalling Message Information: Router includes an RA message in the PFCP Session Modification Request
Advertisement) message and sends the message to the UPF. The UPF returns a
PFCP Session Modification Request PFCP Session Modification Response message and forwards the
(UP Signalling Message Information:
Router Advertisement) RA message to the UE.
PFCP Session Modification Response
Router Advertisement

Contents

1.1 Background of Session Management
1.2 Overview of UE IP Addresses Assignment

Networking
The Static Address User Routing Redundancy feature ensures non-stop services for subscribers with static IP addresses. In network
deployment, a pair of active/standby UDGs are deployed. If the active UDG becomes faulty, the standby UDG will take over
services through the backup GRE tunnel. This prevents network failures and allows subscribers with static IP addresses to continue
using services normally.
Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page22 Page 22
Implementation Principle
 Uplink and downlink data flows in normal cases:
UDGs 1 and 2 both advertise a route destined for the
UE-subscribed static IP address segment to the Internet
over a routing protocol, such as Open Shortest Path
First (OSPF) or Border Gateway Protocol (BGP). UDG
1 has a higher route priority than UDG 2. If there is a
network fault, the functional UDG will take over
services from the faulty one to continue serving the UE.
The UDG used for UE activation works in the active

state, and the other one works in the standby state.
 Uplink data flow: UE -> (R)AN -> PE 1/PE 2 ->

UDG 1 -> PE 5/PE 6 -> PDN/DN
 Downlink data flow: PDN/DN -> PE 5/PE 6 ->

UDG 1 -> PE 1/PE 2 -> (R)AN -> UE
 If UDG 1 becomes faulty, UDG 2 will ensure service continuity by forwarding uplink and downlink data flows of subscribers
with static IP addresses.
If UDG 1 becomes faulty, subscribers with static IP

addresses will be reactivated on UDG 2. On the
uplink, subscriber data will flow to UDG 2 and then
to PE 7/PE 8. On the downlink, subscriber data from
the PDN/DN will flow to PE 7/PE 8 and then to
UDG 2, instead of flowing along the downlink route
(network segment route for UE-subscribed static IP
addresses) advertised by UDG 1.
 Uplink data flow: UE -> (R)AN -> PE 3/PE 4 ->

 Downlink data flow: PDN/DN -> PE 7/PE 8 ->

UDG 2 -> PE 3/PE 4 -> (R)AN -> UE
 After UDG 1 recovers, data of the UE with a static IP address will flow through the backup GRE tunnel to ensure proper service processing.
After UDG 1 recovers, it re-advertises a route destined for the

UE-subscribed static IP address segment. Once again, UDG 1
has a higher route priority than UDG 2. On the uplink, UDG 2
encapsulates received uplink data of subscribers with static IP
addresses into the backup GRE tunnel and forwards the data to
UDG 1. For this to happen, you need to set APN-specific
IPV4 Redund up Switch or APN-specific IPV6 Redund up
Function to ENABLE in SET APNREDUNDUPSW. This
setting prevents downlink data packets from being discarded
when UDGs 1 and 2 are deployed in different DCs and uplink
and downlink data packets along different paths pass through
multiple firewalls.
On the downlink, UDG 1 encapsulates received downlink data
of subscribers with static IP addresses into the backup GRE
tunnel and forwards the data to UDG 2, because UDG 1 does
not have UE contexts after subscribers are activated on UDG 2.
This procedure ensures that uplink and downlink data flows
along the same path.
• Uplink data flow: UE -> (R)AN -> PE 3/PE 4 -> UDG 2 ->
• Downlink data flow: PDN/DN -> PE 5/PE 6 -> UDG 1 ->
UDG 2 -> PE 3/PE 4 -> (R)AN -> UE
Contents


Contents
2.1 Data Configuration for Session Management Basic Services
2.2 Data Configuration for User-Plane IP Address Assignment
2.3 Data Configuration for the Static Address User Routing Redundancy Feature

5GC Session Management Basic Data Configuration Procedure - SMF
Add an APN (the DNN is incorporated

into the configuration).
Configure DNS server information at

the service layer.
Configure the UE IP address

assignment mode.

Session Management Data Plan
Category Parameter Example Value Note
APN (APN) INTERNET
Virtual APN (VIRTUALAPN) DISABLE
ADD APN Configure APN/DNN information.
Has VPN (HASVPN) DISABLE
Has VPN IPv6 (HASVPNIPV6) DISABLE
Primary IPv4 DNS (MDNSSERVERV4) 10.1.1.1 Configure DNS server information at
SET GLOBALDNS
Secondary IPv4 DNS (BDNSSERVERV4) 10.2.2.2 the service layer.
Support IPV4 (SUPPORTIPV4) ENABLE Enable the corresponding IP type based

SET APNADDRESSATTR
Support IPV6 (SUPPORTIPV6) ENABLE on the APN network plan.
Configure the UE IP address
SET ADDRESSATTR AllocPrecedence (ALLOCPRECEDENCE) UPF_FIRST assignment mode (UPF address
allocation).

ADD APN
(DNNs are incorporated into

APN configurations.)

Session Management Data Configuration
 Configure APN information.

ADD APN: APN="INTERNET", VIRTUALAPN=DISABLE, HASVPN=DISABLE, HASVPNIPV6=DISABLE,
LADN=NOTSUPPORT;
 Configure DNS server information at the service layer.

SET GLOBALDNS: MDNSSERVERV4="10.1.1.1", BDNSSERVERV4="10.2.2.2";
 Configure the UE address allocation policy to UPF address allocation.

SET ADDRESSATTR: ALLOCPRECEDENCE=UPF_FIRST;
 Configure the supported address types based on the APN network planning.
SET APNADDRESSATTR: APN="INTERNET", SUPPORTIPV4=ENABLE, SUPPORTIPV4=ENABLE;

Commissioning
 List APN information.
LST APN:APN=" internet"";

 List the default DNS configuration of the entire system.
LST GLOBALDNS;
 List the address attribute.
LST ADDRESSATTR
 List APN-specific address assignment attribute.
LST APNADDRESSATTR

Contents

User-Plane Address Assignment Modes
 The UDG can assign IP addresses based on any of following items or a combination of them (such as
location+APN/DNN and SMF+APN/DNN). The diverse set of address assignment methods can meet a variety of
address management and network O&M requirements of carriers:
 Activating User Plane Address Assignment (Based on APN/DNN)
 Activating Location-based Address Assignment (Based on Location)
 Activating User Plane Address Assignment (Based on SMF)

User-Plane Address Assignment Procedure
Adding a VPN instance Creating a new address pool
Creating a new address Creating a new address pool

pool group segment
Binding the address pool to

Adding an APN instance
the address pool group
Configuring OSPF route Configuring the address

advertisement assignment mode and type

Data Configuration-1
Step Operation Command

Open the MML Command - UDG window.
Binding an address pool to an address pool group
1. Add a VPN instance. ADD VPNINST
2. Add a local address pool. ADD POOL
3. Add an address segment to the local address pool. ADD SECTION
4. Add an address pool group. ADD POOLGROUP
5. Bind the local address pool to the address pool group. ADD POOLBINDGROUP
Configuring a mapping between the APN and address pool group

1. Add an APN/DNN instance. ADD APN
2. Add a mapping between the APN/DNN instance and address pool group. ADD POOLGRPMAP


Configuring an address assignment rule
1. Configure a global address assignment rule. SET IPALLOCRULE
(Optional) If an address assignment rule for a specified APN needs to be

2. different from the global rule, configure an APN-specific address SET APNIPALLOCRULE
assignment rule.
Configuring a mapping between the APN and address pool group

1. Add an APN/DNN instance. ADD APN
2. Add a mapping between the APN/DNN instance and address pool group. ADD POOLGRPMAP


In the MML Command - FrameWork window:
Configuring a downlink route for the UE
1. Add an OSPF process. ADD OSPF
2. Add an OSPF area. ADD OSPFAREA
3. Add an interface that uses OSPF. ADD OSPFNETWORK
4. Import WLR routes. ADD OSPFIMPORTROUTE

Data Planning - Adding an Address Pool on the UDG
Category Parameter Example Value Value Source Description
VPN Instance Network data plan (configurations on other NFs The VPN instance bound using this command must be the same as
ADD VPNINST vpn1
(VPNINSTANCE) need to be considered) that bound to a service APN.
Pool Name Local data plan (configurations on other NFs do
testpool1 -
(POOLNAME) not need to be considered)
Local data plan (configurations on other NFs do
Pool Type (POOLTYPE) LOCAL -
not need to be considered)
A local address pool can contain either IPv4 or IPv6 addresses. If
IP Address Type Local data plan (configurations on other NFs do
IPV4 both IPv4 and IPv6 addresses are planned, add an IPv4 address
(IPVERSION) not need to be considered)
pool and an IPv6 address pool.
ADD POOL
VPN instances bound to the following items must be consistent:
 APN used for subscriber activation
Local data plan (configurations on other NFs do
Has VPN (HASVPN) ENABLE  Address pool
not need to be considered)  External interface for the Gi/SGi/N6 interface of the
PDN/DN
VPN Instance Name

vpn1 Existing configuration You can run LST VPNINST to view the VPN instance name.
(VPNINSTANCE)
Pool Name Local data plan (configurations on other NFs do
testpool1 You can run LST POOL to view the address pool name.
(POOLNAME) not need to be considered)
Segment Number Local data plan (configurations on other NFs do
1 -
(SECTIONNUM) not need to be considered)
IP Address Type Local data plan (configurations on other NFs do
ADD SECTION IPV4 -
(IPVERSION) not need to be considered)
Start IPv4 Address Network data plan (configurations on other NFs
10.10.1.1 A local address pool can contain either IPv4 or IPv6 addresses. If
(V4STARTIP) need to be considered)
both IPv4 and IPv6 addresses are planned, add an IPv4 address
End IPv4 Address Network data plan (configurations on other NFs pool and an IPv6 address pool.
10.10.1.10
(V4ENDIP) need to be considered)

Data Planning - Adding an Address Pool Group and an APN instance on the
UDG
Pool Group Name Local data plan (configurations on other NFs do not
poolgroup1 -
(POOLGRPNAME) need to be considered)
ADD IPv4 Address Allocation
Local data plan (configurations on other NFs do not This parameter must be set to ENABLE if an IPv4 address pool uses the
POOLGROU Priority Algorithm ENABLE
need to be considered) address pool priority-based algorithm.
P (IPV4ALLOCPRIALG)
IPv6 Address Allocation
Local data plan (configurations on other NFs do not This parameter must be set to ENABLE if an IPv6 address pool uses the
Priority Algorithm ENABLE
need to be considered) address pool priority–based algorithm.
(IPV6ALLOCPRIALG)
Pool Group Name
poolgroup1 Existing configuration You can run LST POOLGROUP to view the pool group name.
(POOLGRPNAME)
Local data plan (configurations on other NFs do not
Pool Name (POOLNAME) testpool1 You can run LST POOL to view the address pool name.
ADD need to be considered)
POOLBINDG
ROUP If multiple address pools are bound to an address pool group, IP addresses are
Local data plan (configurations on other NFs do not assigned based on the address pool priority. Priorities can be compared only
Priority of Pool (PRIORITY) 10
need to be considered) for address pools of the same type. For example, the priorities of an IPv4
address pool and an IPv6 address pool cannot be compared.
An APN/DNN instance should be planned after considering all site entities.

APN (APN) apn-test1 The APN/DNN instance configured on the UDG must be consistent with that
need to be considered)
configured on a control-plane NF (SMF/SGW-C/PGW-C).
VPN instances bound to the following items must be consistent:

ADD APN Has VPN Local data plan (configurations on other NFs do not  Address pool
ENABLE
(HASVPN) need to be considered)  APN used for subscriber activation
 External interface for the Gi/SGi/N6 interface of the PDN/DN
VPN Instance Name Local data plan (configurations on other NFs do not
vpn1 You can run LST VPNINST to view the VPN instance name.
(VPNINSTANCE) need to be considered)

Data Planning - Configuring the Address Assignment Mode and Type on the
UDG
Local data plan (configurations on

Mapping Name
mapping1 other NFs do not need to be -
(MAPPINGNAME)
considered)
ADD APN (APN) apn-test1 Existing configuration You can run LST APN to view the APN name.
POOLGRPMAP
Name of Pool Group You can run LST POOLGROUP to view the pool
poolgroup1 Existing configuration
(POOLGROUPNAME) group name.

Switch of First Rule
ENABLE other NFs do not need to be By default, the first-priority rule is enabled.
(FIRSTRULESW)
considered)
APN-1&LOCATION-
First Rule (FIRSTRULE) other NFs do not need to be -
0&SMF-0
SET considered)
IPALLOCRULE Local data plan (configurations on
Switch of Second Rule
DISABLE other NFs do not need to be By default, the second-priority rule is disabled.
(SECONDRULESW)
considered)
Switch of Third Rule
DISABLE other NFs do not need to be By default, the third-priority rule is disabled.
(THIRDRULESW)
considered)

Data Planning - Configuring OSPF Networking and Route Advertisement on
the UDG
Process ID (PROCID) 100 Existing configuration -
You can run LST VPNINST to view the VPN
ADD OSPF VPN Name (VRFNAME) vpn1 Existing configuration
instance name.
Router ID Network data plan (configurations on other NFs need NOTICE
10.10.10.1
(SCHEMAROUID) to be considered) The router ID must be unique across the network.
Process ID (PROCID) 100 -
ADD OSPFAREA
Peer end (local and peer end configurations must
Area ID (AREAID) 0.0.0.0 -
match)
Peer end (local and peer end configurations must
Area ID (AREAID) 0.0.0.0 -
match)
ADD
OSPFNETWORK Network data plan (configurations on other NFs need
Address (IPADDRESS) 10.13.21.0 -
to be considered)
Wildcard Mask Network data plan (configurations on other NFs need
0.0.0.255 -
(WILDCARDMASK) to be considered)
ADD Network data plan (configurations on other NFs need
OSPFIMPORTROUT Topology ID (TOPOID) 0 -
to be considered)
E WLRs must be imported. The UDG advertises
Protocol (PROTOCOL) wlr subscribers' downlink routes to the transport
network.

Configuration Example-Address Assignment Based on APN
 //Run the following commands in the MML Command - UDG window:
 //Bind an address pool to an address pool group.
 ADD VPNINST:VPNINSTANCE="vpn1";
 ADD POOL:POOLNAME="testpool",POOLTYPE=LOCAL,HASVPN=ENABLE,VPNINSTANCE="vpn1";
 ADD SECTION:POOLNAME="testpool",SECTIONNUM=1,IPVERSION=IPV4,V4STARTIP="10.10.1.1",V4ENDIP="10.10.1.10";
 ADD POOLGROUP: POOLGRPNAME="poolgroup1", IPV4ALLOCPRIALG=ENABLE, IPV6ALLOCPRIALG=ENABLE;
 ADD POOLBINDGROUP: POOLGROUPNAME="poolgroup1", POOLNAME="testpool", PRIORITY=10;
 //Configure a mapping between the APN and address pool group.
 ADD APN:APN="apn-test1",HASVPN=ENABLE,VPNINSTANCE="vpn1";
 ADD POOLGRPMAP: MAPPINGNAME="mapping1", APN="apn-test1", POOLGROUPNAME="poolgroup1";
//Configure an address assignment rule.
 SET IPALLOCRULE: FIRSTRULESW=ENABLE, FIRSTRULE=APN-1&LOCATION-0&SMF-0, SECONDRULESW=DISABLE,

THIRDRULESW=DISABLE;

Configuration Example-Address Assignment Based on APN (Continued)
 //Run the following commands in the MML Command - FrameWork window:

 //Configure a downlink route for the UE.
 ADD OSPF:PROCID=100,VRFNAME="vpn1",SCHEMAROUID="10.10.10.1";
 ADD OSPFAREA:PROCID=100,AREAID="0.0.0.0";
 ADD OSPFNETWORK:PROCID=100,AREAID="0.0.0.0", IPADDRESS="10.13.21.0",
WILDCARDMASK="0.0.0.255";
 ADD OSPFIMPORTROUTE:PROCID=100,TOPOID=0,PROTOCOL=wlr;

Commissioning User Plane Address Assignment
 After user plane address assignment is configured, commission the User Plane Address Assignment feature to ensure that it functions
properly.
 Prerequisites
 Data (see the following table.)
 Tool
 Test UE
 WebLMT
Subscriber information IMSI (IMSI) 460000123456789 Test UE -
APN used by the test UE APN/DNN (APN) apn-test Existing configuration -

Procedure
1. Use the test MS/UE to request access to the network with APN apn-test.
2. In the MML Command - UDG_VNFC window, run DSP SESSIONINFO to check
whether the IP address of the test UE is in the local address pool configured on the UDG.
 If the test UE is activated and the value of IPv4 PDP address is in the planned address pool, the test
UE has accessed the network. Commissioning is complete, and no further action is required.
 If the test UE is activated but the value of IPv4 PDP address is not in the planned address pool, go to
the next step.
3. Run DSP SESSIONINFO to check the IP address type for the test UE.
 If the IP address type is UDG ALLOC IP ADDRESS, go to the next step to collect required
information and contact Huawei technical support.
 If the IP address type is EXTERNAL ALLOC IP ADDRESS, reconfigure the parameter.
4. Collect information and contact Huawei technical support.

 Create a user trace task on the WebLMT, and save the captured packets.
 Run EXP MML to export configuration data into a script file.
 Collect all the information mentioned above.
 Contact Huawei technical support.

Checking Whether the Route Between the UDG and PDN Server Is
Operational (1)
 //Run the following commands in the MML Command - UDG window. Configure the UDG to send detection messages to the PDN
server to check whether the route between to the PDN server is operational.
 //Configure the UDG to send PING messages to the PDN server. Check whether the route from the network segment for the address
pool associated with the APN named apn-test to the IP address 10.1.1.1 of the PDN server is operational.
 STR PDNROUTETST:APN="apn-test",DSTIPADDR="10.1.1.1",TESTMETHOD=PING;
 //Configure the UDG to send DNS detection messages to the PDN server. Check whether the route mentioned above is operational.
 STR PDNROUTETST:APN="apn-test",DSTIPADDR="10.1.1.1",TESTMETHOD=DNS;
 //Configure the UDG to send TRACERT messages to the PDN server. Check whether the route mentioned above with the source IP
address 10.2.2.2 is operational.
 STR PDNROUTETST:APN="apn-test",SRCIPADDR="10.2.2.2",DSTIPADDR="10.1.1.1",TESTMETHOD=TRACERT;

Operational (2)
 //Run the following command in the MML Command - UDG window. Configure the UDG to stop sending detection messages to
the PDN server.
 //After this command is executed, the UDG will immediately stop sending detection messages to the PDN server, and the other
routes except for those detected will not be found.
 //Stop route detection.
 STP PDNROUTETST:;

Operational (3)
 //Run the following command in the MML Command - UDG window. Check whether the route between the UDG and PDN server
is operational.
 //Check the ping results to see whether the route from the network segment for the address pool associated with the APN named
apn-test to the IP address 10.1.1.1 of the PDN server is operational. Display the detection result.
 DSP PDNTSTRESULT:;

Contents

Configuration Example
 Configure an active UDG. (Static IPv4 addresses are used as examples. Follow the same procedure
to configure the standby UDG.)
Procedure Operation Command
1 Configure a VPN instance for an IP address ADD VPNINST:VPNINSTANCE="vpn1";

pool.
ADD POOL: POOLNAME="pool1", POOLTYPE=EXTERNAL, IPVERSION=IPV4, HASVPN=ENABLE,
VPNINSTANCE="vpn1", SPUGROUPID=1, REDUNDFUNC=ENABLE;
Configure a static address pool, and
enable the Static Address User Routing
Redundancy feature. ADD SECTION: POOLNAME="pool1", SECTIONNUM=1, IPVERSION=IPV4, V4STARTIP="10.1.1.0",
V4ENDIP="10.1.1.225";
Configure an address pool group and

ADD POOLGROUP: POOLGRPNAME="poolgroup1", IPV4ALLOCPRIALG=ENABLE;
assign an address pool to it.
ADD POOLBINDGROUP:POOLGROUPNAME="poolgroup1", POOLNAME="pool1";

Configure an APN, and assign the
configured address pool group to it.
ADD APN: APN="test", HASVPN=ENABLE, VPNINSTANCE="vpn1";
ADD POOLGRPMAP: MAPPINGNAME="mapping1", APN="test",

POOLGROUPNAME="poolgroup1";
2 Configure a redirection IP address for the ADD REDUNDRDTIP: IPVERSION=IPv4, IPV4ADDRESS="192.168.0.1";

Static Address User Routing Redundancy
feature. Note: If the active UDG fails, the subscribers using static IP addresses are activated on the
standby UDG. When the active UDG receives downlink data for the subscribers, it checks the
destination IP addresses of the data. After finding that the destination IP addresses are static
ones, the UDG redirects the data through the backup GRE tunnel.
3 Enable the Static Address User Routing SET REDUNDUSER:SWITCH=ENABLE;

Redundancy feature.
Page 51
Configuration Example
 Configure an active UDG. (Static IPv4 addresses are used as examples. Follow the same procedure
to configure the standby UDG.)
Procedure Operation Command
4 Configure a loopback interface. ADD VPNINST:VPNINSTANCE="vpn2";

ADD VPNINSTAF:VRFNAME="vpn2", AFTYPE=ipv4uni;
MOD VPNINSTAF:VRFNAME ="vpn2", AFTYPE = ipv4uni, VRFRD="100:1";
ADD INTERFACE: IFNAME="LoopBack0", IFADMINSTATUS=up;
ADD IPBINDVPN: IFNAME="LoopBack0", VRFNAME="vpn2";
ADD IFIPV4ADDRESS: IFNAME="LoopBack0", IFIPADDR="10.11.1.1", SUBNETMASK="255.255.255.255";
5 Add a GRE tunnel. ADD GRETUNNEL: TNLNAME="Tunnel1", SRCTYPE=if_name, DSTIPADDR="10.10.0.1", TNLTYPE=gre,

SRCIFNAME="LoopBack0", DSTVPNNAME="vpn2", REDUNDANCYEN=TRUE;
ADD IPBINDVPN: IFNAME="Tunnel1", VRFNAME="vpn1";
ADD IFIPV4ADDRESS: IFNAME="Tunnel1", IFIPADDR="10.11.1.3", SUBNETMASK="255.255.255.0";
6 Configure a static route whose ADD SRROUTE: AFTYPE=ipv4unicast, PREFIX="192.168.0.1", MASKLENGTH=32, VRFNAME=""vpn1",
destination IP address is the redirection IFNAME="Tunnel1";
IP address and next hop is the backup Note: For load balancing and reliability purposes, you are advised to configure multiple static routes whose destination
GRE tunnel. IP addresses are the redirection IP address and next hops are the backup GRE tunnel. Data of the standby UDG will
then be redirected to one GRE tunnel in the UP state following the load sharing rules.
7 Start OSPF, import WLRs, and advertise ADD OSPF: PROCID=1;

them to the backbone network. ADD OSPFAREA: PROCID=1, AREAID="0.0.0.0";
ADD OSPFNETWORK: PROCID=1, AREAID="0.0.0.0", IPADDRESS="10.11.1.0", WILDCARDMASK="0.0.0.255";
ADD OSPFIMPORTROUTE: PROCID=1, TOPOID=0, PROTOCOL=wlr, IMPTCOSTCFG=TRUE, COST=1;
Note: COST values must be planned by considering all network entities. Ensure that the routes of the active UDG take
precedence over those of the standby UDG.
Page 52
Commissioning
Prerequisites
 You are familiar with the "GWFD-010107 Static Address User Routing Redundancy" feature.
 The UDGs have been deployed as an active/standby pair.
 Static Address User Routing Redundancy has been configured on the active and standby UDGs.
(For details, see CPI/GPI product documentation of the UDG.)
Tools
 Test UEs using static IP addresses
 OM portal
Page 53
Commissioning
1. Create user trace tasks on the WebLMT of the active and standby UDGs. Enter the IMSI of the test UE in the Parameter Configuration
area and select GTPC, UP, and DOWN in Message Type.
2. Use the test UE to request access to the network of the active UDG with APN apn1, and view the user trace result on the OM portal.
 If the test UE accesses the network, go to step 3.
 If the test UE fails to access the network, commission the access function of the UDG.
3. Use the test UE to access www.huawei.com.
 If the test UE successfully accesses the web page, go to step 4.
 If the test UE fails to access the web page, commission the web browsing function of the UDG.
4. View the value of 1914307822 User plane Current activated static backup sessions.
 If the value is available on the active UDG, go to step 5.
 If the value is unavailable on the active UDG, reconfigure this feature.
5. Simulate a fault on the active UDG, for example, reset it. Use the test UE to request access to the network of the standby UDG, and view
the user trace result on the OM portal. Then, use the test UE to visit www.huawei.com.
 If the test UE succeeds in accessing the network, go to step 6.
 If the test UE fails to access the network, commission the access function of the UDG.
Page 54
Commissioning
6. Use the test UE to visit www.huawei.com.
 If the test UE successfully accesses the web page, go to step 7.
 If the test UE fails to access the web page, commission the web browsing function of the UDG.
7. After the active UDG recovers, view the following counters on the active and standby UDGs:
On the active UDG:
1914307630 User plane outgoing static backup users traffic in KB
1914307631 User plane outgoing static backup users traffic in packets
1914307632 User plane outgoing static backup users traffic peak in KB/s
1914307633 User plane outgoing static backup users traffic peak in packets/s
On the standby UDG:
1914307626 User plane incoming static backup users traffic in KB
1914307627 User plane incoming static backup users traffic in packets
1914307628 User plane incoming static backup users traffic peak in KB/s
1914307629 User plane incoming static backup users traffic peak in packets/s
1914307822 User plane Current activated static backup sessions
 If the values are available on the active and standby UDGs, commissioning is complete, and no further action is required.
 If the values are unavailable on the active or standby UDGs, go to step 8.
Page 55
Commissioning
8. Run LST REDUNDUSER to check whether the Static Address User Routing Redundancy feature has been enabled.
 If it has been enabled, go to step 9.
 If it has not been enabled, reconfigure the feature.
9. Run LST POOL to check whether the address pools configured on the active and standby UDGs are as planned.
 If they are as planned, go to step 10.
 If they are not, reconfigure the feature.
Run LST GRETUNNEL to check whether the tunnel between the active and standby UDGs is as planned.
 If it is as planned, go to step 11.
 If It is not, reconfigure the feature.
11. Run LST REDUNDRDTIP to check whether the redirection IP address of the backup channel between the active and
standby UDGs is as planned.
 If it is as planned, go to step 12.
 If It is not, reconfigure the feature.
Page 56
Commissioning
12. Check whether the route of the backup GRE tunnel between the active and standby UDGs is operational.
 If the route is operational, go to step 13.
 If the route is unreachable, reconfigure the feature.
13. Check whether WLRs imported using OSPF are correct.
 If the OSPF/OSPFv3 function is normal, go to step 14.
 If the OSPF/OSPFv3 function is abnormal, reconfigure the feature.
14. Collect required information, and contact Huawei technical support.
 Start the packet capture tool on the mirroring port or server. Perform steps 2 and 5, and save the captured packets on
the active and standby UDGs.
 Run EXP MML to export the current configuration data into an MML script file and then save the file.
 Collect the above mentioned information.
 Contact Huawei technical support.
Page 57
Questions
 What are the functions of 5GC session management?

 What are the functions of the APN and DNN? Is there a configuration correlation between the APN and
DNN?
 How many address assignment modes does the 5GC support? What are the address assignment modes if
IP addresses are allocated from the local address pool?
 What are the benefits if the UDG assigns IP addresses to UEs from its local address pool?
 What is the concept of UE IP address assignment?
 What is the user plane address assignment procedure?

Summary
This section mainly describes the functions of the 5G SA, APN, and DNN as well as the UE address
assignment principles. It also describes the data configuration for the user-plane IP addresses assignment.

Thank You
www.huawei.com

5G Core 21.1 Session Management ISSUE 1.0

Uploaded by

Copyright:

Available Formats

5G Core 21.1 Session Management ISSUE 1.0

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

5G Core 21.1 Session Management ISSUE 1.0

Uploaded by

Copyright:

Available Formats

5GC Session Management Data

Copyright © Huawei Technologies Co., Ltd. All rights reserved.

 After completing this course, you will be able to:

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 3

1. Basic Concepts and Background

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 4

1. Basic Concepts and Background

1.1 Background of Session Management

1.2 Overview of UE IP Addresses Assignment

1.3 Static Address User Routing Redundancy Feature

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 5

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 6

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 7

Domain name: www.yahoo.com www.yahoo.com=211

DNS core network of

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 8

Domain name: www.yahoo.com Internet DNS

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 9

 Select an SMF and a UPF for a PDU session.

 Select an N6 interface (DN) for a PDU session.

 Determine policies to apply to this PDU session.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 10

1. Basic Concepts and Background

1.2 Overview of UE IP Address Assignment

1.3 Static Address User Routing Redundancy Feature

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 11

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 12

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 13

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 14

Protocols and standards

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 15

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 16

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 17

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 18

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 19

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 20

1. Basic Concepts and Background

1.2 Overview of UE IP Addresses Assignment

1.3 Static Address User Routing Redundancy Feature

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 21

The UDG used for UE activation works in the active

 Uplink data flow: UE -> (R)AN -> PE 1/PE 2 ->

 Downlink data flow: PDN/DN -> PE 5/PE 6 ->

If UDG 1 becomes faulty, subscribers with static IP

 Uplink data flow: UE -> (R)AN -> PE 3/PE 4 ->

 Downlink data flow: PDN/DN -> PE 7/PE 8 ->

After UDG 1 recovers, it re-advertises a route destined for the

1. Basic Concepts and Background

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 26

2. 5GC Session Management Data Configuration

2.1 Data Configuration for Session Management Basic Services

2.2 Data Configuration for User-Plane IP Address Assignment

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 27

Add an APN (the DNN is incorporated

Configure DNS server information at

Configure the UE IP address

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 28

Support IPV4 (SUPPORTIPV4) ENABLE Enable the corresponding IP type based

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 29

(DNNs are incorporated into