IP Library › Granted Patent US 12,294,934
Granted Patent B2
US 12,294,934 · App. 17/762,499 · Granted May 6, 2025

Method and apparatus for access or RAT restriction

Inventors: Jinyin Zhu (Shanghai, CN); Xiaoming Li (Shanghai, CN); Jesús Ángel de Gregorio Rodríguez (Madrid, ES)
Assignee: Telefonaktiebolaget LM Ericsson (publ)
H04W48/04H04W8/04H04W48/16H04W60/04H04W60/06
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,294,934
App. No.
17/762,499
Granted
May 6, 2025
Kind
B2
Abstract

Embodiments of the present disclosure provide method and apparatus for access or RAT restriction. A method at a first access management entity of a network comprises determining that a user equipment (UE) is using LTE-M radio access technology (RAT). The method further comprises obtaining access restriction or RAT restriction data associated with the UE, wherein the access restriction or RAT restriction data indicates that LTE-M RAT type is restricted. The method further comprises determining whether the UE using LTE-M is allowed to attach or register to the network based on the obtained access restriction or RAT restriction data associated with the UE.

Claims (61)

1. A method performed by a first access management entity of a network, comprising:

determining whether a user equipment (UE) is using LTE-M radio access technology (RAT);

obtaining access restriction or RAT restriction data associated with the UE, wherein the access restriction or RAT restriction data includes first information indicating whether the UE is allowed to use the LTE-M RAT type and second information indicating whether the UE is allowed to use a WB-E-UTRAN RAT type other than the LTE-M RAT type; and

determining whether the UE is allowed to attach or register to the network based on the obtained access restriction or RAT restriction data associated with the UE;

wherein the access restriction or RAT restriction data indicating whether the UE is allowed to use the LTE-M RAT type is a second bit and the access restriction or RAT restriction data indicating whether the UE is allowed to use a WB-E-UTRAN RAT type other than the LTE-M RAT is a third bit, and wherein the second bit and the third bit are only used when a first bit for indicating whether the WB-E-UTRAN RAT type is not allowed is not set.

2. The method of claim 1 , wherein when the first information indicates that the UE is not allowed to use the LTE-M RAT type, the UE using LTE-M is not allowed to attach or register to the network.

3. The method of claim 1 , wherein when the UE is not allowed to attach or register to the network, the method further comprises:

sending a deregistration request or a detach request to the UE when UE has registered or attached to the network; or

sending a registration reject or an attach reject or a tracking area update (TAU) reject to the UE during a registration procedure or an attach procedure or a TAU procedure.

4. The method of claim 1 , wherein the access restriction or RAT restriction data is obtained from at least one of a subscription data entity of the network;

a second access management entity of the network; or

a second access management entity of another network.

5. The method of claim 1 , wherein the first access management entity is a mobility management entity (MME), the method further comprising:

receiving an attach request or a tracking area update (TAU) request from a UE;

sending an update location request to a home subscriber server (HSS); and

receiving an update location answer from the HSS, wherein the update location answer includes the access restriction or RAT restriction data associated with the UE.

6. The method of claim 1 , wherein the first access management entity is a mobility management entity (MME), the method further comprising:

receiving an insert subscriber data request from a home subscriber server (HSS); and

sending an insert subscriber data answer to the HSS, wherein the insert subscriber data request includes the access restriction or RAT restriction data associated with the UE.

7. The method of claim 1 , wherein the first access management entity is an access and mobility function (AMF), the method further comprising:

receiving a registration request from the UE;

sending a Nudm_SDM_get request to a unified data management (UDM); and

receiving a Nudm_SDM_get response including the access restriction or RAT restriction data associated with the UE from the UDM.

8. The method of claim 1 , wherein the first access management entity is an access and mobility function (AMF), the method further comprising:

receiving an Nudm_SDM_Notification including the access restriction or RAT restriction data associated with the UE from a unified data management (UDM).

9. The method of claim 1 , wherein the first access management entity is a new access and mobility function (AMF), the method further comprising:

receiving a registration request from the UE;

sending an Namf_Communication_UEContextTransfer request for getting a UE context for the UE context to an old AMF; and

receiving an Namf_Communication_UEContextTransfer response including the access restriction or RAT restriction data associated with the UE from the old AMF.

