Granular network access control and methods thereof

• US 10,003,996 B2
• Filed: 05/19/2017
• Issued: 06/19/2018
• Est. Priority Date: 03/21/2012
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Rajadurai, Rajavelsamy, Jamadagni, Satish Nanjunda Swamy
• Primary Examiner(s): Cattungal, Ajay
• Application Number:
  US15/600,145
• Publication Number:
  US 20170257791A1
• Time in Patent Office: 396 Days
• CPC Class Codes: H04L 47/2475 for supporting traffic characterised by the type of applications
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 28/0205 at the air interface dynamic wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 28/0215 based on user or device properties, e.g. MTC-capable devices services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51
• CPC Class Codes: H04W 28/0289 Congestion control load shedding arrangements in network planning H04W16/08; performing reselection for handling the traffic H04W36/22; wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 4/00 Services specially adapted for wireless communication networks; Facilities therefor
• CPC Class Codes: H04W 48/02 Access restriction performed under specific conditions

Abstract

A method and system that enhances the existing access barring mechanism as specified in the current 3GPP specification is disclosed. The method disclosed provides enhancing the access barring mechanism to accommodate application level barring between the User equipment (UE) and the network. The method disclosed individually restricts or permits access of network to every requesting application on the UE, based on granular category of the application and priority levels of the application within the granular category. The method disclosed also specifies handling of back-off timers; reject cause values and Access Point Name (APN) configuration by Access Stratum (AS) and Non Access Stratum (NAS) layer to support application level barring of UEs using the enhanced access barring mechanism. The enhanced access barring mechanism enables providing service to applications independent of other barred applications or priorities. The method disclosed provides a mechanism for access control for connected mode UEs.

Claims

1. A method by a base station, the method comprises:

determining a system information block (SIB) including an application category to be barred and a value related to a barring timer; and

transmitting the SIB to the terminal,

wherein, if a service request for an application is triggered, whether a category of the requested application belongs to the application category to be barred is checked,

wherein whether the service request is to be held is determined in response to the checking result, and

wherein the service request is held until the barring timer is expired.

2. The method of claim 1,

wherein the service request is held until the barring timer is expired, if the category of the requested application belongs to the application category to be barred and the requested application is running, and

wherein the application category to be barred includes at least one of an application category, a traffic category, a quality of service (QoS) category, a bearer type category, a logical channel group category, or a priority level category.

3. The method of claim 1, wherein the value related to the barring timer is determined based on a priority level of the category of the requested application.

4. The method of claim 1, wherein the service request for the application is processed if the category of the application does not belong to the application category to be barred.

5. The method of claim 1, wherein the service request is transmitted via at least one of an explicit service request message, a packet data network (PDN) connectivity request, a bearer resource modification request, a scheduling request (SR), a buffer status report (BSR) message or a bearer resource allocation request.

6. A base station, the base station comprising:

a transceiver; and

at least one processor configured to;

determine a system information block (SIB) including an application category to be barred and a value related to a barring timer; and

transmit the SIB to the terminal,

wherein, if a service request for an application is triggered, whether a category of the requested application belongs to the application category to be barred is checked,

wherein whether the service request is to be held is determined in response to the checking result, and

wherein the service request is held until the barring timer is expired.

7. The base station of claim 6,

wherein the service request is held until the barring timer is expired, if the category of the application belongs to the application category to be barred and the requested application is running, and

wherein the application category to be barred includes at least one of an application category, a traffic category, a quality of service (QoS) category, a bearer type category, a logical channel group category, or a priority level category.

8. The base station of claim 6, wherein the value related to the barring timer is determined based on a priority level of the category of the application.

9. The base station of claim 6, wherein the service request for the application is processed if the category of the application does not belong to the application category to be barred.

10. The base station of claim 6, wherein the service request is transmitted via at least one of an explicit service request message, a packet data network (PDN) connectivity request, a bearer resource modification request, a scheduling request (SR), a buffer status report (BSR) message, or a bearer resource allocation request.

11. A method by a terminal, the method comprising:

receiving a system information block (SIB) including an application category to be barred and a value related to a barring timer from a network;

identifying, if a service request for an application is triggered, a category of the requested application;

checking whether the category of the requested application belongs to the application category to be barred;

determining whether the terminal holds the service request in response to the checking result; and

holding the service request until the barring timer is expired.

12. The method of claim 11, further comprising:

holding the service request until the barring timer is expired, if a category of the requested application belongs to the application category to be barred and the application is running,

wherein the application category to be barred includes at least one of an application category, a traffic category, a quality of service (QoS) category, a logical channel group category, a bearer type category, or a priority level category, and

wherein the value related to the barring timer is determined based on a priority level of the category of the application.

13. The method of claim 11, further comprising:

mapping each application in the terminal to the application category to be barred; and

processing the service request for the application if the category of the application does not belong to the application category to be barred,

wherein the service request is transmitted via at least one of an explicit service request message, a packet data network (PDN) connectivity request, a bearer resource modification request, a scheduling request (SR), a buffer status report (BSR) message, or a bearer resource allocation request.

14. A terminal comprising:

a transceiver; and

at least one processor configured to;

receive a system information block (SIB) including an application category to be barred and a value related to a barring timer from a network,

identify, if a service request for an application is triggered, a category of the requested application,

check whether the category of the requested application belongs to the application category to be barred,

determine whether the terminal holds the service request in response to the checking result, and

hold the service request until the barring timer is expired.

15. The terminal of claim 14,

wherein the at least one processor is further configured to hold the service request until the barring timer is expired, if a category of the requested application belongs to the application category to be barred and the application is running,

wherein the application category to be barred includes at least one of an application category, a traffic category, a quality of service (QoS) category, a logical channel group category, a bearer type category, or a priority level category, and

wherein the value related to the barring timer is determined based on a priority level of the category of the application.

16. The terminal of claim 14, wherein the at least one processor is further configured to:

map each application in the terminal to the barred category; and

process the service request for the application if the category of the application does not belong to the application category to be barred,

wherein the service request is transmitted via at least one of an explicit service request message, a packet data network (PDN) connectivity request, a bearer resource modification request, a scheduling request (SR), a buffer status report (BSR) message, or a bearer resource allocation request.