Allowing allocation of registration areas

Abstract

This document discloses a method for operating a network node (10) and a network node (10) for performing the method, which is capable of defining an allowed area in which data services are provided to a wireless device (42), the size of the allowed area being defined by one or more criteria including a predefined maximum number of tracking areas within the allowed area, the method comprising: upon attachment of the wireless device (42), accepting registration of new tracking areas for the allowed area of ​​the wireless device (42) provided that the one or more criteria defining the size of the allowed area are met.

Description

[0001] This application is a divisional application of the invention patent application filed on June 7, 2017, with application number 201780037964.5 and invention title "Allowing Allocation of Registration Area". Technical Field

[0002] This disclosure relates to allocating or defining permitted areas for user equipment (UE) devices in a cellular communication network. Background Technology

[0003] Within the 3rd Generation Partnership Project (3GPP) SA2, there is a work item (WI) research FS_NextGen, which studies fifth-generation (5G) mobile networks. At this point, 3GPP's progress is still premature. The architecture remains to be defined.

[0004] It is stated in Section 4.1, “Advanced Architecture Requirements,” of 3GPP Technical Report (TR) 23.799 v0.4.0 (2016-4):

[0005] The architecture of the 'next-generation' network should

[0006] 1. Supports new RAT, evolved LTE, and non-3GPP access types. GERAN and UTRAN are not supported.

[0007] a) As part of non-3GPP access types, it should support WLAN access and fixed access. FFS supports satellite access.

