# US 2019/0320381 A1 · Apparatuses and methods for handling access type restriction information

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0320381 A1
- Document ID: US20190320381A1
- Status: Published application
- Kind: A1
- Application number: 16/385,261
- Filed: 2019-04-16
- Published: 2019-10-17
- Earliest claimed: 2018-04-17
- Assignees: MediaTek Singapore Pte. Ltd.
- Applicants: MediaTek Singapore Pte. Ltd.
- Inventors: Marko Niemi; Matti Moisanen
- Web page: https://patentgrep.com/patent/US20190320381A1

## CPC

- H04W 48/02: Access restriction performed under specific conditions
- H04W 48/16: Discovering, processing access restriction or access information
- H04W 8/08: Mobility data transfer
- H04W 8/183: {Processing at user equipment or user record carrier}
- H04W 8/24: Transfer of terminal data
- H04W 60/00: Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W 76/11: Allocation or use of connection identifiers
- H04W 48/18: Selecting a network or a communication service
- H04W 60/001: {Registration rejection or failure}
- H04W 88/06: adapted for operation in multiple networks {or having at least two operational modes}, e.g. multi-mode terminals
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A User Equipment (UE) including a wireless transceiver and a controller is provided. The controller obtains information indicating that the UE is not allowed to access a 3GPP core network over which one or both or none of the 3GPP access network and the non-3GPP access network. Also, the controller refrains the UE from accessing the 3GPP core network over the indicated one or both of the 3GPP access network and the non-3GPP access network in response to the information indicating that the UE is not allowed to access the 3GPP core network over one or both of the 3GPP access network and the non-3GPP access network.

## Claims

### Claim 1

A User Equipment (UE), comprising:
a wireless transceiver, configured to perform wireless transmission and reception to and from one or both of a 3rd Generation Partnership Project (3GPP) access network and a non-3GPP access network; and
a controller, configured to obtain information indicating that the UE is not allowed to access a 3GPP core network over which one or both or none of the 3GPP access network and the non-3GPP access network, and refrain the UE from accessing the 3GPP core network over the indicated one or both of the 3GPP access network and the non-3GPP access network in response to the information indicating that the UE is not allowed to access the 3GPP core network over one or both of the 3GPP access network and the non-3GPP access network.

### Claim 2 (depends on 1)

The UE of claim 1, wherein the refraining of the UE from accessing the 3GPP core network over the indicated one or both of the 3GPP access network and the non-3GPP access network comprises: disabling an N1 mode capability of the UE for the indicated one or both of the 3GPP access network and the non-3GPP access network.

### Claim 3 (depends on 1)

The UE of claim 1, wherein the controller is further configured to perform the following in response to the 3GPP core network being a 5G Core Network (5GCN) and the information indicating that the UE is not allowed to access the 3GPP core network over one or both of the 3GPP access network and the non-3GPP access network:
setting a 5GS update status to “5U3 ROAMING NOT ALLOWED”; and
deleting a 5G Globally Unique Temporary UE Identity (GUTI), a last visited registered Tracking Area Identity (TAI), a TAI list, and a Key Set Identifier for Next Generation Radio Access Network (ngKSI).

### Claim 4 (depends on 1)

The UE of claim 1, wherein the information is obtained from a response message of a registration procedure or a configuration update command received from the 3GPP core network, or from subscription data stored in the UE.

### Claim 5 (depends on 4)

The UE of claim 4, wherein the response message is a Registration Reject message of a 5G Mobility Management (MM) Registration procedure, and the information is a 5GMM cause, and the controller is further configured to reset a registration attempt counter and enter a 5GMM-DEREGISTERED state in response to the information indicating that the UE is not allowed to access the 3GPP core network over one of the 3GPP access network and the non-3GPP access network.

### Claim 6 (depends on 4)

The UE of claim 4, wherein the response message is a Registration Accept message of a 5G Mobility Management (MM) Registration procedure, and the information is a 5G registration result.

### Claim 7 (depends on 4)

The UE of claim 4, wherein the subscription data is a Universal Subscriber Identity Module (USIM) file.

### Claim 8 (depends on 4)

The UE of claim 4, wherein the controller is further configured to store the information in a Universal Subscriber Identity Module (USIM) or a memory, in response to the information being obtained from the response message or the configuration update command.

### Claim 9 (depends on 8)

The UE of claim 8, wherein the information is stored permanently or only for a period of time.

### Claim 10 (depends on 8)

The UE of claim 8, wherein the controller is further configured to determine that the information is valid until the UE is powered off, or until the USIM is changed, or until a location of the UE is changed.

### Claim 11

A method for handling access type restriction information, executed by a UE communicatively connected to a 3rd Generation Partnership Project (3GPP) core network over one or both of a 3GPP access network and a non-3GPP access network, the method comprising:
obtaining information indicating that the UE is not allowed to access the 3GPP core network over which one or both or none of the 3GPP access network and the non-3GPP access network from a response message of a registration procedure or a configuration update command received from the 3GPP core network, or from subscription data stored in the UE; and
refraining the UE from accessing the 3GPP core network over the indicated one or both of the 3GPP access network and the non-3GPP access network in response to the information indicating that the UE is not allowed to access the 3GPP core network over one or both of the 3GPP access network and the non-3GPP access network.

### Claim 12 (depends on 11)

The method of claim 11, wherein the refraining of the UE from accessing the 3GPP core network over the indicated one or both of the 3GPP access network and the non-3GPP access network comprises: disabling an N1 mode capability of the UE for the indicated one or both of the 3GPP access network and the non-3GPP access network.

### Claim 13 (depends on 11)

The method of claim 11, further comprising:
in response to the 3GPP core network being a 5G Core Network (5GCN) and the information indicating that the UE is not allowed to access the 3GPP core network over one or both of the 3GPP access network and the non-3GPP access network,
setting a 5GS update status to “5U3 ROAMING NOT ALLOWED”; and
deleting a 5G Globally Unique Temporary UE Identity (GUTI), a last visited registered Tracking Area Identity (TAI), a TAI list, and a Key Set Identifier for Next Generation Radio Access Network (ngKSI).

### Claim 14 (depends on 11)

The method of claim 11, wherein the information is obtained from a response message of a registration procedure or a configuration update command received from the 3GPP core network, or from subscription data stored in the UE.

### Claim 15 (depends on 14)

The method of claim 14, wherein the response message is a Registration Reject message of a 5G Mobility Management (MM) Registration procedure, and the information is a 5GMM cause, and the method further comprising:
resetting a registration attempt counter and entering a 5GMM-DEREGISTERED state in response to the information indicating that the UE is not allowed to access the 3GPP core network over one of the 3GPP access network and the non-3GPP access network.

### Claim 16 (depends on 14)

The method of claim 14, wherein the response message is a Registration Accept message of a 5G Mobility Management (MM) Registration procedure, and the information is a 5G registration result.

### Claim 17 (depends on 14)

The method of claim 14, wherein the subscription data is a Universal Subscriber Identity Module (USIM) file.

### Claim 18 (depends on 14)

The method of claim 14, further comprising:
storing the information in a Universal Subscriber Identity Module (USIM) or a memory, in response to the information being obtained from the response message or the configuration update command.

### Claim 19 (depends on 18)

The method of claim 18, wherein the information is stored permanently or only for a period of time.

### Claim 20 (depends on 18)

The method of claim 18, further comprising:
determining that the information is valid until the UE is powered off, or until the USIM is changed, or until a location of the UE is changed.
