Method and device for supporting subscriber information for shared network in communication system

The AMF method in 5G systems accurately manages subscriber information in shared networks by identifying terminals through PLMN IDs, addressing misidentification and registration issues, thus enhancing network performance and security.

WO2026235488A1PCT designated stage Publication Date: 2026-11-12SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/096660
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-08
Filing Date
2026-05-07
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

Existing 5G mobile communication systems face challenges in efficiently managing subscriber information in shared networks, particularly when terminals connect via indirect network sharing methods, leading to potential misidentification and registration issues.

Method used

The proposed method involves an access and mobility management function (AMF) that identifies terminals connected via indirect network sharing by checking the Public Land Mobile Network (PLMN) ID, transmitting subscriber data requests to a unified data management (UDM) considering the hosting operator's PLMN ID, and sending registration rejections if the selected PLMN does not match the participating operator network.

Benefits of technology

This approach enhances the accuracy and efficiency of subscriber information management in shared networks, ensuring proper registration and data access for terminals, thereby improving network performance and security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026096660_12112026_PF_FP_ABST
    Figure KR2026096660_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. Specifically, disclosed is a method performed by an access and mobility management function (AMF) of a communication system, the method comprising the steps of: identifying that a terminal is connected in an indirect network sharing manner; transmitting a subscriber data request to unified data management (UDM) of a participating operator network; and when the subscriber data request includes a public land mobile network (PLMN) identifier (ID) of a hosting provider, receiving, from the UDM, subscriber data considering the PLMN ID of the hosting provider.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for supporting subscriber information for a shared network in a communication system

[0001] The present invention relates to a wireless communication system or a mobile communication system, and more specifically, to a method and device for supporting network sharing in a wireless communication system.

[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 frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

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

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

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] The object of the present invention is a method for supporting subscriber information for a shared network.

[0009] The technical problems to be solved by the present invention are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which the present invention belongs from the description below.

[0010] The present invention, for solving the above-mentioned problems, is characterized by a method performed by an access and mobility management function (AMF) of a communication system, comprising: a step of identifying that a terminal is connected via an indirect network sharing method; a step of transmitting a subscriber data request to a unified data management (UDM) of a participating operator network; and a step of receiving subscriber data from the UDM that takes into account the PLMN ID of the hosting operator when the subscriber data request includes the PLMN ID (identifier) ​​of the hosting operator.

[0011] Additionally, the method includes the step of receiving a message related to a registration request containing a PLMN ID selected by the terminal from a RAN (radio access network), and the step of identifying that the terminal is connected via an indirect network sharing method is characterized by identifying that the terminal is connected via an indirect network sharing method based on whether the selected PLMN ID corresponds to the participating operator network, and the AMF is an AMF of the hosting operator network.

[0012] In addition, the above subscriber data request is characterized by including a serving PLMN ID corresponding to the participating operator network and a hosting operator's PLMN ID.

[0013] In addition, the method is characterized by including the step of sending a registration rejection message to the terminal if the PLMN selected by the terminal does not correspond to the participating operator network.

[0014] According to one embodiment, a method performed by a unified data management (UDM) of a communication system comprises: receiving a subscriber data request from an access and mobility management function (AMF) of a hosting operator network; and, if the subscriber data request includes a public land mobile network (PLMN) identifier of the hosting operator, transmitting subscriber data to the AMF that takes into account the PLMN ID of the hosting operator, wherein, in relation to the AMF, the terminal is connected via an indirect network sharing method.

[0015] According to one embodiment, the access and mobility management function (AMF) of a communication system comprises: at least one transceiver; at least one processor connected to the at least one transceiver so as to be communicable; and a memory connected to the at least one processor so as to be communicable and capable of executing the at least one processor individually or in any combination thereof, wherein the AMF identifies that a terminal is connected in an indirect network sharing manner, transmits a subscriber data request to a unified data management (UDM) of a participating operator network, and, if the subscriber data request includes a public land mobile network (PLMN) identifier of a hosting operator, receives subscriber data from the UDM considering the PLMN ID of the hosting operator.

[0016] According to one embodiment, a unified data management (UDM) of a communication system comprises: at least one transceiver; at least one processor connected to the at least one transceiver so as to be communicable; and a memory connected to the at least one processor so as to be communicable and executable individually or in any combination of the at least one processor, wherein the UDM receives a subscriber data request from an access and mobility management function (AMF) of a hosting operator network, and when the subscriber data request includes a public land mobile network (PLMN) ID (identifier) ​​of the hosting operator, the memory stores a command to transmit subscriber data to the AMF considering the PLMN ID of the hosting operator, wherein, in relation to the AMF, the terminal is connected in an indirect network sharing manner.

[0017] According to one embodiment of the present invention, subscriber information for a shared network can be supported more effectively.

[0018] The effects obtainable in the present disclosure are not limited to those mentioned in the various embodiments, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure pertains from the description below.

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

[0020] FIG. 2 illustrates a method for an AMF to obtain subscriber information for a UE of a Participating Operator Network according to one embodiment of the present disclosure.

[0021] FIG. 3 illustrates a method according to one embodiment of the present disclosure in which a PCF of a hosting operator network (e.g., V-PCF (PCF in the visited network)) determines an access and mobility management (AM) policy of a UE connected to the hosting operator network.

[0022] FIG. 4 is a block diagram of a terminal or user equipment according to one embodiment of the present disclosure.

[0023] FIG. 5 is a block diagram of a base station according to one embodiment of the present disclosure.

[0024] FIG. 6 is a block diagram of a network entity performing network functions according to one embodiment of the present disclosure.

[0025] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0026] In describing the embodiments, technical details that are well known in the technical field to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0027] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same or different reference numbers.

[0028] The advantages and features of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of related functions or configurations might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the specification.

[0029] In the present disclosure, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams may be performed based on computer program instructions. Since these computer program instructions may be optionally loaded into at least one processor of a general-purpose computer, a computer for special purposes, or other programmable data processing equipment, the instructions performed through any one or any combination of at least one processor of the computer or other programmable data processing equipment create means for performing the functions described in the flow diagram block(s). Since these computer program instructions may also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the functions in a specific manner, the instructions stored in computer-available or computer-readable memory may also produce a manufactured item containing means of instruction for performing the functions described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0030] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks (or functions) described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to the corresponding function.

[0031] As used in embodiments of the present disclosure, the term “part” refers to a software or hardware component, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and the “part” performs certain roles. However, the term including “part” is not limited to software or hardware. The “part” may be configured to reside in an addressable storage medium or may be configured to run one or more processors. Thus, by example, the “part” includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and “parts” may be combined into a smaller number of components and “parts” or further separated into additional components and “parts.” In addition, the components and '~parts' may be implemented to utilize one or more CPUs (central processing units) within the device or secure multimedia card. Furthermore, in the embodiment, the '~part' may include one or more processors.

[0032] As stated above, it should be noted that the blocks of each flowchart and combinations of flowcharts described in this disclosure may be executed by one or more computer programs including instructions. The entirety of one or more computer programs may be stored in a single memory device, or one or more computer programs may be divided into different parts and stored across multiple memory devices.

[0033] Additionally, any / any function or operation described in this disclosure may be processed by a single processor or a combination of processors. The single processor or combination of processors is a circuitry that performs processing and may include an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural network processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near-field communication (NFC) chip, a connectivity chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driver integrated circuit (IC), an audio codec (CODEC) chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system-on-chip (SoC), an IC, or similar circuitry.

[0034] Additionally, it should be noted that various embodiments in the claims and description of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0035] Such software may be stored on a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium stores one or more computer programs (software modules), and said one or more computer programs include computer-executable instructions that operate an electronic device to perform a method according to the present disclosure when executed alone or collectively by one or more processors of an electronic device.

[0036] The software may be stored in a transient or non-transient storage device, for example, in the form of read-only memory (ROM) (whether or not it is erasable or rewritable), or random access memory (RAM), memory chips, devices, or integrated circuits (ICs). Additionally, the software may be stored in the form of an optically or magnetically readable medium, for example, a compact disc (CD), a digital multifunction disc (DVD), a magnetic disc, or a magnetic tape. It should be understood that the storage device and the storage medium are examples of non-transient machine-readable storage media suitable for storing programs for implementing various embodiments of the present disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing a device or method according to any one of the claims of this specification, and a non-transient machine-readable storage medium storing such program.

[0037] In the following disclosure, determining the priority between A and B may be referred to in various ways, such as selecting the one with the higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with the lower priority.

[0038] Hereinafter, 'A or B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0039] Additionally, 'at least one of A, B, and C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0040] Additionally, 'at least one of A, B, or C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0041] Additionally, 'A / B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0042] Additionally, 'A, B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0043] Additionally, 'A and B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0044] Furthermore, the phrase "when conditions A and B are satisfied" as described in the present disclosure is not necessarily limited to cases where both conditions A and B are satisfied, but may be understood to include cases where either condition A or condition B is satisfied individually, cases where both conditions A and B are satisfied, or cases where one or more additional conditions are satisfied together.

[0045] Furthermore, throughout this specification, ordinal terms (and similar modifiers) such as 'first', 'second', 'third', etc. are used solely for the purpose of distinguishing various instances, occurrences, configurations, messages, stages, or aspects of elements, operations, or information, as described below. Unless clearly required otherwise by the context, the use of such ordinal terms does not require that the elements, operations, or information distinguished by such terms be structurally different, numerically distinct, or essentially different. For example, 'first signal' and 'second signal' may represent instances of the same signal transmitted at different times, signals containing the same core information even with some variations, or signals having different content or characteristics depending on the specific context. Similarly, 'first value' and 'second value' may represent the same magnitude measured or applied in different situations, or may represent different magnitudes. Such interpretation must be determined based on the specific technical context, function, and relationship described in the relevant parts of the specification and claims.

[0046] Furthermore, although terms such as "first," "second," etc., as used in this disclosure are used for various elements such as information, objects, actions, and sequences, they are not intended to limit such elements to a specific order. These terms may be understood merely as distinguishing one element from another. For example, a first element may be referred to as a second element, and likewise, a second element may be referred to as a first element.

[0047] Additionally, the terms 'first' and 'second' described in this disclosure may be understood to refer to identical or different elements. For example, if an element is information, the first information and the second information may both be information, and depending on the case, they may be the same information or different information.

[0048] Furthermore, the expressions 'if' and 'in case that' described in this disclosure or claims may be interpreted, depending on the context, as meaning 'when or upon,' 'in response to,' 'based on,' or 'according to,' and these expressions may be used interchangeably. In addition, other expressions having substantially the same meaning may be used as substitutes, provided that they do not impair the technical features of this disclosure.

[0049] Additionally, the term "not perform" as used in this disclosure or claims may be understood, depending on the context, to mean to omit or skip the corresponding step. Such a term may be replaced with other terms having the same or substantially similar meaning.

[0050] Additionally, the phrase "transmitting a message containing A and B" as described in this specification may be interpreted to include not only (i) cases where A and B are transmitted as a single message, but also (ii) cases where A and B are transmitted individually through multiple messages (e.g., transmitting a first message containing A and a second message containing B). This interpretation may also apply to cases where messages containing two or more items, such as A, B, and C, are transmitted together or individually.

[0051] In addition, 'transmitting a message containing A and transmitting a message containing B' can also be interpreted as transmitting a single message containing A and B.

[0052] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure will be expressed in the singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed in the singular form, or even if a component is expressed in the singular form, it may be composed in the plural form.

[0053] The drawings or flowcharts described below illustrate exemplary methods that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, the various steps of each drawing or flowchart may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, any step may be omitted or replaced with another step.

[0054] The methods and devices proposed in the embodiments of the present disclosure below are not limited to each specific embodiment, and may also be utilized as a combination of all or part of one or more embodiments proposed in the disclosure. Accordingly, the embodiments of the present disclosure may be applied with some modifications within the scope of the present disclosure without significantly departing from the scope of the present disclosure, at the judgment of a person skilled in the art.

[0055] In this case, any wording mentioned in different embodiments may be used interchangeably, combined, or substituted if the concepts correspond. For example, regarding the same or corresponding concepts, even if the expression 'A' is used in one embodiment and the expression 'B' is used in another embodiment, they can be understood by interchangeably, substituted, or combined.

[0056] 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, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used. Furthermore, where appropriate, such terms may be replaced with terms defined in the 3GPP (3rd generation partnership project) Technical Specifications (TS).

[0057] Hereinafter, the base station, as the entity performing resource allocation for terminals, may be at least one of gNode B, eNode B, Node B, BS (base station), wireless access unit, base station controller, or a node on a network. Additionally, the base station of the present disclosure may include a structure split into a central unit (CU) and a distributed unit (DU). In such a structure, the CU is responsible for the upper layer of the control and user plane, and the DU is responsible for wireless resource processing of the lower layer. The embodiments of the present disclosure can be equally applied to a 5G base station structure in which functions are separated into the CU and DU as described above.

[0058] The terminal may include a UE (user equipment), MS (mobile station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions.

[0059] In the present disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by a terminal to a base station.

[0060] In addition, while a 5th generation mobile communication system (5G, new radio, NR) and a 6th generation mobile communication system (6G) may be described below as examples, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, new advanced mobile communication systems developed after 5G and 6G may be included therein. Furthermore, the present disclosure may be applied to other communication systems (e.g., Wi-Fi systems) with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0061] In the following description, the terms "physical channel" and "signal" may be used interchangeably with "data" or "control signal." For example, PDSCH (physical downlink shared channel) is a term referring to a physical channel through which data is transmitted, but PDSCH may also be used to refer to data. That is, in this disclosure, the expression "transmits a physical channel" may be interpreted as equivalent to the expression "transmits data or a signal through a physical channel."

[0062] In describing the present disclosure below, the term "upper layer signaling" may be a signaling corresponding to at least one or a combination of at least one of MIB (master information block), SIB (system information block), SIB M (M=1, 2, …), RRC (radio resource control), MAC (medium access control), CE (control element), NAS (non-access stratum) signaling, or application layer messages. The RRC signaling may also be referred to as L3 signaling (layer 3 signaling).

[0063] Additionally, L1 signaling may be a signaling method corresponding to at least one or a combination of at least one of the following: a physical layer channel or signaling of a PDCCH (physical downlink control channel), a DCI (downlink control information), a UE-specific DCI, a group common DCI, a common DCI, a scheduling DCI (e.g., a DCI used for the purpose of scheduling downlink or uplink data), a non-scheduling DCI (e.g., a DCI not used for the purpose of scheduling downlink or uplink data), a PUCCH (physical uplink control channel), or an UCI (uplink control information). The above L1 signaling may also be referred to as physical layer signaling.

[0064] Hereinafter, the expression in the present disclosure or claims that information can be configured from a base station may mean that, depending on the context, a terminal receives said information from a base station through physical layer signaling or upper layer signaling, and such expression may be replaced with other terms having the same or substantially similar meaning.

[0065] The operating principle of the present disclosure will be explained in detail below with reference to the attached drawings.

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

[0067] A 5G mobile communication network consists of 5G UE (user equipment, terminal), 5G RAN (radio access network, base station), gNB (5G node B), eNB (evolved node B, etc.), and a 5G core network. The 5G core network may be composed of Network Functions (NFs), such as the Access and Mobility Management Function (AMF) which provides mobility management functions for UEs, the Session Management Function (SMF) which provides session management functions, the User Plane Function (UPF) which performs data delivery, the Policy Control Function (PCF) which provides policy control functions, the Unified Data Management (UDM) which provides data management functions such as subscriber data and policy control data, and the Unified Data Repository (UDR) which stores data from various network functions (NFs) including the UDM. The 5G core network may be configured to further include NFs such as the Network Slice Selection Function (NSSF), Network Data Analytic Function (NWDAF), Application Function (AF), Data Network (DN), and Network Slice Admission Control Function (NSACF).

[0068] In 3GPP systems, a conceptual link connecting NFs within a 5G system is defined as a reference point. The following is an example of a reference point included in the 5G system architecture depicted in Figure 1.

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

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

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

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

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

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

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

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

[0077] - N9: Reference point between 2 core UPFs

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

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

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

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

[0082] - N14: Reference point between 2 AMFs

[0083] - N15: Reference point between PCF and AMF in non-roaming scenarios, reference point between PCF and AMF within the visited network in roaming scenarios

[0084] In 5G systems, network slicing technology refers to a technology and structure that enables multiple virtualized, independent logical networks within a single physical network. To satisfy the specialized requirements of services / applications, network operators provide services by configuring virtual end-to-end networks called network slices. At this time, network slices are distinguished by an identifier called S-NSSAI (single-network slice selection assistance information). During a terminal registration procedure (e.g., UE registration procedure), the network transmits a set of allowed slices (e.g., allowed NSSAI(s)) to the terminal, and the terminal transmits and receives application data through a PDU (protocol data unit) session generated via one of these S-NSSAIs (i.e., network slice). In the embodiments of the present disclosure below, the operation of NF may be understood as the operation of OAM (orchestration and management).

[0085] Meanwhile, due to factors such as the increase in mobile communication infrastructure installation costs, technologies for sharing networks among operators are being discussed. A hosting operator (e.g., a shared network hosting network operator) may provide a shared mobile communication network (e.g., a base station and an AMF) to a participating operator (e.g., a shared participating network operator). The base station of the hosting operator leased to the participating operator (e.g., a Shared RAN) may be configured to broadcast the participating operator's PLMN ID. Terminals with the participating operator as their home network (e.g., Home PLMN, HPLMN) can receive services as if they were connected to the home network by selecting an HPLMN ID (e.g., selecting a cell that supports the HPLMN ID) from among one or more PLMN IDs broadcast by the Shared RAN.

[0086] PLMNs can provide logically independent networks through network slices. Each network slice is identified by an S-NSSAI, which consists of an SST (Slice / Service Type) and an SD (Service Differentiator); different SST schemes can be defined and used for each PLMN. In other words, each PLMN can allocate a slice for a terminal to connect to through its own set of S-NSSAIs.

[0087] In the present invention, hosting operator, hosting PLMN, and visited PLMN (VPLMN) may be used interchangeably. Additionally, participating operator, participating PLMN, and home PLMN (HPLMN) may be used interchangeably.

[0088] In the present invention, the Shared RAN is a RAN provided by a hosting operator and can support corresponding PLMN IDs for one or more contracted participating operators.

[0089] A Shared RAN can support one or more of the TAIs included in the set of Tracking Area Identity (TAI) of a supported PLMN.

[0090] A Shared RAN may support one or more of the S-NSSAIs included in the set of S-NSSAIs of a supported PLMN for the supported PLMN. Additionally, a Shared RAN may support one or more of the S-NSSAIs included in the set of Network Slice AS (access stratum) Groups (NSAGs) of a supported PLMN for the supported PLMN. According to one embodiment, an NSAG may represent one or more S-NSSAIs and may be identified by an NSAG ID.

[0091] In the present invention, the Shared AMF can support corresponding PLMN IDs for one or more contracted participating operators as an AMF provided by the hosting operator.

[0092] For a supported PLMN, the Shared RAN may support one or more of the TAIs included in the set of Tracking Area Identity (TAI) of that PLMN. For each supported PLMN ID, the Shared AMF may support one or more of the S-NSSAIs included in the set of S-NSSAIs of that PLMN.

[0093] In the present invention, the Shared NSSF can support corresponding PLMN IDs for one or more contracted participating operators as an NSSF provided by the hosting operator. For each supported PLMN ID, the Shared NSSF can support one or more of the S-NSSAIs included in the S-NSSAI set of the corresponding PLMN.

[0094] In the present invention, a UDM that supports indirect network sharing may correspond to an entity provided by a participating operator.

[0095] FIG. 2 illustrates a method for an AMF to obtain subscriber information for a UE of a Participating Operator Network according to one embodiment of the present disclosure.

[0096] The message names or expressions exemplified in the following steps are examples only and may be interpreted as identical to messages that perform the same or similar functions or contain the same or similar information. Additionally, some of the steps may be omitted or combined.

[0097] At step 210, the UE may transmit an AN message to a Shared RAN (e.g., an AN (access network)). The message may include at least one of the following information:

[0098] - Selected PLMN ID: May include a PLMN ID selected by the UE. In this case, the Selected PLMN ID may be an HPLMN ID for the UE. For example, the UE may select one of the PLMN IDs included in a broadcast message received from the Shared RAN, and if the broadcast message includes a PLMN ID corresponding to its home network, the UE may preferentially select that PLMN ID.

[0099] - Registration request: Represents a registration request message, and the message may include at least one of SUCI (subscription concealed identifier) ​​(which may represent the UE's identifier information in an encrypted format; may also include Home Network Identifier (which may include MCC (mobile country code) and MNC (mobile network code)), UE Routing indicator, etc.), and Requested NSSAI. Additionally, if the Selected PLMN is an HPLMN, the UE may include one or more S-NSSAIs that it wishes to request among the HPLMN S-NSSAIs (e.g., S-NSSAIs used in the Home network) in the Requested NSSAI.

[0100] In step 220, when the RAN receives the AN message, it may send an N2 message to the AMF. The message may include at least one of a Selected PLMN ID, UE location information, Location information and cell Identity, and a Registration request.

[0101] In step 230, the AMF receives an N2 message from the Shared RAN and can identify the PLMN ID selected by the UE based on the information contained in the N2 message. If the AMF supports Indirect Network Sharing, the AMF can operate as the AMF of the Hosting Operator Network and support PLMN IDs for one or more Participating Operator Networks. The AMF can authenticate whether the UE has connected with a valid participating PLMN ID and, if invalid, send a registration reject message to the UE. For example, if the Selected PLMN ID is not a PLMN ID for the Participating Operator Network, the AMF can send a registration reject message to the UE. In this case, the remaining procedures may not be performed.

[0102] At step 240, if the UE's selected PLMN ID is a PLMN ID for a participating Operator network and / or if the AMF has not yet registered the UE ID with the UDM, the AMF may send a request message for registration to the UDM (e.g., a request for UECM (UE configuration management) registration). The message may include at least one of the following information.

[0103] - NF ID: May contain identifier information for the AMF.

[0104] - UE ID: UE identifier information that may include one or more of SUPI (subscriber permanent identifier), GPSI (generic public subscription identifier), and PEI (permanent equipment identifier).

[0105] - serving PLMN ID: May include the selected PLMN ID (or the PLMN ID of the participating operator network corresponding to the selected PLMN ID).

[0106] - INS (indirect network sharing) information: may include one or more of the hosting network operator's PLMN ID (or the AMF's HPLMN ID) and NS (Network Sharing) indicators. The AMF may include the information if the UE's selected PLMN ID is the PLMN ID of the participating operator network.

[0107] - Supported feature: May include features supported by AMF. If Indirect Network Sharing is supported, information indicating support for that feature may be included.

[0108] - GUAMI (globally unique access and mobility management (AMF) identifier): A GUAMI for the AMF may be included. The MCC and MNC included in the GUAMI may use the same values ​​as the MCC and MNC included in the selected PLMN ID (e.g., the PLMN ID of the participating operator network).

[0109] - RAT type, Access type: RAT type indicates the type of radio access technology and may include at least one of NR, E-UTRA, NB-IOT, and NR NTN. Access Type may include information indicating 3GPP access or non-3GPP access.

[0110] In step 250, when the UDM receives the registration request message of step 240 from the AMF, it may send a response message to the registration request (e.g., a UECM registration response) to the AMF.

[0111] The UDM may update and / or store information regarding whether a UE is in an HPLMN supported by the hosting operator network, based on the information contained in the registration message received from the AMF. The UDM may store the relevant information about the UE, serving AMF information, etc., either directly or in the UDR. If the serving PLMN ID is the UE's HPLMN (for example, if the MCC and MNC included in the UE's SUPI are the same as the MCC and MNC included in the serving PLMN ID), the UDM may update the registration status information (or roaming status) to indicate that the UE is in the HPLMN.

[0112] If the serving PLMN ID is not the UE's HPLMN (for example, if one or more of the MCCs and MNCs included in the UE's SUPI differ from the MCCs and MNCs included in the serving PLMN ID), the UDM can update the registration status information (or roaming status) with information indicating that the UE is in the VPLMN (or is not in the HPLMN).

[0113] If the information about the UE received via the AMF includes INS information (or if the supported feature includes information indicating INS support), the UDM may store information indicating that the UE is in the HPLMN provided by the Hosting operator network (e.g., the UE is in a shared network). This information may be stored as registration status information for the UE or as separate information.

[0114] If the UDM receives a registration request message from the AMF that contains INS information (or if the supported feature contains information indicating INS support), the UDM may perform authentication for the registration request message based on the information contained in the INS information. If the INS information contains the PLMN ID of the hosting operator network, the UDM may perform authentication for the PLMN ID of the hosting operator network. If authentication fails (e.g., if the PLMN ID of the hosting operator network received from the AMF (or the VPLMN ID contained in the INS information) is not allowed), the UDM may send a response message to the AMF indicating rejection. The message may include information indicating the rejection of registration and the cause (e.g., an unallowed hosting operator network).

[0115] If the INS information includes an INS indicator or the PLMN ID of the Hosting operator network, the UDM may perform authentication for a registration request to the Hosting operator network. If authentication fails (e.g., if the INS indicator is received from the AMF but the UE is not allowed to connect to the Hosting operator network), the UDM may send a response message to the AMF indicating rejection. The message may include information indicating the rejection of registration and the cause (e.g., connection to the Hosting operator network is not allowed).

[0116] If authentication is successful, the UDM may send a response message to the AMF indicating acceptance of registration. The message may include information indicating acceptance of registration.

[0117] In step 260, if the AMF does not have subscriber information for the UE, it may send a subscriber information request message to the UDM (e.g., Nudm_SDM(subscriber data management)_Get request).

[0118] The request message may include one or more of the following information.

[0119] - UE ID: UE identifier information that may include one or more of SUPI, GPSI, and PEI.

[0120] - serving PLMN ID: May include the selected PLMN ID (or the PLMN ID of the participating operator network corresponding to the selected PLMN ID).

[0121] - INS information: may include one or more of the hosting network operator's PLMN ID (or the AMF's HPLMN ID) and NS (Network Sharing) indicators. The AMF may include the information if the UE's selected PLMN ID is the PLMN ID for the participating operator network (or if the UE has connected to a participating PLMN supported by the hosting operator network).

[0122] - Supported feature: May include features supported by the AMF. May include information indicating that the AMF supports Indirect Network Sharing. The AMF may include this information if the UE's selected PLMN ID is a PLMN ID for a participating operator network (or if the UE has connected to a participating PLMN supported by the hosting operator network).

[0123] - 3gpp-Sbi-Originating-Network-Id: In the case of an INS (e.g., when the UE's selected PLMN ID is the PLMN ID for the participating Operator network), the AMF may include header information (e.g., 3gpp-Sbi-Originating-Network-Id) containing its own PLMN ID (i.e., the PLMN ID of the hosting operator network) in the request message sent to the UDM.

[0124] In step 270, if the serving PLMN included in the message received from the AMF in step 260 is not an HPLMN for the UE, the UDM may transmit the UE's subscriber information for the serving PLMN to the AMF.

[0125] If the serving PLMN included in the message received from the AMF in step 260 is the HPLMN for the UE, the UDM can transmit the UE's subscriber information for the HPLMN to the AMF.

[0126] If the serving PLMN included in the message received from the AMF in step 260 is the HPLMN (or equivalent PLMN (EPLMN)) for the UE, and / or if the message received from the AMF in step 260 includes INS information (e.g., INS indication or PLMN ID of the Hosting operator network), the UDM may transmit subscriber information for the UE connected to the Hosting operator network to the AMF. For example, the UDM may provide separate subscriber information to be applied to the UE in the HPLMN provided by the hosting operator network (e.g., subscriber information containing parameters different from those included in the UE's subscriber information for the HPLMN). Alternatively, for example, the UDM may provide different subscriber information to be applied to the UE located in the HPLMN provided by the hosting operator network, depending on the PLMN ID of the corresponding Hosting operator network. If the message received from the AMF contains the PLMN ID of the hosting operator network, the UDM may include at least one of the following in the message sent to the AMF for each parameter included in the subscriber information according to the configuration information:

[0127] - Subscriber information applicable to the Home PLMN (i.e., when the PLMN ID selected by the UE is an HPLMN and the network the UE is connected to is a participating operator network)

[0128] - Subscriber information applicable to the PLMN ID of the participating operator network

[0129] - Subscriber information applicable to the Hosted Home PLMN (i.e., when the PLMN ID selected by the UE is an HPLMN and the network the UE is connected to is a hosting operator network)

[0130] The INS indication can be transmitted in various forms. For example, it may be an indicator included in a supported feature included in a message sent by the AMF to the UDM (e.g., an indicator indicating that the AMF supports network sharing), or a separate indicator in a message sent by the AMF to the UDM.

[0131] The PLMN ID of the hosting operator can be transmitted in various forms. For example, it may be a PLMN ID included in a specific header (e.g., 3gpp-Sbi-Originating-Network-Id or 3gpp-Sbi-Interplmn-Purpose) in an HTTP message (or, Service Based Interface (SBI) message) that the AMF sends to the UDM, or a separate PLMN ID (other than the serving PLMN ID) included in a message that the AMF sends to the UDM.

[0132] According to one embodiment, “INS case” may be used with the same meaning as the case where the UE selects and connects to a Hosted Home PLMN (i.e., the PLMN ID selected by the UE is an HPLMN and the network connected by the UE is a hosting operator network).

[0133] Subscriber information may include one or more of the following information.

[0134] -RAT (radio access technology) restriction: May include 3GPP RATs and non-3GPP RATs that prevent UE access. In the case of INS, UDM may provide RAT restrictions corresponding to (or related to) the INS.

[0135] For example, if a message received by the UDM from the AMF contains an INS indication or if the AMF supports INS (e.g., if the supported feature contains information indicating support for INS), the UDM may provide a RAT restriction corresponding to the INS.

[0136] For example, if a message received by the UDM from the AMF includes the PLMN ID of the hosting operator network, the UDM can provide a RAT restriction corresponding to the PLMN ID of the hosting operator network.

[0137] -Forbidden area: Can define an area where a terminal cannot initiate communication with the network. In the case of INS, UDM can provide relevant information for the INS case.

[0138] For example, if the message received by the UDM from the AMF contains an INS indication or if the AMF supports INS (e.g., if the supported feature contains information indicating support for INS), the UDM may provide a Forbidden area corresponding to the INS.

[0139] For example, if a message received by the UDM from the AMF includes the PLMN ID of the hosting operator network, the UDM can provide a Forbidden area corresponding to the PLMN ID of the hosting operator network.

[0140] - Service Area Restriction: May indicate an allowed area where the UE and the Network can initiate communication with a Network and / or Non-allowed Area where User Services cannot be obtained by initiating a User Service Request or SM Signaling.

[0141] In the case of INS, UDM can provide relevant information regarding the INS case.

[0142] For example, if a message received by the UDM from the AMF contains an INS indication or if the AMF supports INS (e.g., if the supported feature contains information indicating support for INS), the UDM may provide a Service Area Restriction corresponding to the INS.

[0143] For example, if a message received by the UDM from the AMF includes the PLMN ID of the hosting operator network, the UDM can provide a Service Area Restriction corresponding to the PLMN ID of the hosting operator network.

[0144] -RFSP (radio access type / frequency of selection priority) index: This may be an index representing a specific RRM setting in NG-RAN. In the case of INS, UDM can provide the relevant information for the INS case.

[0145] For example, if a message received by the UDM from the AMF contains an INS indication or if the AMF supports INS (e.g., if the supported feature contains information indicating support for INS), the UDM may provide an RFSP index corresponding to the INS.

[0146] For example, if a message received by the UDM from the AMF includes the PLMN ID of the hosting operator network, the UDM can provide an RFSP index corresponding to the PLMN ID of the hosting operator network.

[0147] -Subscribed S-NSSAIs: May represent the Network Slice identifier information(s) to which the terminal has subscribed. Default S-NSSAIs may represent the slice identifiers among the Subscribed S-NSSAIs that are marked as default S-NSSAIs. In the case of the Roaming Case, it may represent the Subscribed Network Slices applicable to the Serving PLMN. In the case of INS, the UDM may provide the Subscribed S-NSSAIs corresponding to the INS (or applicable to the INS).

[0148] For example, if a message received by the UDM from the AMF contains an INS indication or if the AMF supports INS (e.g., if the supported feature contains information indicating support for INS), the UDM may provide Subscribed S-NSSAIs corresponding to (or applicable to) the INS.

[0149] For example, if a message received by the UDM from the AMF contains the PLMN ID of the hosting operator network, the UDM may provide Subscribed S-NSSAIs corresponding to (or applicable to) the PLMN ID of the hosting operator network.

[0150] -Subscribed UE-Slice-MBR(s): This may be a list of maximum aggregated uplink and downlink MBRs (maximum bit rates) to be shared among all guaranteed bit rate (GBR) and / or non-GBR QoS flows associated with the same S-NSSAI according to the User's Subscription. According to one embodiment, there may be one Uplink and one Downlink value per S-NSSAI. In the case of an INS, the UDM may provide Subscribed UE-Slice-MBR(s) corresponding to the INS (or applicable to the INS).

[0151] For example, if a message received by the UDM from the AMF contains an INS indication or if the AMF supports INS (e.g., if the supported feature contains information indicating support for INS), the UDM may provide a Subscribed UE-Slice-MBR(s) corresponding to (or applicable to) the INS.

[0152] For example, if a message received by the UDM from the AMF includes the PLMN ID of the hosting operator network, the UDM can provide (applicable) Subscribed UE-Slice-MBR(s) corresponding to the PLMN ID of the hosting operator network.

[0153] - LBO (local breakout) Roaming Information (In SMF selection information): Can indicate whether LBO roaming is allowed per DNN (data network name), S-NSSAI, or per subscribed DNN. In the case of INS, UDM can provide the relevant information for the INS case.

[0154] For example, if a message received by the UDM from the AMF contains an INS indication or if the AMF supports INS (e.g., if the supported feature contains information indicating support for INS), the UDM may provide corresponding LBO Roaming Information. For example, the UDM may include information indicating that LBO Roaming is not allowed for all (or one or more) DNNs and / or S-NSSAIs.

[0155] For example, if a message received by the UDM from the AMF includes the PLMN ID of the hosting operator network, the UDM may provide LBO Roaming Information corresponding to the PLMN ID of the hosting operator network. For example, the UDM may include information indicating that LBO Roaming is not allowed for all (or one or more) DNNs and / or S-NSSAIs.

[0156] In step 280, the AMF may include the RFSP index for INS, Mobility Restriction List (MRL) for INS, UE-Slice-MBR for INS, etc. in the N2 message sent to the RAN. The AMF may use the parameters included in the message received in step 270 as is, or may use the parameters determined by the PCF (for example, if the PCF determines the RFSP index, UE-Slice-MBR, etc. for the case of INS and sends them to the AMF, those parameters).

[0157] At step 290, the AMF may include a Service Area Restriction (SAR) for INS in a registration accept or reject message transmitted to the UE over the RAN. The SAR may consist of an area where the UE can initiate communication with the network (e.g., Allowed Area) and / or an area where it may not initiate communication (e.g., Non-allowed Area). The SAR for INS represents a SAR that applies to a UE connected to a shared network (e.g., a hosting operator network that is not the participating network operator or HPLMN) by a participating operator (or the UE's HPLMN). If the SAR includes an Allowed Area, the UE may initiate communication with the network in the Allowed Area. If the SAR includes a Non-allowed Area, the UE may not initiate communication with the network in the Non-allowed Area.

[0158] FIG. 3 illustrates a method according to one embodiment of the present disclosure in which a PCF (e.g., V-PCF) of a hosting operator network determines the AM Policy of a UE connected to the hosting operator network.

[0159] The message names or expressions exemplified in the following steps are examples only and may be interpreted as identical to messages that perform the same or similar functions or contain the same or similar information. Additionally, some of the steps may be omitted or combined.

[0160] According to one embodiment, “INS case” may be used with the same meaning as the case where the UE selects and connects to a Hosted Home PLMN (i.e., the PLMN ID or serving PLMN ID selected by the UE is an HPLMN and the network connected by the UE is a hosting operator network).

[0161] At step 300, the UE can register with the AMF. The AMF can select a PCF for the UE's policy. To select a PCF, the AMF can send an NF discovery request message to the network repository function (NRF) that includes an NF type representing the PCF.

[0162] The AMF may include Support of Network Sharing in the request message if the UE's selected PLMN ID corresponds to the participating operator's PLMN ID.

[0163] If the received NF discovery message contains the PLMN ID of the hosting operator network, a PCF type indicating a PCF, and information indicating Support of Network Sharing, the NRF may include the address of the PCF(s) that support Network Sharing in the NF discovery response message sent to the AMF.

[0164] The AMF can select one of the PCFs received from the NRF as the PCF of the UE corresponding to the INS case.

[0165] In step 310, a policy association can be performed with the PCF and the AM. The AMF may include at least one of the following information in the Policy association request message sent to the PCF.

[0166] - Serving Network Identifier: AMF may include the hosting operator's PLMN ID in the serving network identifier if the UE's selected PLMN ID corresponds to the participating operator's PLMN ID.

[0167] - Selected PLMN ID (e.g., participating operator PLMN ID): The AMF may include the selected PLMN ID received from the UE if the UE's selected PLMN ID corresponds to the participating operator's PLMN ID. Alternatively, the AMF may include the selected PLMN ID received from the UE and / or an indicator indicating that it has connected to a hosting network (non-roaming).

[0168] - UE ID: May contain identifier information for the UE.

[0169] In step 320, if the message received from the AMF in step 310 contains a Selected PLMN ID (or an indicator indicating that it has connected to the hosting operator network), the PCF may use policy control related subscription information corresponding to the PLMN ID contained in the Selected PLMN ID or UE ID (SUPI).

[0170] PCF may include subscription information (e.g., PCR (Policy Control Request) trigger for INS) to receive notifications when connecting to INS in the response message sent to AMF.

[0171] In step 330, if a PCR trigger for INS exists (e.g., if the AMF received a PCR trigger for INS from the PCF in step 320), and / or if the UE's selected PLMN ID is a PLMN ID corresponding to a participating PLMN (or if the selected PLMN ID has been changed to a PLMN ID corresponding to a participating PLMN), the AMF may send a message to the PCF containing an indicator (or the UE's Selected PLMN ID) indicating that the UE has connected to a participating PLMN.

[0172] The AMF may include the parameters in the message transmitted to the PCF if a PCR trigger for RFSP index, a PCR trigger for SAR, or a PCR trigger for UE-Slice-MBR exists (e.g., received from the PCF in step 320), and / or if there are parameters among the parameters included in the UE's Subscription information that require authentication by the PCF. The AMF may include one or more of the RFSP index, SAR, and UE-Slice-MBR in the message transmitted to the PCF if the UE's selected PLMN ID is a PLMN ID corresponding to a participating PLMN, and if a corresponding PCR trigger exists.

[0173] In step 340, if the message received from the AMF contains an indicator (or the UE's Selected PLMN ID) indicating that it has connected to a participating PLMN, the PCF may update the AM policy information for the UE in accordance with the agreement with the participating network operator.

[0174] If updated parameters (e.g., RFSP index, SAR, UE-Slice-MBR, etc.) exist, the PCF can send a message to the AMF to notify them.

[0175] In step 350, the AMF can apply the AM policy information received from the PCF to the network.

[0176] FIG. 4 is a block diagram of a terminal or user equipment (400) according to one embodiment of the present disclosure.

[0177] The terminal (400) is an electronic device capable of wireless communication and may include user equipment (UE), mobile phones, smartphones, tablets, Internet of Things (IoT) devices having various form factors, and can perform wireless communication with a base station through a wireless channel.

[0178] Referring to FIG. 4, the terminal (400) may include at least one transceiver (401) (hereinafter, transceiver), at least one processor (402) (hereinafter, processor), and at least one memory (403) (hereinafter, memory). The transceiver (401), processor (402), and memory (403) of the terminal (400) may operate according to at least one or a combination thereof of methods corresponding to embodiments of the present disclosure. However, the components of the terminal (400) are not limited to the examples of components shown in FIG. 4. In other embodiments, the terminal (400) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the transceiver (401), processor (402), or memory (403) may be integrated into a single component.

[0179] The transceiver (401) may be a basic communication circuit or communication circuitry that enables the terminal (400) to perform wireless communication with a node or entity of a network. For example, the transceiver (401) may enable the terminal (400) to transmit and receive signals to and from a base station via cellular wireless communication, or to transmit and receive signals to and from another terminal via cellular wireless communication. For example, the transceiver (401) may be 3G (3rd generation), 4G (4th generation), LTE (long-term evolution), 5G (5th generation), NR (new radio), 6G (6th It can support at least one of various cellular wireless communication technologies including generation), and the various cellular wireless communication technologies supported by the transceiver (401) may include all subsequent evolved generations of wireless communication.

[0180] According to one embodiment, the terminal (400) may include a plurality of transceivers, and for example, when supporting EN-DC (E-UTRA (evolved-universal terrestrial radio access) - NR dual connectivity), it may include a first transceiver supporting 4G LTE wireless communication and a second transceiver supporting 5G NR wireless communication. According to another embodiment, when the terminal (400) supports NR-DC (NR Dual Connectivity), the terminal (400) may include a plurality of transceivers supporting 5G NR wireless communication. According to another embodiment, if the terminal (400) supports short-range wireless communication, the terminal (400) may separately include a transceiver that supports at least one of a group of wireless communication protocol standards such as those defined by Bluetooth®, wireless LAN or WLAN (wireless local area network) network (including, but not limited to, IEEE (institute of electrical and electronics engineer) 802.11-2016 standard or modifications thereof such as 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba and 802.11be).

[0181] According to one embodiment, the transceiver (401) may include various circuit structures used to transmit and receive signals to and from a base station via a wireless channel. The signals may include control information and data. For example, the transceiver (401) may be configured to include a radio frequency (RF) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (401) may output the signal received via the wireless channel to a processor (402) and transmit the signal output from the processor (402) via the wireless channel.

[0182] The processor (402) can control the overall operation of the terminal (400) according to an embodiment of the present disclosure. The processor (402) may be implemented as one or more IC (integrated circuit (or circuitry)) chips and may perform various data processing operations. The processor (402) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (403) individually, collectively, or in any combination. Additionally, the processor (402) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.

[0183] The processor (402) is electrically, operatively, or communicatively coupled to the transceiver (401) so as to control the transceiver (401).

[0184] The processor (402) may include at least one processor (or processing circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. For example, the processor (402) may include a communication processor (CP) that controls communication operations and an application processor (AP) that controls the execution of an upper layer (e.g., an application layer). In a specific embodiment, at least one part of the processor (402) may be included in one chip, and another part of the processor (402) may be included in a separate chip. Alternatively, at least one processor may be included in other components, e.g., a transceiver (401) or a memory (403).

[0185] The processor (402) may perform, cause, or control the operation of a terminal to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (402) may control the operation of a terminal to process a downlink signal received from a base station or to generate an uplink signal and transmit it to a base station. To this end, the processor (402) may control other components of the terminal (400) to perform various operations by executing computer programs, code, or instructions stored in memory (403).

[0186] Memory (403) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (403) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0187] The memory (403) can be electrically, operatively, or communically coupled with the processor (402) and can be accessed by the processor (402).

[0188] A computer program, code, or instruction that can be executed by a processor (402) may be stored in the memory (403). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (402) may be stored in a single memory device or may be separated and distributed across two or more memory devices. The processor (402) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (403).

[0189] According to one embodiment of the present disclosure, the operation of the terminal (400) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (403), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions.

[0190] FIG. 5 is a block diagram of a base station (500) according to one embodiment of the present disclosure.

[0191] The base station (500) can perform wireless communication with at least one terminal within the area of ​​the base station (500) through a wireless channel.

[0192] Referring to FIG. 5, a base station (500) may include at least one transceiver (501) (hereinafter, transceiver), at least one processor (502) (hereinafter, processor), and at least one memory (503) (hereinafter, memory). According to at least one or a combination thereof of methods corresponding to embodiments of the present disclosure, the transceiver (501), processor (502), and memory (503) of the base station (500) may be operated. However, the components of the base station (500) are not limited to the examples of components shown in FIG. 5. In other embodiments, the base station (500) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the transceiver (501), processor (502), or memory (503) may be integrated into a single component.

[0193] The transceiver (501) may be a communication circuit or communication circuitry that enables the base station (500) to perform wireless communication with a node or entity of the network. For example, the transceiver (501) may enable the base station (500) to transmit and receive signals to and from a terminal (400) via cellular wireless communication or to transmit and receive signals to and from another network entity via wireless communication. For example, the transceiver (501) may be 3G (3rd generation), 4G (4th generation) LTE (long-term evolution), 5G (5th generation) NR (new radio), 6G (6th generation) Various cellular wireless communication technologies, including (generation), etc., can be supported, and the various cellular wireless communication technologies supported by the transceiver (501) may include all subsequent evolved generations of wireless communication. According to one embodiment, the transceiver (501) may include various circuit structures used to transmit and receive signals to and from a terminal through a wireless channel. The signals may include control information and data. For example, the transceiver (501) may be configured to include an RF (radio frequency) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (501) may output the signal received through the wireless channel to a processor (502) and transmit the signal output from the processor (502) through the wireless channel.

[0194] Meanwhile, according to one embodiment of the present disclosure, a base station (500) may communicate with an entity or node of a network via wired or wireless communication. For example, the base station (500) may communicate via wired or wireless communication with an entity or node of an adjacent base station or core network via a backhaul network. Although not shown in the drawings, when the base station (500) performs wired communication, the base station (500) may include a separate network interface for wired communication in addition to the transceiver (501). The network interface may be referred to as network interface circuitry, communication interface circuitry, etc.

[0195] The processor (502) can control the overall operation of the base station (500) according to an embodiment of the present disclosure. The processor (502) may be implemented as one or more IC (integrated circuit or circuitry) chips and may perform various data processing operations. The processor (502) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (503) individually, collectively, or in any combination. Additionally, the processor (502) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.

[0196] The processor (502) is electrically, operatively, or communicatively coupled to the transceiver (501) so as to control the transceiver (501).

[0197] The processor (502) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a specific embodiment, at least one part of the processor (502) may be included in one chip, and another part of the processor (502) may be included in a separate chip. Alternatively, at least one processor may be included in other components, such as a transceiver (501) or memory (503).

[0198] The processor (502) may perform, cause, or control the operation of a base station to execute at least one or a combination of methods according to embodiments of the present disclosure. For example, the processor (502) may control the operation of a base station to generate a downlink signal and transmit it to a terminal, or to process an uplink signal received from a terminal. Alternatively, the base station may transmit and receive signals with an adjacent base station, transmit a signal received from a terminal to an upper node of the network, or receive a signal from an upper node of the network and transmit it to a terminal. To this end, the processor (502) may control other components of the base station (500) to perform various operations by executing computer programs, codes, and instructions stored in memory (503).

[0199] Memory (503) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (503) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semi-permanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0200] The memory (503) can be electrically, operatively, or communically coupled with the processor (502) and can be accessed by the processor (502).

[0201] A computer program, code, or instruction that can be executed by a processor (502) may be stored in the memory (503). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (502) may be stored in a single memory device or may be separated and distributed among two or more memory devices. The processor (502) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (503).

[0202] According to one embodiment of the present disclosure, the operation of a base station (500) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (503), based on a processing circuitry not configured to execute instructions, and / or based on a component of a processing circuitry not configured to execute instructions.

[0203] A terminal or a base station can perform various communication procedures related to the control plane or user plane by interacting with network entities based on communication through a wireless channel. For example, a terminal can communicate with network entities such as an access and mobility management function (AMF) or a session management function (SMF) through a base station. Alternatively, the base station can perform at least one communication procedure by directly transmitting and receiving signals or relaying them with network entities. The structure of the above-mentioned network entities will be explained in more detail through the drawings below.

[0204] FIG. 6 is a block diagram of a network entity (600) that performs network functions according to one embodiment of the present disclosure.

[0205] A network entity (600) may include one or more network functions (NF) that constitute a core network (e.g., 5G (5th generation) core, 5GC) in a communication system, or entities (devices, devices, nodes, or servers, etc.) that perform part of a network function. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across multiple network entities. Additionally, when an NF is implemented within a network entity, the NF may be implemented in the form of software, and in such cases, a program for running the NF may be loaded into the memory of the network entity (600).

[0206] A single NF can be implemented as one or more instances and can operate by being distributed across the same network entity or multiple network entities. Here, the instance is a software unit that logically executes a specific network function and may be separate from physical hardware resources. Additionally, one or more NFs may be implemented as a single network slice to operate in order to satisfy the specifications required by a specific service.

[0207] The above NF may include any one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN).

[0208] Referring to FIG. 6, a network entity (600) may include at least one network interface (601), at least one processor (602) (hereinafter referred to as processor), and at least one memory (603) (hereinafter referred to as memory). As described above, the NF may be implemented in the form of a physical device such as the network entity (600), or may be implemented and executed in the form of a virtualized instance. When the NF is implemented in the form of an instance, it may not necessarily include physical components as illustrated in FIG. 6. In such cases, the instance may be composed of one or more logical functional units and may be logically represented.

[0209] According to at least one or a combination thereof of the methods corresponding to the embodiments of the present disclosure, the network interface (601), processor (602), and memory (603) of the network entity (600) may be operated. However, the components of the network entity (600) are not limited to the examples of components shown in FIG. 6. In other embodiments, the network entity (600) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in one embodiment, the network interface (601), processor (602), or memory (603) may be implemented as a single component.

[0210] The network interface (601) is a collective term for the transmitting and receiving parts of a network entity and may be a communication circuit for transmitting and receiving signals with a terminal (user equipment, UE), a base station, or other network entities. In this case, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for wired communication. For example, the network interface (601) may include circuits, logic, hardware, etc. configured to exchange control plane messages or user plane messages with a terminal, a base station, or other core network entities via wireless or wired communication. The network interface (601) may operate using various protocols (e.g., NAS (Non-Access Stratum) protocol). Depending on the convenience of explanation and technical implementation, the network interface (601) may be referred to as a communication circuitry, a network interface circuitry, or a communication interface circuitry.

[0211] The processor (602) can control the overall operation of the network entity (600) according to an embodiment of the present disclosure. In one embodiment, the processor (602) may be implemented as one or more IC (integrated circuit or circuitry) chips and may execute various data processing operations. The processor (602) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (603) individually, collectively, or in any combination. Additionally, the processor (602) may include a single-core processor or a multi-core processor, and in a specific implementation method, may be composed of a processor assembly including a plurality of processing circuits. Additionally, it should be noted that the processor (602) may not necessarily be composed of physical hardware when the network function (600) is implemented in an instance form according to another embodiment.

[0212] According to one embodiment, the processor (602) is electrically, operatively, or communicatively coupled to the network interface (601) so as to control the network interface (601).

[0213] The processor (602) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a specific embodiment, at least one part of the processor (602) may be included in one chip, and another part of the processor (602) may be included in a separate chip. Alternatively, at least one processor may be included in other components, such as a network interface (601) or memory (603).

[0214] The processor (602) may perform or control the operation of a network entity (600) to perform at least one or a combination thereof of the methods according to the embodiments of the present disclosure. For example, the processor (602) may control the operation of the network entity (600) to exchange control plane messages or user plane messages with terminals, base stations, or other core network entities via wireless or wired communication using various protocols (e.g., NAS protocols). To this end, the processor (602) may control other components of the network entity (600) to perform various operations by executing computer programs, code, or instructions stored in memory (603).

[0215] Memory (603) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (603) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0216] According to one embodiment, the memory (603) may be electrically, operatively, or communically coupled with the processor (602) and may be accessed by the processor (602).

[0217] A computer program, code, or instruction that can be executed by a processor (602) may be stored in the memory (603). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (602) may be stored in a single memory or separated and distributed across two or more memories. The processor (602) can perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (603).

[0218] According to one embodiment of the present disclosure, the operation of a network entity (600) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer programs or code) stored in memory (603), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions. Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments but should be defined by the claims set forth below as well as equivalents thereof.

Claims

1. A method performed by the access and mobility management function (AMF) of a communication system, A step of identifying that the terminal is connecting via an indirect network sharing method; A step of transmitting a subscriber data request to the unified data management (UDM) of the participating operator network; and A method comprising the step of receiving subscriber data from the UDM that takes into account the PLMN ID of the hosting provider when the above subscriber data request includes the PLMN ID (identifier) ​​of the hosting provider.

2. In Paragraph 1, The method includes the step of receiving a message related to a registration request from a RAN (radio access network), which includes a PLMN ID selected by the terminal, and The step of identifying that the terminal is connecting via an indirect network sharing method is to identify that it is connecting via an indirect network sharing method based on whether the selected PLMN ID corresponds to the participating operator network, and A method characterized in that the above AMF is an AMF of a hosting provider network.

3. A method according to claim 1, wherein the subscriber data request comprises a serving PLMN ID corresponding to the participating operator network and a hosting operator's PLMN ID.

4. A method according to claim 1, comprising the step of transmitting a registration rejection message to the terminal when the PLMN selected by the terminal does not correspond to the participating operator network.

5. In a method performed by unified data management (UDM) of a communication system, A step of receiving a subscriber data request from the access and mobility management function (AMF) of the hosting provider network; and If the above subscriber data request includes the PLMN (public land mobile network) ID (identifier) ​​of the hosting provider, the method includes the step of transmitting subscriber data to the AMF considering the PLMN ID of the hosting provider. A method characterized in that, in relation to the above AMF, the terminal is connected via an indirect network sharing method.

6. In Paragraph 5, Based on the PLMN ID selected by the terminal, it is identified that the terminal is connecting via an indirect network sharing method, and A method characterized in that the above UDM is a UDM of a participating business network.

7. A method according to claim 5, wherein the subscriber data request comprises a serving PLMN ID corresponding to the participating operator network and a hosting operator's PLMN ID.

8. In the access and mobility management function (AMF) of a communication system, At least one transceiver; At least one processor connected to the above at least one transceiver so as to be able to communicate; and An AMF that is connected to communicate with at least one processor and can be executed individually or in any combination of the at least one processor, and includes a memory that stores an instruction for the AMF to identify that a terminal is connected in an indirect network sharing manner, to transmit a subscriber data request to a unified data management (UDM) of a participating operator network, and, if the subscriber data request includes a public land mobile network (PLMN) ID (identifier) ​​of a hosting operator, to receive subscriber data from the UDM considering the PLMN ID of the hosting operator.

9. In Paragraph 8, The above command enables the AMF to receive a message related to a registration request including a PLMN ID selected by the terminal from the RAN (radio access network), and to identify that it is connecting via the indirect network sharing method based on whether the selected PLMN ID corresponds to the participating operator network, and The above AMF is characterized as being an AMF of a hosting provider network.

10. In claim 8, the subscriber data request is characterized by including a serving PLMN ID corresponding to the participating operator network and a hosting operator's PLMN ID.

11. An AMF according to claim 8, wherein the command causes the terminal to send a registration rejection message if the PLMN selected by the terminal does not correspond to the participating operator network.

12. In unified data management (UDM) of communication systems, At least one transceiver; At least one processor connected to the above at least one transceiver so as to be able to communicate; and The above-mentioned at least one processor is connected to communicate with the above-mentioned at least one processor and can be executed individually or in any combination thereof, and includes a memory that stores a command to transmit subscriber data to the AMF (access and mobility management function) in consideration of the hosting operator's PLMN (public land mobile network) ID (identifier) ​​when the UDM receives a subscriber data request from the AMF (access and mobility management function) of the hosting operator's network, and when the subscriber data request includes the hosting operator's PLMN ID (identifier). A UDM characterized in that, in relation to the above AMF, the terminal is connected via an indirect network sharing method.

13. In Paragraph 12, Based on the PLMN ID selected by the terminal, it is identified that the terminal is connecting via an indirect network sharing method, and The above UDM is a UDM characterized by being a UDM of a participating operator network.

14. In claim 12, the UDM is characterized in that the subscriber data request includes a serving PLMN ID corresponding to the participating operator network and a hosting operator's PLMN ID.

15. A UDM according to claim 12, wherein if the PLMN selected by the terminal does not correspond to the participating operator network, the terminal receives a registration rejection message from the AMF.