Patent Description:
The concept of "Service Area Restriction", as part of the Mobility Restriction, has been present in Third Generation Partnership Project (3GPP) standards since Release <NUM> (Rel-<NUM>). However, there are some details about the Service Area Restriction that are unclear.

Document 3GPP LS S2-<NUM> represents a reply on service area restriction for CIoT 5GS optimization. The question is whether the UE using CP CIoT or UP CIoT optimization is allowed to send or receive data in a non-allowed area, including exception data. The answer is that, based on policy, the network may send downlink control plane data to a UE that is in CM-CONNECTED state and is in a non-allowed area. Various restrictions and exceptions apply to a UE in a non-allowed area.

According to the present disclosure, methods, a wireless device, a network node and a computer readable storage medium according to the independent claims are provided. Developments are set forth in the dependent claims.

Some embodiments advantageously provide methods, systems, and apparatuses for subscription based service restriction.

In one embodiment, a network node is configured to provide support for at least one service for a wireless device (WD) in a non-allowed area based at least in part on at least one of subscription data associated with the WD and operator policy.

In one embodiment, a wireless device (WD) is configured to operate in a non-allowed area using at least one service that is allowed in the non-allowed area based at least in part on at least one of subscription data and operator policy.

In one claimed aspect of the present disclosure, a method implemented in a wireless device, WD, is provided. The method includes determining that the WD is service area restricted when the WD is in an area defined as a non-allowed area according to subscription data associated with the WD; and operating in the non-allowed area using at least one service that is service area restricted in the non-allowed area based at least in part on at least one of the subscription data associated with the WD and an operator policy.

In some embodiments, the at least one service is not a regulatory prioritized service. In some embodiments, the at least one service includes at least one of a short message service, SMS, over non-access stratum, a location service and an exception reporting service. In some claimed embodiments, the method further includes obtaining information indicating whether the at least one service is allowed for the WD in the non-allowed area. In some embodiments, the information is comprised in at least one of a Nudm_SubscriberDataManagement service message and a Namf_Communication_UEContextTransfer service message.

In some embodiments, the information is included in a registration area field, the registration area field indicating whether the at least one service is allowed for the WD in the non-allowed area. In some embodiments, the information is included in a service area restriction field, the service area restriction field indicating whether the at least one service is allowed for the WD in the non-allowed area. In some embodiments, the non-allowed area is a service area in which the WD is not allowed to initiate a service request, a control plane service request and/or a session management, SM, signalling to obtain user services from a network associated with the network node. In some embodiments, operating in the non-allowed area using the at least one service when the at least one of the subscription data and the operator policy indicates that the at least one service is allowed in the non-allowed area; otherwise, operating in the non-allowed area without using the at least one service.

According to another claimed aspect of the present disclosure, a method implemented in a network node is provided. The method includes determining that a wireless device, WD, is service area restricted when the WD is in an area defined as a non-allowed area based on subscription data associated with the WD; and providing support for the WD for at least one service that is service area restricted in the non-allowed area based at least in part on at least one of the subscription data associated with the WD and an operator policy.

In some claimed embodiments, providing the support further comprises obtaining and/or sending a message indicating that the at least one service that is service area restricted is allowed for the WD in the non-allowed area. In some embodiments, the at least one service is not a regulatory prioritized service. In some embodiments, the at least one service includes at least one of a short message service, SMS, over non-access stratum, a location service and an exception reporting service. In some embodiments, the message is a Namf_Communication_UEContextTransfer service message. In some embodiments, the message includes a registration area field, the registration area field indicating whether the at least one service is allowed for the WD in the non-allowed area.

In some embodiments, the message is a Nudm_SubscriberDataManagement service message. In some embodiments, the message includes a service area restriction field, the service area restriction field indicating whether the at least one service is allowed for the WD in the non-allowed area. In some embodiments, the network node is one of an access and mobility function, AMF, node and a unified data management, UDM, node. In some embodiments, the non-allowed area is a service area in which the WD is not allowed to initiate a service request, a control plane service request and/or a session management, SM, signalling to obtain user services from a network associated with the network node. In some embodiments, providing support for the WD for the at least one service in the non-allowed area when the at least one of the subscription data and the operator policy indicates that the at least one service is allowed in the non-allowed area; otherwise, restricting the WD from using the at least one service in the non-allowed area.