10. A method performed by a subscription data entity, comprising:

obtaining access restriction or radio access technology (RAT) restriction data associated with a user equipment (UE), wherein the access restriction or RAT restriction data includes first information indicating whether the UE is allowed to use an LTE-M RAT type and second information indicating whether the UE is allowed to use a WB-E-UTRAN RAT type other than the LTE-M RAT type; and

sending the access restriction or RAT restriction data associated with the UE to a first access management entity of a network;

wherein the access restriction or RAT restriction data indicating whether the UE is allowed to use the LTE-M RAT type is a second bit and the access restriction or RAT restriction data indicating whether the UE is allowed to use a WB-E-UTRAN RAT type other than the LTE-M RAT is restricted is a third bit, and wherein the second bit and the third bit are only used when a first bit for indicating whether the WB-E-UTRAN RAT type is not allowed is not set.

11. The method of claim 10 , wherein when the first information indicates that the UE is not allowed to use the LTE-M RAT type, the UE using LTE-M is not allowed to attach or register to the network.

12. The method of claim 10 , wherein the first access management entity is a mobility management entity (MME) and the subscription data entity is a home subscriber server (HSS), the method further comprising:

receiving an update location request from the MME; and

sending an update location answer including the access restriction or RAT restriction data associated with the UE to the MME.

13. The method of claim 12 , wherein the update location request includes information indicating that the MME supports restriction related to the LTE-M RAT type and the update location answer includes information indicating that the HSS supports restriction related to the LTE-M RAT type.

14. The method of claim 10 , wherein the first access management entity is a mobility management entity (MME) and the subscription data entity is a home subscriber server (HSS), the method further comprising:

determining a change of the restriction related to the LTE-M RAT type; and

sending an insert subscriber data request including the access restriction or RAT restriction data associated with the UE to the MME.

15. The method of claim 14 , wherein the insert subscriber data request includes information indicating that the HSS supports restriction related to the LTE-M RAT type and the insert subscriber data answer includes information indicating that the MME supports restriction related to the LTE-M RAT type.

16. The method of claim 10 , wherein the first access management entity is an access and mobility function (AMF) and the subscription data entity is a unified data management (UDM), the method further comprising:

receiving a Nudm_SDM_get request from AMF; and

sending a Nudm_SDM_get response including the access restriction or RAT restriction data associated with the UE to the AMF.

17. The method of claim 10 , wherein the first access management entity is an access and mobility function (AMF) and the subscription data entity is a unified data management (UDM), the method further comprising:

determining a change of the restriction related to the LTE-M RAT type; and

sending an Nudm_SDM_Notification including the access restriction or RAT restriction data associated with the UE to the AMF.

18. An apparatus in a first access management entity of a network, comprising:

a processor; and

a memory coupled to the processor, said memory containing instructions executable by said processor, whereby said apparatus is operative to:

determine whether a user equipment (UE) is using an LTE-M radio access technology (RAT);

obtain access restriction or RAT restriction data associated with the UE, wherein the access restriction or RAT restriction data includes first information indicating whether the UE is allowed to use the LTE-M RAT type and second information indicating whether the UE is allowed to use a WB-E-UTRAN RAT type other than the LTE-M RAT type; and

determine whether the UE is allowed to attach or register to the network based on the obtained access restriction or RAT restriction data associated with the UE;

wherein the access restriction or RAT restriction data indicating whether the UE is allowed to use the LTE-M RAT type is a second bit and the access restriction or RAT restriction data indicating whether the UE is allowed to use a WB-E-UTRAN RAT type other than the LTE-M RAT is a third bit, and wherein the second bit and the third bit are only used when a first bit for indicating whether the WB-E-UTRAN RAT type is not allowed is not set.

19. An apparatus in a subscription data entity, comprising:

a processor; and

a memory coupled to the processor, said memory containing instructions executable by said processor, whereby said apparatus is operative to:

obtain access restriction or radio access technology (RAT) restriction data associated with a user equipment (UE), wherein the access restriction or RAT restriction data includes first information indicating whether the UE is allowed to use an LTE-M RAT type and second information indicating whether the UE is allowed to use a WB-E-UTRAN RAT type other than the LTE-M RAT type; and

