Method and apparatus for controlling setting and access of user-installed base station

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. This method performed by a unified data management (UDM) entity in a wireless communication system includes the steps of: receiving, from a network exposure function (NEF) entity, an update request message including provisioning information associated with closed access group (CAG) information; transmitting, to a unified data repository (UDR) entity, the provisioning information to update the provisioning information; and transmitting, to the NEF entity, a response message regarding the update, wherein the CAG information includes a list of CAG identities (IDs) allowed to be accessed by a user equipment (UE), and the provisioning information may include information about at least one CAG ID to be included in the list of the CAG IDs.

Description

Method and device for controlling the setup and connection of a user-installed base station

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for controlling the setup and connection of a user-installed base station.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] According to one embodiment of the present disclosure, a device and method for effectively providing a service in a mobile communication system are provided.

[0009] According to one embodiment of the present disclosure, a method performed by a unified data management (UDM) entity in a wireless communication system includes the steps of receiving, from a network exposure function (NEF) entity, an update request message including provisioning information associated with closed access group (CAG) information, transmitting the provisioning information to a unified data repository (UDR) entity for updating the provisioning information, and transmitting a response message for the update to the NEF entity, wherein the CAG information includes a list of CAG IDs (identities) to which access of a user equipment (UE) is permitted, and the provisioning information may include information on at least one CAG ID to be included in the list of CAG IDs.

[0010] According to one embodiment of the present disclosure, a device and method for effectively providing a service in a wireless communication system can be provided.

[0011] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.

[0012] FIG. 1 illustrates the structure of a 5G system according to various embodiments of the present disclosure.

[0013] Figure 2 describes a method for providing terminal permission group information.

[0014] FIG. 3 is a diagram illustrating a method for providing group information of terminals according to one embodiment.

[0015] Figure 4 is a drawing explaining a method for providing group information of terminals when registering an agreed V-PLNM.

[0016] FIG. 5 illustrates a method for controlling the settings of a user-installed base station according to one embodiment.

[0017] FIG. 6 illustrates a method for controlling the settings of a user-installed base station according to one embodiment.

[0018] Figure 7 illustrates the configuration of an exemplary base station according to one embodiment.

[0019] Figure 8 illustrates the configuration of an exemplary terminal according to one embodiment.

[0020] Figure 9 illustrates the configuration of a core network object according to one embodiment.

[0021] The operating principles of the present disclosure are described in detail below with reference to the attached drawings. In the following description of the present disclosure, detailed descriptions of related known functions or configurations may be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intentions or practices of users and operators. Therefore, the definitions of terms should be based on the contents throughout this specification.

[0022] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, and terms referring to various identification information are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.

[0023] For convenience of explanation, this disclosure uses terms and names defined in the 5GS and NR standards, which are the most recent standards defined by the 3rd Generation Partnership Project (3GPP) among the existing communication standards. However, this disclosure is not limited to the above-described terms and names, and can be equally applied to wireless communication networks conforming to other standards. In particular, this disclosure can be applied to the 3GPP 5GS (5G system) / NR (5th generation mobile communication standard).

[0024] FIG. 1 illustrates the structure of a 5G system according to various embodiments of the present disclosure.

[0025] Referring to FIG. 1, a 5G mobile communication network may include a 5G UE (user equipment, terminal) (100), a 5G RAN (radio access network, base station), a gNB (next generation node B) (5g nodeB), an eNB (evolved nodeB, etc.) (110), and / or a 5G core network. For example, the 5G core network may be composed of NFs such as an AMF (access and mobility management function) (120) that provides a UE mobility management function, an SMF (session management function) (135) that provides a session management function, an UPF (user plane function) (130) that performs a data transfer role, a PCF (policy control function) (140) that provides a policy control function, a UDM (unified data management) (145) that provides a data management function such as subscriber data and policy control data, and a UDR (unified data repository) that stores data of various network functions (NFs) such as UDM. The 5G core network may be configured with a NSSF (network slice selection) It may further include NFs such as a network data analytic function (NWDAF) (160), a network data analytic function (NWDAF) (151), an application function (AF) (170), a data network (DN) (175), and / or a network slice admission control function (NSACF) (180).

[0026] In one embodiment, the 3GPP system defines a conceptual link connecting NFs within a 5G system as a reference point. The following illustrates a reference point included in the 5G system architecture depicted in FIG. 1.

[0027] - N1: Reference point between UE and AMF

[0028] - N2: Reference point between (R)AN and AMF

[0029] - N3: Reference point between (R)AN and UPF

[0030] - N4: Reference point between SMF and UPF

[0031] - N5: Reference point between PCF and AF

[0032] - N6: Reference point between UPF and DN

[0033] - N7: Reference point between SMF and PCF

[0034] - N8: Reference point between UDM and AMF

[0035] - N9: Reference point between two core UPFs

[0036] - N10: Reference point between UDM and SMF

[0037] - N11: Reference point between AMF and SMF

[0038] - N12: Reference point between AMF and AUSF

[0039] - N13: Reference point between UDM and authentication server function (AUSF)

[0040] - N14: Reference point between two AMFs

[0041] - N15: Reference point between PCF and AMF for non-roaming scenarios, reference point between PCF and AMF in visited network for roaming scenarios.

[0042] In 5G systems, network slicing technology refers to the technology and architecture that enables multiple virtualized, independent, logical networks within a single physical network. To meet the specialized requirements of services / applications, network operators configure virtual end-to-end networks called network slices to provide services. At this time, network slices are identified by an identifier called single-network slice selection assistance information (S-NSSAI). During the UE registration procedure (e.g., UE registration procedure), the network transmits a set of allowed slices (e.g., allowed NSSAI(s)) to the UE, and the UE transmits and receives application data through a PDU (protocol data unit) session created through one of these S-NSSAIs (i.e., network slices).

[0043] Figure 2 shows a method for providing terminal permission group information.

[0044] Referring to FIG. 2, in step 201 according to an embodiment, a management entity of a user-installed base station (e.g., a femto base station) may transmit a request message (e.g., Nnef_ServiceProvisioning_Create, Update, and / or Delete message) to 5GC (5G core network) to create, update, and / or delete information of UE(s) allowed to access the user-installed base station (e.g., a femto base station) via AF. (Nnef_ServicePrivisioning_Create / Update (UE ID, Allowed Cell information per UE)) / Delete)

[0045] In this disclosure, the term user-installed base station is only an example, and the term user-installed base station may be replaced with the terms base station, user-installable base station, small cell, small base station, or femto cell.

[0046] In one embodiment, if the AF sends a message directly to the UDM, the AF may send the message of step 203 (e.g., the Nudm_ServiceProvisioning_Create, Update, or Delete message) directly to the UDM without going through the NEF. For example, the message that the AF sends to the NEF (network exposure function) (or the message that it sends to the UDM) may include at least some of the following information:

[0047] -AF ID

[0048] -Application Service Provider (ASP) ID

[0049] -UE ID: May include a Generic Public Subscription Identifier (GPSI) or a Subscription Permanent Identifier (SUPI). Alternatively, it may include an External Group ID representing multiple UEs.

[0050] -Allowed Cell information per UE: Information that can identify allowed base stations(es) per UE may be included. For example, Allowed Cell information per UE may include cell ID(s) and / or TA ID(s), closed access group (CAG) ID(s), cell group ID(s) (i.e., identifiers for one or more cells or base station groups), and / or geographical location information that can identify base stations. Base station identification information may be provided together with a public land mobile network (PLMN) ID. In this case, a separate identifier corresponding to the CAG ID (e.g., AF-Service-Identifier, App ID, AF ID, or external CAG ID, etc.) may be provided. If so, the NEF may convert this into a CAG ID and use it. In addition, a separate identifier corresponding to the cell ID (e.g., external cell ID, etc.) may be provided. If so, the NEF may convert this into a cell ID and use it.

[0051] Additionally, a separate identifier corresponding to the cell group ID (e.g., AF-Service-Identifier, App ID, AF ID, or external cell group ID) may be provided. If provided, NEF can convert this into a cell group ID and use it.

[0052] -indication per UE: If the UE can only connect to the provided cell ID(s), an indicator indicating the Cell ID(s) it can connect to may be included.

[0053] According to one embodiment, in step 202, when the NEF receives the message from the AF in step 201, it performs authorization for the AF's request, and if it fails, it can send a response message to the AF containing information indicating the failure or rejection (Derive CAG information or Allowed Cell ID(s) per UE).

[0054] In one embodiment, if authorization for the AF request is successful, the NEF may derive or identify UE-specific CAG information based on the information contained in the message received in step 201. The CAG information may include an Allowed CAG List (e.g., a list containing allowed CAG ID(s), which may exist per PLMN for one or more PLMNs), a CAG cell only indication (e.g., indicating that the UE can only access a CAG cell), and / or validity information (e.g., information on the validity period of the Allowed CAG List).

[0055] In one embodiment, the NEF may derive or identify an Allowed CAG List based on the CAG ID(s), if the information about allowed base stations(es) received in step 201 includes CAG ID(s).

[0056] In one embodiment, the NEF may derive or identify an allowed CAG List (e.g., Allowed CAG List) for the UE based on the cell-specific supported CAG ID(s) information stored in the configuration information (e.g., supported CAG ID(s) per cell), if the information about allowed base stations (e.g., Allowed Cell Information per UE) received in step 201 includes cell ID(s).

[0057] In one embodiment, if the information about allowed base stations (e.g., Allowed Cell Information per UE) received in step 201 includes cell group ID(s), the NEF may derive an allowed CAG List for the UE based on the internal cell ID(s) information per cell group ID stored in the configuration information and / or the supported CAG ID(s) information per cell.

[0058] In one embodiment, if the information about allowed base stations (e.g., Allowed Cell Information per UE) received in step 201 includes geographical information (e.g., area information), the NEF may derive an allowed CAG List for the UE based on the internal cell ID(s) information and / or the supported CAG ID(s) information per cell per area information stored in the configuration information.

[0059] If the information about the allowed base stations includes cell ID(s), cell group ID(s) or area information, but does not store the CAG ID supported by each cell ID, the NEF can derive or identify the allowed cell ID(s) (Allowed Cell ID(s)) for each UE for the corresponding cell ID(s).

[0060] According to one embodiment, if the message received in step 201 includes a UE identifier other than SUPI (e.g., Generic Public Subscription Identifier (GPSI)), the NEF may send an authentication request including GPSI to the UDM, and if authentication is successful, the UDM may send SUPI corresponding to GPSI to the NEF (not shown).

[0061] According to one embodiment, in step 203, the NEF may send a message to the UDM including CAG information, Allowed Cell ID(s), and / or UE ID (e.g., SUPI) based on the information converted in step 201. (Nudm_ServicePrivisioning_Create / Update (CAG information, Allowed Cell ID(s), UE ID) / Delete)

[0062] In one embodiment, the UDM may identify a SUPI associated with the UE based on stored information if the message received in step 203 contains a UE identifier other than the SUPI (e.g., a Generic Public Subscription Identifier (GPSI)). The UDM may identify a corresponding Internal Group ID based on stored information if the message received in step 202 contains an External Group ID (not shown).

[0063] According to one embodiment, in step 203a, the NEF may transmit a subscription request message (Nudm_Subscribe request / response(Transaction ID)) to receive notification about the processing result of the message transmitted in step 203 (e.g., whether the CAG information provided in step 203 was delivered per UE).

[0064] According to one embodiment, in step 204, the UDM may send a message to the UDR to update CAG information and / or Allowed Cell ID(s) for the UE. The UDR may send a response message to the update request message. (Nudr_DM_Update (CAG information, Allowed Cell ID(s), SUPI) / response)

[0065] In one embodiment, the UDR may send a notification message to the UDM when the update is complete.

[0066] According to one embodiment, the UDM may transmit a notification message to the AMF. Upon receiving the notification message, if the UE is in a connected state (e.g., a Connected state), the AMF may include the updated CAG information in a UE configuration update command through a UE configuration update procedure and transmit it to the UE via the next generation radio access network (NG-RAN). The AMF may include some or all of the CAG information in an N2 message transmitted to the NG-RAN. When the UE receives a message including CAG information from the AMF, the UE may transmit a notification message to the AMF indicating that the message has been successfully received. For example, when the UE successfully receives a message including CAG information from the AMF, the UE may transmit a message indicating that the message has been successfully received to the AMF. The subsequent procedures are the same as steps 214-216.

[0067] In one embodiment, the AMF may decide to update the UE when the UE transmits a registration request message if the UE is in an IDLE state (i.e., the connection with the AMF is not active). In step 205, the UE may transmit a registration request message to the NG-RAN. The message may include information indicating that the UE supports CAG (e.g., CAG Supported). (Registration request (UE 5GMM (5G mobile management) Core Network Capability (CAG supported))

[0068] In one embodiment, in step 206, the NG-RAN may include a registration request together with the CAG ID(s) supported by the CAG cell in the N2 message transmitted to the AMF when the UE is connected to the CAG cell. (N2 message (CAG ID(s), Registration request))

[0069] In one embodiment, at step 207, the AMF may send a message to the UDM to request subscription information of the UE (Nudm_SDM_Get request (SUPI)).

[0070] According to one embodiment, in step 208, the UDM may obtain the subscription information of the UE from the UDR. (Nudr_DM_Query / response)

[0071] According to one embodiment, in step 209, the AMF may receive CAG information and / or Allowed Cell ID(s) in the UE subscriber information received from the UDM. (Nudm_SDM_Get response(subscription information(CAG information, [allowed cell ID(s)])))

[0072] According to one embodiment, in steps 210a and 210b, if the Allowed Cell ID(s) included in the message received from the UDM in step 209 include the cell ID included in the message received in step 206, the AMF may transmit a message to the UDM to update the CAG ID(identifier)(s) (e.g., CAG ID(s) supported by the cell to which the UE is connected) included in the message received in step 206 to the allowed CAG ID(s) of the UE. Upon receiving the message, the UDM may store the message (or information included in the message) in the UDR. The UDR may transmit a notification message including the updated CAG information to the UDM, and the UDM may transmit a notification message including the updated CAG information to the AMF. (Nudm_SDM_Update request (Allowed CAG ID(s), SUPI) / response)

[0073] In one embodiment, at step 211, the AMF may transmit an N2 message to the NG-RAN. The transmitted message may include an N2 message including some or all of the information contained in the CAG information and / or a Registration Accept message including the CAG information. (N2 message(Registration accept (Mobility Restriction (CAG information)))

[0074] According to one embodiment, in step 212, the UE may receive a Registration Accept message or a Registration Reject message. For example, the transmitted message (e.g., Registration Accept message, Registration Reject message) may include CAG information. (Registration Accept or Registration Reject)

[0075] According to one embodiment, in step 213, if the Registration Accept or Reject message includes CAG information, the UE may delete the previously stored CAG information and store the received CAG information. (Registration complete)

[0076] The UE may send a notification to the AMF via the NG-RAN indicating that it has received CAG information.

[0077] In one embodiment, if AMF receives a notification indicating that it has received CAG information from UDM in step 214, it may send a notification indicating that it has received CAG information to UDM. (Nudm_SDM_Info)

[0078] In one embodiment, at step 215, the UDM may send a notification to the NEF indicating that the UE has received Allowed cell information. (Nudm_SDM_Notify (result, Transaction ID)

[0079] In one embodiment, at step 216, the NEF may send a notification to the AF indicating that the UE has received Allowed cell information for one or more UEs. (Notify (whether updated or not for the list of UEs))

[0080] FIG. 3 is a diagram illustrating a method for providing group information of terminals according to one embodiment.

[0081] Referring to FIG. 3, in step 300a according to one embodiment, the AMF can obtain the UE's subscription information from the UDM. (Nudm_SDM_Subscribe)

[0082] In one embodiment, at step 300b, the AMF may perform a registration procedure.

[0083] According to one embodiment, in step 301, the management entity of the user-installed base station (e.g., femto base station) may transmit a request message (e.g., Nnef_ServiceProvisioning_Create, Update, and / or Delete message) to 5GC (5G core network) to create, update, and / or delete information of UE(s) allowed to access the user-installed base station (e.g., femto base station) via AF. (Nnef_ServicePrivisioning_Create / Update (UE ID, Allowed Cell information per UE) / Delete)

[0084] According to one embodiment, in step 302, the NEF may derive or identify an Allowed CAG List based on CAG ID(s) if the information about allowed base station(s) includes CAG ID(s) (derive CAG information or Allowed Cell ID(s) per UE).

[0085] According to one embodiment, in step 303, the NEF may send a message including CAG information, Allowed Cell ID(s), and / or UE ID based on the information converted to the UDM. (Nudm_ServicePrivisioning_Create / Update (CAG information, Allowed Cell ID(s), SUPI) / Delete))

[0086] According to one embodiment, in step 303a, the UDM may obtain subscriber information for the corresponding SUPI(s) from the UDR by transmitting a request message to the UDR to obtain subscriber information for the corresponding SUPI(s) in order to authenticate the change of subscriber information according to the request of step 202 for the terminals (e.g., SUPI(s)). (Nudm_Subscribe / response(Transaction ID))

[0087] In one embodiment, at step 304, the NFE may send a response (e.g., a result for the list of UEs) to the AF in response to the request message (e.g., Nnef_ServicePrivisioning_Create, Update, and / or Delete message) to create, update, and / or delete. (Nnef_ServicePrivisioning_Create / Update / Delete Response (results for the list of UEs))

[0088] In one embodiment, in step 305, the UDM may send a message to the UDR to update CAG information and / or Allowed Cell ID(s) for the UE. The UDR may send a response message to the update request message. (Nudr_DM_Update (CAG information, [allowed cell ID(s)], SUPI) / response)

[0089] In one embodiment, at step 306, the UDM may set a CAG information update indicator. (Set CAG information update indicator)

[0090] In one embodiment, at step 307, the UDM may send the AMF information about CAG information and / or allowed cell IDs. (Nudm_SDM_Notify (CAG information, [allowed cell ID(s)]))

[0091] According to one embodiment, in steps 308a-b, the AMF may send a message to the UDM to update the CAG ID(s) included in the received message (e.g., the CAG ID(s) supported by the cell to which the UE is connected) to the allowed CAG ID(s) of the UE. (Nudm_SDM_Update request (Allowed CAG ID(s), SUPI) / response)

[0092] According to one embodiment, in step 309, the UDM may send an N2 request message to the NG-RAN. For example, the N2 request message may include a mobile restriction list (e.g., updated CAG information), and / or a UCU command (e.g., mobility restriction (updated CAG information)). (N2 request (Mobility Restriction List (updated CAG information), UCU command (Mobility Restriction (updated CAG information)))

[0093] According to one embodiment, at step 310, the NG-RAN may transmit a UCU command to the UE. (UCU (UE configuration update) command)

[0094] In one embodiment, at step 309a, the UE may send a message (or a complete message) indicating to the AMF that the UCU is complete. (UCU complete)

[0095] In one embodiment, at step 309b, the AMF may send an ACK to the UDM. (ack) For example, the AMF may send an ACK to the UDM indicating that the UCU is complete.

[0096] In one embodiment, at step 310a, the UDM may send a notification to the NEF including a Transaction ID, a Group ID, a UE ID, and an Ack. (Nudm Notify (Transaction ID, Group ID, UE ID, Ack)

[0097] In one embodiment, at step 311, the NEF may send a notification to the AF indicating that the UE has received Allowed cell information for one or more UEs (Notify (whether updated or not for the list of UEs))

[0098] Figure 4 is a drawing explaining a method for providing group information of terminals when registering an agreed V(Visited)-PLNM.

[0099] Referring to FIG. 4, in step 405 according to one embodiment, the UE may transmit a registration request to NG-RAN1. For example, the message for the registration request may include information about the UE 5GMM (5G Mobility Management) core network capability (e.g., information indicating that CAG is supported). (Registration request (UE 5GMM Core Network Capability (CAG supported)))

[0100] In one embodiment, at step 406, NG-RAN1 may send an N2 message to the AMF. For example, the N2 message may include CAG ID(s) and / or a registration request. (N2 message (CAG ID(s), Registration request))

[0101] In one embodiment, at step 407, the AMF may send a message to the UDM to request subscription information of the UE (Nudm_SDM_Get request (SUPI)).

[0102] According to one embodiment, at step 408, the UE may perform cell re-selection. (Cell re-selection)

[0103] According to one embodiment, in step 409, the UDM may obtain the subscription information of the UE from the UDR. (Nudm_SDM_Get response(subscription information))

[0104] In one embodiment, at step 410, the AMF may send a request message to the UDM to obtain UE subscriber information (Nudm_SDM_Subscribe request).

[0105] According to one embodiment, information may be exchanged between the AMF and the AF at step 411. For example, a request containing a UE ID and / or an AMF ID (or a cell ID or an external cell group ID or a CAG ID(s)) may be forwarded from the AMF to the AF via the NEF. The AF determines whether the UE is an allowed UE for the corresponding CAG ID (or cell ID or external cell group ID) based on the received message. If allowed, a response containing CAG information may be forwarded from the AF to the AMF via the NEF. (request (UE ID, AMF ID) / response (CAG information))

[0106] In one embodiment, in step 411a, the AMF may send an N2 message to NG-RAN1. For example, the N2 message may include a registration accept message and / or mobility restriction (e.g., CAG information). (N2 message(Registration accept (Mobility Restriction (CAG information)))

[0107] In one embodiment, at step 412, NG-RAN1 may send a registration request or registration reject message to the UE. (Registration accept or Registration reject)

[0108] In one embodiment, at step 413, the UE may send a registration complete message to NG-RAN1. (Registration complete)

[0109] In one embodiment, at step 414, the AMF may transmit subscriber information to the UDM. (Nudm_SDM_Info)

[0110] In one embodiment, at step 415, the UDM may notify the NEF of the result and / or Transaction ID for the CAG information update. (Nudm_SDM_Notify (result for CAG info updated, Transaction ID))

[0111] In one embodiment, at step 416, the NEF may update the results for the list of UEs to the AF. (Notify (Update result for the list of UEs))

[0112] FIG. 5 illustrates a method for controlling the settings of a user-installed base station according to one embodiment.

[0113] Referring to FIG. 5, in step 501 according to an embodiment, the AF may send a message to the NEF for creating / updating / deleting a configuration. If the AF is a trusted AF, the message may be sent directly to the PCF or NSSF without going through the NEF. For example, the message may include the AF ID, cell ID(s) and / or TA (tracking area) ID(s) for one or more cells (i.e., a list of cells), and CAG ID(s) to be set for the corresponding cell ID(s) and / or TA ID(s). Instead of the cell ID or TA ID, the message may include area information (e.g., regional information for identifying one or more base stations, geographical location information, group ID, etc.).

[0114] (Nnef_Configuration_Create / Update / Delete (cell ID and CAG ID(s) for a list of cells)

[0115] According to one embodiment, in step 502, NEF may perform authentication for AF's request via setup information or UDM (not shown). (Authentication)

[0116] The NEF may verify whether the AF (i.e., AF ID) is an AF ID allowed to be set for the cell ID(s) and / or tracking area (TA) ID(s) or cell ID(s) and / or tracking area (TA) ID(s) corresponding to the area information included in the message, and may perform step 503 only if allowed. In one embodiment, in step 501a, the NEF may send a response message to the message for setting creation / update / deletion to the AF. If the authentication is successful in step 502, information indicating the success may be included in the response message. If the authentication is unsuccessful in step 502, information indicating the failure may be included in the response message. In one embodiment, in step 503, the NEF may send a request and / or a response to the PCF or NSSF. (request / response)

[0117] The message that the NEF requests from the PCF or NSSF may include information contained in the message received from the AF. If the message received from the PCF or NSSF contains area information, the NEF may convert it into a TA ID and / or cell ID.

[0118] According to one embodiment, in step 504, the PCF or NSSF may send an NF discovery request to the NRF, which may include NF type (e.g., AMF), capability information (e.g., CAG supported), and / or location (e.g., TA or cell ID). The NRF may send a response message including an NF profile to the PCF or NSSF. (NF discovery request (NF Type=AMF, Capability=CAG support, location (list of TA(s) and / or cell ID(s)) / response (NF profile(s))).

[0119] The NRF may include NF profile(s) for NF instances that satisfy the information included in the NF discovery request message. For example, if the NF Type is AMF, the NF profile(s) may include the address of the NF, CAG ID(s) supported by the NF, cell ID(s) supported by the NF, and / or TA ID(s). The PCF or NSSF may select an AMF based on the NF Profile(s) included in the message received from the received NRF, and may transmit the message of step 505 to the selected AMF. If there is more than one AMF responsible for the cell ID and / or TA ID(s) included in the message received in step 503 (or the cell ID and / or TA ID(s) corresponding to the area information included in the message received in step 503), the message of step 505 may be transmitted to each AMF. According to one embodiment, in step 505, the PCF or NSSF may send a request message to the AMF, including cell ID(s) and / or tracking area (TA) ID(s) for one or more cells (i.e., a list of cells) for which the AMF is responsible, and CAG ID(s) that should be set to the corresponding cell ID(s) and / or TA ID(s). (request (cell ID and CAG ID(s) for a list of cells))

[0120] In one embodiment, in step 505, the PCF or NSSF may send a request message including an indicator requesting the AMF to provide cell ID(s) and / or tracking area (TA) ID(s) for one or more cells (i.e., a list of cells) for which the AMF is responsible, along with the corresponding cell IDs and the CAG ID(s) supported for those cells.

[0121] In one embodiment, if the message received from the PCF or NSSF in step 505 does not include CAG ID(s), the AMF may include in the response message transmitted to the PCF or NSSF in step 506 the CAG ID(s) information supported by the cell(s) corresponding to the message received in step 505. In this case, the PCF or NSSF may include in the message transmitted to the AF via the NEF the CAG ID(s) information supported by the region (e.g., by area information, TA ID(s) and / or cell ID(s)).

[0122] In one embodiment, if the message received in step 505 includes CAG ID(s), then in step 506, the AMF may send an N2 request to the NG-RAN, wherein the N2 request may include cell ID(s) and / or tracking area (TA) ID(s) for one or more cells (i.e., a list of cells) and CAG ID(s) to be set to the corresponding cell IDs and / or TA ID(s). (N2 request (CAG ID(s) per cell for a list of cell(s)))

[0123] When the NG-RAN receives the N2 request message from the AMF in step 506, it sets the CAG ID(s) included in the N2 request message to the CAG ID(s) that it supports for the cells corresponding to the TA ID(s) and / or cell ID(s) included in the N2 request message.

[0124] FIG. 6 illustrates a method for controlling the settings of a user-installed base station according to one embodiment.

[0125] Referring to Figure 6, in step 601, NG-RAN 1 may send an N2 message to the AMF. For example, the N2 message may include information about the CAG ID(s) supported by the CAG cell. (N2 message (supported CAG ID(s) for cells)

[0126] In one embodiment, in step 602, the AMF may send a request message to the Operations, Administration, and Maintenance (OAM) containing information about the CAG ID(s) supported by the CAG cell. (request(supported CAG ID(s) for cell(s))

[0127] In one embodiment, in step 603, the OAM may send a response to the AMF containing information about the update of the CAG ID(s) supported by the CAG cell. (response (updated supported CAG ID(s) for cell(s))

[0128] In one embodiment, at step 604, the AMF may send an N2 message to NG-RAN1. For example, the N2 message may include information about updated CAG ID(s). (N2 message(updated supported CAG ID(s) for cell(s))

[0129] In one embodiment, in step 605, the OAM may send a request message to the AMF containing information about updated CAG ID(s). (Request (updated supported CAG ID(s) for cell(s))

[0130] In one embodiment, at step 606, the AMF may send an N2 message containing information about the updated CAG ID(s) to the NG-RAN 2. (N2 message (updated supported CAG ID(s) for cell(s))

[0131] FIG. 7 illustrates a configuration of an exemplary base station according to one embodiment of the present disclosure.

[0132] Referring to FIG. 7, the configuration illustrated in FIG. 7 according to one embodiment may be understood as the configuration of the gNB and / or eNB of FIG. 1. Terms such as "...unit" and "...unit" used hereinafter refer to a unit that processes at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software.

[0133] According to one embodiment, the base station includes a communication unit (705), a storage unit (710), and / or a control unit (715).

[0134] The communication unit (705) performs functions for transmitting and receiving signals via a wireless channel. For example, the communication unit (705) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the communication unit (705) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the communication unit (705) restores a reception bit stream by demodulating and decoding the baseband signal. In addition, the communication unit (705) upconverts a baseband signal into an RF band signal and transmits it through an antenna, and downconverts an RF band signal received through the antenna into a baseband signal. For example, the communication unit (705) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.

[0135] In addition, the communication unit (705) may include a plurality of transmit / receive paths. Furthermore, the communication unit (405) may include at least one antenna array composed of a plurality of antenna elements. In terms of hardware, the communication unit (705) may be composed of digital circuits and analog circuits (e.g., radio frequency integrated circuits (RFIC)). Here, the digital circuits and analog circuits may be implemented in a single package. In addition, the communication unit (705) may include a plurality of RF chains. Furthermore, the communication unit (705) may perform beamforming.

[0136] The communication unit (705) transmits and receives signals as described above. Accordingly, all or part of the communication unit (705) may be referred to as a "transmitter," a "receiver," or a "transmitting and receiving unit." Furthermore, in the following description, transmission and reception performed via a wireless channel are used to mean that the communication unit (705) performs the processing described above.

[0137] The storage unit (710) stores data such as basic programs, application programs, and setting information for the operation of the base station. The storage unit (710) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the storage unit (710) provides the stored data upon request from the control unit (715).

[0138] The control unit (715) controls the overall operations of the base station. For example, the control unit (715) transmits and receives signals through the communication unit (705). In addition, the control unit (715) records and reads data in the storage unit (710). In addition, the control unit (715) can perform the functions of the protocol stack required by the communication standard. To this end, the control unit (715) may include at least one processor or microprocessor, or may be a part of a processor. In addition, a part of the communication unit (705) and the control unit (715) may be referred to as a CP (communication processor). According to various embodiments, the control unit (715) may control to perform synchronization using a wireless communication network. For example, the control unit (715) may control the base station to perform operations according to the various embodiments described above.

[0139] FIG. 8 illustrates the configuration of an exemplary terminal according to one embodiment of the present disclosure. The configuration illustrated in FIG. 8 may be understood as the configuration of the UE (or NR UE) of FIG. 1. Terms such as "...unit" and "...unit" used hereinafter refer to a unit that processes at least one function or operation, which may be implemented by hardware, software, or a combination of hardware and software.

[0140] Referring to FIG. 8, the terminal includes a communication unit (805), a storage unit (810), and / or a control unit (815).

[0141] The communication unit (805) performs functions for transmitting and receiving signals via a wireless channel. For example, the communication unit (805) performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the communication unit (805) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the communication unit (805) restores a reception bit stream by demodulating and decoding the baseband signal. In addition, the communication unit (805) upconverts a baseband signal to an RF band signal and transmits it through an antenna, and downconverts an RF band signal received through the antenna to a baseband signal. For example, the communication unit (805) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.

[0142] In addition, the communication unit (805) may include a plurality of transmit / receive paths. Furthermore, the communication unit (505) may include at least one antenna array composed of a plurality of antenna elements. In terms of hardware, the communication unit (805) may be composed of digital circuits and analog circuits (e.g., a radio frequency integrated circuit (RFIC)). Here, the digital circuits and analog circuits may be implemented in a single package. In addition, the communication unit (805) may include a plurality of RF chains. Furthermore, the communication unit (805) may perform beamforming.

[0143] The communication unit (805) transmits and receives signals as described above. Accordingly, all or part of the communication unit (805) may be referred to as a "transmitter," a "receiver," or a "transmitting and receiving unit." Furthermore, in the following description, transmission and reception performed via a wireless channel are used to mean that the communication unit (805) performs the processing described above.

[0144] The storage unit (810) stores data such as basic programs, application programs, and setting information for the operation of the terminal. The storage unit (810) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the storage unit (810) provides the stored data upon request from the control unit (815).

[0145] The control unit (815) controls the overall operations of the terminal. For example, the control unit (815) transmits and receives signals through the communication unit (805). In addition, the control unit (815) records and reads data in the storage unit (810). In addition, the control unit (815) can perform the functions of the protocol stack required by the communication standard. To this end, the control unit (815) may include at least one processor or microprocessor, or may be a part of a processor. In addition, a part of the communication unit (505) and the control unit (815) may be referred to as a CP (communication processor). According to various embodiments, the control unit (815) may control to perform synchronization using a wireless communication network. For example, the control unit (815) may control the terminal to perform operations according to various embodiments described below.

[0146] FIG. 9 illustrates a configuration of a core network object according to an embodiment of the present disclosure. It illustrates a configuration of a core network object in a wireless communication system according to various embodiments of the present disclosure. The configuration illustrated in FIG. 9 may be understood to correspond to at least one of the network entities of FIGS. 1 to 8. Terms such as "... unit" and "... unit" used hereinafter mean a unit that processes at least one function or operation, and this may be implemented by hardware, software, or a combination of hardware and software.

[0147] Referring to FIG. 9, the core network object may include a communication unit (940), a storage unit (945), and / or a control unit (950).

[0148] The communication unit (940) provides an interface for communicating with other devices within the network. That is, the communication unit (940) converts a bit string transmitted from a core network object to another device into a physical signal, and converts a physical signal received from another device into a bit string. That is, the communication unit (940) can transmit and receive signals. Accordingly, the communication unit (940) may be referred to as a modem, a transmitter, a receiver, or a transceiver. In this case, the communication unit (940) enables the core network object to communicate with other devices or systems via a backhaul connection (e.g., a wired backhaul or a wireless backhaul) or via a network.

[0149] The storage unit (945) stores data such as basic programs, application programs, and configuration information for the operation of the core network object. The storage unit (945) may be composed of volatile memory, non-volatile memory, or a combination of volatile and non-volatile memory. In addition, the storage unit (945) provides the stored data upon request from the control unit (950).

[0150] The control unit (950) controls the overall operations of the core network object. For example, the control unit (950) transmits and receives signals through the communication unit (940). In addition, the control unit (950) records and reads data from the storage unit (945). For this purpose, the control unit (950) may include at least one processor. According to various embodiments of the present disclosure, the control unit (950) may control synchronization using a wireless communication network. For example, the control unit (950) may control the core network object to perform operations according to various embodiments described below.

[0151] The methods according to the embodiments described in the claims or specification of the present invention may be implemented in the form of hardware, software, or a combination of hardware and software.

[0152] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present invention.

[0153] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0154] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present invention via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present invention.

[0155] In the specific embodiments of the present invention described above, components included in the invention are expressed in the singular or plural form depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present invention is not limited to singular or plural components. Even components expressed in the plural form may be composed of singular elements, or even components expressed in the singular form may be composed of plural elements.

[0156] While the detailed description of the present invention has described specific embodiments, it is clear that various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims but also by equivalents thereof.

Claims

1. A method performed by a UDM (unified data management) entity in a wireless communication system, A step of receiving an update request message including provisioning information associated with closed access group (CAG) information from a network exposure function (NEF) entity; A step of transmitting provisioning information to a UDR (unified data repository) entity for updating the provisioning information; and comprising a step of transmitting a response message for the update to the NEF entity; The above CAG information includes a list of CAG IDs (identities) to which UE (user equipment) access is permitted, A method wherein the provisioning information includes information about at least one CAG ID to be included in the list of CAG IDs.

2. In claim 1, The above provisioning information further includes information about the ID of the UE, A method wherein the ID of the UE includes a generic public subscription identifier (GPSI).

3. In claim 2, A method further comprising a step of identifying a subscription permanent identifier (SUPI) based on the GPSI.

4. In claim 1, The CAG information including the list of CAG IDs is updated, The above updated CAG information is valid for a specified period of time based on time validation information.

5. In a method performed by a network exposure function (NEF) entity in a wireless communication system, A step of receiving provisioning information associated with closed access group (CAG) information from an AF (application function) entity; A step of transmitting an update request message including the provisioning information to a UDM (unified data management) entity; and A step of receiving a response message for updating the provisioning information from the UDM entity, The above CAG information includes a list of CAG IDs (identities) to which UE (user equipment) access is permitted, A method wherein the provisioning information includes information about at least one CAG ID to be included in the list of CAG IDs.

6. In claim 5, The above provisioning information further includes information about the ID of the UE, A method wherein the ID of the UE includes a generic public subscription identifier (GPSI).

7. In claim 6, SUPI (subscription permanent identifier) ​​for the above update is based on the GPSI.

8. In claim 5, The CAG information including the list of CAG IDs is updated, The above updated CAG information is valid for a specified period of time based on time validation information.

9. In the UDM (unified data management) entity in the wireless communication system, transceiver; and A controller coupled with the above transceiver, The above controller: Receive an update request message containing provisioning information associated with closed access group (CAG) information from a network exposure function (NEF) entity, Send the provisioning information to the UDR (unified data repository) entity to update the provisioning information, is set to send a response message for the update to the above NEF entity, The above CAG information includes a list of CAG IDs (identities) to which UE (user equipment) access is permitted, A UDM entity, wherein the provisioning information includes information about at least one CAG ID to be included in the list of CAG IDs.

10. In claim 9, The above provisioning information further includes information about the ID of the UE, The ID of the above UE is a UDM entity that includes a generic public subscription identifier (GPSI).

11. In claim 10, The above controller: A UDM entity further configured to identify a subscription permanent identifier (SUPI) based on the above GPSI.

12. In claim 9, The CAG information including the list of CAG IDs is updated, The above updated CAG information is a UDM entity that is valid for a specified period of time based on time validation information.

13. In a wireless communication system, in the NEF (network exposure function) entity, transceiver; and A controller coupled with the above transceiver, The above controller: Receive provisioning information associated with closed access group (CAG) information from an AF (application function) entity, Send an update request message including the provisioning information to the UDM (unified data management) entity, It is set to receive a response message for an update of the provisioning information from the above UDM entity, The above CAG information includes a list of CAG IDs (identities) to which UE (user equipment) access is permitted, An NEF entity, wherein the provisioning information includes information about at least one CAG ID to be included in the list of CAG IDs.

14. In claim 13, The above provisioning information further includes information about the ID of the UE, The ID of the above UE is an NEF entity that includes a generic public subscription identifier (GPSI).

15. In claim 14, The SUPI (subscription permanent identifier) ​​for the above update is based on the GPSI, The CAG information including the list of CAG IDs is updated, The above updated CAG information is a NEF entity that is valid for a specified period of time based on time validation information.

Images