According to yet another aspect, a wireless device, WD, configured to communicate with a network node is provided. The WD comprises processing circuitry configured to cause the WD to perform any one or more of the WD methods above.

According to yet another aspect, a network node is provided. The network node comprises processing circuitry configured to cause the network node to perform any one or more of the network node methods above.

According to yet another aspect, a computer readable storage medium is provided. The computer readable storage medium comprises computer instructions executable by at least one processor to perform any one or more of the WD methods above.

According to yet another aspect, a computer readable storage medium is provided. The computer readable storage medium comprises computer instructions executable by at least one processor to perform any one or more of the network node methods above.

According to yet another aspect, a system comprising processing circuitry is provided. The processing circuitry is configured to cause the system to determine that a wireless device, WD, is service area restricted when the WD is in an area defined as a non-allowed area according to subscription data associated with the WD; provide support for the WD for at least one service that is service area restricted in the non-allowed area based at least in part on at least one of the subscription data associated with the WD and an operator policy; and as a result of the support, allow the WD to operate in the non-allowed area using the at least one service.

As discussed above, the concept of "Service Area Restriction", as part of the Mobility Restriction, has been present in 3GPP wireless communication standards since Rel-<NUM>. However, there are some details that are not clear. For example, it is not clear what services may be allowed and what services may not be allowed in an area (so called "Non-Allowed Area"), especially for the services carried out via the signaling such as, e.g., short message service (SMS) and Location service (LS).

The 3GPP has also defined that a wireless device (WD), such as a user equipment (UE), may send "Exception Reporting/Data" even in cases where a certain data rate limit is reached. However, it is not clear if such "Exception Reporting/data" is to be allowed or not in a Non-Allowed Area.

Some embodiments propose to introduce control parameters in the subscription data for the services related to, for example, SMS, Location Service and Exception data reporting.

Some advantages of proposed embodiments include providing a per WD/UE level control, and providing an arrangement that works well with the local serving network policy control. Some embodiments provide a solution with backwards compatibility.

Before describing in detail example embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to subscription based service restriction. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

The term "network node" used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), relay node, integrated access and backhaul (IAB), donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term "radio node" used herein may be used to also denote a wireless device (WD) such as a wireless device (WD) or a radio network node.

It can be any kind of a radio network node which may comprise any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell/multicast Coordination Entity (MCE), IAB, relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

Some embodiments provide arrangements in which a service that is "service area restricted" may be allowed on a per WD/subscription or operator policy basis; which may be distinguished from services like emergency services and other regulatory prioritized services that can be used by the WD <NUM> in non-allowed areas. In other words, some embodiments provide arrangements for one or more specific services that are "service area restricted" generally but can nevertheless override the restriction and be used in the non-allowed area if so indicated in the subscription information for the particular WD and/or per operator policy, as opposed to a regulatory requirement.

In some embodiments, the "support" to be provided to a WD for at least one service, as described herein may be considered support from a network, such as a core network from one or more core network nodes, such as AMF, UDM, SMF, etc..

In some embodiments, the term "obtain" or "obtaining" is used herein and may indicate obtaining in e.g., memory such as in the case where the information is e.g., predefined. The term "obtain" or "obtaining" as used herein may also indicate obtaining by receiving signaling indicating the information obtained.

The term "signaling" used herein may comprise any of: high-layer signaling (e.g., via Radio Resource Control (RRC) or a like), lower-layer signaling (e.g., via a physical control channel or a broadcast channel), or a combination thereof. The signaling may be implicit or explicit. The signaling may further be unicast, multicast or broadcast. The signaling may also be directly to another node or via a third node.

Receiving (or obtaining) information may comprise receiving one or more information messages (e.g., an RRC or NAS message). It may be considered that receiving control signaling comprises demodulating and/or decoding and/or detecting one or more messages, in particular a message carried by the control signaling, e.g. based on an assumed set of resources, which may be searched and/or listened for the control information. It may be assumed that both sides of the communication are aware of the configurations, and may determine the set of resources, e.g. based on the reference size.

