IP Library Granted Patent US 12,245,324
Granted Patent B2
US 12,245,324 · App. 17/592,824 · Granted Mar 4, 2025

Method and apparatus for controlling access in next generation mobile communication system

Inventors: Sangbum Kim (Suwon-si, KR); Donggun Kim (Seoul, KR); Alexander Sayenko (Seoul, KR); Jaehyuk Jang (Suwon-si, KR); Seungri Jin (Suwon-si, KR); Soenghun Kim (Suwon-si, KR)
Assignee: Samsung Electronics Co., Ltd.
H04W76/50H04W4/90H04W12/08H04W48/02H04W76/19H04W76/27H04W76/28
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,245,324
App. No.
17/592,824
Filed
Feb 4, 2022
Granted
Mar 4, 2025
Kind
B2
Art Unit
2647
USPC
455/337
Abstract

An apparatus and a method to apply 5G communication systems to IoT networks is provided. The apparatus includes technologies, such as a sensor network, machine type communication (MTC), and machine-to-machine (M2M) communication may be implemented by beamforming, multiple-input multiple-output (MIMO), and array antennas. Application of a cloud radio access network (RAN) as the above-described big data processing technology may also be considered to be as an example of convergence between the 5G technology and the IoT technology. The disclosure relates to a method and an apparatus for controlling network access in a next generation mobile communication system.

Claims (21)

1. A terminal in a wireless communication system, the terminal comprising:

a transceiver; and

at least one processor coupled with the transceiver and configured to:

receive, from a base station, at least one barring configuration, and

determine whether an access attempt is allowed or not based on a barring configuration corresponding to an access category of the access attempt from the at least one barring configuration, the barring configuration including information for a barring factor and information for a barring time,

wherein, in case that the access attempt is categorized into both a first standardized access category included in standardized access categories and a non-standardized access category associated with an operator classification, the first standardized access category included in the standardized access categories is applied to the access category of the access attempt, wherein the first standardized access category is a predetermined standardized access category including an access category associated with an emergency,

wherein, in case that the access attempt is categorized into both a second standardized access category included in the standardized access categories and the non-standardized access category associated with the operator classification, the non-standardized access category associated with the operator classification is applied to the access category of the access attempt, wherein the second standardized access category is not the predetermined standardized access category included in the standardized access categories, and

wherein the access attempt is determined to be allowed in case that a random value is lower than the barring factor.

2. The terminal of claim 1 , wherein the non-standardized access category associated with the operator classification is defined based on a slicing type or an application.

3. The terminal of claim 1 , wherein in case that the access attempt is determined to be barred, the access attempt is considered as barred during a timer value determined based on the barring time.

4. The terminal of claim 1 , wherein the access attempt is categorized into at least one standardized access category.

5. An access control method of a terminal in a wireless communication system, the method comprising:

receiving, from a base station, at least one barring configuration; and

determining whether an access attempt is allowed or not based on a barring configuration corresponding to an access category of the access attempt from the at least one barring configuration, the barring configuration including information for a barring factor and information for a barring time,

wherein, in case that the access attempt is categorized into both a first standardized access category included in standardized access categories and a non-standardized access category associated with an operator classification, the first standardized access category included in the standardized access categories is applied to the access category of the access attempt,

wherein the first standardized access category is a predetermined standardized access category including an access category associated with an emergency,

wherein, in case that the access attempt is categorized into both a second standardized access category included in the standardized access categories and the non-standardized access category associated with the operator classification, the non-standardized access category associated with the operator classification is applied to the access category of the access attempt, wherein the second standardized access category is not the predetermined standardized access category included in the standardized access categories, and

wherein the access attempt is determined to be allowed in case that a random value is lower than the barring factor.

6. The method of claim 5 , wherein the non-standardized access category associated with the operator classification is defined based on a slicing type or an application.

7. The method of claim 5 , wherein in case that the access attempt is determined to be barred, the access attempt is considered as barred during a timer value determined based on the barring time.

