Filter authorization list for private networks

Abstract

According to an example embodiment of the present invention, a method includes: receiving, at a network node in a registration area (RA), a list of cells and their associated tracking area identifiers (TAIs) from at least one other network node of the RA; determining which of the received TAIs are neighboring TAIs of a TAI of the network node; building a list of neighboring TAIs corresponding to at least one other network node; transmitting to a network management entity a list of closed access group identifiers (CAG IDs) supported by the TAI of the network node and a list of neighboring TAIs corresponding to at least one other network node; and receiving, from the network management entity, a list of allowed CAG IDs of a user equipment (UE).

Description

Technical Field

[0001] Some example embodiments may relate generally to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology, or to other communication systems. For example, certain embodiments may relate to systems and / or methods for supporting Public Network Integrated Non-Public Network (PNI-NPN) in such communication systems. Background Art

[0002] Examples of mobile or wireless telecommunication systems may include Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), Advanced LTE (LTE-A), MulteFire, LTE-A Pro, and / or fifth generation (5G) radio access technology or new radio (NR) access technology. 5G wireless systems refer to next generation (NG) radio systems and network architectures. 5G is primarily built on new radio (NR), but 5G (or NG) networks can also be built on E-UTRA radio. It is estimated that NR provides bit rates of 10-20Gbit / s or higher and can support at least enhanced mobile broadband (eMBB) and ultra-reliable low latency communications (URLLC) and massive machine type communications (mMTC). NR is expected to provide ultra-wideband and ultra-robust low latency connections and large-scale networks to support the Internet of Things (IoT). As IoT and machine-to-machine (M2M) communications become more and more common, the need for networks that can meet the requirements of low power consumption, low data rates, and long battery life will continue to grow. Next Generation Radio Access Network (NG-RAN) refers to the RAN of 5G, which can provide both NR and LTE wireless access. It is worth noting that in 5G, a node that can provide radio access functions to user equipment (i.e., similar to Node B in UTRAN or eNB in ​​LTE) can be named gNB when built on NR radio, and can be named NG-eNB when built on LTE / E-UTRA radio. Summary of the invention

[0003] Various aspects of examples of the invention are set out in the claims.

[0004] According to a first aspect of the present invention, a method includes: receiving, at a network node of a registration area (RA), a list of cells and their associated tracking area identifiers (TAIs) from at least one other network node of the RA; determining which of the received TAIs are neighboring TAIs of a TAI of the network node; constructing a list of neighboring TAIs corresponding to at least one other network node; transmitting to a network management entity a list of closed access group identifiers (CAG IDs) supported by the TAI of the network node and a list of neighboring TAIs corresponding to at least one other network node; and receiving from the network management entity a list of allowed CAG IDs of a user equipment (UE).

[0005] According to a second aspect of the present invention, an apparatus comprises: at least one processor; and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, enable the apparatus to at least: receive, at the apparatus in a registration area (RA), a list of cells and their associated tracking area identifiers (TAIs) from at least one other network node of the RA; determine which of the received TAIs are neighboring TAIs of a TAI in the TAI of the apparatus; construct a list of neighboring TAIs corresponding to at least one other network node; transmit to a network management entity a list of closed access group identifiers (CAG IDs) supported by the TAI of the apparatus and a list of neighboring TAIs corresponding to at least one other network node; and receive from the network management entity a list of allowed CAG IDs of a user equipment (UE).

[0006] According to a third aspect of the present invention, a non-transitory computer storage medium is encoded with a computer program, the program including instructions, which when executed by one or more computers causes the one or more computers to execute the following: at a network node in a registration area (RA), receiving a list of cells and their associated tracking area identifiers (TAIs) from at least one other network node in the RA; determining which of the received TAIs are neighboring TAIs of a TAI in the TAI of the network node; constructing a list of neighboring TAIs corresponding to at least one other network node; transmitting to a network management entity a list of closed access group identifiers (CAG IDs) supported by the TAI of the network node and a list of neighboring TAIs corresponding to at least one other network node; and receiving from the network management entity a list of allowed CAG IDs of user equipment (UE).

[0007] According to a fourth aspect of the present invention, a device includes: a component for receiving a list of cells and their associated tracking area identifiers (TAIs) from at least one other network node of a registration area (RA) at the device in the RA; a component for determining which of the received TAIs are neighboring TAIs of a TAI in the TAI of the device; a component for constructing a list of neighboring TAIs corresponding to at least one other network node; a component for transmitting to a network management entity a list of closed access group identifiers (CAG IDs) supported by the TAI of the device and a list of neighboring TAIs corresponding to at least one other network node; and a component for receiving a list of allowed CAG IDs of a user equipment (UE) from the network management entity.

[0008] According to a fifth aspect of the present invention, a method includes: receiving information from at least one network node of a registration area (RA), the information including a list of closed access group identifiers (CAG IDs) supported by a tracking area identifier (TAI) of the at least one network node and a list of neighboring TAIs corresponding to one or more other network nodes of the RA adjacent to the at least one network node; based on the received information, determining a list of CAG IDs supported in the RA and a list of CAG IDs supported by TAIs adjacent to the RA to generate a list of CAG IDs allowed by a user equipment (UE); filtering the list of UE allowed CAG IDs to derive a list of CAG ID subsets allowed by the UE; and transmitting the list of CAG ID subsets allowed by the UE to at least one network node.

[0009] According to a sixth aspect of the present invention, a device includes: at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, enable the device to at least: receive information from at least one network node of a registration area (RA), the information including a list of closed access group identifiers (CAG IDs) supported by a tracking area identifier (TAI) of the at least one network node and a list of neighboring TAIs corresponding to one or more other network nodes of the RA adjacent to the at least one network node; determine, based on the received information, a list of CAG IDs supported in the RA and a list of CAG IDs supported by the TAIs adjacent to the RA to generate a list of CAG IDs allowed by a user equipment (UE); filter the list of UE allowed CAG IDs to derive a list of CAG ID subsets allowed by the UE; and transmit the list of CAG ID subsets allowed by the UE to at least one network node.