[0008] Today, an "initial high-level view" of this architecture exists (Nokia et al., "S2-162146: Architectural Requirements, Principles, and Assumptions: An Assumption-Based Reference Architecture Model," SA WG2 meeting #S2-114, April 11 - May 15, 2016), which was approved in SA2#114 (April 2016), as... Figure 1 As shown.

[0009] Ericsson contributed a reference architecture to the SA2#115 meeting (Ericsson, “S2-162502: Core Network Architecture and Functional Assignments”, SA WG2 meeting #115, May 23-27, 2016), but it was not addressed at the meeting. Figures 2 to 5 This stems from this contribution.

[0010] Next-generation (NG) subscriber data management (NG SDM or SDM) is a subscription information store that contains all the information about an operator's users. When a user connects to the network, their subscription information is retrieved from the SDM. In roaming scenarios, the serving operator retrieves the subscription information located within the home operator's network. The SDM can be viewed as similar to a Home Subscriber Server (HSS) or Home Location Register (HLR), the former used for Long Term Evolution (LTE) / Evolved Packet System (EPS), and the latter for Global System for Mobile Communications (GSM) / GSM Evolution Enhanced Data Rate (EDGE) Radio Access Network (GERAN) and Universal Terrestrial Radio Access Network (UTRAN).

[0011] NG Policy Control (NG PC) is a function similar to the Policy Charging Rules Function (PCRF) used for GERAN, UTRAN, and Evolved UTRAN (E-UTRAN).

[0012] NG Core Control (NG CC) represents the control plane of the core network (CN) and has similar functions to the Mobility Management Entity (MME), as well as the control plane of the Serving Gateway (S-GW) and Packet Data Network (PDN) Gateway (P-GW) in E-UTRAN.

[0013] The Service Processing Function (THF) represents a portion of the CN's control plane and has functions similar to the mobility portion of the MME in E-UTRAN.

[0014] The Connection Processing Function (CHF) represents another part of the CN's control plane, but also the CN's user plane, and has similar functions to the session portion of the MME in E-UTRAN and the control plane portions of the S-GW and P-GW in E-UTRAN.

[0015] THF and CHF have the same functionality as NG CC.

[0016] Note that GERAN and UTRAN are not supported in 5G and are not included in this application.

[0017] Regarding the critical issue #3 "Mobility Framework", 3GPP TR 23.799 (V0.4.0) includes the concept of "Mobility on Demand":

[0018] "-How to support mobility on demand based on different mobility levels. Different mobility levels..."

[0019] Possible examples of motion support are as follows:

[0020] - Supported in a given area within a single RAN node (e.g., a cell of an eNodeB).

[0021] - Supported within a single RAN node (e.g., eNodeB).

[0022] - Supported in UE registration areas (e.g., TA in EPC).

[0023] - Supported in the service areas of CN entities in the control plane or user plane (such as the MME pool area or service GW service area in EPC).

[0024] - Supported within a combination of RATs integrated at a given RAT or RAN level (e.g., LTE and 5G RATs).

[0025] - Supported between two access technologies.

[0026] Note: Research on mobility restrictions in RAN will be conducted in conjunction with the RAN working group.

[0027] - How to determine the level of UE mobility support, such as by what features / methods, which

[0028] One standard; and

[0029] - How to obtain information (e.g., application requirements, device (UE) capabilities, and services used) to determine the appropriate level of UE mobility.

[0030] Regarding the key question #6, "Support for session and service continuity":

[0031] "To address the specific needs of different applications and services, the next-generation system architecture of mobile networks should support different levels of data session continuity or service continuity based on the on-demand mobility concept defined in the mobility framework in Key Issue 3."

[0032] The approved SA2#115 contribution S2-163164 (Ericsson, “S2-163164: On-Demand Mobility Solution”, SAWG2 Meeting #115, May 23-27, 2016) introduces mobility classes into the solution in 3GPP TR 23.799:

[0033] "6.3x.2.1 Mobility Classes: By dividing the user's allowed geographic area into several..."

[0034] A subrange can be formed, for example, into the following mobility classes:

[0035] A. Unlimited (or high) mobility

[0036] - There are no (or very few) restrictions on the permitted geographic areas for users such as MBB.

[0037] B. Low mobility

[0038] - Geographic regions are allowed to be restricted, for example, for fixed users. The size can be limited to, for example, 5 TAs.

[0039] C. No mobility

[0040] - The geographical area allowed can be restricted, for example, for users who only access the network via a fixed point (which has its own access network with possible mobility). The size can be limited, for example, to 1TA. Summary of the Invention

[0041] Since the mobility class only defines the size of the allowed area (AA), it does not specify the location where the UE can obtain service. Without any such restriction (i.e., no allowed tracking area (TA) is defined), the assigned mobility class will not impose any restrictions on the UE's mobility, as the UE will not occupy more than one TA anyway. Therefore, it is necessary to define the actual AA, not just the area size.

[0042] It should also be noted that the AA of a UE does not necessarily have to be a continuous area. For example, for digital subscriber line (DSL) replacement, one area is used for residential areas and another area is used for summer villas, and the AA is divided into two sub-parts.

[0043] Due to the large number of UEs and their respective AAs, defining AAs, whether statically defined by the operator or dynamically defined by UE registration attempts, must be relatively easy.

[0044] Three different solutions are described. However, it should be noted that, in some cases, solution 1 is considered an alternative to solution 3.

[0045] Solution 1 is based on the pre-configuration of each user's AA in the contract database. Optionally, the AA is tuned by NG PC.

[0046] Solution 2 is based on a pre-configured number of sub-parts for each user and their respective sizes. With the help of the end user, the actual regions are configured in the UE, provided to the CN, and stored in the subscription database.

[0047] Solution 3 is based on dynamic and ad-hoc definitions executed by the UE. AA definitions used by the UE and provided to the CN are only valid upon UE attachment. Upon detachment, any previous AA definitions are deleted, and upon attachment, new TAs are automatically added to the new AA definitions until the maximum allowed number of TAs is reached. This solution also relies on the pre-configuration of the number of AAs per user. As in Solution 1, the operator can optionally configure all or part of the AAs for users in the subscription database. This pre-configured AA is provided to the UE upon Attach Acceptance and forms the basis of the AAs used by the UE. If only part of the AA is configured in the subscription database, the NG PC can optionally add TAs to the pre-configured AA.

[0048] The advantage of this solution is its ease of use from an operations and management (O&M) perspective. It provides operators with the possibility of using pre-configured AA when feasible, and if not, the process automatically handles the UE's AA definition. The disadvantage is the lack of pre-configured AA; users can obtain service from any location simply by performing detach and reattach. However, this is also an advantage, as it provides a solution for UEs requiring multiple operating areas, such as for nomadic DSL replacement, where one area is for residential use and another for summer retreats.

[0049] This solution enables some frameworks to allocate allowed regions to UEs. Two methods for statically and dynamically allocating TAs to allowed regions, as well as combinations thereof, are described.

[0050] Some embodiments of this solution relate to a method of operating a network node capable of defining an allowed area in which data services are provided to a wireless device, the size of which is defined by one or more criteria including a predefined maximum number of tracking areas within the allowed area. The method includes: upon attachment of the wireless device, accepting registration of new tracking areas for the allowed area of ​​the wireless device, provided that the one or more criteria defining the size of the allowed area are met.

[0051] Some other embodiments of this solution relate to a network node capable of defining an allowed area in which data services are provided to a wireless device, the size of which is defined by one or more criteria including a predefined maximum number of tracking areas within the allowed area. The network node is adapted to accept registration of new tracking areas for the allowed area of ​​the wireless device upon attachment, provided that the one or more criteria defining the size of the allowed area are met.

[0052] Some other embodiments of this solution relate to a network node capable of defining an allowed area in which data services are provided to a wireless device, the size of which is defined by one or more criteria including a predefined maximum number of tracking areas within the allowed area. The network node includes: at least one processor; and a memory storing instructions executable by the at least one processor, thereby enabling the network node to be operable to accept registration of new tracking areas for the allowed area of ​​the wireless device upon attachment, provided that the one or more criteria defining the size of the allowed area are met.

[0053] Some other embodiments of this solution relate to a network node capable of defining an allowed area in which data services are provided to a wireless device, the size of which is defined by one or more criteria including a predefined maximum number of tracking areas within the allowed area. The network node includes a registration processing module operable to accept registration of new tracking areas for the allowed area of ​​the wireless device upon attachment, provided that the one or more criteria defining the size of the allowed area are met.

[0054] After reading the following detailed description of the embodiments in conjunction with the accompanying drawings, those skilled in the art will understand the scope of this disclosure and recognize its other aspects. Attached Figure Description

[0055] Several aspects of this disclosure are illustrated in conjunction with and form a part of this specification, and are used together with the specification to explain the principles of this disclosure. These drawings are:

[0056] Figure 1 The NG network architecture is shown;

[0057] Figure 2 A reference architecture for non-roaming functionality is shown;

[0058] Figure 3 This demonstrates a non-roaming, distributed user plane deployment;

[0059] Figure 4 This shows the roaming (home-routed) route;

[0060] Figure 5 This demonstrates roaming (local breakout in a visited public terrestrial mobile network (VPLMN));

[0061] Figures 6A to 6I Various example scenarios according to some embodiments of this disclosure are shown;

[0062] Figure 7The operation of a network node according to some embodiments of this disclosure is illustrated;

[0063] Figures 8 to 10 An example embodiment of a network node is shown; and

[0064] Figure 11 and 12 An example embodiment of the UE is shown. Detailed Implementation

[0065] The embodiments described below illustrate information that enables those skilled in the art to practice the embodiments, and demonstrate the best mode for practicing the embodiments. By reading the following description in conjunction with the accompanying drawings, those skilled in the art will understand the concepts of this disclosure and will recognize the application of these concepts not specifically set forth herein. It should be understood that these concepts and applications fall within the scope of this disclosure.

[0066] Wireless node: As used in this article, a “wireless node” is a wireless access node or wireless device.

[0067] Wireless Access Node: As used herein, a “wireless access node” is any node in the wireless access network of a cellular communication network that is used to wirelessly transmit and / or receive signals. Some examples of wireless access nodes include, but are not limited to, base stations (such as enhanced or evolved Node B (eNB) in a 3GPP LTE network), high-power or macro base stations, low-power base stations (such as micro base stations, pico base stations, home eNBs, etc.), and relay nodes.

[0068] Core Network Node: As used in this document, a “core network node” is any type of node in the CN. Some examples of core network nodes include, for example, MME, P-GW, Service Capability Open Function (SCEF), THF, CHF Control Plane (CHF-C), CHF User Plane (CHF-U), SDM, NG PC, Device Identification Register (EIR), etc.

[0069] Wireless device: As used herein, “wireless device” may be used interchangeably with “UE”. The terms “wireless device” and “UE” are used herein to refer to any type of device that accesses a cellular communication network (i.e., is served by a cellular communication network) by wirelessly transmitting and / or receiving signals from a wireless access node. Some examples of wireless devices include, but are not limited to, 3GPP LTE UEs in 3GPP networks (or similar devices in NG networks) and machine-type communication (MTC) devices.

[0070] Network node: As used herein, a “network node” is any node that is part of a wireless access network or cellular communication network / system (CN).

[0071] Note that the descriptions presented herein focus on 3GPP cellular communication systems, and therefore 3GPP terminology or similar terms are frequently used. However, the concepts disclosed herein are not limited to 3GPP systems.

[0072] Note that the term “cell” may be used in the description in this article; however, in particular for the 5G concept, beams may be used instead of cells, so it is important to note that the concepts described in this article also apply to cells and beams.

[0073] Since the mobility class only defines the size of the Area Assist (AA), it does not specify the location where the UE can obtain service. Without any such restrictions (i.e., without defining allowed TAs, etc.), the assigned mobility class will not impose any limitations on the UE's mobility, because the UE will occupy no more than one TA at this time. Therefore, it is necessary to define the actual AA, not just the size of the area.

[0074] It should also be noted that the AA of a UE does not necessarily have to be a continuous area. For example, for DSL replacement, one area is a residential area and another area is a summer villa, and the AA is divided into two sub-parts.

[0075] Due to the large number of UEs and their respective AAs, whether defined statically by the operator or dynamically by means of UE registration attempts, defining AAs must be relatively easy.

[0076] When defining AA (Action Class), there is a risk of errors leading to imperfect AA, thus necessitating the use of mechanisms that allow for correction. Misuse must also be prevented. If users are to be allowed to correct their AA, the correction mechanism must impose a certain degree of effort from the user or some service degradation during the change; otherwise, the assigned mobility class will not introduce any perceived geographical limitations. Without such constraints, a low mobility class subscription might be purchased, yet the UE could still be used with full service in all locations.

[0077] When defining the TA of an AA, the mechanism must largely ensure that the addition of the TA is intentional or that errors are easily corrected. There is a balance: the easier it is to make an error, the easier it is to correct it.

[0078] Many solutions are described below. Note that while these solutions are described individually, they can be combined as needed or desired for any particular implementation.

[0079] Solution 1

[0080] One solution is to have the operator configure AA in the subscription database for each UE with a low mobility class or no mobility class, and then optionally have NG PC or similar policy control functions adjust the AA.

[0081] The advantage of doing this is that AA can be divided into just as many sub-parts as TA, and misuse is virtually impossible since every change must go through the operator.

[0082] For many stationary Internet of Things (IoT) devices, this becomes a heavy O&M task for operators, and knowing the exact operating location of each device at the time of sale and contract signing is not always feasible. For UEs that are allowed to roam, it may also be difficult to know the TA (Target Area) in the allowed area of ​​the network being visited.

[0083] For example, this solution is particularly useful when the operator knows the exact location of the UE's operation.

[0084] Solution 2

[0085] Another solution is to assign a number of permitted sub-parts in the AA and a number of permitted TAs or similar to each sub-part to the UE during registration.

[0086] This information is provided by SDM or a similar subscription data store or subscription database, and optionally adjusted by NG PC or a similar policy control function. It allows the UE to register at any location but only allows the UE to use data services included in the TA or similarly included in the TA. To add a TA or similar to the AA, the user must first initiate the process via configuration, identifying the sub-part to be used, and then, after each completed attach or TA update (TAU) or similar, accepting or rejecting the addition of the current TA or similar to the identified sub-part of the AA. The TA then also needs to be stored in the subscription database.

[0087] Adding new TAs or similar items will continue until the maximum number of TAs or similar items has been added, or until the user stops the process via configuration or begins the definition process for another sub-part of the AA.

[0088] In the absence of an accepted TA or similar, the UE will not be allowed to use data services, deny service requests, and mobile termination (MT) data.

[0089] During registration, the UE is provided with its stored AA (Agent Action) definition. This is provided to the UE whenever subscription data is retrieved from the subscription database, such as from the SDM (Subscription Data Management) via the THF (Trust of Funds). The AA definition may include TAs or similar from the home network and the access network. The home operator can correct incorrectly added TAs or similar by changing the stored AA.

[0090] Figures 6A to 6IThe diagram illustrates how the UE configures and selects different sub-regions for various embodiments of Solution 2. However, it should be noted that while many scenarios are shown, this disclosure is not limited thereto. Furthermore, in some embodiments, Figures 6A to 6I Not all of the steps shown are performed. Figures 6A to 6I The diagram illustrates several scenarios where a UE registers with different TAs, and if the user has already enabled inclusion in a specific sub-area, the TA can be attached to the sub-area based on the user's decision. It also shows how to send the configured sub-area or allowed area in the UE to the network and store it in the THF. After changing the THF, the stored information is sent between the source and target THFs, as well as from the SDM to the target THF.

[0091] The advantage of this solution is that the AA is defined by the end user, and the end user must (i.e., intentionally) confirm the addition of the TA. Similar to the previous solutions, the AA can be divided into as many sub-parts as the TA, and misuse becomes virtually impossible since each calibration must go through the operator.

[0092] Having end users initiate the process and then confirm each TA might be too cumbersome for some. There is also the risk that TAs might be mistakenly added due to the prospect of accessing services at the current location, while a small number of accepted TAs should actually be saved for more valuable locations.

[0093] To minimize the deployment cost of simple IoT devices, manual intervention should be reduced to a minimum. The definition of its Area of ​​Action (AA) needs to be automated, for example, by initiating a process to define its unique area upon attachment, and then simply accepting any Targeting Aspects (TAs) until the maximum number of TAs is reached. If the IoT device needs to be moved to another location, the AA needs to be reset, which requires operator intervention.

[0094] As can be seen from the above, the following risks exist: a large number of incorrect AA definitions, calls to the service desk, and eventual operator intervention to correct the errors.

[0095] Solution 3

[0096] An automatic AA definition process is created by initiating the definition process each time a UE attaches, and then accepting each new TA or similar until the maximum number of TAs is reached. The maximum number of TAs is provided by the SDM and optionally adjusted by the NG PC. Once the AA is fully defined (i.e., the maximum number of TAs is reached), the UE will be rejected when attempting to register a new TA. Incorrectly added TAs can be easily handled by de-attaching and then re-attaching, thus restarting the AA. When the CN node changes, the AA definition is transferred from the old node to the new node if an interface exists; otherwise, the UE will be forced to re-attach (as in a legacy network). The allowed TAs can be served by different CN nodes.

[0097] Optionally, operators can also configure and store all or part of the AA for the UE. The pre-configured AA is transmitted to the UE in the Attach Accept message. Optionally, the NG PC in the serving network can add a TA in case only a portion of the AA is defined in the subscription database. Operators can also use this option to restrict the mobility of UEs that misuse the feature in some way (e.g., repeatedly performing attach and detach). Operators can then configure static AA for the UE.

[0098] in this regard, Figure 7 An example of Solution 3 is shown. In this example, the network node (e.g., THF) operates upon UE attachment to accept the registration of new TAs or similar for the UE's AA, provided that one or more criteria defining the maximum size of the UE's AA are met. As mentioned above, one or more criteria defining the maximum size of the UE's AA may include the maximum number of TAs or similar within the AA. Once the UE is attached, in some embodiments, the UE includes TA(multiple) or similar in the AA. The network node (e.g., THF) then performs... Figure 7 The process involves accepting or rejecting registration based on the maximum number of TAs allowed for the AA (i.e., accepting registration if the number of TAs or similar items already registered in the AA is less than the maximum value, otherwise rejecting registration). Furthermore, upon accepting registration, the network node (e.g., THF) stores information about the registration of TAs or similar items in the UE's AA. Additionally, in some embodiments, the network node may provide information about the UE's AA (e.g., information about TAs or similar items registered in the UE's AA) to one or more other network nodes.

