Method and apparatus for handling a femto access control in a wireless communication system

Abstract

The disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Embodiments herein disclose methods and systems for enabling an authorized administrator to update CAG information to a network for 5G Femto access control, in a home and visited network. Subscription data of a UE (102) is updated with femto IDs, in case of a roamer. The method further addresses enabling mobility of UEs in between CSG cells in 4G to CAG cells of 5G femto by enhancing UE subscription information exchange across 5GC and EPC to allow seamless mobility in between CSG and 5G Femto cells. In an embodiment. The method includes exposing, by an UDM entity (122), a service to allow a CAG administrator to provision a CAG subscription associated with at least one User Equipment (UE) (102). The service exposed by the UDM entity (122) is enhanced to allow an action. Further, the method includes handling, by the UDM entity (122), a femto access control based on the CAG subscription.

Description

METHOD AND APPARATUS FOR HANDLING A FEMTO ACCESS CONTROL IN A WIRELESS COMMUNICATION SYSTEM

[0001] Embodiments disclosed herein relate to a wireless communication network, and more particularly to systems (or wireless communication network) and methods for allowing an authorized administrator providing access to a Femto / Closed Access Group　(CAG) cell for a set of local users and / or visiting users.

[0002] 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in "Sub 6GHz" bands such as 3.5GHz, but also in "Above 6GHz" bands referred to as mmWave including 28GHz and 39GHz. In addition, it has been considered to implement 6G mobile communication technologies (referred to as Beyond 5G systems) in terahertz (THz) bands (for example, 95GHz to 3THz bands) in order to accomplish transmission rates fifty times faster than 5G mobile communication technologies and ultra-low latencies one-tenth of 5G mobile communication technologies.

[0003] At the beginning of the development of 5G mobile communication technologies, in order to support services and to satisfy performance requirements in connection with enhanced Mobile BroadBand (eMBB), Ultra Reliable Low Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), there has been ongoing standardization regarding beamforming and massive MIMO for mitigating radio-wave path loss and increasing radio-wave transmission distances in mmWave, supporting numerologies (for example, operating multiple subcarrier spacings) for efficiently utilizing mmWave resources and dynamic operation of slot formats, initial access technologies for supporting multi-beam transmission and broadbands, definition and operation of BWP (BandWidth Part), new channel coding methods such as a LDPC (Low Density Parity Check) code for large amount of data transmission and a polar code for highly reliable transmission of control information, L2 pre-processing, and network slicing for providing a dedicated network specialized to a specific service.

[0004] Currently, there are ongoing discussions regarding improvement and performance enhancement of initial 5G mobile communication technologies in view of services to be supported by 5G mobile communication technologies, and there has been physical layer standardization regarding technologies such as V2X (Vehicle-to-everything) for aiding driving determination by autonomous vehicles based on information regarding positions and states of vehicles transmitted by the vehicles and for enhancing user convenience, NR-U (New Radio Unlicensed) aimed at system operations conforming to various regulation-related requirements in unlicensed bands, NR UE Power Saving, Non-Terrestrial Network (NTN) which is UE-satellite direct communication for providing coverage in an area in which communication with terrestrial networks is unavailable, and positioning.

[0005] Moreover, there has been ongoing standardization in air interface architecture / protocol regarding technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and convergence with other industries, IAB (Integrated Access and Backhaul) for providing a node for network service area expansion by supporting a wireless backhaul link and an access link in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access for simplifying random access procedures (2-step RACH for NR). There also has been ongoing standardization in system architecture / service regarding a 5G baseline architecture (for example, service based architecture or service based interface) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) for receiving services based on UE positions.

[0006] As 5G mobile communication systems are commercialized, connected devices that have been exponentially increasing will be connected to communication networks, and it is accordingly expected that enhanced functions and performances of 5G mobile communication systems and integrated operations of connected devices will be necessary. To this end, new research is scheduled in connection with eXtended Reality (XR) for efficiently supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality) and the like, 5G performance improvement and complexity reduction by utilizing Artificial Intelligence (AI) and Machine Learning (ML), AI service support, metaverse service support, and drone communication.

[0007] Furthermore, such development of 5G mobile communication systems will serve as a basis for developing not only new waveforms for providing coverage in terahertz bands of 6G mobile communication technologies, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.

[0008] A femtocell is a small, low-power cellular base station, which typically connects to a service provider's network via the Internet through a wired broadband link. In current state of art, the wireless networks based on 3rd Generation Partnership Project (3GPP) technologies utilize femtocells to enhance coverage of the wireless network to residential areas when a signal quality and / or capacity are not satisfactory, (e.g. in hard-to-reach areas).

[0009] The 3GPP is studying whether and how to enhance a fifth generation (5G) technology to support Femto cells in its Rel-19 version of specification. The study details are captured in 3GPP technical report (TR) 23.700-45, and it is assumed that an existing CAG concept defined for Public Network Integrate- Non-Public Network (PNI-NPN) is re-used for Femto access control.

[0010] A CAG refers to a Closed Access Group, and a CAG identity is associated with a cell to which only a select group of UEs have access. These select User Equipment's (UEs) are configured with these CAG identities. Similarly, their subscription data in an Unified data management (UDM) entity contains a list of CAG identities that they have access. When the UE wishes to access a CAG cell, the UE first checks a local configuration before the initiating access. Further, the network verifies whether the UE has the required subscription to access the cell. The detailed procedure is defined in 3GPP technical (TS) 23.501 and 3GPP TS 23.502. The allowed CAG list may be provisioned to the UE through downlink NAS (non-access stratum) message (e.g., configuration update command or registration accept, service reject or network initiated de-registration request). The allowed CAG list is CAG-ID(s) included in the CAG information list or extended CAG information list IE (information elements). Additionally the, the CAG-ID can be associated with the validity time where the validity timer specifies the time period for which the CAG-ID is valid / applicable. The detailed methods for sharing the CAG information is specified in TS 24.501.

[0011] Further, In fourth generation (4G), CSG or Closed Subscriber Group is an architecture where 4G cells broadcast one or more CSG IDs per cell. Such cells allow restricted access only for the UEs that support CSG, and are configured with allowed CSG IDs associated with the Public Land Mobile Network (PLMN). The UE is typically configured with an Allowed CSG list and an Operator CSG list and associated PLMN identities. Both lists can be retrieved either from a Universal Subscriber Identity Module (USIM) if the lists are available in the USIM, or as described in 3GPP TS 24.285 if the lists are not available in the USIM. The architecture for the above is described in 3GPP TS 23.401. Further, the network selection logic for the CSG cells are defined in 3GPP TS 23.122 and 3GPP TS 24.301.

[0012] One of the issue that the study aims to address is how to enable an authorized administrator or CAG owner or 3rd party to provision / update CAG information to the network for 5G Femto access control, for allowing access to the CAG cell in a home network and a visited network. This may require updating the UE's subscription data as described above. Further, in case of a roamer, update of UE's subscription data may not be allowed by the home network of the UE. Further, existing technologies do not address how to enable mobility of UEs in between CSG cells in 4G to CAG cells of 5G Femto.