send the access restriction or RAT restriction data associated with the UE to a first access management entity of a network;

wherein the access restriction or RAT restriction data indicating whether the UE is allowed to use the LTE-M RAT type is a second bit and the access restriction or RAT restriction data indicating whether the UE is allowed to use a WB-E-UTRAN RAT type other than the LTE-M RAT is restricted is a third bit, and wherein the second bit and the third bit are only used when a first bit for indicating whether the WB-E-UTRAN RAT type is not allowed is not set.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 22, 2022
From: ZHU, JINYIN; LI, XIAOMING; DE GREGORIO RODRÍGUEZ, JESÚS ÁNGEL
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 059339/0109 →
Priority Claims (1)
WO PCT/CN2019/108589 · Sep 27, 2019 · international
Continuity (1)
Related Publication 20220338099A1 · Oct 20, 2022
References Cited (35)
US 20180054796A1 · Edge · 2018 [cited by applicant]
US 20180103426A1 · Nacer et al. · 2018 [cited by applicant]
US 20190182897A1 · Jain · 2019 [cited by examiner]
US 20200059888A1 · Cui · 2020 [cited by examiner]
US 20210014685A1 · Betti · 2021 [cited by examiner]
US 20210204180A1 · Chun · 2021 [cited by applicant]
US 20210409942A1 · De Kievit · 2021 [cited by examiner]
US 20220201638A1 · Arrobo Vidal · 2022 [cited by examiner]
CN 101511076A · 2009 [cited by applicant]
CN 102845085A · 2012 [cited by applicant]
CN 108347744A · 2018 [cited by applicant]
WO 2018172408A1 · 2018 [cited by applicant]
WO 2019074325A1 · 2019 [cited by applicant]
Unknown, Author, “Reply LS on Differentiation of LTE-M (eMTC) traffic from other LTE data traffic”, 3GPP TSG-RAN WG3#100, R3-182550, Busan, South Korea, May 21-25, 2018, pp. 1-2. [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (… [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (… [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Access and Mobility Management Services; Stage 3 (Release 15)”, 3GPP TS 29.518 V15.3.0, Mar. 2019, pp. 1-1… [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Common Data Types for Service Based Interfaces; Stage 3 (Release 15)”, 3GPP TS 29.571 V15.3.0, Mar. 2019, … [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Common Data Types for Service Based Interfaces; Stage 3 (Release 16)”, 3GPP TS 29.571 V16.0.0, Jun. 2019, … [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Session Management Services; Stage 3 (Release 16)”, 3GPP TS 29.502 V16.0.0, Jun. 2019, pp. 1-164. [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Unified Data Management Services; Stage 3 (Release 15)”, 3GPP TS 29.503 V15.3.0, Mar. 2019, pp. 1-187. [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Unified Data Management Services; Stage 3 (Release 16)”, 3GPP TS 29.503 V16.0.0, Jun. 2019, pp. 1-205. [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related Interfaces… [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related Interfaces… [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for non-3GPP accesses (Release 16)”, 3GPP TS 23.402 V16.0.0, Jun. 2019, pp. 1-314. [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) ac… [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) ac… [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 16)”, 3GPP TS 23.502 V16.5.1, Aug. 2020, pp. 1-594. [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 16)”, 3GPP TS 23.502 V16.1.1, Jun. 2019, pp. 1-495. [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System (5GS); Stage 2 (Release 16)”, 3GPP TS 23.501 V16.2.0, Sep. 2019, pp. 1-391. [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16)”, 3GPP TS 23.501 V16.6.0, Sep. 2020, pp. 1-447. [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 16)”, 3GPP TS 23.501 V16.1.0, Jun. 2019, pp. 1-368. [cited by applicant]
QUALCOMM Incorporated , “LTE-M identification in 5GC”, SA WG2 Meeting #133, S2-1905276, (was S2-190xxxx), Reno, NV, USA, May 13-17, 2019, pp. 1-2. [cited by applicant]
3GPP , “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) ac… [cited by applicant]
Unknown, Author , “Draft Report of SA WG2 meetings #126”, SA WG2 Meeting #126 Draft Report, Montreal, Canada, Version 0.0.5, Feb. 26-Mar. 2, 2018, 1-595. [cited by applicant]