Method and device for processing terminal context in wireless communication system supporting network sharing
The method addresses inefficiencies in terminal context processing during network sharing by verifying slice mapping information and transmitting UE context between AMFs, ensuring seamless mobility and effective network slicing in 5G systems.
Patent Information
- Application Number
- PCT/KR2026/005880
- 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
Existing wireless communication systems face challenges in efficiently processing terminal context during network sharing, particularly when a terminal moves between networks, leading to inefficiencies in mobility management and network slicing operations.
A method and apparatus for processing terminal context in a wireless communication system that supports network sharing, involving verification of slice mapping information and transmission of UE context information between access and mobility management functions (AMFs) during a registration procedure, utilizing slice mapping information to facilitate seamless transitions between hosting and participating networks.
Enables efficient and stable mobility management by ensuring rapid and accurate processing of terminal context, supporting network slicing services across different networks, thereby enhancing the functionality and performance of 5G mobile communication systems.
Smart Images

Figure KR2026005880_12112026_PF_FP_ABST
Abstract
Description
Method and apparatus for processing terminal context in a wireless communication system supporting network sharing
[0001] The present disclosure relates to a method and apparatus for communication in a wireless communication system that supports network sharing.
[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 present disclosure may provide a method and apparatus for processing terminal context for a shared network.
[0009] The present disclosure may provide a method and apparatus for efficiently processing a terminal context in a wireless communication system that supports network sharing.
[0010] The present disclosure may provide a method and apparatus for processing a terminal context during a registration procedure following the movement of a terminal in a wireless communication system that supports network sharing.
[0011] The present disclosure may provide a method and apparatus for processing a terminal context among access and mobility management functions (AMFs) involved in a registration procedure following the movement of a terminal in a wireless communication system that supports network sharing.
[0012] According to an embodiment of the present disclosure, a method performed by a first access and mobility management function (AMF) of a first network in a wireless communication system that supports network sharing between a first network of a hosting operator and a second network of a participating operator may include a step of verifying slice mapping information related to a UE during a registration procedure involving the movement of a UE from a first AMF of the first network to a second AMF of the second network. The method may include a step of verifying first network slice information related to the hosting operator that provides network slicing services to the UE using the network sharing in the first network, based on the slice mapping information. The method may include a step of transmitting UE context information, including second network slice information related to the participating operator corresponding to the first network slice information, to the second AMF during the registration procedure.
[0013] In one embodiment, the network sharing utilizes indirect network sharing, and the first network may include the UE's VPLMN (visited public land mobile network), and the second network may include the UE's HPLMN (home public land mobile network).
[0014] In one embodiment, the slice mapping information may include mapping information between the first network slice information of the hosting operator and the second network slice information of the participating operator.
[0015] In one embodiment, the UE context information may include the second network slice information without the first network slice information.
[0016] In one embodiment, the first network slice information may include at least one first S-NSSAI (single-network slice selection assistance information) of the hosting operator, and the second network slice information may include at least one second S-NSSAI of the participating operator.
[0017] According to an embodiment of the present disclosure, in a wireless communication system that supports network sharing between a first network of a hosting operator and a second network of a participating operator, a first AMF of the first network comprises at least one transceiver, at least one processor coupled to the at least one transceiver in a communicable manner, and at least one memory coupled to the at least one processor in a communicable manner, wherein the at least one memory stores instructions executable by the at least one processor individually or in any combination thereof, and the instructions cause the first AMF to perform a plurality of operations, wherein the plurality of operations may include an operation to check slice mapping information related to the UE during a registration procedure by the movement of the UE (user equipment) from the first AMF of the first network to the second AMF of the second network. The plurality of operations may include an operation to check first network slice information related to the hosting operator who provides network slicing services to the UE using the network sharing in the first network based on the slice mapping information. The above plurality of operations may include the operation of transmitting UE context information, including second network slice information related to the participating operator corresponding to the first network slice information, to the second AMF during the registration procedure.
[0018] According to an embodiment of the present disclosure, in a wireless communication system that supports network sharing between a first network of a hosting operator and a second network of a participating operator, a second AMF of the second network comprises at least one transceiver, at least one processor commutably coupled to the at least one transceiver, and at least one memory commutably coupled to the at least one processor, wherein the at least one memory stores instructions executable individually or in any combination by the at least one processor, and the instructions cause the second AMF to perform a plurality of operations, and the plurality of operations may include an operation of transmitting a UE context request message for the UE during a registration procedure by moving the UE from the first AMF of the first network to the second AMF of the second network. The above plurality of operations may include, in response to the transmission of the UE context request message, an operation of receiving UE context information including second network slice information associated with the participating operator corresponding to the first network slice information from the first AMF, and the first network slice information may be associated with the hosting operator that provides network slicing services to the UE using the network share in the first network.
[0019] FIG. 1 shows an example of the structure of a 5G system according to an embodiment of the present disclosure.
[0020] FIG. 2 illustrates an example of a method for processing an Old AMF-based UE context when changing the AMF of a terminal in a wireless communication system that supports network sharing according to an embodiment of the present disclosure.
[0021] FIG. 3 illustrates an example of a New AMF-based UE context processing method when an AMF changes due to the movement of a terminal in a wireless communication system that supports network sharing according to an embodiment of the present disclosure.
[0022] FIG. 4 illustrates an example of a method for processing an Old AMF-based UE context when an AMF changes due to the movement of a terminal in a wireless communication system that supports network sharing according to an embodiment of the present disclosure.
[0023] FIG. 5 illustrates an example of a New AMF-based UE context processing method when an AMF changes due to the movement of a terminal in a wireless communication system that supports network sharing according to an embodiment of the present disclosure.
[0024] FIG. 6 shows an example of the structure of a network entity in a wireless communication system according to an embodiment of the present disclosure.
[0025] FIG. 7 shows an example of the structure of a terminal in a wireless communication system according to an embodiment of the present disclosure.
[0026] The operating principles of the present disclosure are described in detail below with reference to the attached drawings. Furthermore, the terms described below are defined in consideration of their functions in the present disclosure. Since these may vary depending on the intent or convention of the user or operator, their definitions should be determined according to the content throughout this specification. In this regard, it should be noted that identical components in the attached drawings are represented by the same reference numerals whenever possible. Additionally, detailed descriptions of known functions and configurations that could obscure the essence of the present disclosure will be omitted.
[0027] In describing the embodiments in this specification, descriptions of 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.
[0028] 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 reference numbers.
[0029] 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. The embodiments provided are merely to ensure that the disclosure of the present 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.
[0030] Terms used in this disclosure to refer to network entities or network functions, objects of a wireless communication system, messages, identification information, etc., are examples provided for convenience of explanation. Accordingly, this disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.
[0031] For convenience, the present disclosure uses terms and names that may be applied to next-generation communication systems or defined in 5G system specifications, but is not limited by said terms and names. The present disclosure may be similarly applied to wireless communication systems following other specifications or next-generation specifications through some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.
[0032] Hereinafter, a base station (BS) is an entity that performs resource allocation to a terminal (user equipment: UE) and may be at least one of a gNode B (gNB), eNode B (eNB), Node B, a wireless access unit, a base station controller, or a node on a network. A terminal (UE) may be at least one of a Mobile Station (MS), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing communication functions. In this 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.
[0033] At this time, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can 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 function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing the means of instruction to perform the function 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).
[0034] 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 instance, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may be executed in reverse order according to their corresponding functions.
[0035] In this embodiment, the term "part" refers to a software or hardware component, such as an FPGA or ASIC, and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to operate one or more processors. Accordingly, as an 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." Furthermore, the components and "parts" may be implemented to operate one or more CPUs within a device or secure multimedia card. In addition, in the embodiment, '~part' may include one or more processors.
[0036] In the present disclosure, each of the phrases such as “A and / or B,” “A or B,” “at least one of A and B,” “at least one of A or B,” “A, B or C,” “at least one of A, B and C,” and “at least one of A, B, or C” may include any one of the items listed together in the corresponding phrase, or all possible combinations thereof. Terms such as “first,” “second,” or “first” or “second” may be used simply to distinguish a component from another component and do not limit the components in any other aspect (e.g., importance or order).
[0037] In this disclosure, network technology may refer to standard specifications defined by the International Telecommunication Union (ITU) or 3GPP (e.g., TS 23.501, TS 23.502, TS 23.503, etc.), and the components included in the network structure of 33 may each refer to a physical entity, or to software that performs an individual function, or to hardware combined with software. Since the relevant description can be found in the standard specifications, a detailed description is omitted.
[0038] Terms used in the following description to identify connection nodes, terms referring to network entities (NE) or network functions (NF), terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are provided as examples 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.
[0039] For convenience of explanation below, some terms and names defined in the 3GPP (3rd generation partnership project long term evolution) standard may be used. However, the present disclosure is not limited by the above terms and names and may be equally applied to systems conforming to other standards.
[0040] FIG. 1 shows an example of the structure of a 5G system according to an embodiment of the present disclosure.
[0041] A 5G mobile communication network may include a 5G terminal (UE) (100), a 5G RAN (radio access network, base station), a gNB (5G nodeB), an eNB (evolved nodeB, etc.) (110), and a 5G core network. The 5G core network may include NFs such as an access and mobility management function (AMF) (120) that provides a function to manage the mobility of the terminal (100), a session management function (SMF) that provides a session management function, a user plane function (UPF) (130) that performs a data delivery role, a policy control function (PCF) (140) that provides a policy control function, a unified data management function (UDM) (145) that provides data management functions such as subscriber data and policy control data, and a unified data repository (UDR) that stores data of various network functions (NFs) such as the UDM. The 5G core network may include a network slice selection function (NSSF) (160), a network data analytic function (NWDAF) (165), and an application function (AF). It may further include NFs such as function)(170), DN (data network)(175), and NSACF (network slice admission control function)(180).
[0042] 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.
[0043] - N1: Reference point between UE and AMF
[0044] - N2: Reference point between (R)AN and AMF
[0045] - N3: Reference point between (R)AN and UPF
[0046] - N4: Reference point between SMF and UPF
[0047] - N5: Reference point between PCF and AF
[0048] - N6: Reference point between UPF and DN
[0049] - N7: Reference point between SMF and PCF
[0050] - N8: Reference point between UDM and AMF
[0051] - N9: Reference point between 2 core UPFs
[0052] - N10: Reference point between UDM and SMF
[0053] - N11: Reference point between AMF and SMF
[0054] - N12: Reference point between AMF and AUSF
[0055] - N13: Reference point between UDM and the authentication server function (AUSF)
[0056] - N14: Reference point between 2 AMFs
[0057] - N15: Reference point between PCF and AMF in non-roaming scenarios, reference point between PCF and AMF within the visited network in roaming scenarios
[0058] In 5G systems, network slicing technology refers to a technology and structure that enables multiple virtualized, independent logical networks within a single physical network. Network operators may provide services by configuring virtual end-to-end networks called network slices to satisfy the specialized requirements of services / applications. In this case, network slices can be distinguished by an identifier called S-NSSAI (single-network slice selection assistance information). The network transmits a set of allowed slices (e.g., allowed NSSAI(s)) to a terminal during a terminal registration procedure (e.g., UE registration procedure), and the terminal can transmit and receive application data through a PDU (protocol data unit) session created via one of the allowed slice sets' S-NSSAIs (i.e., network slice). Hereinafter, in the embodiments of the present disclosure, the operation of NF may be understood as the operation of OAM (orchestration and management) for efficiently configuring, monitoring, and / or managing a 5G network.
[0059] 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 / or AMF of the shared network, etc.) to a participating operator (e.g., a shared participating network operator). The base station of the hosting operator (e.g., a Shared RAN) leased by the participating operator may be configured to broadcast the participating operator's PLMN (public land mobile network) ID. Terminals using the participating operator as their home network (Home PLMN) may 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.
[0060] PLMNs can provide logically independent networks through network slices. Each network slice is identified by an S-NSSAI, which includes 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 network slice for a terminal to connect to through its own set of S-NSSAIs.
[0061] In this disclosure, the terms "hosting operator," "hosting PLMN," "visited PLMN" (VPLMN), and "visited network" may be used interchangeably. Additionally, the terms "participating operator," "participating PLMN," "home PLMN" (HPLMN), and "home network" may be used interchangeably.
[0062] In the present disclosure, a Shared RAN (or Shared Base Station) is a RAN provided by a hosting operator, and the Shared RAN may support corresponding PLMN IDs for one or more contracted participating operators.
[0063] A shared RAN can support one or more of the TAIs included in the set of TAIs (Tracking area identities) of a supported PLMN.
[0064] A shared RAN may support one or more of the S-NSSAIs included in the S-NSSAI set of a supported PLMN for the supported PLMN. Additionally, a shared RAN may support one or more of the S-NSSAIs included in the NSAG (Network Slice AS (access stratum) Group) set of a supported PLMN for the supported PLMN. An NSAG represents one or more S-NSSAIs and is identified by an NSAG ID.
[0065] In the present disclosure, a shared AMF may support corresponding PLMN IDs for one or more contracted participating operators as an AMF provided by a hosting operator.
[0066] A shared RAN can support one or more of the TAIs included in the set of TAIs (Tracking area identities) of a supported PLMN for each supported PLMN. A shared AMF can support one or more of the S-NSSAIs included in the set of S-NSSAIs of a supported PLMN for each supported PLMN ID.
[0067] In the present disclosure, a shared NSSF may support corresponding PLMN IDs for one or more contracted participating operators as an NSSF provided by a hosting operator. For each supported PLMN ID, the shared NSSF may support one or more of the S-NSSAIs included in the S-NSSAI set of the corresponding PLMN.
[0068] In the present disclosure, a UDM that supports indirect network sharing (INS) is a network entity provided by a participating operator.
[0069] In the embodiments of FIGS. 2 to 5 described below, it can be assumed that the terminal is a terminal joined to a participating operator network, and that the Old AMF, which supports Indirect Network Sharing (INS) to the participating operator network, is an AMF of the hosting operator network that manages the mobility of the terminal joined to the participating operator network. As the terminal moves from the hosting operator network to the participating operator network, the AMF managing the terminal's mobility may change from the Old AMF to the New AMF, and it can be assumed that the New AMF is an AMF of the participating operator network. In the present disclosure, the Old AMF and the New AMF may be referred to as the first AMF and the second AMF, respectively. Additionally, the hosting operator network and the participating operator network may be referred to as the first network and the second network, respectively. Furthermore, the first AMF may be an AMF of the hosting operator network (e.g., Old AMF), and the second AMF may be an AMF of the participating operator network (e.g., New AMF).
[0070] FIG. 2 illustrates an example of a method for processing an Old AMF-based UE context when an AMF changes due to the movement of a terminal in a wireless communication system that supports network sharing according to an embodiment of the present disclosure. Here, the terminal may be in an idle mode / state.
[0071] Referring to FIG. 2, in step S210, a registration procedure may be performed according to the movement of the terminal (201) between the terminal (201), the New AMF (203), and the Old AMF (205). In step 210, the terminal (201) may perform a registration procedure in which it sends a registration request message to the Old AMF (205) or the New AMF (203) according to the movement, and receives a registration acceptance / rejection message from the Old AMF (205) or the New AMF (203), and may use a registration procedure disclosed in the 3GPP standard.
[0072] In FIG. 2, the Old AMF (205) may be an AMF that supports the Home PLMN (HPLMN) or Equivalent PLMN (EPLMN) of the terminal (201). The Old AMF (205) is an AMF that supports network sharing, and the PLMN ID of the Old AMF (205) may be different from the HPLMN and EPLMN of the terminal (201) (i.e., the Old AMF (205) is an AMF of the hosting operator network, but may support the HPLMN or EPLMN of the terminal (201) as a participating operator network). The terminal (201) may have the Old AMF (205) as the last registered AMF. The above step S210 may be performed optionally and may be a non-essential step.
[0073] In step S210 above, the terminal (201) may send a new registration request message to the RAN (not shown) as it moves. The RAN may select a New AMF (203) depending on the location of the terminal (201).
[0074] In step S210 above, the terminal (201) can transmit a registration request message containing a selected PLMN ID to the New AMF (203) through the RAN.
[0075] In step S212, if the New AMF (203) is newly selected as the AMF managing the mobility of the terminal (201), it may send a UE context request message to the Old AMF (205) requesting the transmission of the UE context for the terminal (201). The UE context request message may include at least one of the 5G GUTI (globally unique temporary identifier), which is a temporary identifier of the terminal (201), the SUPI (subscription permanent identifier), which is a unique identifier, and a supported feature. Step S212 may be performed optionally and may be a non-essential step.
[0076] In step S214, the Old AMF (205) can verify and determine whether the new AMF (203) is an AMF of the participating operator network. Step S214 may be performed optionally and may be a non-essential step. The Old AMF (205) may receive the message of step S212 from an AMF of another PLMN (for example, if the PLMN ID included in the UE context request message of step S212 is different from its own PLMN ID, or if the 3gpp-Sbi-Originating-Network-Id header, which is an HTTP (hypertext transfer protocol) header defined in the 3GPP TS 29.500 specification that identifies the source network (PLMN ID or SNPN (standalone non-public network) ID) in the 5G Service Infrastructure (SBI) request, is included, or if it receives the UE context request message of the New AMF (203) through a security edge protection proxy (SEPP)), or if it receives the UE context request message of step S212 from an AMF of a participating operator network (for example, if the PLMN ID included in the UE context request message of step S212 is the PLMN ID of the participating operator network, or if it represents the HPLMN or EPLMN of the UE (201), or If the PLMN ID included in the 3gpp-Sbi-Originating-Network-Id header is the PLMN ID of the participating operator network or represents the HPLMN or EPLMN of the UE, or if the operator network of the AMF managing the mobility of the terminal (201) has changed from the hosting operator network to the participating operator network, then in step S216, the Old AMF (205) may transmit UE context information to the new AMF (203) including at least one of the following examples of information.The above S216 step may be performed optionally and may be a non-essential step.
[0077] - The above UE context information may include HPLMN S-NSAIs corresponding to Allowed NSSAIs and Partially Allowed NSSAIs for each Access Type. However, Old AMF (205) may not include slice mapping information (e.g., S-NSSAI(s) of the hosting operator corresponding to the S-NSSAI(s) of the participating operator) in the above UE context information.
[0078] - Old AMF (205) may not include at least one of the RFSP (RAT / Frequency Selection Priority) index, SAR (Specific Absorption Rate), and / or UE-Slice-MBR (Slice Maximum Bit Rate) in the UE context information.
[0079] - Old AMF (205) may not include the HR SBO (Home Routed with Session Breakout in VPLMN) indication in the UE context information.
[0080] In step S218, the remaining registration procedures defined in the 3GPP standard may be performed between the UE (201), New AMF (203), Old AMF (205), and UDM (207). Since the remaining registration procedures may utilize known procedures, a detailed description is omitted. The New AMF (203) may make a request to the UDM (207) to obtain information that is not included in the information received in step S218. Step S218 may be performed optionally and may be a non-essential step.
[0081] According to an embodiment of FIG. 2, a method performed by a first AMF of a first network in a wireless communication system that supports network sharing between a first network of a hosting operator and a second network of a participating operator may include, during a registration procedure by moving a UE from a first AMF of the first network to a second AMF of the second network, a process of verifying slice mapping information related to the UE; a process of verifying first network slice information related to the hosting operator who provides network slicing services to the UE using the network sharing in the first network based on the slice mapping information; and a process of transmitting UE context information including second network slice information related to the participating operator, corresponding to the first network slice information, to the second AMF during the registration procedure.
[0082] In one embodiment, the network sharing utilizes indirect network sharing, the first network may include the VPLMN of the UE, and the second network may include the HPLMN of the UE.
[0083] In one embodiment, the slice mapping information may include mapping information between the first network slice information of the hosting operator and the second network slice information of the participating operator.
[0084] In one embodiment, the UE context information may include the second network slice information without the first network slice information.
[0085] In one embodiment, the first network slice information may include at least one first S-NSSAI of the hosting operator, and the second network slice information may include at least one second S-NSSAI of the participating operator.
[0086] According to the embodiment of FIG. 2, terminal context can be efficiently processed between AMFs (e.g., New AMF (203), Old AMF (205)) involved in the registration procedure following the movement of a terminal (201) in a wireless communication system that supports network sharing. Through this, when the AMF is changed following the movement of the terminal (201) from the Old AMF (205) that supports indirect network sharing (INS) in the VPLMN of the terminal (201) to the AMF (i.e., New AMF (203)) in the HPLMN of the terminal (201), a suitable UE context can be transmitted between the AMFs involved in the registration procedure to support rapid and stable mobility.
[0087] FIG. 3 illustrates an example of a method for processing a UE context based on New AMF when changing an AMF due to the movement of a terminal in a wireless communication system that supports network sharing according to an embodiment of the present disclosure. Here, the terminal may be in an idle mode / state.
[0088] Referring to FIG. 3, in step S310, a registration procedure can be performed according to the movement of the terminal (301) between the terminal (301), the New AMF (303), and the Old AMF (305) (S310). In step 310, the terminal (301) can perform a registration procedure in which it sends a registration request message to the Old AMF (305) or the New AMF (303) according to the movement, and receives a registration acceptance / rejection message from the Old AMF (205) or the New AMF (203), and can use a registration procedure disclosed in the 3GPP standard.
[0089] In FIG. 3, the Old AMF (305) may be an AMF that supports the Home PLMN (HPLMN) or EPLMN of the terminal (301). The Old AMF (305) is an AMF that supports network sharing, and the PLMN ID of the Old AMF (305) may be different from the HPLMN and EPLMN of the terminal (301) (i.e., the Old AMF (305) is an AMF of the hosting operator network, but may support the HPLMN or EPLMN of the terminal (301) as a participating operator network). The terminal (301) may have the Old AMF (305) as the last registered AMF. Step S310 may be performed optionally and may be a non-essential step.
[0090] In step S310 above, the terminal (301) may send a new registration request message to the RAN (not shown). The RAN may select a New AMF (303) depending on the location of the terminal (301).
[0091] In step S310 above, the terminal (301) can transmit a registration request message containing a selected PLMN ID to the New AMF (303) through the RAN.
[0092] In step S312, if the New AMF (303) is newly selected as the AMF managing the mobility of the terminal (301), it may send a UE context request message to the Old AMF (305) requesting the transmission of the UE context for the terminal (301). The UE context request message may include at least one of 5G GUTI, SUPI, and supported features. Step S312 may be performed optionally and may be a non-essential step.
[0093] In step S314, if the Old AMF (305) receives the UE context request message from the New AMF (303) in step S312, it may transmit the UE context information to the New AMF (303). Step S314 may be performed optionally and may be a non-essential step.
[0094] In step S316, the New AMF (303) may delete one or more of the following information from 1-1) to 1-3) from the UE context information received in step S314 when the AMF managing the mobility of the terminal (301) is changed from the AMF of the hosting operator network to the AMF of the participating operator network. Step S316 may be performed optionally and may be a non-essential step.
[0095] 1-1) Slice mapping information (e.g., S-NSSAI(s) of the hosting operator corresponding to the S-NSSAI(s) of the participating operator)
[0096] 1-2) RFSP index, SAR, UE-Slice-MBR
[0097] 1-3) HR SBO indication
[0098] In step S318, the remaining registration procedures defined in 3GPP standards may be performed between the UE (301) and the New AMF (303). Since the remaining registration procedures may utilize known procedures, a detailed description is omitted. The New AMF may make a request to the UDM (307) to obtain information not included in the information received in step S316. Step S318 may be performed optionally and may be a non-essential step.
[0099] According to the embodiment of FIG. 3, terminal context can be efficiently processed between AMFs (e.g., New AMF (303), Old AMF (305)) involved in the registration procedure following the movement of a terminal (201) in a wireless communication system that supports network sharing.
[0100] FIG. 4 illustrates an example of a method for processing an Old AMF-based UE context when an AMF changes due to the movement of a terminal in a wireless communication system that supports network sharing according to an embodiment of the present disclosure. Here, the terminal may be in a connected mode / state.
[0101] Referring to FIG. 4, in step S410, an N2-based handover procedure may be performed between the UE (401), New AMF (405), and Old AMF (403). In step S410, the Source-RAN (S-RAN) (not shown) performs a handover request to the Old AMF (403). Step S410 may be performed optionally and may be a non-essential step.
[0102] In step S412, if the Old AMF (or Source-AMF) (403) can no longer handle the terminal (401), the Old AMF (403) can discover / select a new AMF (or Target-AMF). Step S412 may be performed optionally and may be a non-essential step.
[0103] In step S414, the Old AMF (403) may utilize a Network Repository Function (NRF) or configuration information to discover the New AMF (405). If an NRF is used, the Old AMF (403) may send an NF discovery request message to the V-NRF (407), which is the NRF of the VPLMN or the hosting operator network. The NF discovery message sent by the Old AMF (403) to the V-NRF (407) may include one or more of the following: a Target NF representing the AMF, location information of the UE (e.g., Tracking Area Identifier (TAI)), a PLMN ID set to a selected PLMN ID (or participating operator PLMN ID), and a capability including a network sharing function.
[0104] If the PLMN ID included in the NF discovery request message is different from the PLMN ID that V-NRF (407) is responsible for, and / or if there is no NF (i.e., AMF) that satisfies the NF discovery request message, V-NRF (407) may forward the NF discovery request message to H-NRF (409), which is an NRF of the HPLMN or participating operator network corresponding to the PLMN ID included in the NF discovery request message. When H-NRF (409) receives an NF discovery message from Old AMF (403) via V-NRF (407), it may include information of NFs that satisfy the information included in the NF discovery message (e.g., at least one of the NF's address, NF's PLMN ID, PLMN ID supported by the NF, and Capability) in an NF discovery response message sent to Old AMF (403) via V-NRF (407). The Old AMF (403) can select the New AMF (405) based on information contained in a message received from the V-NRF (407) or H-NRF (409). The above step S414 may be performed optionally and may be a non-essential step.
[0105] In step S416, the Old AMF (403) can verify and determine whether the new AMF (405) is an AMF of the participating network operator. If the Old AMF (403) determines that the selected New AMF is an AMF of the same PLMN as itself and is an AMF that supports the selected PLMN ID (i.e., an AMF of the hosting network operator), then in step S418, the Old AMF (403) can transfer the stored UE Context as is to the selected New AMF (405). Step S418 may be performed optionally and may be a non-essential step.
[0106] In step S418 above, if the selected New AMF (403) is the AMF of the participating network operator (e.g., if the PLMN ID of the New AMF (405) is different from the PLMN ID of the Old AMF (403) and / or the PLMN ID of the New AMF (405) is the same as the selected PLMN ID of the terminal (401), the Old AMF (403) may transmit UE context information including at least one of the following information to the New AMF (405).
[0107] - HPLMN S-NSAIs corresponding to Allowed NSSAIs and Partially Allowed NSSAIs by Access Type may be included in the UE context information. However, Old AMF (403) may not include slice mapping information (e.g., S-NSSAI(s) of the hosting operator corresponding to the S-NSSAI(s) of the participating operator) in the UE context information.
[0108] - Old AMF (403) may not include at least one of the RFSP index, SAR, and UE-Slice-MBR in the UE context information.
[0109] - Old AMF (403) may not include HR SBO indication in the above UE context information.
[0110] In step S420, when the New AMF (405) receives a message containing the UE context information from step S418, it may send a response message to the Old AMF (403). Step S420 may be performed optionally and may be a non-essential step.
[0111] In step S422, the remaining N2 handover procedure may be performed through at least one of UE (401), New AMF (405), Old AMF (403), V-NRF (407) and / or H-NRF (409). Since the remaining handover procedure may utilize known procedures, a specific description is omitted. Step S422 may be performed optionally and may be a non-essential step.
[0112] FIG. 5 illustrates an example of a method for processing a UE context based on New AMF when changing an AMF due to the movement of a terminal in a wireless communication system that supports network sharing according to an embodiment of the present disclosure. Here, the terminal may be in a connected mode / state.
[0113] Referring to FIG. 5, in step S510, an N2-based handover procedure may be performed between the UE (501), New AMF (505), and Old AMF (503). In step S510, the Source-RAN (S-RAN) (not shown) may request a handover to the Old AMF (503). Step S510 may be performed optionally and may be a non-essential step.
[0114] In step S512, if the Old AMF (or Source-AMF) (503) can no longer handle the terminal (401), the Old AMF (503) can discover / select a new AMF (or Target-AMF). Step S512 may be performed optionally and may be a non-essential step.
[0115] In step S514, the Old AMF (503) may utilize NRF or configuration information to discover the New AMF (505). If NRF is used, the Old AMF (503) may send an NF discovery request message to the V-NRF (507), which is the NRF of the VPLMN or the hosting operator network. The NF discovery message sent by the Old AMF (503) to the V-NRF (507) may include one or more of the following: a Target NF representing the AMF, location information of the UE (e.g., Tracking Area Identifier (TAI)), a PLMN ID set to a selected PLMN ID (or participating operator PLMN ID), and a capability including network sharing capabilities.
[0116] If the PLMN ID included in the NF discovery request message is different from the PLMN ID that V-NRF (507) is responsible for, and / or if there is no NF (i.e., AMF) that satisfies the NF discovery request message, V-NRF (507) may forward the NF discovery request message to H-NRF (509), which is an NRF of the HPLMN or participating operator network corresponding to the PLMN ID included in the NF discovery request message. When H-NRF (509) receives an NF discovery message from Old AMF (503) via V-NRF (407), it may include information of NFs that satisfy the information included in the NF discovery message (e.g., at least one of the NF's address, NF's PLMN ID, PLMN ID supported by the NF, and Capability) in an NF discovery response message sent to Old AMF (503) via V-NRF (507). The Old AMF (503) can select the New AMF (505) based on information contained in a message received from the V-NRF (507) or H-NRF (409). Step S514 may be performed optionally and may be a non-essential step.
[0117] In step S516, the Old AMF (503) can send a message to the selected New AMF (505) that includes the UE Context information stored in the Old AMF (503) as is. Step S516 may be performed optionally and may be a non-essential step.
[0118] In step S518, after receiving the message containing the UE Context information from step S516, the New AMF (505) can identify / confirm that the AMF managing the mobility of the terminal (501) has changed from the AMF of the hosting operator network to the AMF of the participating operator network (or that the PLMN ID of the AMF has changed). For example, the AMF can identify / confirm that the PLMN ID of the AMF has changed through the following method. The New AMF (505) can confirm that the AMF managing the mobility of the terminal (501) has changed if the PLMN ID included in the message containing the UE Context information from step S516 is different from its own PLMN ID, if the message from step 516 includes a 3gpp-Sbi-Originating-Network-Id header, or if the message from step 516 is received via SEPP, etc.
[0119] In step S518, the New AMF may delete or not store at least one of the following information 2-1) to 2-3) from the UE context information received in step 516.
[0120] 2-1) Slice mapping information (e.g., S-NSSAI(s) of the hosting operator corresponding to the S-NSSAI(s) of the participating operator)
[0121] 2-2) RFSP index, SAR, UE-Slice-MBR
[0122] 2-3) Old AMF is an HR SBO indication
[0123] The above S518 step may be performed optionally and may be a non-essential step.
[0124] In step S520, the New AMF (505) may send a response message to the Old AMF (503) in response to the reception of the message in step 516. Step S520 may be performed optionally and may be a non-essential step.
[0125] In step S522, the remaining N2 handover procedure may be performed through at least one of UE (501), New AMF (505), Old AMF (503), V-NRF (507) and / or H-NRF (509). Since the remaining handover procedure may utilize known procedures, a specific description is omitted. Step S422 may be performed optionally and may be a non-essential step.
[0126] FIG. 6 illustrates an example of the structure of a network entity in a wireless communication system according to an embodiment of the present disclosure. The network entity (601) of FIG. 6 may be implemented as any one of the RAN, AMF, SMF, NRF, UPF, data collection function, and training server shown in the embodiments of FIG. 2 to 5.
[0127] Referring to FIG. 6, a network entity (601) may include a transceiver (602), a processor (603), and a memory (604). The network entity (601) may include at least one of an electronic device, a server, a UE, a terminal, a network entity, an AP, a base station, an NRF, a RAN, an AMF, an SMF, a UDM, a UPF, a DCF, and a training server. In the present disclosure, the processor (603) may be defined as a circuit or an application-specific integrated circuit or at least one processor.
[0128] The transceiver (602) can transmit and receive signals to and from an external electronic device (or other network entity) via wired or wireless means. The transceiver (602) may be referred to as a transceiver. Additionally, the transceiver (602) may include a communication interface for communicating with other network entities.
[0129] The processor (603) can control the overall operation of the network entity (601) according to the embodiment proposed in the present disclosure. For example, the processor (603) can control the signal flow between each block to perform operations according to the flowchart described above. Specifically, the processor (603) can control the operation of the network entity of FIG. 6 according to at least one method of the embodiments of FIG. 2 to FIG. 5, for example.
[0130] The memory (604) can store at least one of the information transmitted and received through the transmission and reception unit (602) and the information generated through the processor (603).
[0131] According to an embodiment of the present disclosure, in a wireless communication system supporting network sharing between a first network of a hosting operator and a second network of a participating operator, a first AMF (601) of the first network comprises at least one transceiver (602), at least one processor (603) coupled to the at least one transceiver (602) for communication, and at least one memory (604) coupled to the at least one processor (603) for communication, wherein the at least one memory (604) stores instructions that can be executed individually or in any combination by the at least one processor, and the instructions cause the first AMF to perform a plurality of operations, wherein the plurality of operations include, during a registration procedure by which a UE moves from the first AMF of the first network to the second AMF of the second network, an operation to check slice mapping information related to the UE, and, based on the slice mapping information, an operation to check first network slice information related to the hosting operator who provides network slicing services to the UE using the network sharing in the first network, and the registration During the procedure, the operation may include transmitting UE context information, including second network slice information related to the participating operator corresponding to the first network slice information, to the second AMF.
[0132] In one embodiment, the network sharing utilizes indirect network sharing, the first network may include the VPLMN of the UE, and the second network may include the HPLMN of the UE.
[0133] In one embodiment, the slice mapping information may include mapping information between the first network slice information of the hosting operator and the second network slice information of the participating operator.
[0134] In one embodiment, the UE context information may include the second network slice information without the first network slice information.
[0135] In one embodiment, the first network slice information may include at least one first S-NSSAI of the hosting operator, and the second network slice information may include at least one second S-NSSAI of the participating operator.
[0136] According to an embodiment of the present disclosure, in a wireless communication system that supports network sharing between a first network of a hosting operator and a second network of a participating operator, a second AMF (601) of the second network comprises at least one transceiver (602), at least one processor (603) communicably coupled to the at least one transceiver (602), and at least one memory (604) communicably coupled to the at least one processor (603). The at least one memory (604) stores instructions that can be executed individually or in any combination by the at least one processor (603), and the instructions cause the second AMF to perform a plurality of operations. The plurality of operations include, during a registration procedure involving the movement of a UE from a first AMF of the first network to a second AMF of the second network, an operation of transmitting a UE context request message for the UE, and in response to the transmission of the UE context request message, a second network slice information related to the participating operator corresponding to the first network slice information to the first AMF. It includes an operation to receive UE context information, and the first network slice information may be related to the hosting operator that provides network slicing services to the UE using the network share in the first network.
[0137] FIG. 7 shows an example of the structure of a terminal in a wireless communication system according to an embodiment of the present disclosure.
[0138] Referring to FIG. 7, the terminal (701) may include a transceiver (702), a processor (703), and a memory (704). The terminal (701) may include at least one of an electronic device, a server, a UE, a terminal, an AP, or a base station. In the present disclosure, the processor may be defined as a circuit or an application-specific integrated circuit or at least one processor.
[0139] The transceiver (702) can transmit and receive signals with an external electronic device. The transceiver (602) may be referred to as a transceiver.
[0140] The processor (703) can control the overall operation of the terminal (701) according to the embodiment proposed in the present disclosure. For example, the processor (703) can control the signal flow between each block to perform an operation according to at least one method of the embodiments of FIGS. 2 to 5. Specifically, the processor (703) can control the terminal (701) to perform communication (or signaling) with a base station or network entity illustrated in FIGS. 2 to 5, for example.
[0141] The memory (704) can store at least one of the information transmitted and received through the transceiver (702) and the information generated through the processor (703).
[0142] It should be noted that the system configuration diagrams, method example diagrams, device configuration diagrams, etc., illustrated in FIGS. 1 to 7 above are not intended to limit the scope of the rights of the present disclosure. That is, all configurations or operations described in FIGS. 1 to 7 above should not be interpreted as essential components for the implementation of the present disclosure, and may be implemented within a scope that does not impair the essence of the present disclosure even if only some components are included.
[0143] Methods according to the claims or embodiments described in the specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0144] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs may include instructions that cause the electronic device to execute methods according to the claims or embodiments described in the specification of this disclosure.
[0145] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), EEPROM (Electrically Erasable Programmable Read Only Memory), magnetic disc storage devices, CD-ROM (Compact Disc-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.
[0146] Additionally, the program may be stored on an attachable storage device accessible via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.
[0147] In the specific embodiments of the present disclosure described above, the components included in the present disclosure are expressed in a 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, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.
Claims
1. A method performed by a first AMF (access and mobility management function) of a first network in a wireless communication system that supports network sharing between a first network of a hosting operator and a second network of a participating operator, said method A process of verifying slice mapping information related to the UE during the registration procedure involving the movement of a UE (user equipment) from the first AMF of the first network to the second AMF of the second network; A process of identifying first network slice information related to the hosting operator who provides network slicing services to the UE using the network share in the first network based on the slice mapping information; and A method comprising the process of transmitting UE context information, including second network slice information related to the participating operator corresponding to the first network slice information, to the second AMF during the above registration procedure.
2. In Paragraph 1 The above network sharing utilizes indirect network sharing, and A method in which the first network includes the visited public land mobile network (VPLMN) of the UE, and the second network includes the home public land mobile network (HPLMN) of the UE.
3. In Paragraph 1 A method in which the slice mapping information includes mapping information between the first network slice information of the hosting operator and the second network slice information of the participating operator.
4. In Paragraph 1 A method in which the above UE context information includes the second network slice information without the first network slice information.
5. In Paragraph 1 The above first network slice information includes at least one first S-NSSAI (single-network slice selection assistance information) of the hosting operator, and A method comprising at least one second S-NSSAI of the participating operator, wherein the above second network slice information.
6. In a wireless communication system that supports network sharing between a first network of a hosting operator and a second network of a participating operator, the first AMF (access and mobility management function) of the first network, At least one transmitter / receiver; At least one processor coupled to the above at least one transceiver in a manner that enables communication; and It includes at least one memory coupled to communicate with the above at least one processor, and The at least one memory stores instructions executable individually or in any combination by the at least one processor, and the instructions cause the first AMF to perform a plurality of operations, and The above plurality of operations are, During the registration procedure involving the movement of a UE (user equipment) from the first AMF of the first network to the second AMF of the second network, an operation to verify slice mapping information related to the UE, An operation to identify first network slice information related to the hosting operator who provides network slicing services to the UE using the network share in the first network based on the above slice mapping information, and A first AMF comprising the operation of transmitting to the second AMF during the above registration procedure UE context information including second network slice information related to the participating operator corresponding to the first network slice information.
7. In Paragraph 6 The above network sharing utilizes indirect network sharing, and The first network above includes the visited public land mobile network (VPLMN) of the UE, and the second network includes the home public land mobile network (HPLMN) of the UE, forming a first AMF.
8. In Paragraph 6 The above slice mapping information is a first AMF comprising mapping information between the first network slice information of the hosting operator and the second network slice information of the participating operator.
9. In Paragraph 6 The above UE context information is a first AMF including the second network slice information without the first network slice information.
10. In Paragraph 6 The above first network slice information includes at least one first S-NSSAI (single-network slice selection assistance information) of the hosting operator, and The above second network slice information is a first AMF comprising at least one second S-NSSAI of the participating operator.
11. In a wireless communication system that supports network sharing between a first network of a hosting operator and a second network of a participating operator, the second AMF (access and mobility management function) of the second network, At least one transmitter / receiver; At least one processor coupled to the above at least one transceiver in a manner that enables communication; and It includes at least one memory coupled to communicate with the above at least one processor, and The at least one memory stores instructions executable individually or in any combination by the at least one processor, and the instructions cause the second AMF to perform a plurality of operations, and The above plurality of operations are, During the registration procedure involving the movement of a UE (user equipment) from a first AMF of the first network to a second AMF of the second network, the operation of transmitting a UE context request message for the UE; and In response to the transmission of the above UE context request message, the operation includes receiving UE context information including second network slice information associated with the participating operator, corresponding to the first network slice information, from the first AMF. The first network slice information is related to the second AMF of the hosting operator that provides network slicing services to the UE using the network share in the first network.
12. In Paragraph 11 The above network sharing utilizes indirect network sharing, and The first network above includes the visited public land mobile network (VPLMN) of the UE, and the second network includes the home public land mobile network (HPLMN) of the UE, forming a second AMF.
13. In Paragraph 11 The above UE context information is a second AMF received based on slice mapping information between the first network slice information of the hosting operator and the second network slice information of the participating operator.
14. In Paragraph 11 The above UE context information is a second AMF including the second network slice information without the first network slice information.
15. In Paragraph 11 The above first network slice information includes at least one first S-NSSAI (single-network slice selection assistance information) of the hosting operator, and The above second network slice information is a second AMF comprising at least one second S-NSSAI of the participating operator.