[0013] Hence, there is a need in the art for solutions which will overcome the above mentioned drawback(s), among others.

[0014] The principal object of embodiments herein is to disclose methods and systems for enabling an authorized administrator to provision / update CAG information to the network for a 5G Femto access control, for allowing access to a CAG cell in the home and visited network.

[0015] Another object of embodiments herein is to update the UE's subscription data.

[0016] Another object of embodiments herein is to enable the subscription data of the UE to be updated, in case of a roamer.

[0017] Another object of embodiments herein is to provide a system and method of allowing mobility across 4G and 5G femto cells.

[0018] Another object of embodiments herein is to enable mobility of UEs in between CSG cells in the 4G to CAG cells of the 5G Femto.

[0019] Another object of embodiments herein is to handle a handover from a 5GS to an EPS.

[0020] Another object of embodiments herein is to handle a handover from the EPS to the 5GS.

[0021] Accordingly embodiments herein disclose a method for handling a Femto access control. The method includes exposing, by a UDM entity, a service to allow a CAG administrator to provision a CAG subscription associated with at least one UE, where the service exposed by the UDM entity is enhanced to allow an action. Further, the method includes handling, by the UDM entity, a Femto access control based on the CAG subscription.

[0022] Accordingly, embodiments herein disclose an UDM entity including an Femto access control handling controller coupled with a processor and a memory. The Femto access control handling controller is configured to expose a service to allow a CAG administrator to provision CAG subscription associated with at least one UE. The service exposed by the UDM entity is enhanced to allow an action. The Femto access control handling controller is configured to handle a Femto access control based on the CAG subscription.

[0023] In an embodiment, the method comprises storing, by the UDM entity, data associated with the service into a Unified Data Repository (UDR) entity.

[0024] In an embodiment, the method comprises informing, by the UDM entity, about an updated allowed CAG list associated with the at least one UE to an Access & Mobility Management Function (AMF) entity, wherein the AMF entity informs the updated allowed CAG list associated with the at least one UE to a first network entity, wherein the first network entity is a gNB.

[0025] In an embodiment, the method comprises notifying, by the UDM entity, the AMF entity to update a CAG subscription data in at least one the UE by sending a UE configuration update command or any other downlink NAS message (e.g., registration accept or service reject or network initiated deregistration request).

[0026] In an embodiment, the service is a Nudm parameter provision service, wherein the CAG owner provisions the CAG subscription to the UDM entity directly if the CAG owner plays a role of a trusted Application Function (AF) entity, wherein the CAG owner provisions to the UDM entity through a Network Exposure Function (NEF) entity if the CAG owner plays a role of an untrusted Application Function (AF) entity.

[0027] In an embodiment, the action corresponding to enforce the femto access control by at least one of: the UE, a first network entity and an AMF entity.

[0028] In an embodiment, a request associated with the service comprises at least one detail associated with the at least one UE, an indication, and a validity time up to which association of the at least one UE to the CAG is allowed or valid. The indication comprises at least one of: an add service related indication and a remove service related indication.

[0029] In an embodiment, at least one of: the AF entity and the NEF entity in a visited network configures an Access & Mobility Management Function (AMF) entity associated with a visited-network to allow at least one roamer access the network through a CAG cell.

[0030] In an embodiment, the method includes providing, by at least one of: the UDM entity and an UDR entity, an allowed Femto list to an AMF entity, wherein the AMF entity shares the Allowed Femto list to a first network entity. Further, the method includes providing, by at least one of: the UDM entity and the UDR entity, the allowed Femto list to a Mobility Management Entity (MME) entity through at least one of: a Home Subscriber Server (HSS) entity and a Closed Subscriber Server (CSS) entity, wherein the MME entity provides the allowed Femto list to a second network entity. At least one of: the MME and the second network entity provides the allowed Femto list to the UE if the UE is connected or registered in at least one of: a 4GS or Evolved Packet Core (EPC). At least one of: the AMF and the first network entity provides the allowed Femto list to the UE when the UE is connected or registered to a fifth generation core (5GC).

[0031] In an embodiment, the allowed Femto list is at least one of: a combination of the allowed CAG list and an operator CSG list and mapping of the allowed CAG list and an Operator CSG list.

[0032] In an embodiment, the Femto list is configured in a Universal Subscriber Identity Module (USIM) in the UE or updated to the UE with a non-access stratum (NAS) signalling messages.

[0033] In an embodiment, the method includes receiving, by the AMF entity, a handover request from a first network entity, wherein the first network entity uses an allowed CSG list received from the AMF entity to determine a target-cell during a handover preparation procedure. Further, the method includes sending, by the AMF entity, a relocation request to the target MME entity, wherein the AMF entity finds an MME entity that supports at least one required feature for the UE and identifies the MME entity using existing 3GPP mechanisms. Further, the method includes additionally taking into consideration the allowed CSG list or an operator CSG list supported by at least one of: the target MME entity and the second network entity. Further, the method includes sending, by the MME entity, a handover request to the second network entity based on the relocation request. Further, the method includes receiving, by the MME entity, a handover response from the second network entity based on the handover request.

[0034] In an embodiment, to support mobility from a fifth generation (5G) or a fifth generation core (5GC) to a fourth generation system (4GS) or an Evolved Packet Core (EPC), a supported CSG IDs corresponding to a serving PLMN of the target MME ensures that the UE that supports a CSG will only be allowed to move to an allowed CSG cell.

[0035] In an embodiment, further, the method includes receiving, by the MME entity, a handover request from a second network entity. Further, the method includes sending, by the MME entity, a relocation request to the target AMF wherein the MME entity identifies a target AMF entity that will support at least one required feature for the UE and identifies the AMF entity using existing 3GPP mechanisms. Further, the method includes additionally considering the allowed CAG identifiers from the Allowed CAG list in the UE which are supported by the target AMF entity. Further, the method includes sending, by the AMF entity, a handover request to the first network entity based on the relocation request. Further, the method includes receiving, by the AMF entity, a handover response from the first network entity based on the handover request.

[0036] In an embodiment, a decision to continue with a handover is performed by the target AMF entity, wherein the target AMF entity determines whether a target cell supports the allowed CAG list configured for the UE.

[0037] In an embodiment, a validation of the target AMF target AMF entity, based on the Allowed CAG IDs of the UE for the corresponding PLMN, is done at the AMF entity, wherein when the target AMF entity does not identify any one of a CAG ID from the Allowed CAG list for the PLMN, for the UE, the AMF entity rejects a forward relocation request to the MME Forward relocation request, based on which the MME Forward relocation request performs another AMF selection.

[0038] In an embodiment, the first network entity selects a target eNB for a 5GC to an EPC handover, wherein the second network entity selects a target gNB for the 5GC to EPC handover.