Signaling may generally comprise one or more symbols and/or signals and/or messages. A signal may comprise or represent one or more bits. An indication may represent signaling, and/or be implemented as a signal, or as a plurality of signals. One or more signals may be included in and/or represented by a message. Signaling, in particular control signaling, may comprise a plurality of signals and/or messages, which may be transmitted on different carriers and/or be associated to different signaling processes, e.g. representing and/or pertaining to one or more such processes and/or corresponding information. An indication may comprise signaling, and/or a plurality of signals and/or messages and/or may be comprised therein, which may be transmitted on different carriers and/or be associated to different acknowledgement signaling processes, e.g. representing and/or pertaining to one or more such processes. Signaling associated to a channel may be transmitted such that represents signaling and/or information for that channel, and/or that the signaling is interpreted by the transmitter and/or receiver to belong to that channel. Such signaling may generally comply with transmission parameters and/or format/s for the channel.

An indication (e.g., an indication of whether one or more services is allowed for a WD within a non-allowed area per the WD's/operator's subscription data/information, etc.) generally may explicitly and/or implicitly indicate the information it represents and/or indicates. Implicit indication may for example be based on position and/or resource used for transmission. Explicit indication may for example be based on a parametrization with one or more parameters, and/or one or more index or indices corresponding to a table, and/or one or more bit patterns representing the information.

Some embodiments provide for subscription based service restriction.

Referring now to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in <FIG> a schematic diagram of a communication system <NUM>, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and/or NR (<NUM>), which comprises an access network <NUM>, such as a radio access network, and a core network <NUM>. The access network <NUM> comprises a plurality of network nodes 16a, 16b, 16c, 16d (referred to collectively as network nodes <NUM>), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas <NUM>). Each network node 16a, 16b, 16c is connectable to the core network <NUM> over a wired or wireless connection <NUM>. Network node 16d may be a network node of the core network <NUM>, such as a mobility node (e.g., MME, AMF, etc.), a data management node (e.g., unified data management (UDM) node), or other core network node. A first wireless device (WD) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second WD 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of WDs 22a, 22b (collectively referred to as wireless devices <NUM>) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole WD is in the coverage area or where a sole WD is connecting to the corresponding network node <NUM>. Note that although only two WDs <NUM> and three network nodes <NUM> are shown for convenience, the communication system may include many more WDs <NUM> and network nodes <NUM>.

A network node <NUM> is configured to include an indication unit <NUM> which is configured to provide support for at least one service for a WD <NUM> in a non-allowed area based at least in part on at least one of subscription data associated with the WD <NUM> and operator policy.

A wireless device <NUM> is configured to include an operation unit <NUM> which is configured to operate in a non-allowed area using at least one service that is allowed in the non-allowed area based at least in part on at least one of subscription data and operator policy.

Example implementations, in accordance with an embodiment, of the WD <NUM> and network node <NUM> discussed in the preceding paragraphs will now be described with reference to <FIG>.

The communication system <NUM> further includes a network node <NUM> provided in a communication system <NUM> and including hardware <NUM> enabling it to communicate with the WD <NUM>.

Thus, the network node <NUM> further has software <NUM> stored internally in, for example, memory <NUM>, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node <NUM> via an external connection. The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by network node <NUM>. Processor <NUM> corresponds to one or more processors <NUM> for performing network node <NUM> functions described herein. The memory <NUM> is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software <NUM> may include instructions that, when executed by the processor <NUM> and/or processing circuitry <NUM>, causes the processor <NUM> and/or processing circuitry <NUM> to perform the processes described herein with respect to network node <NUM>. For example, processing circuitry <NUM> of the network node <NUM> may include indication unit <NUM> configured to perform network node methods discussed herein, such as the methods discussed with reference to <FIG> as well as other figures.

The client application <NUM> may be operable to provide a service to a human or non-human user via the WD <NUM>.

The processing circuitry <NUM> may be configured to control any of the methods and/or processes described herein and/or to cause such methods, and/or processes to be performed, e.g., by WD <NUM>. The processor <NUM> corresponds to one or more processors <NUM> for performing WD <NUM> functions described herein. The WD <NUM> includes memory <NUM> that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software <NUM> and/or the client application <NUM> may include instructions that, when executed by the processor <NUM> and/or processing circuitry <NUM>, causes the processor <NUM> and/or processing circuitry <NUM> to perform the processes described herein with respect to WD <NUM>. For example, the processing circuitry <NUM> of the wireless device <NUM> may include operation unit <NUM> configured to perform WD methods discussed herein, such as the methods discussed with reference to <FIG> as well as other figures.