8. The method of claim 5 , wherein the access attempt is categorized into at least one standardized access category.

Priority Claims (4)
KR 10-2017-0098553 · Aug 3, 2017 · national
KR 10-2018-0001960 · Jan 5, 2018 · national
KR 10-2018-0003416 · Jan 10, 2018 · national
KR 10-2018-0008417 · Jan 23, 2018 · national
Continuity (2)
Continuation 16054517 · Aug 3, 2018
Related Publication 20220159779A1 · May 19, 2022
References Cited (87)
US 20120040643A1 · Diachina et al. · 2012 [cited by applicant]
US 20130148490A1 · Yi et al. · 2013 [cited by applicant]
US 20130242859A1 · Celik et al. · 2013 [cited by applicant]
US 20140036794A1 · Koc et al. · 2014 [cited by applicant]
US 20140044029A1 · Chou et al. · 2014 [cited by applicant]
US 20150004924A1 · Kim et al. · 2015 [cited by applicant]
US 20150036489A1 · Rajadurai et al. · 2015 [cited by applicant]
US 20150111520A1 · Hsu · 2015 [cited by applicant]
US 20150223146A1 · Pinheiro et al. · 2015 [cited by applicant]
US 20160014672A1 · Jang et al. · 2016 [cited by applicant]
US 20160219493A1 · Kim et al. · 2016 [cited by applicant]
US 20170013498A1 · Yi et al. · 2017 [cited by applicant]
US 20170013501A1 · Kim et al. · 2017 [cited by applicant]
US 20170019820A1 · Das · 2017 [cited by applicant]
US 20170064534A1 · Loehr et al. · 2017 [cited by applicant]
US 20170201939A1 · Lee et al. · 2017 [cited by applicant]
US 20170094525A1 · Salkini et al. · 2017 [cited by applicant]
US 20170318496A1 · Yi et al. · 2017 [cited by applicant]
US 20180020382A1 · Kim et al. · 2018 [cited by applicant]
US 20180213435A1 · Kim et al. · 2018 [cited by applicant]
US 20180359681A1 · Futaki · 2018 [cited by applicant]
US 20190097936A1 · Yang et al. · 2019 [cited by applicant]
US 20190116521A1 · Qiao et al. · 2019 [cited by applicant]
US 20190174392A1 · Chun · 2019 [cited by examiner]
US 20190200273A1 · Pedersen et al. · 2019 [cited by applicant]
US 20200077299A1 · Wu et al. · 2020 [cited by applicant]
US 20200187092A1 · Lindheimer et al. · 2020 [cited by applicant]
CN 102625421A · 2012 [cited by applicant]
CN 102905388A · 2013 [cited by applicant]
CN 103581861A · 2014 [cited by applicant]
CN 104137612A · 2014 [cited by applicant]
CN 106664596A · 2017 [cited by applicant]
CN 106921996A · 2017 [cited by applicant]
EP 2809102A1 · 2014 [cited by applicant]
EP 3300431A1 · 2018 [cited by applicant]
KR 1020160130405A · 2016 [cited by applicant]
KR 1020180007697A · 2018 [cited by applicant]
TW 201703489A · 2017 [cited by applicant]
WO 2012155597A1 · 2012 [cited by applicant]
WO 2015035591A1 · 2015 [cited by applicant]
WO 2016003140A1 · 2016 [cited by applicant]
WO 2016184500A1 · 2016 [cited by applicant]
WO 2016190639A1 · 2016 [cited by applicant]
WO 2017017890A1 · 2017 [cited by applicant]
WO 2018142203A1 · 2018 [cited by applicant]
Indian Office Action dated Apr. 6, 2022, issued in a counterpart Indian Application No. 202037025247. [cited by applicant]
Chinese Office Action dated May 30, 2022, issued in a counterpart Chinese Application No. 201980007804.5. [cited by applicant]
CATT; Introduction of DEFLATE based UDC Solution; 3GPP TSG-RAN2 Meeting #100; R2-1714278; Dec. 1, 2017, Reno, USA. [cited by applicant]
International Search Report dated Nov. 20, 2018, issued in International Application No. PCT/KR2018/008855. [cited by applicant]
LG Electronics Inc., ‘Supporting IMS Emergency services in NR’, R2-1707179, 3GPP TSG-RAN WG2 Meeting NR AH#2, Qingdao, China, Jun. 16, 2017, See section 2. [cited by applicant]
International Search Report dated Apr. 19, 2019, issued in an International application No. PCT/KR2019/000395. [cited by applicant]
3GPP; TSGRAN; E-UTRA and NR; Service Data Adaptation Protocol (SDAP) specification (Release 15)', 3GPP TS 37.324 V1.1.1, Sections 4-6; and Figure 4.2.2-1; Nov. 16, 2017. [cited by applicant]
Asustek, ‘Discussion on changing presence of SDAP header’, R2-1712207, 3GPP TSG-RAN WG2 Meeting #100, Section 2, Nov. 16, 2017; Reno, USA. [cited by applicant]
LG Electronics Inc., ‘Configurability for the presence of SDAP header’, R2-1713659, 3GPP TSG-RAN2 Meeting #100, Section 2; Nov. 17, 2017; Reno, USA. [cited by applicant]
3GPP; TSGRAN; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15) 3GPP TS 38.300 V15.0.0, Sections 6.4-6.6; Jan. 4, 2018. [cited by applicant]
A U.S. Notice of Allowance dated Oct. 2, 2020, issued by the U.S. Patent and Trademark Office; U.S. Appl. No. 16/244,655. [cited by applicant]
Extended European Search Report dated Oct. 1, 2020, issued in a counterpart European Application No. 19738121.3-1212. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification (Release 15)”, 3GPP Standard; Technical Specification; 3GPP TS 38.323, 3… [cited by applicant]
Nokia Alcatel-Lucent Shanghai Bell: “Soap header”, 3GPP Draft; R2-1702644 Soap Header, 3rd Generation Partnership Project (3GPP), vol. RAN WG2, No. XP051253235; Mar. 24, 2017, Spokane, USA. Retrieved from the Internet: … [cited by applicant]
Qualcomm Incorporated: “SOAP header hardware implications”, 3GPP Draft; R2-1713727, 3rd Generation Partnership Project (3GPP), vol. RAN WG2, No. XP051372385; Nov. 17, 2017, Reno, USA. Retrieved from the Internet: URL: h… [cited by applicant]
VIVO: “Discussion on the SOAP header format”, 3GPP Draft; R2-1704594_DISCUSSION On the SOAP Header Format, 3rd Generation Partnership Project (3GPP), vol. RAN WG2, No. XP051275149; May 14, 2017, Hangzhou, China. Retriev… [cited by applicant]
Korean Office Action dated Jun. 15, 2021, issued in a counterpart Korean Application No. 10-2017-0098553. [cited by applicant]
Chinese Office Action dated Sep. 24, 2021, issued in a counterpart Chinese Application No. 201880050623.6. [cited by applicant]
Chinese Office Action dated Jan. 28, 2021, issued in a counterpart Chinese Application No. 201980007804.5. [cited by applicant]
Extended European Search Report dated Mar. 25, 2021, issued in a counterpart European Application No. 18842264.6-1212/3649805. [cited by applicant]
European Office Action dated Apr. 19, 2021, issued in a counterpart European Application No. 19 738 121.3-1212. [cited by applicant]
ERICSSON: “Access Control for NR”, 3GPP Draft; R2-1702865 Access Control for NR, 3rd Generation Partnership Project (3GPP), vol. RAN WG2, No. XP051244845; Apr. 3, 2017, Spokane, USA. Retrieved from the Internet: URL: ht… [cited by applicant]
Intel Corporation: “5G access control mechanism”, 3GPP Draft; R2-1707046_NR_ACCESS_CONTROL, 3rd Generation Partnership Project (3GPP), vol. RAN WG2, No. XP051307295; Jun. 17, 2017, Qingdao, China Retrieved from the Inte… [cited by applicant]
Qualcomm Incorporated: “Unified Access Control in different RRC Modes”, 3GPP Draft; R2-1706890_NR_ACCESS_CONTROL, 3rd Generation Partnership Project (3GPP), vol. RAN WG2, No. XP051307185; Jun. 17, 2017, Qingdao, China. … [cited by applicant]
LG Electronics Inc: “Access category based access barring for RRCJDLE and RRCJNACTIVE”, 3GPP Draft; R2-1707138 Category Based Access Barring in Idle and Inactive, 3rd Generation Partnership Project (3GPP), vol. RAN WG2,… [cited by applicant]
Mediatek Inc: “Discussion on Unified Access Control in 5GS”, 3GPP Draft; C1-171579 Unified Access Control in 5GS, 3rd Generation Partnership Project (3GPP), vol. CT WG1, No. XP051241722; Apr. 2, 2017, Spokane (WA), USA.… [cited by applicant]
Qualcomm Incorporated: “SDAP header excluded from PDCP ciphering”, 3GPP Draft; R2-1710906, 3rd Generation Partnership Project (3GPP), vol. RAN WG2, No. XP051354400; Sep. 28, 2017, Prague, Czech Republic. Retrieved from … [cited by applicant]
U.S. Office Action dated Jan. 19, 2022, issued by the U.S. Appl. No. 17/128,867. [cited by applicant]
Korean Office Action dated Nov. 10, 2021, issued in a counterpart Korean Application No. 10-2018-0008417. [cited by applicant]
3GPP TS 22.261 V15.3.0 (2017-12) 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for the 5G system; Stage 1. [cited by applicant]
Indian Hearing Notice dated Jul. 4, 2023, issued in Indian Patent Application No. 202037025247. [cited by applicant]
“3 Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification (Release 14)”, 3GPP Stand… [cited by applicant]
Huawei et al., “CR on UDC functionality in PDCP layer”, 3GPP Draft; R2-1712723, 3GPP TSG-RAN2 Meeting #100, Reno, Nevada, Nov. 17, 2017, XP051371629. [cited by applicant]
Huawei et al., “Discussion on UDC functionality in PDCP layer”, 3GPP Draft; R2-1712722, 3GPP TSG RAN2 Meeting #100, Reno, Nevada, Nov. 17, 2017, XP051371628. [cited by applicant]
Extended European Search Report dated Feb. 21, 2023, issued in European Patent Application No. 22196560.1. [cited by applicant]
Intel, 5G Access Control, 3GPP Draft, C1-172291, 3GPP TSG CT WG1 Meeting #104, May 14, 2017, XP051270531. [cited by applicant]
European Office Action dated May 17, 2024, issued in European Patent Application No. 18842264.6. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification (Release 15), 3GPP TS 38.323 V15.1.0 (Mar. 2018), Apr. 2, 2018, pp. 1-25,… [cited by applicant]
Samsung, Changes to delay budget reporting related to ASN.1 review, R2-1705496, 3GPP TSG-RAN2 Meeting #98, May 8, 2017. [cited by applicant]
Zhuo Chen, Status Report for WI Core part: Voice and Video Enhancement for LTE, RP-170803, 3GPP TSG RAN meeting #75, Mar. 10, 2017. [cited by applicant]
European Office Action dated Aug. 30, 2024, issued in European Patent Application No. 22196560.1. [cited by applicant]
Chinese Office Action dated Aug. 19, 2024, issued in Chinese Patent Application No. 202211441326.9. [cited by applicant]
Cited By (1)
US 12,676,701