[0039] In an embodiment, the first network entity is a gNB and the second network entity is an eNB

[0040] in an embodiment, the authorized administrator can be a CAG owner or a 3rdparty service provider.

[0041] in an embodiment, the allowed CAG identifier list is interchangeably used for the CAG information list or extended CAG information list. The CAG information list or extended CAG list contains the CAG-ID allowed for the UE. The extended CAG information list additionally contain validity time where the validity timer specifies the "time period" for which the CAG-ID is valid / applicable for the UE

[0042] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating at least one embodiment and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the scope thereof, and the embodiments herein include all such modifications.

[0043] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide efficient communication methods in a wireless communication system.

[0044] Embodiments herein are illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the following illustratory drawings. Embodiments herein are illustrated by way of examples in the accompanying drawings, and in which:

[0045] FIG. 1 shows network architecture and example flow of a UE that is accessing 4GS / EPC via a CSG cell and 5GC via a Femto CAG cell, according to prior art;

[0046] FIG. 2 shows network architecture and example flow of CAG authorization information across different constituents of the network, according to embodiments as disclosed herein;

[0047] FIG. 3 depicts an example call-flow of events leading to updating of CAG subscription data for homer UEs, according to embodiments as disclosed herein;

[0048] FIG. 4 depicts an example call-flow of events leading to configuration of CAG authorization data for visited UEs, according to embodiments as disclosed herein;

[0049] FIG.5 shows an example call-flow of events leading to mobility (handover) from the EPS to 5GC, according to embodiments enclosed herein. In an embodiment herein;

[0050] FIG.6 shows an example call-flow of events leading to mobility (handover) from the 5GS to the EPS, according to embodiments enclosed herein. In an embodiment herein;

[0051] FIG.7 depicts an example call-flow of events leading to handover from the EPS to the 5GC, according to embodiments enclosed herein. In an embodiment herein;

[0052] FIG. 8 depicts a block diagram of a UDM entity for handling femto access control, according to embodiments as disclosed herein;

[0053] FIG. 9 depicts a method for handling a femto access control, according to embodiments as disclosed herein;

[0054] FIG. 10 depicts a block diagram of a user equipment (UE), according to embodiments as disclosed herein;

[0055] FIG. 11 depicts a block diagram of a base station (BS), according to embodiments as disclosed herein; and

[0056] FIG. 12 depicts a block diagram of a network entity, according to embodiments as disclosed herein.

[0057] Aspects of the disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the disclosure is to provide a terminal and a communication method thereof in a wireless communication system.

[0058] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

[0059] For the purposes of interpreting this specification, the definitions (as defined herein) will apply and whenever appropriate the terms used in singular will also include the plural and vice versa. It is to be understood that the terminology used herein is for the purposes of describing particular embodiments only and is not intended to be limiting. The terms "comprising", "having" and "including" are to be construed as open-ended terms unless otherwise noted.

[0060] The words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.,", "i.e.," are merely used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein using the words / phrases "exemplary", "example", "illustration", "in an instance", "and the like", "and so on", "etc.", "etcetera", "e.g.,", "i.e.," is not necessarily to be construed as preferred or advantageous over other embodiments.

[0061] Embodiments herein may be described and illustrated in terms of blocks which carry out a described function or functions.　These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.　The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block.　Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure.　Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

[0062] It should be noted that elements in the drawings are illustrated for the purposes of this description and ease of understanding and may not have necessarily been drawn to scale. For example, the flowcharts / sequence diagrams illustrate the method in terms of the steps required for understanding of aspects of the embodiments as disclosed herein. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Furthermore, in terms of the system, one or more components / modules which comprise the system may have been represented in the drawings by conventional symbols, and the drawings may show only those specific details that are pertinent to understanding the present embodiments so as not to obscure the drawings with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.

[0063] The accompanying drawings are used to help easily understand various technical features and it should be understood that the embodiments presented herein are not limited by the accompanying drawings. As such, the disclosure should be construed to extend to any modifications, equivalents, and substitutes in addition to those which are particularly set out in the accompanying drawings and the corresponding description. Usage of words such as first, second, third etc., to describe components / elements / steps is for the purposes of this description and should not be construed as sequential ordering / placement / occurrence unless specified otherwise.

[0064] The embodiments herein achieve methods and systems for enabling an authorized administrator to provision or update CAG information to the network for 5G femto access control.

[0065] In an embodiment, the method can be used for handling the Femto access control. The method includes exposing, by a UDM entity, a service to allow a CAG administrator to provision a CAG subscription associated with at least one UE, where the service exposed by the UDM entity is enhanced to allow an action. Further, the method includes handling, by the UDM entity, a Femto access control based on the CAG subscription.

[0066] In an embodiment, UDM exposes a service to allow a 3rd party update CAG subscription of the UE. The Nudm_ParameterProvision service exposed by the UDM may be enhanced to allow such action. The UDM may further store the data into UDR. Such a service may be used by the AF / NEF to configure UDM with the request sent by the 3rdparty.

[0067] In an embodiment, the NEF may expose a new service, or enhance the existing service to allow a trusted AF send such a request.

[0068] In an embodiment, The request may include UE details, e.g. the MSISDN numbers, GPSI or SUPI of UE1, UE2, UE3 and UE4, add / remove indication, the validity time up to which such association of UE to CAG is allowed / valid

[0069] In case of roamer, the AF / NEF in visited network directly configures the AMFs of visited-network to allow such roamers access the network through a specific CAG cell.

[0070] In one aspect the objects are achieved by providing a system and method of allowing mobility across 4G and 5G femto cells. The method addresses is how to enable mobility of UEs in between CSG cells in 4G to CAG cells of 5G Femto. The disclosure proposes to enhance the UE subscription information exchange across 5GC and 4GS / EPC and modifications in existing procedures to allow seamless mobility in between CSG and 5G Femto cells. The proposed solution allows mobility initiated by the UE and mobility which is triggered by the network across these 2 different systems.

[0071] Accessing the network through a base station requires the following:

[0072] a) UDM & UE are configured with an allowed list of CAG identifiers;

[0073] b) During registration, UDM provides AMF with an allowed list of CAG identifiers for the UE. If UE is connected from a non-allowed CAG cell, its request is denied;

[0074] ▷AMF provides the list of allowed CAG identifiers to the RAN (e.g. FEMTO device) whenever UE connects to the network. If UE is connecting from a non-allowed CAG cell, its request is denied;

[0075] ▷AMF updates UE if it determines that UE may not be updated with the latest CAG subscription information;

[0076] ▷HSS and / or CSS (Closed Subscriber Server) is configured with the Allowed or Operator CSG list of the UE;

[0077] ▷The HSS and / or CSS provides the Allowed or Operator CSG list of the UE to the MME; and

[0078] ▷MME provides the Allowed or Operator CSG list of the UE to the eNB.

[0079] ▷eNB / gNB utilize CSG / CAG IDs supported by target cells to determine whether to allow / disallow handovers.