[0010] According to a seventh aspect of the present invention, a non-transitory computer storage medium is encoded with a computer program, the program comprising instructions, which when executed by one or more computers causes the one or more computers to execute the following: receiving information from at least one network node of a registration area (RA), the information comprising a list of closed access group identifiers (CAG IDs) supported by a tracking area identifier (TAI) of the at least one network node and a list of adjacent TAIs corresponding to one or more other network nodes of the RA adjacent to the at least one network node; determining, based on the received information, a list of CAG IDs supported in the RA and a list of CAG IDs supported by TAIs adjacent to the RA to generate a list of CAG IDs allowed by a user equipment (UE); filtering the list of UE allowed CAG IDs to derive a list of a subset of CAG IDs allowed by the UE; and transmitting the list of CAG ID subsets allowed by the UE to at least one network node.

[0011] According to an eighth aspect of the present invention, an apparatus includes: a component for receiving information from at least one network node of a registration area (RA), the information including a list of closed access group identifiers (CAG IDs) supported by a tracking area identifier (TAI) of the at least one network node and a list of neighboring TAIs corresponding to one or more other network nodes of the RA adjacent to the at least one network node; a component for determining, based on the received information, a list of CAG IDs supported in the RA and a list of CAG IDs supported by TAIs adjacent to the RA to generate a list of CAG IDs allowed by a user equipment (UE); a component for filtering the list of UE allowed CAG IDs to derive a list of CAG ID subsets allowed by the UE; and a component for transmitting the list of CAG ID subsets allowed by the UE to at least one network node. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] For a proper understanding of the example embodiments, reference should be made to the accompanying drawings, in which:

[0013] Figure 1 shows an example signaling flow diagram according to one embodiment;

[0014] Figure 2 shows an example signaling flow diagram according to one embodiment;

[0015] Figure 3 shows an example signaling flow diagram according to one embodiment;

[0016] Figure 4 shows an example signaling flow diagram according to one embodiment;

[0017] Figure 5a An example flow chart of a method according to one embodiment is shown;

[0018] Figure 5b An example flow chart of a method according to one embodiment is shown;

[0019] Figure 6a An example block diagram showing an apparatus according to one embodiment; and

[0020] Figure 6b An example block diagram of an apparatus according to one embodiment is shown. DETAILED DESCRIPTION

[0021] It will be readily appreciated that the components of certain example embodiments as generally described and illustrated in the figures herein may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for supporting Public Network Integrated Non-Public Networks (PNI-NPN) is not intended to limit the scope of certain embodiments, but is representative of selected example embodiments.

[0022] The features, structures, or characteristics of the example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, use of the phrases "certain embodiments," "some embodiments," or other similar language throughout this specification means that a particular feature, structure, or characteristic described in conjunction with an embodiment may be included in at least one embodiment. Thus, the appearance of the phrases "certain embodiments," "in some embodiments," "in other embodiments," or other similar language throughout this specification does not necessarily refer to the same set of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

[0023] In addition, if desired, the different functions or processes discussed below can be performed in different orders and / or simultaneously with each other. In addition, if desired, one or more of the functions or processes described can be optional or can be combined. Therefore, the following description should be regarded as merely illustrating the principles and teachings of certain example embodiments, rather than limiting them.

[0024] It is expected that Public Network Integrated Non-Public Network (PNI-NPN) will be supported as part of the 3rd Generation Partnership Project (3GPP) Radio Access Network (RAN) work item on supporting private networks in 5G. According to the characteristics of PNI-NPN, a UE may be associated with a UE allowed closed access group (CAG) identifier (ID) list that identifies the closed access group to which the UE belongs. One CAG cell in NG-RAN may support one or more CAG IDs. If at least one of the UE allowed CAG IDs is supported in the cell, the UE is authorized to access the cell of the Public Land Mobile Network (PLMN).

[0025] In order for the NG-RAN to control the cells that a UE in connected mode mobility is allowed to access, or simply to enable the NG-RAN to select a suitable cell for a UE in connected mode mobility, the NG-RAN node needs to know this list of UE allowed CAG IDs. Therefore, the Access Management Function (AMF) provides the NG-RAN node with the list of UE allowed CAG IDs within the Mobility Restriction List Information Element (IE), which is sent in an NG Application Protocol (NGAP) message that creates a context for the UE in the NG-RAN node, for example in the Initial Context Establishment.

[0026] Given that one or more CAG IDs can be associated with one private network and a UE can be authorized to access dozens of private networks across a country / region, the list of UE allowed CAG IDs to be included in the Mobility Restriction List IE can be very large, resulting in signaling overhead. This can also increase the processing load in the NG-RAN node whenever a mobility check has to be done. Therefore, it is desirable to reduce this list by some filtering mechanism.

[0027] It is sufficient if the NG-RAN node knows the list of UE allowed CAG IDs as long as the UE is in the current Registration Area (RA), which is useful because the AMF has the opportunity to download a new updated list of UE allowed CAG IDs whenever the UE changes RA. This updated list may be referred to in this document as the RA useful list of UE allowed CAG IDs. Obviously, this list is smaller than the complete list of UE allowed CAG IDs for the complete PLMN.

[0028] In order to appropriately determine the mobility of the UE in connected mode, the RA useful list of CAG IDs allowed by the UE may contain: (1) a list of all CAG IDs supported by the cell including the current RA, and / or (2) a list of all CAG IDs supported by cells including tracking areas (TAs) adjacent to the RA (because the UE may trigger a change of RA in such an adjacent TA).