In some embodiments, the inner workings of the network node <NUM> and WD <NUM>, may be as shown in <FIG> and independently, the surrounding network topology may be that of <FIG>.

Although <FIG> and <FIG> show various "units" such as indication unit <NUM> and operation unit <NUM> as being within a processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

<FIG> is a flowchart of an example process in a network node <NUM> according to some embodiments of the present disclosure. One or more Blocks and/or functions and/or methods performed by the network node <NUM> may be performed by one or more elements of network node <NUM> such as by indication unit <NUM> in processing circuitry <NUM>, processor <NUM>, communication interface <NUM>, radio interface <NUM>, etc. according to the example method. The example method includes providing (Block S100), such as via indication unit <NUM>, processing circuitry <NUM>, processor <NUM>, communication interface <NUM> and/or radio interface <NUM>, support for at least one service for the WD in a non-allowed area based at least in part on at least one of subscription data associated with the WD and operator policy.

In some embodiments, the providing support further includes obtaining and/or sending, such as via indication unit <NUM>, processing circuitry <NUM>, processor <NUM>, communication interface <NUM> and/or radio interface <NUM>, a message indicating whether the at least one service is allowed for the WD in the non-allowed area. In some embodiments, the at least one service includes at least one of a short message service, SMS, over non-access stratum, a location service and an exception reporting service. In some embodiments, the message is a Namf_Communication_UEContextTransfer service message. In some embodiments, the message includes an indication of whether the at least one service is allowed for the WD <NUM> in the non-allowed area in a registration area field. In some embodiments, the message is a Nudm_SubscriberDataManagement service message. In some embodiments, the message includes an indication of whether the at least one service is allowed for the WD <NUM> in the non-allowed area in a service area restriction field. In some embodiments, the network node is one of an access and mobility function, AMF, node <NUM> and a unified data management, UDM, node <NUM>. In some embodiments, the non-allowed area is: a service area in which the WD <NUM> is restricted based on subscription; and/or in which initiating a service request, a control plane service request or a session management, SM, signalling to obtain user services is not allowed.

<FIG> is a flowchart of an example process in a wireless device <NUM> according to some embodiments of the present disclosure. One or more Blocks and/or functions and/or methods performed by WD <NUM> may be performed by one or more elements of WD <NUM> such as by operation unit <NUM> in processing circuitry <NUM>, processor <NUM>, communication interface <NUM>, radio interface <NUM>, etc. The example method includes operating (Block S <NUM>), such as via indication unit <NUM>, processing circuitry <NUM>, processor <NUM>, communication interface <NUM> and/or radio interface <NUM>, in a non-allowed area using at least one service that is allowed in the non-allowed area based at least in part on at least one of subscription data and operator policy.

In some embodiments, the at least one service includes at least one of a short message service, SMS, over non-access stratum, a location service and an exception reporting service. In some embodiments, the method further includes obtaining and/or sending, such as via indication unit <NUM>, processing circuitry <NUM>, processor <NUM>, communication interface <NUM> and/or radio interface <NUM>, a message indicating whether the at least one service is allowed for the WD <NUM> in the non-allowed area. In some embodiments, the message is at least one of a Nudm_SubscriberDataManagement service message and a Namf_Communication_UEContextTransfer service message. In some embodiments, the non-allowed area is: a service area in which the WD <NUM> is restricted based on subscription; and/or in which initiating a service request, a control plane service request or a session management, SM, signalling to obtain user services is not allowed.

<FIG> is a flowchart of another example process in a network node <NUM> according to some embodiments of the present disclosure. One or more Blocks and/or functions and/or methods performed by the network node <NUM> may be performed by one or more elements of network node <NUM> such as by indication unit <NUM> in processing circuitry <NUM>, processor <NUM>, communication interface <NUM>, radio interface <NUM>, etc. according to the example method. The example method includes determining (Block S <NUM>), such as by indication unit <NUM> in processing circuitry <NUM>, processor <NUM>, communication interface <NUM> and/or radio interface <NUM>, that the WD <NUM> is service area restricted when the WD <NUM> is in an area defined as a non-allowed area according to subscription data associated with the WD <NUM>. The method includes providing (Block S <NUM>), such as by indication unit <NUM> in processing circuitry <NUM>, processor <NUM>, communication interface <NUM> and/or radio interface <NUM>, support for the WD <NUM> for at least one service that is service area restricted in the non-allowed area based at least in part on at least one of the subscription data associated with the WD and an operator policy.