[0080] The method can be used to allow the 3rdparty or the CAG owner or the administrator to configure the UE with the information to access the Femto cell in an effective manner.

[0081] Referring now to the drawings, and more particularly to FIGS. 2 through 9, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.

[0082] FIG. 1 shows network architecture and example flow of the UE that is accessing 4GS / EPC via a CSG cell and 5GC via a Femto CAG cell, according to prior art. In other words, FIG. 1 shows a case where the UE can access the 4GS / EPC via a CSG cell while connected to an eNB or can connect to 5GC via a CAG cell of 5G Femto.

[0083] Consider that the UE is initially connected to 4GS / EPC via the CAG cell, and there is a neighbouring CAG cell of 5G Femto. To support mobility of the UE to the neighbouring CAG cell of 5G Femto, necessary information will be required in the NFs or UE. For example, to support X2 based handover, the eNB needs to know the allowed list of CAG identifiers for the UE for the corresponding PLMN supported by the neighbouring gNB. This is because the gNB may be broadcasting cells of PLMN-1, cell 1, which have supported CAG IDs CAG ID1 & CAG ID 2, & another cell which is cell 2, which has supported CAG IDs as CAG ID 1, and CAG ID 3. Let's assume that the UE is configured with PLMN-1, CAG-ID 3 in the Allowed CAG list. If the eNB performs a handover of the UE to gNB cell-1, which broadcasts PLMN-1 CAG IDs 1 & 2, the handover will eventually fail due to CAG access restrictions. Similarly, if the MME wants to perform Xn based handover of the UE, the MME needs to know whether there are any CAG IDs part of the Allowed CAG list of the UE corresponding to the PLMN supported by the AMF in 5GC.

[0084] In the same way, to support mobility from the CAG cell of the 5GC to the CSG cell of the UE, the gNB needs to know the Allowed or Operator CSG list of the UE corresponding to the PLMN supported by the eNB / MME in EPS / EPC.

[0085] FIG. 2 shows a network architecture and example flow of CAG authorization information across different constituents of the network, according to embodiments as disclosed herein. In an embodiment herein, the system includes a plurality of user equipment's (UE1 (102), UE2 (104), UE3 (106), UE4 (108)), an administrator UE (112), and a femto base station device (114). Further, the system of network elements comprises a visitor UE (UE5 (110)), an Application Function (AF) entity (114), a Network Exposure Function　entity (NEF) (116), a Unified Data Management (UDM) entity (122), and an Access and Mobility Management Function entity (AMF) (124). In an embodiment herein, the femto base station device (114) can be deployed inside an indoor environment. The femto base station device (114) is a low-power and low-range femtocell providing improved cellular coverage of a cellular network, to the indoor environment. In an embodiment herein, the AMF entity (124) of the system can provide femto low-power base station service to a UE through the femto base station device (114). Further, in an embodiment herein, Accessing the network through the base station requires the following:

[0086] a) The UDM (122) and the UE are configured with an allowed list of femto IDs such as CAG identifiers in 5G femtocells;

[0087] b) During registration, the UDM entity (122) provides the AMF entity (124) with the allowed list of CAG identifiers for the UE. If the UE is connected from a non-allowed CAG cell, its request is denied;

[0088] c) The AMF entity (124) provides the list of allowed CAG identifiers to the RAN (e.g. FEMTO device), whenever the UE connects to the network.

[0089] d) If the UE is connected from the non-allowed CAG cell, its request is denied. The AMF entity (124) updates the UE if it determines that UE may not be updated with the latest CAG subscription information.

[0090] In an embodiment herein, a UE of the plurality of UEs (UE1, UE2, UE3, UE4) can be designated as administrator UE of the femto base station device, wherein the administrator UE can be allowed to add or remove a UE who wants to access the cellular network through the femto base station device. In an embodiment herein, the administrator UE can add or remove a UE through the AF (118). Further, in an embodiment herein, the administrator UE can provide a UE access to the AF (118), through which the administrator UE adds or removes a femto ID to a UE. In an embodiment herein, the administrator UE can access the AF (118) either via broadband Internet, or via a UE-SIM embedded into the femto device, or via a subscription to the AF, wherein the femto device has access to the network. In an embodiment herein, the administrator UE can add a UE to access the AF via subscription of the UE which have access to the network.

[0091] In an example embodiment herein, the plurality of UEs (UE1, UE2, UE3, UE4) in the indoor environment can be administrator UEs, and may have subscription (e.g. via a SIM) to the cellular network which provides the femto base station device (114). In order to be able to access the network through the FEMTO device, their subscription data needs to be updated with corresponding femto identifier (ID) (such as CAG identifier for 5G femtocell). Additionally, the administrator of the femto base station device (114) may be able to add or remove the UEs as and when needed. In an embodiment herein, the administrator UEs can configure the CAG subscription data in the UDM entity (122), thus the administrator UE can be able to update CAG subscription data of the administrator UE.

[0092] In an embodiment herein, the UDM entity (122) exposes a service to allow the administrator UE to update CAG subscription of the administrator UE. In an embodiment herein, the Nudm_ParameterProvision service exposed by the UDM (122) can be enhanced to allow an action of updating CAG subscription of the administrator UE. In an embodiment herein, the UDM entity (122) can store CAG subscription data of the administrator UE in a UDR. In an embodiment herein, the AF entity (118) and the NEF entity (120) use the Nudm_ParameterProvision service to configure the UDM entity with a CAG subscription request sent by the administrator UE.

[0093] FIG. 3 example call-flow of events leading to updating of CAG subscription data for homer UEs, according to embodiments as disclosed herein.

[0094] At step 1, a FEMTO administrator UE, accesses the AF entity. The AF entity (118) can present to the administrator UE a webpage prompting the user to input the details of the UEs, the administrator UE wants to allow access to the AF entity (118). This process is preceded by authentication and authorization of the FEMTO administrator. In an example embodiment herein, the administrator UE, can enter UE details, e.g. the MSISDN numbers, GPSI or SUPI of UE1, UE2, UE3 and UE4, add / remove indication of UEs to a CAG, and so on. In an embodiment herein, the femto administrator can transmit a request of accessing network and adding or removing UEs to CAG is sent to the AF entity (118).

[0095] At step 2, the AF entity (118) sends the request of accessing network and adding or removing UEs to CAG to the NEF entity (120). In an embodiment herein, a trusted AF entity (118) is allowed by the NEF entity (120) to send the request. The NEF entity (120) may expose a new service of Nudm_ParameterProvision, or enhance an existing service of allowing a trusted AF entity to send the request to the NEF entity (120). In an example embodiment herein, the request includes a list of UEs, and a CAG identifier which is allowed for the UEs and the add or remove indication for the UEs. Further, in an example embodiment herein, the request may include a validity time up to which association of UE to a CAG is allowed (or valid). In an example embodiment herein, the AF entity (120) may send a separate request for each UE, depending on the NEF entity (120) is required to receive the separate request per-UE, in order to facilitate further transmission of the request.