[0029] The AMF can determine a list of all CAG IDs supported by the cells including the current RA as described below. First, it has been recommended that the NG-RAN node sends a list of CAG IDs it supports to the AMF at the time of the NG establishment request, and the NG-RAN node also sends a list of TAs it supports in this message. Therefore, the signaling of the CAG IDs supported by the NG-RAN node can be organized in the NG establishment request for each TA. The AMF can then obtain a list of all CAG IDs supported by the cells of the current RA by accumulating the list of CAG IDs of all TAs including the RA received from the NG-RAN nodes involved in the RA. However, currently, the AMF cannot determine a list of all CAG IDs supported by cells including tracking areas (TAs) adjacent to the RA because the AMF does not know which TAs are adjacent to the RA.

[0030] Each NG-RAN node of a RA may include cells of one or more TAs. For each of these TAs, the NG-RAN node can determine the neighboring TAs by looking at the TAs associated with the neighboring cells. The NG-RAN node should also know what the CAG IDs supported by each of these neighboring TAs are, since the neighboring TAs have cells belonging to a neighboring NG-RAN node that has communicated a list of CAG IDs supported by each of its cells over Xn, for example, during an Xn setup message.

[0031] In one embodiment, the NG-RAN node is configured to report to the AMF the CAGIDs supported by each TA of the NG-RAN node and the TAs adjacent to its TA. As described above, the NG-RAN node may determine the TAs adjacent to its TA from the Xn setup message previously received from the neighboring NG-RAN node. For any of these neighboring TAs, the AMF shall have received a list of supported CAG IDs from other NG-RAN nodes. According to one embodiment, using the list of supported CAGIDs received from other NG-RAN nodes, the AMF may be configured to build a list of CAG IDs supported by cells of all neighboring TAs. According to some embodiments, the AMF may be configured to use the received one or more CAG IDs to filter the list of UE allowed CAG IDs, for example, to determine the RA useful list of UE allowed CAG IDs. In certain embodiments, when the UE becomes connected via a NG-RAN node of a RA, the AMF may also send the RA useful list of UE allowed CAG IDs to the NG-RAN node, for example, in the mobility restriction list IE in the initial context setup message.

[0032] In one embodiment, the NG-RAN node may be configured to report to the AMF the CAG IDs supported by the NG-RAN node per TA, and the CAG IDs supported by cells of TAs adjacent to its TA (e.g., which were previously received from the neighboring NG-RAN node in the Xn establishment). According to one embodiment, the AMF may be configured to filter the list of UE allowed CAG IDs using the CAG IDs received from at least one NG-RAN node, for example, to determine the RA useful list of UE allowed CAG IDs. In certain embodiments, when the UE becomes connected via a NG-RAN node of a RA, the AMF may also be configured to send the RA useful list of UE allowed CAG IDs to the NG-RAN node within the Mobility Restriction List IE in the Initial Context Setup message.

[0033] Note that in another embodiment, the Neighbor Tracking Area Identity (TAI) list reported by the NG-RAN node may also be used by the AMF for other purposes in addition to those discussed above.

[0034] Figure 1 An example signaling diagram or message flow according to some embodiments is shown. Figure 1 As shown in the example of , at 102 and 103, the NG-RAN node 1 may receive a list of cells with their TAIs in the Xn setup message from the NG-RAN node 2 and / or the NG-RAN node 3, for example. Note that the NG-RAN node 2 and / or the NG-RAN node 3 may or may not be in the RA of the NG-RAN node 1. In one embodiment, at 105, the NG-RAN node 1 may determine which of the received TAIs are neighboring TAIs of one of its own TAIs based on the knowledge of which cells are neighboring cells of its own cell. In this way, the NG-RAN node 1 may build a list of all neighboring TAIs corresponding to the NG-RAN node 2 and / or the NG-RAN node 3. Note that the NG-RAN node 1 may do the same thing for any (multiple) NG-RAN node x from which the Xn setup procedure is exchanged, and these (multiple) NG-RAN node x may be outside the RA of the NG-RAN node 1. Therefore, the NG-RAN node 1 may build a complete list of its neighboring TAIs.

[0035] Figure 2 Another example signaling diagram or message flow according to certain embodiments is shown. Figure 2As shown in the example of , at 201, the NG-RAN node 1 may send, for each of its own TAIs, a list of all CAG IDs supported by the TAI (the sum of all CAG IDs supported by the cells that include the TAI) to the AMF. The NG-RAN node 1 may also send to the AMF a list of all neighboring TAIs that it knows about, as discussed above Figure 1 The place is built. Figure 2 As shown in the example of , NG-RAN node 2 may similarly send to the AMF a list of all CAG IDs supported by its TAI, and a list of neighboring TAIs that it knows about. Note that other NG-RAN nodes may similarly provide their lists to the AMF. At 205, the AMF may then build a list of CAG IDs supported by the TAI of the RA including the UE and a list of CAG IDs supported by TAIs neighboring the TAI including the RA based on the information received from all NG-RAN nodes of the RA. In this way, the AMF may combine the information received by the NG-RAN node of the RA and the NG-RAN nodes neighboring the RA to build a RA-related list of CAG IDs, which corresponds to the list of CAG IDs supported in the RA area and in TAIs neighboring the RA.