[0099] Example embodiments of network nodes and UEs

[0100] Figure 8This is a schematic block diagram of a network node 10 according to some embodiments of the present disclosure. Network node 10 can be any network node in a Radio Access Network (RAN) or a CN. For example, network node 10 can be a base station or other radio access node in the RAN, or a THF, CHF-C, CHF-U, SDM, NG PC, or EIR or the like in the CN. As shown, network node 10 includes a control system 12, which includes one or more processors 14 (e.g., a central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), and / or the like), memory 16, and a network interface 18. Furthermore, if network node 10 is a radio access node, it includes one or more wireless units 20, each wireless unit 20 including one or more transmitters 22 and one or more receivers 24 coupled to one or more antennas 26. In some embodiments, the wireless units(multiple) 20 are external to the control system 12 and connected to the control system 12 via, for example, a wired connection (e.g., optical fiber). However, in some other embodiments, the wireless units(multiple) 20 and possibly the antennas(multiple) 26 are integrated with the control system 12. One or more processors 14 are used to provide one or more functions of the network node 10 described herein. In some embodiments, the functions(s) are implemented in software, which is stored in, for example, memory 16 and executed by one or more processors 14.

[0101] Figure 9 This is a schematic block diagram illustrating a virtualized embodiment of a network node 10 according to some embodiments of the present disclosure. As used herein, a “virtualized” network node 10 is an implementation of a network node 10 in which at least a portion of the functionality of the network node 10 is implemented as a virtual component (e.g., via a virtual machine executed on a physical processing node in the network). As shown, in this example, the network node 10 includes a control system 12, which includes one or more processors 14 (e.g., CPU, ASIC, FPGA, etc.), memory 16, and a network interface 18, and optionally one or more wireless units 20 as described above, each wireless unit 20 including one or more transmitters 22 and one or more receivers 24 coupled to one or more antennas 26. The control system 12 is connected to the wireless units(plural) 20 via, for example, optical fiber. The control system 12 is connected to one or more processing nodes 28 coupled to or part of a network 30 via the network interface 18. Each processing node 28 includes one or more processors 32 (e.g., CPU, ASIC, FPGA, and / or the like), memory 34, and a network interface 36.