[0096] At step 3, the NEF entity (120) may authorize the request from the AF optionally for the UEs to access network (core network node e.g., UDM / PCF etc.), and may need to translate the GPSI or MSISDN of the UEs to SUPI (Subscription Permanent Identifier) of the UEs.

[0097] At step 4, the NEF entity (120) sends a request to the UDM entity (122) to update subscription data of the UEs (UE1, UE2, UE3, UE4) with the CAG identifiers (or remove CAG identifiers). In an embodiment herein, the UDM entity can expose a new service of Nudm_ParameterProvision, or enhance an existing service of Nudm_ParameterProvision service in order to allow the NEF entity (120) (or AF entity) to send request of updating of the CAG information to the UDM entity. In an example embodiment herein, the request for updating the CAG information includes, the list of UEs, and at least one CAG identifier which is allowed or disallowed for the UEs, validity time etc. Alternatively, the NEF entity (120) may send a separate request for each UE, depending on whether the UDM is required to receive a request per-UE.

[0098] At step 5, the UDM entity (122) performs local validation of at least, whether the AF entity is allowed to initiate such a request of updating CAG subscription. Further, the UDM entity (122) performs local validation of whether such CAG information is allowed for the indicated UEs. In an embodiment herein, the UDM entity stores the information of CAG subscription in a UDR.

[0099] At step 6, the UDM entity (122) informs the AMF entity (124) with respect to updating the CAG subscription of the UEs. In an embodiment herein, the AMF entity (124) then informs a gNB about the updated allowed CAG list of the UEs. Further, in an embodiment herein, the UDM entity (122) notifies the AMF entity (124) to update the CAG subscription data in the UEs, wherein updating the CAG subscription data in is carried out by sending a UE Configuration Update command to each UEs. Thus, the 3rd party (or an administrator or CAG owner) is allowed to update UE's CAG subscription information in the UDM entity (122).

[0100] Going back to FIG. 2, consider the UE5 which does not belong to the same network as the FEMTO device. It is a roamer, e.g. visiting from another country. In order to provide a superior coverage, the administrator of the FEMTO device may want to allow a visitor to access the network through a FEMTO device temporarily. It is assumed that there is a roaming agreement between the two operators involved (FEMTO operator and the home-operator of the roamer).

[0101] The UDM of such a roamer resides in its home country. It may not be possible for the UDM / NEF in the home country to provide authorization to thousands of AFs / Femto-administrators around the world to update the subscription data of its subscribers. This is a security issue as well as difficult to manage so many authorizations. A method is required whereby a roamer is allowed to access a FEMTO device without the involvement of its home-network as long as required roaming agreements are in place.

[0102] In an embodiment, it is proposed that the AF / NEF in the visited network directly configures the AMFs of visited network to allow such roamers to access the network through a specific CAG cell. the administrator sends a request to the AF to allow a roamer's SUPI / GPSI / MSISDN to access the FEMTO, wherein the request includes the tracking area configured in the FEMTO, or the geographic location of the FEMTO. The AF and the NEF then determine the AMFs responsible for serving the given tracking area and / or geographic area and / or the FEMTO device identifier, and sends the request to all such AMFs. The AMFs store such notifications in their database. Later, when the roamer UE sends a registration request via the FEMTO device, the request is allowed based on presence of such notification from the AF / NEF. The notification may additionally include a validity time and / or the tracking-area ID and / or FEMTO ID in which the CAG is allowed for the visitor.

[0103] Such a procedure can also be used for a visitor from the same network as the FEMTO operator, e.g. to serve temporary guests at home.

[0104] FIG. 4 depicts an example call-flow of events leading to configuration of CAG authorization data for visited UEs, according to embodiments as disclosed herein.

[0105] At step 1, a FEMTO administrator UE accesses the AF entity (118), wherein the AF entity (118) presents to the femto administrator a webpage prompting a user to input the details of the visiting UE that the user wants to allow access to the AF entity (118). In an embodiment herein, authentication and authorization of the FEMTO administrator is performed by the AMF entity (118). The user of the administrator UE, enters the details of the UE, e.g. the MSISDN numbers, GPSI or SUPI, add / remove CAG indication etc. In an embodiment herein, the administrator UE, sends a request of addition / removal of UEs to CAG to the AF entity (118).

[0106] At step 2, the AF entity (118) sends the request to the NEF entity (120) of the home cellular network. In an embodiment herein, the NEF entity (120) exposes a new service, or enhance the existing service to allow a trusted AF entity to send such a request to the NEF entity. In an embodiment herein, the request includes the UE, and the CAG identifier that is allowed for the UE and the add / remove CAG indication. Further, in an embodiment herein, in case of a plurality of visitor UEs, the AF entity (118) may send a separate request for each UE, depending on whether the NEF is required to receive one request per UE. Further, in an embodiment herein, in case of a plurality of visitor UEs, the AF entity may send one request for all the visiting UEs.

[0107] At step 3, the NEF entity (120) may authorize the AF entity (118), by such as validating, if valid roaming agreements are correct. Further, in an embodiment herein, the NEF entity (120) may need to translate the GPSI or MSISDN of the UE to the SUPI of the UE.

[0108] At step 4, the NEF entity (120) determines a candidate AMF of a visitor cellular network, which will serve a femto cell, based on at least one of: a femto ID (such as, CAG ID for 5G). tracking areas for the UE, the geographical area for the UE. In an embodiment herein, the NEF entity can query a network repository function (NRF) for an AMF may have registered, or may have a local policy, for serving the femto cell.

[0109] At step 5, the NEF entity sends a notification to the candidate AMF entity informing local CAG policy for the visiting UE. This may require the candidate AMF to register a well-known notification endpoint to the NRF, or expose a new service operation to which such notification (or request) can be sent, or enhance an existing service operation in order to allow receiving such notification (or request). In an embodiment herein, the request includes at least, validity time up to which association of the visiting UE to a CAG is allowed and area of validity in femtocell.

[0110] At step 6, the candidate AMF entity may validate the received request. In an example embodiment herein, validating the received request include such as validating e.g., whether the UE is allowed to access the Femto cell server by the AMF, the UE is registered in the tracking area etc. The tracking areas served by the AMF entity, whether the visitor UE is already registered with the tracking areas and whether requisite roaming agreements are in place.

[0111] At step 7, the visitor UE sends a registration request to the candidate AMF entity via the femto cell (CAG cell). In an embodiment herein, the request lands on the candidate AMF entity, wherein the AMF entity already receive the notification from the NEF entity regarding local CAG policy for the visiting UE. The candidate AMF entity proceeds with the registration procedure, wherein the registration procedure takes place as per the registration method specified in 3GPP TS 23.502.

[0112] At step 8, the candidate AMF entity provides the CAG cell as a list of allowed cells to the FEMTO base-station device, as part of the registration procedure,.