In some embodiments, providing the support further comprises obtaining and/or sending, such as by indication unit <NUM> in processing circuitry <NUM>, processor <NUM>, communication interface <NUM> and/or radio interface <NUM>, a message indicating that the at least one service that is service area restricted is allowed for the WD in the non-allowed area. In some embodiments, the at least one service is not a regulatory prioritized service. In some embodiments, the at least one service includes at least one of a short message service, SMS, over non-access stratum, a location service and an exception reporting service. In some embodiments, the message is a Namf_Communication_UEContextTransfer service message. In some embodiments, the message includes a registration area field, the registration area field indicating whether the at least one service is allowed for the WD in the non-allowed area.

In some embodiments, the message is a Nudm_SubscriberDataManagement service message. In some embodiments, the message includes a service area restriction field, the service area restriction field indicating whether the at least one service is allowed for the WD in the non-allowed area. In some embodiments, the network node is one of an access and mobility function, AMF, node and a unified data management, UDM, node. In some embodiments, the non-allowed area is a service area in which the WD is not allowed to initiate a service request, a control plane service request and/or a session management, SM, signalling to obtain user services from a network associated with the network node. In some embodiments, providing, such as by indication unit <NUM> in processing circuitry <NUM>, processor <NUM>, communication interface <NUM> and/or radio interface <NUM>, support for the WD for the at least one service in the non-allowed area when the at least one of the subscription data and the operator policy indicates that the at least one service is allowed in the non-allowed area; otherwise, restricting, such as by indication unit <NUM> in processing circuitry <NUM>, processor <NUM>, communication interface <NUM> and/or radio interface <NUM>, the WD from using the at least one service in the non-allowed area.

<FIG> is a flowchart of another example process in a wireless device <NUM> according to some embodiments of the present disclosure. One or more Blocks and/or functions and/or methods performed by WD <NUM> may be performed by one or more elements of WD <NUM> such as by operation unit <NUM> in processing circuitry <NUM>, processor <NUM>, communication interface <NUM>, radio interface <NUM>, etc. The example method includes determining (Block S108), such as by operation unit <NUM> in processing circuitry <NUM>, processor <NUM>, communication interface <NUM> and/or radio interface <NUM>, that the WD <NUM> is service area restricted when the WD <NUM> is in an area defined as a non-allowed area according to subscription data associated with the WD <NUM>. The method includes operating (Block S110), such as by operation unit <NUM> in processing circuitry <NUM>, processor <NUM>, communication interface <NUM> and/or radio interface <NUM>, in the non-allowed area using at least one service that is service area restricted in the non-allowed area based at least in part on at least one of the subscription data associated with the WD <NUM> and an operator policy.

In some embodiments, the at least one service is not a regulatory prioritized service. In some embodiments, the at least one service includes at least one of a short message service, SMS, over non-access stratum, a location service and an exception reporting service. In some embodiments, the method further comprises obtaining, such as by operation unit <NUM> in processing circuitry <NUM>, processor <NUM>, communication interface <NUM> and/or radio interface <NUM>, information indicating whether the at least one service is allowed for the WD <NUM> in the non-allowed area. In some embodiments, the information is comprised in at least one of a Nudm_SubscriberDataManagement service message and a Namf_Communication_UEContextTransfer service message.

In some embodiments, the information is included in a registration area field, the registration area field indicating whether the at least one service is allowed for the WD in the non-allowed area. In some embodiments, the information is included in a service area restriction field, the service area restriction field indicating whether the at least one service is allowed for the WD in the non-allowed area. In some embodiments, the non-allowed area is a service area in which the WD is not allowed to initiate a service request, a control plane service request and/or a session management, SM, signalling to obtain user services from a network associated with the network node.

