Patent Application
20230189121
The present disclosure relates to wireless communications, and in particular, to subscription based service restriction.
The concept of “Service Area Restriction”, as part of the Mobility Restriction, has been present in Third Generation Partnership Project (3GPP) standards since Release 15 (Rel-15). However, there are some details about the Service Area Restriction that are unclear.
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 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 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 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 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.
A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:
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-15. 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. Like numbers refer to like elements throughout the description.
As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and/or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate and modifications and variations are possible of achieving the electrical and data communication.
In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and/or wireless connections.
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.
In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The WD herein can be any type of wireless device capable of communicating with a network node or another WD over radio signals, such as wireless device (WD). The WD may also be a radio communication device, target device, device to device (D2D) WD, machine type WD or WD capable of machine to machine communication (M2M), low-cost and/or low-complexity WD, a sensor equipped with WD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (IoT) device, or a Narrowband IoT (NB-IOT) device etc.
Also, in some embodiments the generic term “radio network node” is used. 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 22 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.
Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and/or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.
Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein. 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
Also, it is contemplated that a WD 22 can be in simultaneous communication and/or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a WD 22 can have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, WD 22 can be in communication with an eNB for LTE/E-UTRAN and a gNB for NR/NG-RAN.
A network node 16 is configured to include an indication unit 24 which is configured to provide support for at least one service for a WD 22 in a non-allowed area based at least in part on at least one of subscription data associated with the WD 22 and operator policy.
A wireless device 22 is configured to include an operation unit 26 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 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to
The communication system 10 further includes a network node 16 provided in a communication system 10 and including hardware 27 enabling it to communicate with the WD 22. The hardware 27 may include a communication interface 28 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 10, as well as a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a WD 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
In the embodiment shown, the hardware 27 of the network node 16 further includes processing circuitry 34. The processing circuitry 34 may include a processor 36 and a memory 38. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 34 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 36 may be configured to access (e.g., write to and/or read from) the memory 38, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
Thus, the network node 16 further has software 40 stored internally in, for example, memory 38, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 40 may be executable by the processing circuitry 34. The processing circuitry 34 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 16. Processor 36 corresponds to one or more processors 36 for performing network node 16 functions described herein. The memory 38 is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 40 may include instructions that, when executed by the processor 36 and/or processing circuitry 34, causes the processor 36 and/or processing circuitry 34 to perform the processes described herein with respect to network node 16. For example, processing circuitry 34 of the network node 16 may include indication unit 24 configured to perform network node methods discussed herein, such as the methods discussed with reference to
The communication system 10 further includes the WD 22 already referred to. The WD 22 may have hardware 42 that may include a radio interface 44 configured to set up and maintain a wireless connection 32 with a network node 16 serving a coverage area 18 in which the WD 22 is currently located. The radio interface 44 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and/or one or more RF transceivers.
The hardware 42 of the WD 22 further includes processing circuitry 46. The processing circuitry 46 may include a processor 48 and memory 50. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 46 may comprise integrated circuitry for processing and/or control, e.g., one or more processors and/or processor cores and/or FPGAs (Field Programmable Gate Array) and/or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 48 may be configured to access (e.g., write to and/or read from) memory 50, which may comprise any kind of volatile and/or nonvolatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory).
Thus, the WD 22 may further comprise software 52, which is stored in, for example, memory 50 at the WD 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the WD 22. The software 52 may be executable by the processing circuitry 46. The software 52 may include a client application 54. The client application 54 may be operable to provide a service to a human or non-human user via the WD 22. The client application 54 may interact with the user to generate the user data that it provides.
The processing circuitry 46 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 22. The processor 48 corresponds to one or more processors 48 for performing WD 22 functions described herein. The WD 22 includes memory 50 that is configured to store data, programmatic software code and/or other information described herein. In some embodiments, the software 52 and/or the client application 54 may include instructions that, when executed by the processor 48 and/or processing circuitry 46, causes the processor 48 and/or processing circuitry 46 to perform the processes described herein with respect to WD 22. For example, the processing circuitry 46 of the wireless device 22 may include operation unit 26 configured to perform WD methods discussed herein, such as the methods discussed with reference to
In some embodiments, the inner workings of the network node 16 and WD 22, may be as shown in
Although
In some embodiments, the providing support further includes obtaining and/or sending, such as via indication unit 24, processing circuitry 34, processor 36, communication interface 28 and/or radio interface 30, 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 22 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 22 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 16 and a unified data management, UDM, node 16. In some embodiments, the non-allowed area is: a service area in which the WD 22 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.
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 24, processing circuitry 34, processor 36, communication interface 28 and/or radio interface 30, a message indicating whether the at least one service is allowed for the WD 22 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 22 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.
In some embodiments, providing the support further comprises obtaining and/or sending, such as by indication unit 24 in processing circuitry 34, processor 36, communication interface 28 and/or radio interface 30, 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 24 in processing circuitry 34, processor 36, communication interface 28 and/or radio interface 30, 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 24 in processing circuitry 34, processor 36, communication interface 28 and/or radio interface 30, the WD from using the at least one service 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 method further comprises obtaining, such as by operation unit 26 in processing circuitry 46, processor 48, communication interface 28 and/or radio interface 44, information indicating whether the at least one service is allowed for the WD 22 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 26 in processing circuitry 46, processor 48, communication interface 28 and/or radio interface 44, 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 26 in processing circuitry 46, processor 48, communication interface 28 and/or radio interface 44, 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 16 and/or wireless device 22.
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 22 based specific service control in service restricted areas.
3GPP Technical Specification (TS) 23.501 Update
Mobility Restrictions—General
In some embodiments, Mobility Restrictions restrict mobility handling or service access of a WD 22. The Mobility Restriction functionality may be provided by the WD 22 (only for mobility restriction categories provided to the WD 22), 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 22 and the network (e.g., network node 16) 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 22 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 22 is not allowed to access in a public land mobile network (PLMN). In a restricted RAT a WD 22 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 22.
Forbidden Area: In a Forbidden Area, the WD 22, based on subscription, is not permitted to initiate any communication with the network for this PLMN. The WD 22 behaviour in terms of cell selection, RAT selection and PLMN selection depends on the network response that informs the WD 22 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) 23.316.
NOTE 1: If the N3GPP tracking area identity (TAI) (see clause 5.3.2.3 of 3GPP TS 23.501) is forbidden in a PLMN, non-3GPP Access is forbidden altogether in this PLMN.
NOTE 2: The WD 22 reactions to specific network responses are described in 3GPP TS 24.501.
Service Area Restriction: Defines areas in which the WD 22 may or may not initiate communication with the network (e.g., network node 16) as follows:
NOTE 3: When the services are restricted in 3GPP 5GS (also, called 5G 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 4: 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 5.17 of 3GPP TS 23.501.
For a given WD 22, the core network (e.g., network node 16d) determines the Mobility Restrictions based on WD 22 subscription information, WD 22 location and/or local policy (e.g. if the Home PLMN (HPLMN) has not deployed 5GC, HPLMN ID of the WD 22 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 22 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 22 location, permanent equipment identifier (PEI) and network policies. Service Area Restrictions may be updated during a Registration procedure or WD 22 Configuration Update procedure.
NOTE 5: The subscription management ensure that for MPS service subscriber the Mobility Restrictions is not included.
If the network (e.g., network node 16) sends Service Area Restrictions to the WD 22, the network sends only either an Allowed Area, or a Non-Allowed Area, but not both at the same time, to the WD 22. If the WD 22 has received an Allowed Area from the network, any tracking area (TA) not part of the Allowed Area is considered by the WD 22 as non-allowed. If the WD 22 has received a Non-Allowed Area from the network, any TA not part of the Non-Allowed Area is considered by the WD 22 as allowed. If the WD 22 has not received any Service Area Restrictions, any TA in the PLMN is considered as allowed.
If the WD 22 has overlapping areas between Forbidden Areas, Service Area Restrictions, or any combination of them, the WD 22 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 23.008 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.
TS 23.502 Update
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.
Namf_Communication_UEContextTransfer Service Operation
Service operation name: Namf_Communication_UEContextTransfer
Description: Provides the WD 22 context to the consumer Network Function (NF).
Input, Required: 5G globally unique temporary identifier (5G-GUTI) or a globally unique subscription permanent identifier (SUPI), Access Type, Reason.
Input, Optional: Integrity protected message from the WD 22 that triggers the context transfer.
Output, Required: The WD 22 context of the identified WD 22 or only the SUPI and an indication that the Registration Request has been validated. The WD 22 context is detailed in Table 1 below.
Output, Optional: Mobile Equipment Identifier (if available), Allowed network slice selection assistance information (NSSAI), Mapping Of Allowed NSSAI.
See clause 4.2.2.2.2 of 3GPP TS 23.502 for example of usage of this service operation. If the consumer NF sent an integrity protected message from the WD 22, the AMF (e.g., network node 16d) uses it to verify whether this request is permitted to retrieve the WD context of the WD 22. 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 1, illustrates the WD Context:
Subscription data types used in the Nudm_SubscriberDataManagement Service (e.g., provided by UDM) are defined in Table 2 below.
Some embodiments may include one or more of the following embodiments:
Embodiment A1. A network node configured to communicate with a wireless device (WD), the network node configured to, and/or comprising a radio interface and/or comprising processing circuitry configured to:
provide 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.
Embodiment A2. The network node of Embodiment A1, wherein the processing circuitry is configured to provide support by being configured to:
obtain and/or send a message indicating whether the at least one service is allowed for the WD in the non-allowed area.
Embodiment A3. The network node of any one of Embodiments A1 and A2, wherein 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.
Embodiment A4. The network node of any one of Embodiments A1-A3, wherein the message is a Namf_Communication_UEContextTransfer service message.
Embodiment A5. The network node of Embodiment A4, wherein the message includes an indication of whether the at least one service is allowed for the WD in the non-allowed area in a registration area field.
Embodiment A6. The network node of any one of Embodiments A1-A3, wherein the message is a Nudm_SubscriberDataManagement service message.
Embodiment A7. The network node of Embodiment A6, wherein the message includes an indication of whether the at least one service is allowed for the WD in the non-allowed area in a service area restriction field.
Embodiment A8. The network node of any one of Embodiments A1-A7, wherein the network node is one of an access and mobility function, AMF, node and a unified data management, UDM, node.
Embodiment A9. The network node of any one of Embodiments A1-A8, wherein the non-allowed area is:
a service area in which the WD 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.
Embodiment B1. A method implemented in a network node, the method comprising:
providing 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.
Embodiment B2. The method of Embodiment B 1, wherein the providing support further comprises:
obtaining and/or sending a message indicating whether the at least one service is allowed for the WD in the non-allowed area.
Embodiment B3. The method of any one of Embodiments B1 and B2, wherein 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.
Embodiment B4. The method of any one of Embodiments B1-B3, wherein the message is a Namf_Communication_UEContextTransfer service message.
Embodiment B5. The method of Embodiment B4, wherein the message includes an indication of whether the at least one service is allowed for the WD in the non-allowed area in a registration area field.
Embodiment B6. The method of any one of Embodiments B1-B3, wherein the message is a Nudm_SubscriberDataManagement service message.
Embodiment B7. The method of Embodiment B6, wherein the message includes an indication of whether the at least one service is allowed for the WD in the non-allowed area in a service area restriction field.
Embodiment B8. The method of any one of Embodiments B1-B7, wherein the network node is one of an access and mobility function, AMF, node and a unified data management, UDM, node.
Embodiment B9. The method of any one of Embodiments B1-B8, wherein the non-allowed area is:
a service area in which the WD 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.
Embodiment C1. A wireless device (WD) configured to communicate with a network node, the WD configured to, and/or comprising a radio interface and/or processing circuitry 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.
Embodiment C2. The WD of Embodiment A1, wherein 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.
Embodiment C3. The WD of any one of Embodiments C1 and C2, wherein the processing circuitry is further configured to:
obtain and/or send a message indicating whether the at least one service is allowed for the WD in the non-allowed area.
Embodiment C4. The WD of Embodiment C3, wherein the message is at least one of a Nudm_SubscriberDataManagement service message and a Namf_Communication_UEContextTransfer service message.
Embodiment C5. The WD of any one of Embodiments C1-C4, wherein the non-allowed area is:
a service area in which the WD 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.
Embodiment D1. A method implemented in a wireless device (WD), the method comprising:
operating 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.
Embodiment D2. The method of Embodiment D1, wherein 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.
Embodiment D3. The method of any one of Embodiments D1 and D2, further comprising:
obtaining and/or sending a message indicating whether the at least one service is allowed for the WD in the non-allowed area.
Embodiment D4. The method of Embodiment D3, wherein the message is at least one of a Nudm_SubscriberDataManagement service message and a Namf_Communication_UEContextTransfer service message.
Embodiment D5. The method of any one of Embodiments D1-D4, wherein the non-allowed area is:
a service area in which the WD 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.
As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and/or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and/or functionality described herein may be performed by, and/or associated to, a corresponding module, which may be implemented in software and/or firmware and/or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.
Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the “C” programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.
It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/IB2021/054174 | 5/14/2021 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 63025450 | May 2020 | US |