[0113] At step 9, the candidate AMF entity updates the UE with allowed CAG identifier list, optionally with validity timer by sending to the gNB, a UE Configuration Update command for a current serving PLMN or including the allowed CAG identifier list in an other downlink message (e.g., registration accept, service reject or network initiated deregistration request).

[0114] Thus, a visitor UE is able to latch onto a CAG cell in a visited network without the involvement of its home network.

[0115] In another embodiment, the list of allowed UEs in the CAG cell operated by the femto base station device is provided to the AMF via NGAP messaging over an N2 Interface between FEMTO and AMF. AMF may further update the information to the UDM, or may use the authorization information locally.

[0116] FIG.5 shows an example call-flow of events leading to mobility (handover) from the EPS to 5GC, according to embodiments enclosed herein. In an embodiment herein, the UE (102) supports mobility between the EPS and the 5GC through femto ID information exchange across corresponding NFs or network nodes and from the 4GS (EPC) or the 5GC to the UE (102). In an embodiment herein, the Allowed femto list ((CAG list) + (Allowed or Operator CSG list)) is referred to as Allowed femto list in this illustration.

[0117] At Step 1, the UDM entity (122) or a UDR provides the allowed femto list to the AMF entity (124). At Step 2, the AMF entity (124) provides the allowed femto list to the gNB (406). Similarly,

[0118] At Step 3, the HSS / CSS provides the allowed femto list to the MME entity (402). At Step 4, the MME entity (402) provides the allowed femto list to the eNB (404).

[0119] At Step 5, the MME (402) or the eNB (404) provides the allowed femto list to the UE(102) if the UE is connected or registered in the 4GS (EPC). Similarly the AMF (gNB) provides the allowed femto list to the UE (102) when the UE is connected or registered to the 5GC.

[0120] Thus, the Allowed Femto list will be updated both in the 5GC and 4GS (EPC) and also the UE (102). The allowed femto list needs to be provided by the network to the UE when the UE is registered in 4GS (EPC) and / or in the 5GC. In an embodiment herein, the allowed femto list can also be configured in the USIM or updated to the UE via an NAS procedures such as without limitation, Attach, Tracking Area Update or Registration procedure, or UE configuration update (UCU) command or via other downlink NAS messages defined in 3GPP TS.23.401 and 3GPP TS 24.501 (e.g., registration accept message). In an embodiment herein, the UE (102) 2can use this information to perform a plurality of operations such as a cell selection, a cell re-selection, a PLMN or a RAT selection. In an example embodiment herein, while registered in the 5GC via the CAG cell of the 5G femto, the UE (102) can use the configured allowed or operator CSG list to move to a neighbouring CSG cell. Similarly while registered in the EPC via the CSG cell, the UE (102) can move to a neighbouring 5G CAG cell belonging to the 5G Femto.

[0121] FIG.6 shows an example call-flow of events leading to mobility (handover) from the 5GS to the EPS, according to embodiments enclosed herein. In an embodiment herein. The AMFs and the UE (102) are configured by a femto administrator with CAG information. The figure illustrates the initial steps of the handover process from 5GC to 4GS, and its related message exchanges between the NFs and the CP Nodes in the network. It is assumed that the UE is connected to the 5GC via a CAG cell of a 5G femto.

[0122] At step 1, the UDM entity (122) (UDR) in the 5GC or the HSS entity (412) or CSS in the 4GS / EPC will send the allowed femto list to the AMF entity (124) and the MME entity (402).

[0123] At step 2, the AMF entity (124) shares the allowed femto list with the gNB (406). At step 3, the MME entity (402) shares the allowed femto list with the eNB (404).

[0124] At step 4, the gNB (406) decides to handover the UE (102) from 5GC to 4GS (EPC) and initiates the Handover required message to the AMF entity (124). According to embodiments enclosed herein, the gNB (406) may use the allowed CSG list received from AMF to determine the target-cell during, e.g. handover preparation procedure.

[0125] At step 5, the AMF entity (124) finds a target MME that will support the required features for the UE and identifies an MME. The procedures for selecting an MME are described in 3GPP TS 23.401. In an embodiment herein, the AMF now may also take into consideration of the allowed CSG cells supported by the target MME (eNB) while selecting the target MME. In an embodiment herein, when none of the CSG IDs corresponding to the PLMN being served by the MME are configured as part of the allowed or operator CSG list in the UE (102), the AMF entity (124) will not continue with the handover procedure, and optionally find another MME that will support the CSG IDs configured in the UE. Further, in an embodiment herein, the decision to continue with the handover may be performed by the target-MME, which determines whether the target cell supports the allowed CSG list.

[0126] At step 6, the target MME transmits the handover request to the eNB, when the AMF finds the target MME supporting the allowed CSG cells. At step 7, the eNB (404) transmits a handover request ACK to the target MME, with regard to accepting the handover request.

[0127] Therefore, to support mobility from the 5GC to the 4GS (EPC), supported CSG IDs corresponding to the serving PLMN of the target MME will ensure that the UE that supports CSG will only be allowed to move to an allowed CSG cell.

[0128] FIG.7 depicts an example call-flow of events leading to handover from the EPS to the 5GC, according to embodiments enclosed herein. In an embodiment herein, the UE (102) is connected to the 4GS (EPC) via the CSG cell.

[0129] At step 1, the UDM entity (122) (UDR) in the 5GC or the HSS or the CSS in the 4GS (EPC) will send the allowed femto list to the AMF entity (124) and the MME entity (402). At step 2, the AMF entity (124) shares the allowed femto list with the gNB (406). At step 3, the MME entity (402) shares the allowed femto list with the eNB (404).

[0130] At step 4, the eNB (404) decides that UE (102) needs to perform handover from the 4GS (EPC) to the 5GC, according to embodiments enclosed herein, the handover preparation between the eNB (404) and the gNB (406) may involve assistance from gNB to determine a target cell, as the eNB may not have been upgraded to support the CAG-cells of 5GS. The eNB (404) sends a handover required message to the MME entity (402).

[0131] At step 5, MME needs to select a target AMF. the target AMF may be decided based on the allowed CAG identifiers from the Allowed CAG list in the UE which are supported by the target AMF. The MME entity (402) can find the target AMF which supports at least one of the allowed CAG IDs of the UE for a given PLMN. Alternatively, the decision to continue with the handover may be performed by the target-AMF, which determines whether the target cell supports the allowed CAG list.

[0132] Optionally, at step 5, the validation of the target AMF based on the Allowed CAG IDs of the UE for the corresponding PLMN can be done at the target AMF itself. If the target AMF does not find any one of the CAG IDs from the Allowed CAG list for the PLMN, for the UE (102), the target AMF will reject the Forward relocation request to the MME entity (402), based on which the MME entity (402) performs another AMF selection.

[0133] At step 6, the target AMF transmits the handover request to the gNB, when the MME finds the target AMF supporting the allowed CSG cells.

[0134] At step 7, the gNB (406) transmits a handover request ACK to the target AMF, with regard to accepting the handover request. Both the solutions proposed in Figure 6 and Figure 7 can be extended for handover performed by the gNB selecting a target eNB for 5GC to EPC handover, and eNB selecting a target gNB for the 5GC to EPC handover.

[0135] In an embodiment herein, a femto access control handling controller (146) of the UDM entity, can provide an allowed femto list to the AMF entity (124), wherein the AMF entity can share the allowed femto list to the gNB (406). Further, in an embodiment herein, the femto access control handling controller (146) of the UDM entity, can provide the allowed femto list to the MME entity (402) through at least one of: a Home Subscriber Server (HSS) entity and a Closed Subscriber Server (CSS) entity, wherein the MME entity (402) provides the Allowed Femto list to a second network entity. Further, in an embodiment herein, at least one of: the MME entity (402) and the eNB (404) provides the allowed femto list to the UE (102) if the UE (102) is connected or registered in at least one of: a 4GS and an Evolved Packet Core　(EPC). Further, in an embodiment herein, at least one of: the AMF entity (124) and the gNB (406) provides the allowed femto list to the UE (102) when the UE (102) is connected or registered to a fifth generation core (5GC).

[0136] In an embodiment herein, to support mobility from the CAG cell of the 5GC to the CSG cell of the UE (102), the gNB (406) needs to know the allowed or operator CSG list of the UE corresponding to the PLMN supported by the eNB (404) and the MME entity (402) in the EPS (EPC).

[0137] FIG. 8 depicts a block diagram of the UDM entity for handling femto access control, according to embodiments as disclosed herein. The UDM entity includes a processor, a memory and a Femto access control handling controller (146). The processor is coupled with the memory and the Femto access control handling controller (146).

[0138] The Femto access control handling controller (146) exposes the service to allow the CAG administrator to provision the CAG subscription associated with the at least one UE. The service exposed by the UDM entity is enhanced to allow an action. The action corresponding to at least one of: the UE, the first network entity and the AMF entity enforces the femto access control. Based on the CAG subscription, the Femto access control handling controller (146) handles the Femto access control.

[0139] Further, the Femto access control handling controller (146) stores data associated with the service into the UDR entity.

[0140] Further, the Femto access control handling controller (146) informs us about the updated allowed CAG list associated with the at least one UE to the AMF entity. The AMF entity informs the updated allowed CAG list associated with the at least one UE to the first network entity (e.g., gNB).

[0141] Further, the Femto access control handling controller (146) notifies the AMF entity to update a CAG subscription data in at least one the UE by sending a UE configuration update command or other downlink NAS message (e.g., registration accept or service reject or network initiated deregistration request).

[0142] Further, the Femto access control handling controller (146) provides the allowed Femto list to the AMF entity, where the AMF entity shares the Allowed Femto list to a first network entity. Further, the Femto access control handling controller (146) provides the allowed Femto list to the MME entity through at least one of: the HSS entity and the CSS entity. The MME entity provides the allowed Femto list to the second network entity. In an example embodiment herein, the communication modules may include at least one of the Internet, a wired network (a Local Area Network (LAN), a Controller Area Network (CAN), a Universal Asynchronous Receiver / Transmitter (UART), a bus network, Ethernet and so on), a wireless network (a Wi-Fi network, a cellular network, a Wi-Fi Hotspot, Bluetooth, Zigbee and so on using Wireless Application Protocol), a direct interconnection, and so on.

[0143] In an embodiment herein, the communication modules can be configured for communicating internally between internal hardware components of the UE and with the network. In an embodiment herein, the cellular network can be at least a wired network and a wireless network, wherein the wireless network can be for example, a fourth generation (4G) network, a fifth generation (5G) network, or the like.

[0144] In an embodiment herein, the Femto access control handling controller (146) can include analog and / or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware.

[0145] The Femto access control handling controller (146) may further, include one or a plurality of processors. The one or the plurality of processors may be a general-purpose processor, such as a central processing unit (CPU), an Application processor (AP), or the like, a graphics-only processing unit such as a graphics processing unit (GPU), a visual processing unit (VPU), and / or an AI-dedicated processor such as a neural processing unit (NPU). The mobility controlling processor may include multiple cores and is configured to execute the instructions stored in the memory.

[0146] Further, the Femto access control handling controller (146) is configured to execute instructions stored in the memory and to perform various processes. The memory can also store instructions to be executed by the mobility controlling processor. The memory may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. In addition, the memory may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted that the memory is non-movable. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in Random Access Memory (RAM) or cache). In an embodiment herein, the mobility controlling processor allows mobility across 4G and 5G femto cells.

[0147] FIG. 9 depicts a method (S900) for handling the femto access control, according to embodiments herein. At step S902, the method includes exposing the service to allow the CAG administrator to provision the CAG subscription associated with the UE. The service exposed by the UDM entity is enhanced to allow the action. In an embodiment, the action corresponding to at least one of: the UE, the first network entity and the AMF entity enforces the femto access control. At step S904, the method includes handling the Femto access control based on the CAG subscription.

[0148] FIG. 10 depicts a block diagram of a user equipment (UE), according to embodiments as disclosed herein.

[0149] As shown in FIG. 10, the UE according to an embodiment may include a transceiver 1010, a memory 1020, and a processor 1030. The transceiver 1010, the memory 1020, and the processor 1030 of the UE may operate according to a communication method of the UE described above. However, the components of the UE are not limited thereto. For example, the UE may include more or fewer components than those described above. In addition, the processor 1030, the transceiver 1010, and the memory 1020 may be implemented as a single chip. Also, the processor 1030 may include at least one processor. Furthermore, the UE of FIG. 10 corresponds to the UE of the disclosure.

[0150] The transceiver 1010 collectively refers to a UE receiver and a UE transmitter, and may transmit / receive a signal to / from a base station or a network entity. The signal transmitted or received to or from the base station or a network entity may include control information and data. The transceiver 1010 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver 1010 and components of the transceiver 1010 are not limited to the RF transmitter and the RF receiver.

[0151] Also, the transceiver 1010 may receive and output, to the processor 1030, a signal through a wireless channel, and transmit a signal output from the processor 1030 through the wireless channel.

[0152] The memory 1020 may store a program and data required for operations of the UE. Also, the memory 1020 may store control information or data included in a signal obtained by the UE. The memory 1020 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0153] The processor 1030 may control a series of processes such that the UE operates as described above. For example, the transceiver 1010 may receive a data signal including a control signal transmitted by the base station or the network entity, and the processor 1030 may determine a result of receiving the control signal and the data signal transmitted by the base station or the network entity.

[0154] FIG. 11 depicts a block diagram of a base station (BS), according to embodiments as disclosed herein.

[0155] As shown in FIG. 11, the base station according to an embodiment may include a transceiver 1110, a memory 1120, and a processor 1130. The transceiver 1110, the memory 1120, and the processor 1130 of the base station may operate according to a communication method of the base station described above. However, the components of the base station are not limited thereto. For example, the base station may include more or fewer components than those described above. In addition, the processor 1130, the transceiver 1110, and the memory 1120 may be implemented as a single chip.

[0156] The transceiver 1110 collectively refers to a base station receiver and a base station transmitter, and may transmit / receive a signal to / from a terminal (UE) or a network entity. The signal transmitted or received to or from the terminal or a network entity may include control information and data. The transceiver 1110 may include a RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and a RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver 1110 and components of the transceiver 1110 are not limited to the RF transmitter and the RF receiver.

[0157] Also, the transceiver 1110 may receive and output, to the processor 1130, a signal through a wireless channel, and transmit a signal output from the processor 1130 through the wireless channel.

[0158] The memory 1120 may store a program and data required for operations of the base station. Also, the memory 1120 may store control information or data included in a signal obtained by the base station. The memory 1120 may be a storage medium, such as read-only memory (ROM), random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0159] The processor 1130 may control a series of processes such that the base station operates as described above. For example, the transceiver 1110 may receive a data signal including a control signal transmitted by the terminal, and the processor 1130 may determine a result of receiving the control signal and the data signal transmitted by the terminal.

[0160] FIG. 12 depicts a block diagram of a network entity, according to embodiments as disclosed herein.

[0161] Referring to FIG. 12, the network entity includes a transceiver (1210), a memory (1220), and a processor (1230). The transceiver (1210), the memory (1220), and the processor (1230) of the network entity may operate according to a communication method of the network entity described above. However, the components of the terminal are not limited thereto. For example, the network entity may include fewer or a greater number of components than those described above. However, the components of the network entity are not limited thereto. For example, the network entity may include more or fewer components than those described above. In addition, the processor (1230), the transceiver (1210), and the memory (1220) may be implemented as a single chip. Also, the processor (1230) may include at least one processor. Furthermore, the network entity of FIG. 12 corresponds to a network entity of the disclosure.

[0162] The network entity includes at least one entity of a core network. For example, the network entity includes an AMF, a session management function (SMF), a policy control function (PCF), a network repository function (NRF), a user plane function (UPF), a network slicing selection function (NSSF), an authentication server function (AUSF), a UDM and a network exposure function (NEF), but the network entity is not limited thereto.

[0163] The transceiver (1210) collectively refers to a network entity receiver and a network entity transmitter, and may transmit / receive a signal to / from a base station or a UE. The signal transmitted or received to or from the base station or the UE may include control information and data. In this regard, the transceiver (1210) may include an RF transmitter for up-converting and amplifying a frequency of a transmitted signal, and an RF receiver for amplifying low-noise and down-converting a frequency of a received signal. However, this is only an example of the transceiver (1210) and components of the transceiver (1210) are not limited to the RF transmitter and the RF receiver.

[0164] The transceiver (1210) may receive and output, to the processor (1230), a signal through a wireless channel, and transmit a signal output from the processor (1230) through the wireless channel.

[0165] The memory (1220) may store a program and data required for operations of the network entity. Also, the memory (1220) may store control information or data included in a signal obtained by the network entity. The memory (1220) may be a storage medium, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0166] The processor (1230) may control a series of processes such that the network entity operates as described above. For example, the transceiver (1210) may receive a data signal including a control signal, and the processor (1230) may determine a result of receiving the data signal.

[0167] The various actions, acts, blocks, steps, or the like in the method may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments of some of the actions, acts, blocks, steps, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the invention.

[0168] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The elements include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.

[0169] The embodiments disclosed herein describe methods and systems for enabling an authorized administrator to provision or update CAG information to the network for 5G femto access control and handling UE-mobility using femto IDs. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a readable computer means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in at least one embodiment through or together with a software program written in e.g., Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g., hardware means like e.g., an ASIC, or a combination of hardware and software means, e.g., an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g., using a plurality of CPUs.

[0170] The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and / or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of embodiments and examples, those skilled in the art will recognize that the embodiments and examples disclosed herein can be practiced with modification within the scope of the embodiments as described herein.

Claims

1.A method performed by a network exposure function (NEF) entity in a wireless communication system, the method comprising:receiving, from an application function (AF) entity, a first message including information on a user equipment (UE) identifier and cell identifier allowed for a UE; andtransmitting, to a unified data management (UDM) entity, a second message including closed access group (CAG) information for the UE.2.The method of claim 1, wherein the information on the UE identifier includes at least one of a mobile station international subscriber directory number (MSISDN), generic public subscription identifier (GPSI), or a subscription permanent identifier (SUPI).3.The method of claim 1, further comprising:authorizing the first message from the AF entity;determining a SUPI from a GPSI or a MSISDN included in the information on the UE identifier.4.The method of claim 1, wherein the first message further includes a validity time for the UE.5.The method of claim 1, wherein the transmitting of the second message is based on a procedure related to Nudm_ParameterProvision.6.A method performed by a unified data management (UDM) entity in a wireless communication system, the method comprising:receiving, from a network exposure function (NEF) entity, a first message including closed access group (CAG) information for a UE; andtransmitting, to a user equipment (UE) via an access and mobility management function (AMF) entity, a second message including the CAG information for the UE.7.The method of claim 6, wherein the transmitting of the second message is based on a user configuration update (UCU) procedure.8.The method of claim 6, further comprising:transmitting, to a unified data repository (UDR), the third message including the CAG information.9.A network exposure function (NEF) entity in a wireless communication system, the NEF entity comprising:a transceiver; anda controller coupled with the transceiver and configured to:receive, from an application function (AF) entity, a first message including information on a user equipment (UE) identifier and cell identifier allowed for a UE; andtransmit, to a unified data management (UDM) entity, a second message including closed access group (CAG) information for the UE.10.The NEF entity of claim 9, wherein the information on the UE identifier includes at least one of a mobile station international subscriber directory number (MSISDN), generic public subscription identifier (GPSI), or a subscription permanent identifier (SUPI).11.The NEF entity of claim 9, wherein the controller further configured to:authorize the first message from the AF entity;determine a SUPI from a GPSI or a MSISDN included in the information on the UE identifier.12.The NEF entity of claim 9, wherein the first message further includes a validity time for the UE.13.The NEF entity of claim 9, wherein the transmitting of the second message is based on a procedure related to Nudm_ParameterProvision.14.A unified data management (UDM) entity in a wireless communication system, the UDM comprising:a transceiver; anda controller coupled with the transceiver and configured to:receive, from a network exposure function (NEF) entity, a first message including closed access group (CAG) information for a UE; andtransmit, to a user equipment (UE) via an access and mobility management function (AMF) entity, a second message including the CAG information for the UE.15.The UDM entity of claim 14, wherein the controller further configured to:transmit, to a unified data repository (UDR), the third message including the CAG, andwherein the transmitting of the second message is based on a user configuration update (UCU) procedure.

Images