[0036] Figure 3 Another example signaling diagram or message flow according to certain embodiments is shown. Figure 3 As shown in the example of , at 301, using the RA-related list of CAG IDs (i.e., the list of CAG IDs supported by the TAI including the RA of the UE plus the list of CAG IDs supported by the TAI adjacent to the TAI including the RA), the AMF may filter the complete PLMN range list of CAG IDs allowed by the UE to derive the RA useful list of CAG IDs allowed by the UE. Then, when the UE becomes connected via the NG-RAN node 4 of its RA, at 305, the AMF may send the RA useful list of CAG IDs allowed by the UE to the NG-RAN node 4 of the RA, for example, within the Mobility Restriction List IE included in the NGAP Initial Context Setup Request message, and may also send the RA useful list of CAG IDs allowed by the UE to the UE. At 310, the NG-RAN node 4 may store the received RA useful list of CAG IDs allowed by the UE and may use it for connected mode mobility, and the UE may also use it for idle mode purposes.

[0037] Figure 4 Another example signaling diagram or message flow according to certain embodiments is shown. Figure 4As shown in the example of , when the UE changes to a new RA via the NG-RAN node 5 of a neighboring TAI, at 401, the UE may send a NAS registration update message to the AMF. In this example, at 405, the AMF may recalculate a new RA useful list of UE allowed CAG IDs corresponding to the new RA, and at 410, when it sends the new RA to the UE, it may send the updated list to the NG-RAN node 5. In one embodiment, the AMF may also send the new RA useful list of UE allowed CAG IDs to the UE. At 415, the NG-RAN node 5 may store the updated RA useful list of UE allowed CAG IDs and may use it for connected mode mobility, and the UE may use the updated RA useful list of UE allowed CAG IDs for idle mode mobility.

[0038] Figure 5a An example flow chart of a method for supporting a private network in 5G according to an example embodiment is shown. In certain example embodiments, Figure 5a The flowchart may be executed by a network entity or a network node (such as LTE or 5G NR) in a communication system. For example, in some example embodiments, Figure 5a The method can be performed by a base station, an access point, a NG-RAN node, an eNB and / or a gNB, or other network nodes.

[0039] like Figure 5a As shown in the example of , at 500, the method may include: receiving, at the network node of the RA, a list of cells and their associated TAIs from at least one other network node that can be connected via Xn. For example, receiving 500 may include receiving the list in an Xn setup message. In some embodiments, the method may then include: determining, at 510, which of the received TAIs are neighboring TAIs of one of the TAIs of the network node, for example, using knowledge of which cells are neighboring cells of the network node's own cell.

[0040] In one embodiment, Figure 5aThe method may further include: at 520, building a list of neighboring TAIs corresponding to at least one other network node. According to some embodiments, the method may include: at 530, transmitting to the AMF a list of CAG IDs supported by the TAI of the network node and a list of neighboring TAIs corresponding to at least one other network node. Then, for example, when the UE is connected via the network node of its RA, the method may include: at 540, receiving a RA useful list of CAG IDs allowed by the UE from the AMF. In one example, receiving 540 may include receiving the RA useful list of CAG IDs allowed by the UE within a mobility restriction list IE included in the NGAP initial context establishment request message. According to some embodiments, the method may further include: at 550, storing the received RA useful list of CAG IDs allowed by the UE, and optionally using it for connected mode mobility, and propagating the RA useful list of CAG IDs allowed by the UE towards the UE.

[0041] Figure 5b An example flow chart of a method for supporting a private network in 5G according to an example embodiment is shown. In certain example embodiments, Figure 5b The flowchart may be executed by a network entity or a network node (such as LTE or 5G NR) in a communication system. For example, in some example embodiments, Figure 5b The method can be performed by AMF or other access or management network nodes.

[0042] like Figure 5b As shown in the example of , at 560, the method may include receiving information from at least one network node of the RA, the information including a list of CAG IDs supported by the TAI of the at least one network node and a list of neighboring TAIs corresponding to one or more other network nodes neighboring the at least one network node. According to certain embodiments, the one or more other network nodes may or may not belong to the RA of the at least one network node. In one embodiment, the method may also include: at 570, determining a RA-related list of CAG IDs using the received information, the list including a list of CAG IDs supported in the RA and a list of CAG IDs supported by TAIs neighboring the RA. According to certain embodiments, the method may then include: at 580, filtering a list of UE-allowed CAG IDs using the RA-related list of CAG IDs to derive a RA useful list of UE-allowed CAG IDs.

[0043] In some embodiments, when the UE is connected to at least one network node of its RA, the method may include: at 590, transmitting a RA useful list of CAG IDs allowed by the UE to at least one network node. In one embodiment, the RA useful list of CAG IDs allowed by the UE may also be sent to the UE. In one example, transmission 590 may include: transmitting the RA useful list of CAG IDs allowed by the UE within a mobility restriction list IE included in the NGAP initial context establishment request message, and / or transmitting the RA useful list of CAG IDs allowed by the UE to the UE. According to certain embodiments, the method may also include: when the UE changes to a new RA via a network node of a neighboring TAI, calculating an updated RA useful list of CAG IDs allowed by the UE, and transmitting the updated list to the network node and / or UE of the neighboring TAI.

[0044] Figure 6a An example of an apparatus 10 according to one embodiment is shown. In one embodiment, the apparatus 10 may be a node, host, or server in a communication network, or serve such a network. For example, the apparatus 10 may be a satellite, a base station, a Node B, an evolved Node B (eNB), a 5G Node B or access point, an NG-RAN node, a next generation Node B (NG-NB or gNB), and / or a WLAN access point associated with a radio access network (such as an LTE network, 5G, or NR). In an example embodiment, the apparatus 10 may represent an NG-RAN node.

[0045] It should be understood that in some example embodiments, the device 10 may include an edge cloud server as a distributed computing system, where the server and the wireless nodes may be independent devices that communicate with each other via a radio path or via a wired connection, or they may be located in the same entity that communicates via a wired connection. For example, in certain example embodiments where the device 10 represents a gNB, it may be configured in a central unit (CU) and distributed unit (DU) architecture that divides the gNB functionality. In such an architecture, the CU may be a logical node that includes gNB functionality (such as transmission of user data, mobility control, radio access network sharing, positioning and / or session management, etc.). The CU may control the operation of (multiple) DUs via a fronthaul interface. The DU may be a logical node that includes a subset of gNB functionality, depending on the functional splitting option. It should be noted that a person of ordinary skill in the art will understand that the device 10 may include Figure 6a Components or features not shown.

[0046] like Figure 6aAs shown in the example of , the device 10 may include a processor 12 for processing information and executing instructions or operations. The processor 12 may be any type of general or special purpose processor. In fact, for example, the processor 12 may include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although Figure 6a A single processor 12 is shown in the figure, but according to other embodiments, multiple processors may be used. For example, it should be understood that in some embodiments, the device 10 may include two or more processors, which may form a multi-processor system that can support multi-processing (e.g., in this case, the processor 12 may represent a multi-processor). In some embodiments, the multi-processor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0047] Processor 12 may perform functions associated with the operation of device 10, which may include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits that form communication messages, formatting of information, and overall control of device 10, including processes associated with management of communication resources.

[0048] The device 10 may also include or be coupled to a memory 14 (internal or external), which may be coupled to the processor 12, and which is used to store information and instructions that can be executed by the processor 12. The memory 14 may be one or more memories and of any type suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 14 may include a random access memory (RAM), a read-only memory (ROM), a static storage device such as a magnetic disk or optical disk, a hard disk drive (HDD), or any other type of non-transitory memory or computer-readable medium. The instructions stored in the memory 14 may include program instructions or computer program codes that, when executed by the processor 12, enable the device 10 to perform the tasks described herein.

[0049] In one embodiment, the device 10 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software for execution by the processor 12 and / or the device 10.

[0050] In some embodiments, the device 10 may also include or be coupled to one or more antennas 15 for transmitting signals and / or data to and receiving signals and / or data from the device 10. The device 10 may also include or be coupled to a transceiver 18 configured to transmit and receive information. The transceiver 18 may include, for example, multiple radio interfaces that may be coupled to (multiple) antennas 15. The radio interface may correspond to a variety of radio access technologies, including one or more of the following: GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identification (RFID), ultra-wideband (UWB), MulteFire, etc. The radio interface may include components such as filters, converters (e.g., digital-to-analog converters, etc.), mappers, fast Fourier transform (FFT) modules, etc., to generate symbols for transmission via one or more downlinks and receive symbols (e.g., via uplinks).

[0051] Thus, the transceiver 18 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 15 and to demodulate information received via the antenna(s) 15 for further processing by other elements of the apparatus 10. In other embodiments, the transceiver 18 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some embodiments, the apparatus 10 may include input and / or output devices (I / O devices).

[0052] In one embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. The modules may include, for example, an operating system that provides operating system functionality for device 10. The memory may also store one or more functional modules, such as applications or programs, to provide additional functionality to device 10. The components of device 10 may be implemented in hardware, or as any suitable combination of hardware and software.

[0053] According to some embodiments, the processor 12 and the memory 14 may be included in or may form part of processing circuitry or control circuitry.Furthermore, in some embodiments, the transceiver 18 may be included in or may form part of transceiver circuitry.

[0054] As used herein, the term "circuitry" may refer to any portion of a hardware circuit implementation (e.g., analog and / or digital circuitry), a combination of hardware circuitry and software, a combination of analog and / or digital hardware circuitry and software / firmware, a combination of (multiple) hardware processors (including digital signal processors) with software that work together to enable a device (e.g., device 10) to perform various functions, and / or (multiple) hardware circuits and / or (multiple) processors or portions thereof that operate using software but may not be present when the software is not required for operation. As a further example, as used herein, the term "circuitry" may also encompass an implementation of a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor, and its accompanying software and / or firmware. The term circuitry may also encompass, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.

[0055] As described above, in some embodiments, the apparatus 10 may be a network node, a RAN node, or a NG-RAN node, such as a base station, an access point, a Node B, an eNB, a gNB, a WLAN access point, etc. According to some embodiments, the apparatus 10 may be controlled by the memory 14 and the processor 12 to perform functions associated with any one of the example embodiments described herein, such as Figures 1 to 4 , Figure 5a or Figure 5b Flowchart or signaling diagram shown. In some embodiments, for example, the apparatus 10 may be configured to perform a process for supporting a dedicated network. In one embodiment, the apparatus 10 may represent a network node of the RA, such as an NG-RAN node of the RA.

[0056] In one embodiment, the device 10 may be controlled by the memory 14 and the processor 12 to receive a list of cells and their associated TAIs from at least one other network node that may be connected to the device 10 via Xn. For example, the list may be received in an Xn setup message. In some embodiments, the device 10 may be controlled by the memory 14 and the processor 12 to determine which of the received TAIs are neighboring TAIs of one of the TAIs of the device 10, for example, using knowledge of which cells are neighboring cells of the cell of the device 10.

[0057] In one embodiment, the device 10 may be controlled by the memory 14 and the processor 12 to construct a list of neighboring TAIs corresponding to at least one other network node. According to some embodiments, the device 10 may be controlled by the memory 14 and the processor 12 to transmit to the AMF a list of CAG IDs supported by the TAI of the device 10 and a list of neighboring TAIs corresponding to at least one other network node. Then, for example, when the UE is connected via the network node of its RA, the device 10 may be controlled by the memory 14 and the processor 12 to receive from the AMF a RA useful list of CAG IDs allowed by the UE. In one example, the RA useful list of CAG IDs allowed by the UE may be received within a mobility restriction list IE included in the NGAP initial context establishment request message. According to some embodiments, the device 10 may be controlled by the memory 14 and the processor 12 to store the received RA useful list of CAG IDs allowed by the UE and optionally use it for connected mode mobility. In one embodiment, the device 10 may also be controlled to propagate the RA useful list of CAG IDs allowed by the UE to the UE.