[0102] In this example, the functionality 38 of the network node 10 described herein is implemented at one or more processing nodes 28, or distributed in any desired manner across the control system 12 and one or more processing nodes 28. In some specific embodiments, some or all of the functionality 38 of the network node 10 described herein is implemented as virtual components executed by one or more virtual machines implemented in a virtual environment hosted by the processing nodes 28. Those skilled in the art will understand that additional signaling or communication is used between the processing nodes 28 and the control system 12 to perform at least some of the desired functionality 38. It is noteworthy that in some embodiments, the control system 12 may not be included, in which case the wireless unit 20 (if included) communicates directly with the processing nodes 28 via a suitable network interface. In other embodiments, the network node 10 does not include the control system 12 or the wireless unit 20, thereby making the network node 10 fully virtualized.

[0103] In some embodiments, a computer program including instructions is provided that, when executed by at least one processor, cause the at least one processor to perform the functions of a network node 10 according to any embodiment described herein, or the functions of a node (e.g., processing node 28) implementing one or more functions 38 of the network node 10 in a virtual environment. In some embodiments, a carrier including the aforementioned computer program product is provided. The carrier is one of an electrical signal, an optical signal, a wireless signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0104] Figure 10 This is a schematic block diagram of a network node 10 according to some other embodiments of the present disclosure. The network node 10 includes one or more modules 40, each module 40 being implemented in software. Modules 40 provide the functionality of the network node 10 described herein. This discussion also applies to... Figure 9 The processing node 28, wherein module 40 may be implemented at one of the processing nodes 28 or distributed across multiple processing nodes 28 and / or distributed across the processing nodes 28 and the control system 12. As an example, module 40 may include operable to perform Figure 7 One or more modules of the process.