In some embodiments, operating, such as by operation unit <NUM> in processing circuitry <NUM>, processor <NUM>, communication interface <NUM> and/or radio interface <NUM>, in the non-allowed area using the at least one service when the at least one of the subscription data and the operator policy indicates that the at least one service is allowed in the non-allowed area; otherwise, operating, such as by operation unit <NUM> in processing circuitry <NUM>, processor <NUM>, communication interface <NUM> and/or radio interface <NUM>, in the non-allowed area without using the at least one service.

Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements for subscription based service restriction, which may be implemented by the network node <NUM> and/or wireless device <NUM>.

As noted above, the current arrangements for signaling allowed in a Non-Allowed Area is unclear. Some embodiments propose a clarification on what is allowed or not allowed in the Non-Allowed Area. Some embodiments propose a clarification on what services are not allowed, what services are allowed, and what services on based on operator policy in a Non-Allowed Area.

Some embodiments provide arrangements that support a per WD/UE <NUM> based specific service control in service restricted areas.

In some embodiments, Mobility Restrictions restrict mobility handling or service access of a WD <NUM>. The Mobility Restriction functionality may be provided by the WD <NUM> (only for mobility restriction categories provided to the WD <NUM>), the radio access network (e.g., network node 16a) and the core network (e.g., network node 16d).

Unless otherwise stated herein, it is contemplated that Mobility Restrictions may only apply to 3GPP access and wireline access, they do not apply to other non-3GPP accesses.

The WD <NUM> and the network (e.g., network node <NUM>) may override any Forbidden Area, Non-Allowed area restrictions and Core Network type restriction whenever accessing the network for regulatory prioritized services like Emergency services and MPS (multi-media priority service).

Service Area restrictions and handling of Forbidden Areas for Connection Management Idle (CM-IDLE) state and, for Connection Management Connected (CM-CONNECTED) state when in radio resource control (RRC) Inactive state are executed by the WD <NUM> based on information received from the core network. Mobility Restrictions for CM-CONNECTED state when in RRC-Connected state are executed by the radio access network (e.g., network node 16a) and the core network (e.g., network node 16d).

In a CM-CONNECTED state, the core network (e.g., network node 16d) provides Mobility Restrictions to the radio access network (e.g., network node 16a) within Mobility Restriction List. Mobility Restrictions may include radio access technology (RAT) restriction, Forbidden Area, Service Area Restrictions, Core Network type restriction and Closed Access Group (CAG) information as follows.

RAT restriction: Defines the 3GPP Radio Access Technology(ies), a WD <NUM> is not allowed to access in a public land mobile network (PLMN). In a restricted RAT a WD <NUM> based on subscription is not permitted access to the network for this PLMN. For CM-CONNECTED state, when radio access network determines target RAT and target PLMN during Handover (HO) procedure, it may take per PLMN RAT restriction into consideration. The RAT restriction is enforced in the network, and not provided to the WD <NUM>.

Forbidden Area: In a Forbidden Area, the WD <NUM>, based on subscription, is not permitted to initiate any communication with the network for this PLMN. The WD <NUM> behaviour in terms of cell selection, RAT selection and PLMN selection depends on the network response that informs the WD <NUM> of the Forbidden Area. A Forbidden Area applies either to 3GPP access or to non-3GPP access.

Further description on Forbidden Area when using wireline access is available in 3GPP Technical Specification (TS) <NUM>.

NOTE <NUM>: If the N3GPP tracking area identity (TAI) (see clause <NUM>. <NUM> of 3GPP TS <NUM>) is forbidden in a PLMN, non-3GPP Access is forbidden altogether in this PLMN.

NOTE <NUM>: The WD <NUM> reactions to specific network responses are described in 3GPP TS <NUM>.

Service Area Restriction: Defines areas in which the WD <NUM> may or may not initiate communication with the network (e.g., network node <NUM>) as follows:.

NOTE <NUM>: When the services are restricted in 3GPP 5GS (also, called <NUM> system or 3GPP New Radio/NR system) due to Service Area Restriction, then it is assumed that the services will be also restricted in all RATs/Systems at the same location(s) using appropriate mechanisms available in the other RATs/Systems.

NOTE <NUM>: The Core Network type restriction can be used e.g. in network deployments where the Evolved Universal Terrestrial Radio Access Network (E-UTRAN) connects to both EPC and 5GC as described in clause <NUM> of 3GPP TS <NUM>.