[0058] Figure 6b An apparatus 20 according to an example embodiment is shown. In an example embodiment, the apparatus 20 may be a node, host or server in a communication network, or serve such a network. For example, the apparatus 20 may be a satellite, a base station, a Node B, an evolved Node B (eNB), a 5G Node B or access point, a next generation Node B (NG-NB or gNB) and / or a WLAN access point associated with a radio access network (RAN) such as an LTE network, 5G or NR. In one embodiment, it may be an AMF, or other access or management network node. It should be noted that a person of ordinary skill in the art will understand that the apparatus 20 may include Figure 6b Components or features not shown.

[0059] like Figure 6b As shown in the example of , the device 20 may include a processor 22 for processing information and executing instructions or operations. The processor 22 may be any type of general or special purpose processor. For example, the processor 22 may include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although Figure 6bA single processor 22 is shown in FIG. 1 , but according to other embodiments, multiple processors may be used. For example, it should be understood that in some embodiments, the device 20 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in this case, the processor 22 may represent a multiprocessor). In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0060] According to certain example embodiments, processor 22 may perform functions associated with the operation of apparatus 20, which may include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of apparatus 20, including Figure 2 The process shown.

[0061] The device 20 may also include or be coupled to a memory 24 (internal or external), which may be coupled to the processor 22, and which is used to store information and instructions that can be executed by the processor 22. The memory 24 may be one or more memories and of any type suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 24 may include a random access memory (RAM), a read-only memory (ROM), a static storage device such as a magnetic disk or optical disk, a hard disk drive (HDD), or any other type of non-transitory memory or computer-readable medium. The instructions stored in the memory 24 may include program instructions or computer program codes that, when executed by the processor 22, enable the device 20 to perform tasks as described herein.

[0062] In one embodiment, the device 20 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store data for execution by the processor 22 and / or the device 20 to perform at least Figure 1 A computer program or software according to the method shown in Figure 5.

[0063] In certain example embodiments, the apparatus 20 may also include or be coupled to one or more antennas 25 for transmitting signals and / or data to and receiving signals and / or data from the apparatus 20. The apparatus 20 may also include or be coupled to a transceiver 28 configured to transmit and receive information. The transceiver 28 may include, for example, a plurality of radio interfaces that may be coupled to the (multiple) antennas 25. The radio interfaces may correspond to a variety of radio access technologies, including one or more of the following: GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, radio frequency identifier (RFID), ultra-wideband (UWB), MulteFire, etc. The radio interfaces may include components such as filters, converters (e.g., digital-to-analog converters, etc.), mappers, fast Fourier transform (FFT) modules, etc., to generate symbols for transmission via one or more downlinks and receive symbols (e.g., via uplinks).

[0064] Thus, the transceiver 28 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 25 and to demodulate information received via the antenna(s) 25 for further processing by other elements of the apparatus 20. In other embodiments, the transceiver 18 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some embodiments, the apparatus 20 may include input and / or output devices (I / O devices).

[0065] According to an example embodiment, the apparatus 20 may optionally be configured to communicate with the apparatus 10 via a wireless or wired communication link 70 according to any radio access technology such as NR. In one embodiment, the link 70 may represent an Xn interface.

[0066] In one embodiment, memory 24 may store software modules that provide functionality when executed by processor 22. The modules may include, for example, an operating system that provides operating system functionality for device 20. The memory may also store one or more functional modules, such as applications or programs, to provide additional functionality to device 20. The components of device 20 may be implemented in hardware, or as any suitable combination of hardware and software.

[0067] According to some embodiments, the processor 22 and the memory 24 may be included in or may form part of processing circuitry or control circuitry.Furthermore, in some embodiments, the transceiver 28 may be included in or may form part of transceiver circuitry.

[0068] As described above, in some embodiments, the apparatus 20 may be a node, host, or server in a communication network, or serve such a network. For example, the apparatus 20 may be an AMF or other access or management node associated with a radio access network (RAN) such as an LTE network, 5G, or NR. According to some embodiments, the apparatus 20 may be controlled by the memory 24 and the processor 22 to perform processes associated with any of the example embodiments described herein, such as Figure 1 to those shown in Figure 5. For example, in one embodiment, the apparatus 20 may be controlled by the memory 24 and the processor 22 to execute a process for building a filtered authorization list for a private network.

[0069] According to certain embodiments, the device 20 may be controlled by the memory 24 and the processor 22 to receive information from at least one network node of the RA, the information including a list of CAG IDs supported by the TAI of the at least one network node and a list of neighboring TAIs corresponding to one or more other network nodes neighboring the at least one network node. According to some embodiments, the one or more other network nodes may or may not belong to the RA of the at least one network node. In one embodiment, the device 20 may be controlled by the memory 24 and the processor 22 to use the received information to determine a RA-related list of CAG IDs, the list including a list of CAG IDs supported in the RA and a list of CAG IDs supported by TAIs neighboring the RA. According to certain embodiments, the device 20 may be controlled by the memory 24 and the processor 22 to use the RA-related list of CAG IDs to filter the list of UE-allowed CAG IDs to derive a RA useful list of UE-allowed CAG IDs.

[0070] In some embodiments, for example, when the UE is connected to a network node of its RA, the device 20 may be controlled by the memory 24 and the processor 22 to transmit the RA useful list ID of the CAG allowed by the UE to at least one network node, and controlled to transmit the RA useful list of the CAG ID allowed by the UE to the UE. In one example, the RA useful list of the CAG ID allowed by the UE may be transmitted to the UE within the mobility restriction list IE included in the NGAP initial context setup request message and within the NAS PDU information element of the NGAP message (such as the NGAP initial context setup request message). According to certain embodiments, the device 20 may be controlled by the memory 24 and the processor 22 to calculate the updated RA useful list of the CAG ID allowed by the UE when the UE changes to a new RA via a network node of a neighboring TAI and transmit the updated list to the network node of the neighboring TAI, and may also be controlled to send the updated RA useful list of the CAG ID allowed by the UE to the UE.

[0071] Thus, certain example embodiments provide several technical improvements, enhancements and / or advantages over prior art procedures and constitute improvements in at least the technical field of wireless network control and management. For example, signaling overhead and processing load may be reduced due to certain embodiments described herein. Thus, use of certain example embodiments may improve the functionality of a communication network and its nodes (such as a base station, NG-RAN node, eNB, gNB and / or UE or mobile station).

[0072] In some example embodiments, the functionality of any method, process, signaling diagram, algorithm or flow chart described herein may be implemented by software and / or computer program code or code portions stored in a memory or other computer readable or tangible medium and executed by a processor.

[0073] In some example embodiments, an apparatus may be included in or associated with at least one software application, module, unit, or entity configured for (multiple) arithmetic operations, or configured as a program or portion thereof (including added or updated software routines) executed by at least one operating processor. A program (also referred to as a program product or computer program, including software routines, applets, and macros) may be stored in any apparatus-readable data storage medium and may include program instructions for performing specific tasks.

[0074] The computer program product may include one or more computer executable components that are configured to perform some example embodiments when the program is run. The one or more computer executable components may be at least one software code or code portion. Modifications and configurations required to implement the functionality of the example embodiments may be performed as (multiple) routines, which may be implemented as (multiple) added or updated software routines. In one example, (multiple) software routines may be downloaded to the device.

[0075] As an example, the software or computer program code or code portion may be in source code form, object code form or some intermediate form, and it may be stored in some carrier, distribution medium or computer readable medium, which may be any entity or device capable of carrying the program. For example, such a carrier may include a recording medium, a computer memory, a read-only memory, an optoelectronic and / or electrical carrier signal, a telecommunication signal and / or a software distribution packet. Depending on the processing power required, the computer program may be executed in a single electronic digital computer or distributed among multiple computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.

[0076] In other example embodiments, the functions may be performed by hardware or circuitry included in a device (e.g., device 10 or device 20), such as by using an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other hardware and software combination. In yet another example embodiment, the functions may be implemented as a signal, such as an intangible device that may be carried by an electromagnetic signal downloaded from the Internet or other network.

[0077] According to example embodiments, an apparatus such as a node, a device or a corresponding component may be configured as a circuit device, a computer or a microprocessor, such as a single-chip computer element, or as a chipset, which may include at least a memory for providing storage capacity for (multiple) arithmetic operations and / or an operation processor for performing (multiple) arithmetic operations.

[0078] Those skilled in the art will readily appreciate that the example embodiments discussed above may be practiced with processes in a different order and / or with hardware elements in a different configuration than disclosed. Therefore, although some embodiments have been described based on these example embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative constructions will be apparent while remaining within the spirit and scope of the example embodiments.

[0079] A first embodiment relates to a method which may include receiving, at a network node of a RA, a list of cells and their associated TAIs from at least one other network node that may be connected to the network node via Xn. The method may then include determining which of the received TAIs are neighboring TAIs of one of the TAIs of the network node. The method may also include building a list of neighboring TAIs corresponding to at least one other network node. The method may also include transmitting to an AMF a list of CAG IDs supported by the TAI of the network node and a list of neighboring TAIs corresponding to at least one other network node. The method may also include receiving from the AMF a RA useful list of CAG IDs allowed by the UE, for example, when the UE is connected via the network node of the RA of the UE.

[0080] In one variation, receiving the RA useful list of CAG IDs allowed by the UE may include receiving the RA useful list of CAG IDs allowed by the UE within a Mobility Restriction List IE included in the NGAP Initial Context Setup Request message.

[0081] According to one variant, the method may further comprise storing the received RA useful list of UE allowed CAG IDs and optionally using it for connected mode mobility.In another variant, the method may further comprise propagating the RA useful list of UE allowed CAG IDs to the UE, for example via a NAS container.

[0082] In one variant, receiving the list of cells may include receiving the list in an Xn setup message from at least one other network node.

[0083] In one variant, determining which of the received TAIs are neighbour TAIs of one of the network node's TAIs may be done using knowledge of which cells are neighbour cells of the network node's own cell.

[0084] A second embodiment relates to a method, which may include: the AMF receives information from at least one network node of a RA, the information including a list of CAG IDs supported by a TAI of the at least one network node and a list of adjacent TAIs corresponding to one or more other network nodes adjacent to the at least one network node. In some examples, the one or more other network nodes may not belong to the RA of the at least one network node. The method may also include using the received information to determine an RA-related list of CAG IDs, the list including CAG IDs supported in the RA and a list of CAG IDs supported by TAIs adjacent to the RA. The method may then include filtering a list of UE-allowed CAG IDs using the RA-related list of CAG IDs to derive a RA useful list of UE-allowed CAG IDs. The method may include transmitting a RA useful list of UE-allowed CAG IDs to at least one network node, and may include transmitting a RA useful list of UE-allowed CAG IDs to the UE.

[0085] In one variant, when a UE connects to a network node of the UE's RA, a RA useful list of CAG IDs allowed by the UE may be transmitted.

[0086] In one variant, transmitting the RA useful list of CAG IDs allowed by the UE may include transmitting the RA useful list of CAG IDs allowed by the UE to the network node within a mobility restriction list IE included in an NGAP initial context setup request message, and transmitting the RA useful list of CAG IDs allowed by the UE towards the UE in the same NGAP initial context setup request message or an equivalent NGAP message, within a NAS PDU.

[0087] According to one variant, the method may further include: when the UE changes to a new RA via a network node of a neighboring TAI, calculating an updated RA useful list of CAG IDs allowed by the UE, and transmitting the updated list to the network node of the neighboring TAI, and transmitting the updated list to the UE.

[0088] A third embodiment relates to an apparatus comprising at least one processor and at least one memory comprising computer program code. The at least one memory and the computer program code may be configured to, together with the at least one processor, cause the apparatus to at least perform a method according to the first embodiment or the second embodiment or any variant thereof.

[0089] A fourth embodiment relates to an apparatus, which may include a circuit arrangement configured to perform the method according to the first embodiment or the second embodiment or any variants thereof.

[0090] A fifth embodiment relates to an apparatus which may include modules for performing the method according to the first embodiment or the second embodiment or any variants thereof.

[0091] A sixth embodiment is directed to a non-transitory computer-readable medium including program instructions stored thereon for performing at least the method according to the first embodiment or the second embodiment or any variants thereof.

Claims

1. A communication method, comprising: receiving, at a network node of a registration area, a list of cells and associated tracking area identities (TAIs) of the cells from at least one other network node of the registration area; determining which of the received TAIs are neighboring TAIs of one of the TAIs of the network node; constructing a list of neighboring TAIs corresponding to the at least one other network node; transmitting to a network management entity a list of closed access group identifiers (CAGIDs) supported by the TAI of the network node and the list of neighboring TAIs corresponding to the at least one other network node; as well as Receive a list of CAGIDs allowed by the user equipment from the network management entity, wherein the list of CAGIDs allowed by the user equipment is derived by filtering the registration area related list of CAGIDs by the network management entity, wherein the registration area related list of CAG IDs includes a list of CAG IDs supported in the registration area and a list of CAGIDs supported by TAIs adjacent to the registration area.

2. The method of claim 1 , wherein receiving the list of cells comprises: The list is received in an Xn setup message from the at least one other network node.

3. The method of claim 1 , wherein receiving a list of CAGIDs allowed by the user equipment comprises: A list of CAGIDs allowed by the user equipment is received in a mobility restriction list information element (IE).

4. The method according to claim 3, wherein the mobility restriction list IE is included in an initial context setup request message.

5. The method according to any one of claims 1 to 4, wherein receiving a list of CAG IDs allowed by the user equipment comprises: When a user equipment is connected via the network node of a registration area of ​​the user equipment, a list of CAG IDs allowed by the user equipment is received.

6. A communication device, comprising: means for receiving, by the apparatus of a registration area, from at least one network node of the registration area, a list of cells and associated tracking area identities (TAIs) of the cells; means for determining which of the received TAIs are neighboring TAIs of one of the TAIs of the device; means for constructing a list of neighboring TAIs corresponding to the at least one network node; means for transmitting to a network management entity a list of closed access group identifiers (CAGIDs) supported by the TAI of the apparatus and the list of neighboring TAIs corresponding to the at least one network node; as well as A component for receiving a list of CAG IDs allowed by a user equipment from the network management entity, wherein the list of CAG IDs allowed by the user equipment is derived by filtering a registration area related list of CAGIDs by the network management entity, wherein the registration area related list of CAGIDs includes a list of CAG IDs supported in the registration area and a list of CAGIDs supported by TAIs adjacent to the registration area.

7. The apparatus of claim 6, wherein the apparatus comprises a next generation radio access network node and the network management entity comprises an access management function.

8. The apparatus of claim 6 or 7, wherein receiving the list of cells comprises receiving the list in an Xn setup message from the at least one network node.

9. The apparatus of claim 6 or 7, wherein determining which of the received TAIs are neighboring TAIs of one of the TAIs of the apparatus is performed using knowledge of which cells are neighboring cells of the apparatus' own cell.

10. The apparatus according to claim 6 or 7, wherein receiving a list of CAGIDs allowed by the user equipment comprises: A list of CAGIDs allowed by the user equipment is received in a mobility restriction list information element (IE).

11. The apparatus of claim 10, wherein the mobility restriction list IE is included in an initial context setup request message.

12. The apparatus according to claim 6 or 7, wherein receiving a list of CAG IDs allowed by the user equipment comprises: When a user equipment connects via the apparatus of a registration area of ​​the user equipment, a list of CAGIDs allowed by the user equipment is received.

13. The device according to claim 6 or 7, further comprising: Means for storing the received list of CAG IDs allowed by the user equipment and means for using the list of CAG IDs allowed by the user equipment for connected mode mobility.

14. A communication device, comprising: means for receiving information from at least one network node of a registration area, the information comprising a list of closed access group identifiers (CAGIDs) supported by a tracking area identity (TAI) of the at least one network node and a list of neighboring TAIs corresponding to one or more other network nodes of the registration area neighboring the at least one network node; means for generating a list of CAGIDs allowed by a user equipment based on the received information, determining a list of CAGIDs supported in the registration area and a list of CAGIDs supported by a TAI adjacent to the registration area; means for filtering the list of CAG IDs allowed by the user equipment to derive a subset list of CAG IDs allowed by the user equipment; as well as Means for transmitting to the at least one network node a list of a subset of CAG IDs allowed by the user equipment.

15. The apparatus of claim 14, wherein the transmitting comprises: The subset list of CAGIDs allowed by the user equipment is transmitted in a mobility restriction list information element included in the initial context setup request message.

Images