[0105] Figure 11This is a schematic block diagram of a UE 42 according to some embodiments of the present disclosure. As shown, the UE 42 includes one or more processors 44 (e.g., CPU, ASIC, FPGA, etc.), a memory 46, and one or more transceivers 48, each transceiver 48 including one or more transmitters 50 and one or more receivers 52 coupled to one or more antennas 54. In some embodiments, the functionality of the UE 42 described above may be implemented entirely or partially in software, which is stored, for example, in the memory 46 and executed by the processor 44.

[0106] In some embodiments, a computer program including instructions is provided that, when executed by at least one processor, causes the at least one processor to perform the functions of UE 42 according to any embodiment described herein. In some embodiments, a carrier including the aforementioned computer program product is provided. The carrier is one of an electrical signal, an optical signal, a wireless signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0107] Figure 12 This is a schematic block diagram of a UE 42 according to some other embodiments of the present disclosure. UE 42 includes one or more modules 56, each module 56 being implemented in software. Modules 56 provide the functionality of the UE 42 described herein.

[0108] Example Implementation

[0109] While not limited thereto, some example embodiments of this disclosure are provided below.

[0110] 1. A method of operating a network node (10) capable of defining an allowed area in which data services are provided to a wireless device (42), the size of the allowed area being defined by one or more criteria including a predefined maximum number of tracking areas within the allowed area, the method comprising:

[0111] • When the wireless device (42) is attached, registration of a new tracking area for the allowed area of ​​the wireless device (42) is accepted as long as one or more criteria defining the size of the allowed area are met.

[0112] 2. The method according to embodiment 1, wherein accepting the registration includes: accepting the registration of a new tracking area if the number of tracking areas already accepted for the allowed area of ​​the wireless device (42) is less than the predefined maximum number of tracking areas within the allowed area.

[0113] 3. The method according to embodiment 1 or 2 further includes: if the number of tracking regions already accepted for the allowed area of ​​the wireless device (42) is greater than or equal to the predefined maximum number of tracking regions in the allowed area, then the registration of a new tracking region is rejected.

[0114] 4. The method according to any one of the embodiments 1 to 3 further includes: resetting the allowed area of ​​the wireless device (42) when the wireless device (42) deattaches.

[0115] 5. The method according to any one of embodiments 1 to 3 further includes: resetting the allowed area of ​​the wireless device (42) when the wireless device (42) reattaches after the wireless device (42) has deattached.

[0116] 6. The method according to any one of embodiments 1 to 5, wherein a portion of the permitted area of ​​the wireless device (42) is configured by a network operator.

[0117] 7. The method according to any one of embodiments 1 to 6, wherein a portion of the permitted area of ​​the wireless device (42) is configured by the network node (10).

