mirror of
https://github.com/open5gs/open5gs.git
synced 2026-04-28 03:19:31 +00:00
[AMF/MME] Support TAI Range
This commit is contained in:
parent
2944fa2549
commit
424f382265
17 changed files with 691 additions and 276 deletions
|
|
@ -348,34 +348,57 @@ sbi:
|
|||
# <TAI>
|
||||
#
|
||||
# o Multiple TAI
|
||||
#
|
||||
# When multiple TAIs are configured as shown below,
|
||||
# the Served TAI is determined by comparing UserLocationInformation
|
||||
# of UplinkNASTransport sent from gNB.
|
||||
#
|
||||
# For example, if the gNB sends TAC with 30 to the AMF,
|
||||
# the fourth TAI (TAC: 20, 28, 29-32, 36-38, 40-42, 50, 60, 70, 70)
|
||||
# is determined as the Served TAI. The result is transmitted to the gNB
|
||||
# as a Tracking Area identity List in Registration Accept.
|
||||
#
|
||||
# amf:
|
||||
# tai:
|
||||
# - plmn_id:
|
||||
# mcc: 001
|
||||
# mnc: 01
|
||||
# tac: [1, 2, 3]
|
||||
# tac: [1, 3, 5]
|
||||
# tai:
|
||||
# - plmn_id:
|
||||
# mcc: 002
|
||||
# mnc: 02
|
||||
# tac: 4
|
||||
# tac: [6-10, 15-18]
|
||||
# tai:
|
||||
# - plmn_id:
|
||||
# mcc: 003
|
||||
# mnc: 03
|
||||
# tac: 5
|
||||
# tai:
|
||||
# tac: 20
|
||||
# - plmn_id:
|
||||
# mcc: 004
|
||||
# mnc: 04
|
||||
# tac: [6, 7]
|
||||
# tac: 21
|
||||
# tai:
|
||||
# - plmn_id:
|
||||
# mcc: 005
|
||||
# mnc: 05
|
||||
# tac: 8
|
||||
# tac: [22, 28]
|
||||
# - plmn_id:
|
||||
# mcc: 006
|
||||
# mnc: 06
|
||||
# tac: [9, 10]
|
||||
# tac: [30-32, 34, 36-38, 40-42, 44, 46, 48]
|
||||
# - plmn_id:
|
||||
# mcc: 007
|
||||
# mnc: 07
|
||||
# tac: 50
|
||||
# - plmn_id:
|
||||
# mcc: 008
|
||||
# mnc: 08
|
||||
# tac: 60
|
||||
# - plmn_id:
|
||||
# mcc: 009
|
||||
# mnc: 09
|
||||
# tac: [70, 80]
|
||||
#
|
||||
# <PLMN Support>
|
||||
#
|
||||
|
|
|
|||
|
|
@ -217,35 +217,57 @@ logger:
|
|||
# <TAI>
|
||||
#
|
||||
# o Multiple TAI
|
||||
#
|
||||
# When multiple TAIs are configured as shown below,
|
||||
# the Served TAI is determined by comparing UserLocationInformation
|
||||
# of UplinkNASTransport sent from eNB.
|
||||
#
|
||||
# For example, if the eNB sends TAC with 30 to the MME,
|
||||
# the fourth TAI (TAC: 20, 28, 29-32, 36-38, 40-42, 50, 60, 70, 70)
|
||||
# is determined as the Served TAI. The result is transmitted to the eNB
|
||||
# as a Tracking Area identity List in Registration Accept.
|
||||
#
|
||||
# mme:
|
||||
# tai:
|
||||
# - plmn_id:
|
||||
# mcc: 001
|
||||
# mnc: 01
|
||||
# tac: [1, 2, 3]
|
||||
# tac: [1, 3, 5]
|
||||
# tai:
|
||||
# - plmn_id:
|
||||
# mcc: 002
|
||||
# mnc: 02
|
||||
# tac: 4
|
||||
# tac: [6-10, 15-18]
|
||||
# tai:
|
||||
# - plmn_id:
|
||||
# mcc: 003
|
||||
# mnc: 03
|
||||
# tac: 5
|
||||
# tai:
|
||||
# tac: 20
|
||||
# - plmn_id:
|
||||
# mcc: 004
|
||||
# mnc: 04
|
||||
# tac: [6, 7]
|
||||
# tac: 21
|
||||
# tai:
|
||||
# - plmn_id:
|
||||
# mcc: 005
|
||||
# mnc: 05
|
||||
# tac: 8
|
||||
# tac: [22, 28]
|
||||
# - plmn_id:
|
||||
# mcc: 006
|
||||
# mnc: 06
|
||||
# tac: [9, 10]
|
||||
#
|
||||
# tac: [30-32, 34, 36-38, 40-42, 44, 46, 48]
|
||||
# - plmn_id:
|
||||
# mcc: 007
|
||||
# mnc: 07
|
||||
# tac: 50
|
||||
# - plmn_id:
|
||||
# mcc: 008
|
||||
# mnc: 08
|
||||
# tac: 60
|
||||
# - plmn_id:
|
||||
# mcc: 009
|
||||
# mnc: 09
|
||||
# tac: [70, 80]
|
||||
#
|
||||
# <Network Name>
|
||||
# mme:
|
||||
|
|
|
|||
|
|
@ -501,7 +501,7 @@ sbi:
|
|||
# - plmn_id:
|
||||
# mcc: 999
|
||||
# mnc: 70
|
||||
# range:
|
||||
# tac:
|
||||
# - 1-9
|
||||
# - s_nssai:
|
||||
# - sst: 2
|
||||
|
|
@ -517,7 +517,7 @@ sbi:
|
|||
# - plmn_id:
|
||||
# mcc: 999
|
||||
# mnc: 70
|
||||
# range:
|
||||
# tac:
|
||||
# - 10-20
|
||||
# - 30-40
|
||||
#
|
||||
|
|
@ -562,13 +562,13 @@ sbi:
|
|||
# - plmn_id:
|
||||
# mcc: 999
|
||||
# mnc: 70
|
||||
# range:
|
||||
# tac:
|
||||
# - 100-200
|
||||
# - 300-400
|
||||
# - plmn_id:
|
||||
# mcc: 999
|
||||
# mnc: 70
|
||||
# range:
|
||||
# tac:
|
||||
# - 500-600
|
||||
# - 700-800
|
||||
# - 900-1000
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue