UAC统一接入控制.docx

1、UAC统一接入控制Unified Access Control （通用接入控制）上周将NR重选的时候，在SIB2中定义了 UAC当时由于时间问题，没有展开来 进行解释，所以考虑补充一个专题文档。UAC是UE接入控制或状态改变的机制集合。在LTE中，我们就经常会碰到需要接入控制的时候， 比如某个小区超载了，大量 UE接入到一个小区，导致 UE间相互干扰严重，无法成功解码。在 4G中，接入 控制主要有两种类型：UE初始接入请求的时候，网络下发拒绝消息；自己阻止UE尝试初始接入（也就是 CellBar）Case1: SIB1配置bar，所有UE都不能接入，含紧急呼叫Case2: SIB2配备Bar，

2、只针对特定服务特定的 UE禁止接入在LTE中，接入控制主要在RRC层进行，但是，在NR中，不仅在RRC层进行控 制，还可以在NAS层进行控制。具体如下：UACAlgorithmUSIMFactorsDescripti onRRC? uac-Barri ngl nfo in SIB1? RRC State (Idle, Co nn ected,I nactive)NAS? 见下文USIM? EFUAC AIC, EFACCUAC触发根据24.501 4.5.1 总结如下：Trigger Descripti onNAS状态改变服务请求 (in5GMM-C0NNECTED)5GMM-IDLE - 5

3、GMM-C0NNECTEDMO-MMTEL-voice-call-started in dicati on MO-MMTEL-video-call-started in dicatio n MO-SMSolP-attempt-startedMO SMS over NASUL NAS TRANSPORTmessage for PDU session establishme nt (except for the purpose of IDLE - CONNECTED NAS State chan ge)UL NAS TRANSPORTmessage for PDU session modifica

4、ti on (except for the purpose of IDLE - CONNECTED NAS State cha nge)Request to re-establish the user-pla neresources for an existi ng PDU sessi onNotification for an uplink user data packet to be sent for a PDU sessi on with suspe nded user- pla ne resourcesSIM卡信息相关的UACEFUAC_AIC (UAC Access Identiti

5、es Configuration) , 31.102 定义如下:b1=0: UE is not configured for Multimedia PriorityService in the HPLMN,EHPLMN or a visited PLMN of the home country.b1=1: UE is configured for Multimedia Priority Service inthe HPLMN,EHPLMN or a visited PLMN of the home country.b2=0: UE is not configured for Mission C

6、ritical Servicesin the HPLMN,EHPLMN or a visited PLMN of the home country.b2=1: UE is configured for Mission Critical Services inthe HPLMN,EHPLMN or a visited PLMN of the home country.RFUb8b7b6b5b4b3b2b115 14 13 12 11 10 09 08 Number of the ACC (except for bit b3)Byte 2:b8b7b6b5b4b3b2blFF1nnrFn-I-07

7、06050403020100Identifier: 6F78Structure: transparentMandatorySFI: 06File size: 2 bytesUpdate activity: lowAccess Conditions:READPINUPDATEADMDEACTIVATEADMACTIVATEADMBytesDescriptionM/OLength1 to 2Access control classesM2 bytesNumber of the ACC如何获取接入标识符?Access ide ntitiesAccess Identity numberUE confi

8、guration0UE is not configured with any parameters from this table1 (NOTE 1)UE is configured for multimedia priority service (MPS).2 (NOTE 2)UE is configured for mission critical service (MCS).3-10Reserved for future use11 (NOTE 3)Access Class 11 is configured in the UE.12 (NOTE 3)Access Class 12 is

9、configured in the UE.13 (NOTE 3)Access Class 13 is configured in the UE.14 (NOTE 3)Access Class 14 is configured in the UE.15 (NOTE 3)Access Class 15 is configured in the UE.NOTE 1: Access identity 1 is valid when:-the USIM file EF uac_aic indicates the UE is configured for access identity 1 and the

10、 selected PLMN, if a new PLMN is selected, or RPLMN is the HPLMN (if the EHPLMN list is not present or is empty) or EHPLMN (if the EHPLMN list is present), or a visited PLMN of the home country (see the definition of home country in 3GPP TS 24.301 15); or -the UE receives the 5GS network feature sup

11、port IE with the MPS indicator bit set to Access identity 1 valid from the RPLMN as described in subclause 5.5.1.2.4 and subclause 5.5.1.3.4.NOTE 2: Access identity 2 is used by UEs configured for MCS and is valid when:-the USIM file EF uac_aic indicates the UE is configured for access identity 2 an

12、d the selected PLMN, if a new PLMN is selected, or RPLMN is the HPLMN (if the EHPLMN list is not present or is empty) or EHPLMN (if the EHPLMN list is present), or a visited PLMN of the home country (see 3GPP TS 23.122 5); or-the UE receives the 5GS network feature support IE with the MCS indicator

13、bit set to Access identity 2 valid from the RPLMN as described in subclause 5.5.1.2.4 and subclause 5.5.1.3.4.NOTE 3: Access identities 11 and 15 are valid in HPLMN (if the EHPLMN list is not present or is empty) or EHPLMN (if the EHPLMN list is present). Access Identities 12, 13 and 14 are valid in

14、 HPLMN and visited PLMNs of home country only (see the definition of home country in 3GPP TS 24.301 15).那么，接入等级能够提供哪些服务呢？Mapp ing table for access categoriesRule #Type of access attemptRequirements to be metAccessCategory1Response to paging or NOTIFICATION over non- 3GPP access; 5GMM connection mana

15、gement procedure initiated for the purpose of transporting an LPP message without an ongoing 5GC-M0-LR procedure; Access attempt to handover of ongoing MMTEL voice call, MMTEL video call or SMSoIP from non-3GPP accessAccess attempt is for MT access, or handover of ongoing MMTEL voice call, MMTEL vid

16、eo call or SMSoIP from non- 3GPP access0 (= MT_acc)2EmergencyUE is attempting access for an emergency session (NOTE 1, NOTE 2)2 (= emergency)3Access attempt for operator-defined access categoryUE stores operator-defined access category definitions valid in the current PLMN as specified in subclause

17、4.5.3, and access attempt is matching criteria of an operator- defined access category definition32-63(=based on operator classification)3.1Access attempt for MO exception dataUE is in NB-N1 mode and allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS confi

18、guration MO in3GPP TS 24.368 17 or the USIM file EF nasconfig in 3GPP TS 31.102 22), and access attempt is for MO data or for MO signalling initiated upon receiving a request from upper layers to transmit user data related to an exceptional event.10(= MO exception data)4Access attempt for delay tole

19、rant service(a)UE is configured for NAS signalling low priority or UE supporting S1 mode is configured for EAB (see the ExtendedAccessBarring leaf of NAS configuration MO in 3GPP TS 24.368 17 or 3GPP TS 31.102 22) where EAB override does not apply, and(b): the UE received one of the categories a, b

20、or c as part of the parameters for unified access control in the broadcast system information, and the UE is a member of the broadcasted category in the selected PLMN or RPLMN/equivalent PLMN (NOTE 3, NOTE 5, NOTE 6, NOTE 7, NOTE 8)1 (= delay tolerant)4.1MO IMS registration related signallingAccess

21、attempt is for MO IMS registration related signalling (e.g. IMS initial registration, re-registration, subscription refresh)or for NAS signalling connection recovery during ongoing procedure for MO IMS registration related signalling (NOTE 2a)9 (= MO IMS registration related signalling)5MO MMTel voi

22、ce callAccess attempt is for MO MMTel voice call or for NAS signalling connection recovery during ongoing MO MMTel voice call (NOTE 2)4 (= MO MMTelvoice)6MO MMTel video callAccess attempt is for MO MMTel video call or for NAS signalling connection recovery during ongoing MO MMTel video call (NOTE 2)

23、5 (= MO MMTel video)7MO SMS over NAS or MOSMSoIPAccess attempt is for MO SMS over NAS (NOTE 4) or MO SMS over SMSoIP transfer or for NAS signalling connection recovery during ongoing MO SMS or SMSoIP transfer (NOTE 2)6 (= MO SMS and SMSoIP)8UE NAS initiated 5GMMspecific proceduresAccess attempt is f

24、or MO signalling3 (= MO_sig)8.1Mobile originated locationrequestAccess attempt is for mobile originated location request (NOTE 9)3 (= MO_sig)8.2Mobile originated signalling transaction towards the PCFAccess attempt is for mobile originated signalling transaction towards the PCF (NOTE 10)3 (= MO_sig)

25、9UE NAS initiated 5GMM connection management procedure or 5GMM NAS transport procedureAccess attempt is for MO data7 (= MO_data)10An uplink user data packet is to be sent for a PDU session with suspended user-plane resourcesNo further requirement is to be met7 (= MO_data)NOTE 1:This includes 5GMM sp

26、ecific procedures while the service is ongoing and 5GMM connection management procedures required to establish a PDU session with request type = initial emergency request or existing emergency PDU session, or to re-establish user-plane resources for such a PDU session. This further includes the serv

27、ice request procedure initiated with a SERVICE REQUEST message with the Service type IE set to emergency services fallback.NOTE 2:Access for the purpose of NAS signalling connection recovery during an ongoing service as defined in subclause 4.5.5, or for the purpose of NAS signalling connection esta

28、blishment following fallback indication from lower layers during an ongoing service as defined in subclause 4.5.5, is mapped to the access category of the ongoing service in order to derive an RRC establishment cause, but barring checks will be skipped for this access attempt.NOTE 2a:Access for the

29、purpose of NAS signalling connection recovery during an ongoing procedure for MO IMS registration related signalling as defined in subclause 4.5.5, or for the purpose of NAS signalling connection establishment following fallback indication from lower layers during an ongoing procedure for MO IMS reg

30、istration related signalling as defined in subclause 4.5.5, is mapped to the access category of the MO IMS registration related signalling in order to derive an RRC establishment cause, but barring checks will be skipped for this access attempt.NOTE 3:If the UE selects a new PLMN, then the selected

31、PLMN is used to check the membership; otherwise the UE uses the RLPMN or a PLMN equivalent to the RPLMN.NOTE 4:This includes the 5GMM connection management procedures triggered by the UE-initiated NAS transport procedure for transporting the MO SMS.NOTE 5:The UE configured for NAS signalling low priority is not supported in this release of specification. If a UE supporting both S1 mode and N1 mode i