[0118] 8. The method according to any one of embodiments 1 to 7, wherein one or more tracking areas are added by a network node (10) to the permitted area of ​​the wireless device (42).

[0119] 9. The method according to any one of embodiments 1 to 8 further includes: storing information about the permitted area of ​​the wireless device (42).

[0120] 10. The method according to any one of embodiments 1 to 9 further includes: providing information about the permitted area of ​​the wireless device (42) to another network node (10).

[0121] 11. A network node (10) capable of defining a permissible area in which data services are provided to a wireless device (42), the size of the permissible area being defined by one or more criteria including a predefined maximum number of tracking areas within the permissible area, the network node (10) being adapted to:

[0122] • When the wireless device (42) is attached, registration of a new tracking area for the allowed area of ​​the wireless device (42) is accepted as long as one or more criteria defining the size of the allowed area are met.

[0123] 12. The network node (10) according to embodiment 11, wherein the network node (10) is also adapted to operate according to any one of embodiments 2 to 10.

[0124] 13. A network node (10) capable of defining a permitted area in which data services are provided to a wireless device (42), the size of the permitted area being defined by one or more criteria including a predefined maximum number of tracking areas within the permitted area, the network node (10) comprising:

[0125] • At least one processor (14); and

[0126] • A memory (16) storing instructions that can be executed by the at least one processor (14), thereby enabling the network node (10) to accept registration of a new tracking area for the allowed area of ​​the wireless device (42) when the wireless device (42) is attached, provided that one or more criteria defining the size of the allowed area are met.

[0127] 14. A network node (10) capable of defining a permissible area in which data services are provided to a wireless device (42), the size of the permissible area being defined by one or more criteria including a predefined maximum number of tracking areas within the permissible area, the network node (10) comprising:

[0128] • Registration processing module (40) operable to accept registration of a new tracking area for the allowed area of ​​the wireless device (42) when the wireless device (42) is attached, provided that one or more criteria defining the size of the allowed area are met.

[0129] The following abbreviations are used throughout this disclosure.

[0130] ·3GPP Third Generation Partnership Program

[0131] 5G (Fifth Generation)

[0132] AA permitted areas

[0133] Application-Specific Integrated Circuits (ASICs)

[0134] CC Core Control

[0135] CHF connection processing function

[0136] CHF-C Control Processing Function Control Plane

[0137] CHF-U Control Processing Function User Plane

[0138] CN Core Network

[0139] CPU (Central Processing Unit)

[0140] DSL (Digital Subscriber Line)

[0141] • EDGE Global Mobile Communications System Enhanced Data Rate

[0142] • EIR Device Identification Register

[0143] • eNB Enhanced or Evolved Node B

[0144] EPS Evolution Grouping System

[0145] E-UTRAN evolved universal terrestrial radio access network

[0146] FPGA (Field Programmable Gate Array)

[0147] GERAN (Global System for Mobile Communications) Enhanced Data Rate

[0148] GPRS General Packet Radio Service

[0149] GSM Global System for Mobile Communications

[0150] Home Location Register (HLR)

[0151] HSS (Home Server)

[0152] IoT (Internet of Things)

[0153] LTE Long Term Evolution

[0154] • MME (Mobility Management Entity)

[0155] ·MT movement terminated

[0156] MTC machine-type communication

[0157] NG Next Generation

[0158] O&M Operations Management

[0159] PC policy control

[0160] • PCRF policy billing rules function

[0161] • PDN (Packet Data Network)

[0162] P-GW Packet Data Network Gateway

[0163] RAN (Radio Access Network)

[0164] • SCEF service capability opening function

[0165] SDM User Data Management

[0166] • SGSN service General Packet Radio Service Support Node

[0167] S-GW Service Gateway

[0168] TA tracking area

[0169] • TAU tracking area updates

[0170] ·THF business processing function

[0171] TR Technical Report

[0172] UE (User Equipment)

[0173] UTRAN (Universal Terrestrial Radio Access Network)

[0174] VPLMN (Virtual Land Mobile Network) surveyed

[0175] WI Work Projects