For a given WD <NUM>, the core network (e.g., network node 16d) determines the Mobility Restrictions based on WD <NUM> subscription information, WD <NUM> location and/or local policy (e.g. if the Home PLMN (HPLMN) has not deployed 5GC, HPLMN ID of the WD <NUM> and the operator's policy are used in the Visited PLMN (VPLMN) for determining the Core Network type restriction). The Mobility Restriction may change due to e.g. WD's <NUM> subscription, location change and local policy. Optionally the Service Area Restrictions or the Non-Allowed Area may in addition be fine-tuned by the policy control function (PCF) e.g. based on WD <NUM> location, permanent equipment identifier (PEI) and network policies. Service Area Restrictions may be updated during a Registration procedure or WD <NUM> Configuration Update procedure.

NOTE <NUM>: The subscription management ensure that for MPS service subscriber the Mobility Restrictions is not included.

If the network (e.g., network node <NUM>) sends Service Area Restrictions to the WD <NUM>, the network sends only either an Allowed Area, or a Non-Allowed Area, but not both at the same time, to the WD <NUM>. If the WD <NUM> has received an Allowed Area from the network, any tracking area (TA) not part of the Allowed Area is considered by the WD <NUM> as non-allowed. If the WD <NUM> has received a Non-Allowed Area from the network, any TA not part of the Non-Allowed Area is considered by the WD <NUM> as allowed. If the WD <NUM> has not received any Service Area Restrictions, any TA in the PLMN is considered as allowed.

If the WD <NUM> has overlapping areas between Forbidden Areas, Service Area Restrictions, or any combination of them, the WD <NUM> may proceed in the following precedence order:.

The Unified Data Management (UDM) may provide to the Access and Mobility Function (AMF) the information defined in TS <NUM> about the subscriber's NR or E-UTRA access restriction set by the operator determined e.g. by subscription scenario and roaming scenario, as follows:.

In order to enforce all primary access restrictions, the related access is to be deployed in different Tracking Area Codes and the subscriber may not be allowed to access the network in TAs using the particular access.

With all secondary access restrictions, the subscriber may not be allowed to use this access as secondary access.

Some embodiments of the present disclosure may provide for clarifying that the information of the Restriction Area may also include specific indications which indicate if SMS over NAS service, Location Service and Exception Reporting are allowed in a Non-Allowed Area.

Description: Provides the WD <NUM> context to the consumer Network Function (NF).

Input, Required: <NUM> globally unique temporary identifier (<NUM>-GUTI) or a globally unique subscription permanent identifier (SUPI), Access Type, Reason.

Input, Optional: Integrity protected message from the WD <NUM> that triggers the context transfer.

Output, Required: The WD <NUM> context of the identified WD <NUM> or only the SUPI and an indication that the Registration Request has been validated. The WD <NUM> context is detailed in Table <NUM> below.

Output, Optional: Mobile Equipment Identifier (if available), Allowed network slice selection assistance information (NSSAI), Mapping Of Allowed NSSAI.

See clause <NUM>. <NUM> of 3GPP TS <NUM> for example of usage of this service operation. If the consumer NF sent an integrity protected message from the WD <NUM>, the AMF (e.g., network node 16d) uses it to verify whether this request is permitted to retrieve the WD context of the WD <NUM>. If it is permitted, the AMF (e.g., network node 16d) provides WD context to the consumer NF in the
Namf_Communication_UEContextTransfer response. The following table, Table <NUM>, illustrates the WD Context:.

Subscription data types used in the Nudm_SubscriberDataManagement Service (e.g., provided by UDM) are defined in Table <NUM> below.

Claim 1:
A method implemented in a wireless device, WD (<NUM>), the method comprising:
determining (S108) that the WD (<NUM>) is service area restricted when the WD (<NUM>) is in an area defined as a non-allowed area according to subscription data associated with the WD (<NUM>); and
operating (S110) in the non-allowed area using at least one service that is service area restricted in the non-allowed area based at least in part on at least one of the subscription data associated with the WD (<NUM>) and an operator policy,
wherein the method further comprises:
obtaining information indicating whether the at least one service is allowed for the WD (<NUM>) in the non-allowed area.