[0176] Those skilled in the art will recognize improvements and modifications to the embodiments of this disclosure. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.

Claims

1. A method of operating a network node (10) capable of defining an allowed area in which data services are provided to a wireless device (42), the size of the allowed area being defined by one or more criteria including a predefined maximum number of tracking areas within the allowed area, the method comprising: • When the wireless device (42) is attached, registration of a new tracking area for the allowed area of ​​the wireless device (42) is accepted as long as one or more criteria defining the size of the allowed area are met; Accepting the registration includes: if the number of tracking regions already accepted for the allowed area of ​​the wireless device (42) is less than the predefined maximum number of tracking regions within the allowed area, then accepting the registration of a new tracking region; wherein the method includes: The number of sub-regions and the number of tracking areas allowed per sub-region are sent to the wireless device (42) for the wireless device (42) to confirm whether a tracking area should be included in the sub-region; Receive report allowed area information from the wireless device (42), the report allowed area information containing tracking areas that should be included in the sub-regions as determined by the wireless device; Send a message to the wireless device (42) indicating whether the report allows the area information to be accepted or the report allows the area information to be rejected.

2. The method of claim 1, further comprising: If the number of tracking regions already accepted for the allowed region of the wireless device (42) is greater than or equal to the predefined maximum number of tracking regions within the allowed region, then the registration of a new tracking region is rejected.

3. The method of claim 1, further comprising: When the wireless device (42) detaches, the allowed area of ​​the wireless device (42) is reset.

4. The method of claim 1, further comprising: After the wireless device (42) is deattached, the allowed area of ​​the wireless device (42) is reset when the wireless device (42) is reattached.

5. The method of claim 1, wherein, A portion of the permitted area of ​​the wireless device (42) is configured by the network operator.

6. The method of claim 1, wherein, A portion of the permitted area of ​​the wireless device (42) is configured by the network node (10).

7. The method of claim 1, wherein, One or more tracking areas are added by network node (10) to the allowed area of ​​the wireless device (42).

8. The method of claim 1, further comprising: Store information about the permitted area of ​​the wireless device (42).

9. The method of claim 1, further comprising: The information about the permitted area of ​​the wireless device (42) is provided to another network node (10).

10. A network node (10) capable of defining a permitted area in which data services are provided to a wireless device (42), the size of the permitted area being defined by one or more criteria including a predefined maximum number of tracking areas within the permitted area, the network node (10) comprising: • At least one processor (14); as well as • A memory (16) storing instructions executable by the at least one processor (14), thereby enabling the network node (10) to accept registration of a new tracking region for the allowed area of ​​the wireless device (42) upon attachment of the wireless device (42), provided that one or more criteria defining the size of the allowed area are met; wherein accepting the registration includes: accepting registration of a new tracking region if the number of tracking regions already accepted for the allowed area of ​​the wireless device (42) is less than the predefined maximum number of tracking regions within the allowed area; wherein the network node (10) is operable to: The number of sub-regions and the number of tracking areas allowed per sub-region are sent to the wireless device (42) for the wireless device (42) to confirm whether a tracking area should be included in the sub-region; Receive report allowed area information from the wireless device (42), the report allowed area information containing tracking areas that should be included in the sub-regions as determined by the wireless device; Send a message to the wireless device (42) indicating whether the report allows the area information to be accepted or the report allows the area information to be rejected.

11. The network node (10) according to claim 10, wherein The network node (10) is also adapted to operate according to the method of claim 2.

12. A network node (10) capable of defining a permitted area in which data services are provided to a wireless device (42), the size of the permitted area being defined by one or more criteria including a predefined maximum number of tracking areas within the permitted area, the network node (10) comprising: • Registration processing module (40) operable to accept registration of a new tracking area for the allowed area of ​​the wireless device (42) when the wireless device (42) is attached, provided that one or more criteria defining the size of the allowed area are met; Accepting the registration includes: if the number of tracking areas already accepted for the allowed area of ​​the wireless device (42) is less than the predefined maximum number of tracking areas within the allowed area, then accepting the registration of a new tracking area; wherein the network node (10) is operable to: The number of sub-regions and the number of tracking areas allowed per sub-region are sent to the wireless device (42) for the wireless device (42) to confirm whether a tracking area should be included in the sub-region; Receive report allowed area information from the wireless device (42), the report allowed area information containing tracking areas that should be included in the sub-regions as determined by the wireless device; Send a message to the wireless device (42) indicating whether the report allows the area information to be accepted or the report allows the area information to be rejected.

Images