Device and method for supporting terminal application service

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure relates to a method and a device for supporting a terminal performing data communication by using a network slice and, more specifically, to a method and a device for, when a terminal roams in communication using network slices, allowing the terminal to select a slice related to an application to be used by the terminal and a network providing the slice.

Description

Device and method for supporting terminal application services

[0001] The present disclosure relates to a method and device for supporting a terminal performing data communication using a network slice, and more specifically, to a method and device for selecting a slice related to an application that the terminal wishes to use and a network providing the slice when the terminal roams in communication using a network slice.

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

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

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

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

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

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

[0008] The present disclosure aims to provide a method and device for supporting a terminal performing data communication using a network slice.

[0009] In addition, the present disclosure provides a method and device for selecting a slice related to an application that the terminal wishes to use and a network providing the slice when the terminal roams in communication using a network slice.

[0010] The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned can be clearly understood by a person having ordinary skill in the technical field to which the present invention belongs from the description below.

[0011] According to an embodiment of the present invention for solving the above-described problem, a method performed by a terminal of a wireless communication system may include the steps of: transmitting a first message related to a change of a slice to an access and mobility management function (AMF) of a home public land mobile network (HPLMN); receiving a second message including information on at least one slice and information on at least one PLMN providing the at least one slice from the AMF of the HPLMN; transmitting a registration request message to the AMF of a first PLMN; receiving a registration rejection message from the AMF of the first PLMN indicating that a slice requested by the terminal in the first PLMN is not allowed; selecting a slice based on the registration rejection message; selecting a second PLMN providing the selected slice; and transmitting a registration request message to the AMF of the selected second PLMN.

[0012] According to an embodiment, the registration rejection message may include information about at least one slice and information about at least one PLMN associated with the at least one slice.

[0013] In an embodiment, the step of selecting the slice may further include receiving a policy from a policy control function (PCF), the policy including information about at least one slice and information about at least one PLMN providing each of the at least one slice.

[0014] In some embodiments, the second message may further include information regarding the priority of the at least one slice.

[0015] In some embodiments, the slice may be selected based on information regarding the priority of the at least one slice.

[0016] In an embodiment, when there are multiple PLMNs providing the selected slice, the second PLMN may be selected by giving priority to a PLMN that provides slices that overlap with the applications that the terminal wishes to receive.

[0017] In an embodiment, if there are multiple PLMNs providing the selected slice, the second PLMN may be selected by giving priority to a PLMN providing a greater number of slices.

[0018] According to an embodiment, the second message may include information of at least one PLMN and information of at least one slice provided by the at least one PLMN.

[0019] In addition, a terminal of a wireless communication system according to an embodiment of the present invention for solving the above-described problem may include a transceiver; and a control unit configured to transmit a first message related to a change of a slice to an access and mobility management function (AMF) of a home public land mobile network (HPLMN) through the transceiver, receive a second message including information on at least one slice and information on at least one PLMN providing the at least one slice from the AMF of the HPLMN through the transceiver, transmit a registration request message to the AMF of a first PLMN through the transceiver, receive a registration rejection message from the AMF of the first PLMN through the transceiver, indicating that the slice requested by the terminal in the first PLMN is not allowed, select a slice based on the registration rejection message, select a second PLMN providing the selected slice, and transmit a registration request message to the AMF of the selected second PLMN through the transceiver.

[0020] One embodiment of the present disclosure may provide a method and device for supporting a terminal performing data communication using a network slice.

[0021] In addition, one embodiment of the present disclosure can provide a method and device for selecting a slice related to an application that the terminal wishes to use and a network providing the slice when the terminal roams in communication using a network slice.

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

[0023] FIG. 1 illustrates an example of a 5G network environment according to one embodiment of the present disclosure.

[0024] FIG. 2 is a flowchart illustrating an embodiment for enabling network slice support and communication in a 5G network according to an embodiment of the present disclosure.

[0025] FIG. 3A and FIG. 3B are flowcharts illustrating an embodiment for enabling network slice support and communication in a 5G network according to an embodiment of the present disclosure.

[0026] FIGS. 4A and 4B are flowcharts illustrating an embodiment for enabling network slice support and communication in a 5G network according to an embodiment of the present disclosure.

[0027] FIG. 5A and FIG. 5B are flowcharts illustrating an embodiment for enabling network slice support and communication in a 5G network according to an embodiment of the present disclosure.

[0028] FIG. 6A and FIG. 6B are flowcharts illustrating an embodiment for enabling network slice support and communication in a 5G network according to an embodiment of the present disclosure.

[0029] FIG. 7 is a diagram showing the configuration of a terminal according to an embodiment of the present disclosure.

[0030] FIG. 8 is a diagram illustrating a configuration of a network entity according to an embodiment of the present disclosure.

[0031] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. In describing the embodiments, descriptions of technical details that are well-known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.

[0032] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0033] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided solely 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 invention, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification.

[0034] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0035] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0036] Here, the term '~ part' used in the present embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, 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'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~part' may include one or more processors.

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

[0038] For the convenience of explanation below, the present disclosure uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard or the 3GPP NR standard, or terms and names modified based thereon. However, the present disclosure is not limited to the above-described terms and names, and may be equally applied to systems conforming to other standards. In the present disclosure, a base station is an entity that performs resource allocation to a terminal (user equipment: UE), and may be at least one of a gNode B, a gNB, an eNode B, an eNB, a Node B, a BS, a RAN (radio access network), a NG-RAN (next generation-RAN), a base station controller, or a node on a network. The base station may provide network access to the terminal(s) in an LTE system or an NR system. For the convenience of explanation, eNB and gNB may be used interchangeably. That is, a base station described as an eNB may represent a gNB. In the present disclosure, the term terminal may refer to various wireless communication devices, including UE (User Equipment), MS (Mobile Station), 5G UE, cellular phones, smartphones, computers, mobile phones, NB (narrow band)-IoT devices, sensors, and may include a multimedia system capable of performing a communication function.

[0039] In addition, the embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems with some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge. For example, the fifth generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included here, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge. That is, in specifically explaining the embodiments of the present disclosure, the communication standards specified by 3GPP will be the main target, but the main gist of the present disclosure can be applied to other communication systems with similar technical backgrounds with slight modifications within a range that does not significantly deviate from the scope of the present disclosure, and this can be done at the discretion of a person skilled in the technical field of the present disclosure.

[0040] In 5G or NR systems, the access and mobility management function (AMF), which manages the mobility of terminals, and the session management function (SMF), which manages sessions, are separated. Accordingly, unlike in 4G LTE communication systems where the mobility management entity (MME) performed both mobility management and session management, in 5G or NR systems, the entities performing mobility management and session management are separated into the AMF and the SMF, respectively, which has changed the communication method and communication management method between terminals and network entities.

[0041] In 5G or NR systems, mobility management for non-3GPP access is performed through the AMF via the N3IWF (non-3GPP inter-working function), and session management is performed through the SMF. Furthermore, security-related information, a crucial element in mobility management, is also processed through the AMF.

[0042] As described above, in 4G LTE systems, the MME is responsible for both mobility management and session management. 5G or NR systems can support a non-standalone (NSA) architecture that utilizes these network entities from the 4G LTE system to perform communications.

[0043] With the development of 5G communication systems, network slice (or network slicing) technology has been introduced for radio access network (RAN) and core network (CN) structures.

[0044] The present disclosure relates to a method and device for supporting a terminal performing data communication using a network slice.

[0045] In addition, the present disclosure relates to a method and device for selecting a slice related to an application that a terminal wishes to use and a network providing the slice when the terminal roams in communication using a network slice.

[0046] FIG. 1 illustrates an example of a 5G network environment according to one embodiment of the present disclosure.

[0047] Referring to FIG. 1, a 5G or NR core network may be configured to include at least one of network functions (NFs), such as a user plane function (UPF) (131), a session management function (SMF) (121), an access and mobility management function (AMF) (111), a 5G radio access network (RAN) (base station) (103), a user data management (UDM) (151), and a policy control function (PCF) (161). In addition, the 5G or NR core network may include entities, such as an authentication server function (AUSF) (141) and an authentication, authorization, and accounting (AAA) (171), for authentication of these entities.

[0048] The above AMF (111) is an entity for managing access and mobility of the UE (101). For example, the AMF (111) can perform network functions such as registration, connection, reachability, mobility management, access confirmation, authentication, and mobility event generation of the UE (101).

[0049] The above SMF (121) can perform a management function for a PDU (protocol data unit) session of the UE (101). For example, the SMF (121) can perform a session management function through the establishment, modification, and release of sessions and the maintenance of a tunnel between the UPF (131) and the RAN (103) required therefor, an IP (Internet protocol) address allocation and management function of the UE (101), user plane selection and control, traffic processing control in the UPF (131), and charging data collection control, etc., and network functions.

[0050] The above UPF (131) performs the role of processing data of the UE (101), and can perform the role of processing data so that data transmitted by the UE (101) can be transmitted to an external network or data received from an external network can be transmitted to the UE (101). For example, the UPF (131) can perform network functions such as serving as an anchor between radio access technologies (RATs), packet routing and forwarding, packet inspection, user plane policy application, traffic usage report creation, buffering, etc.

[0051] The above UDM (151) can perform functions such as generating authentication information for 3GPP security, processing user identifiers (user IDs), managing a list of network functions (NFs) supporting terminals (101), and managing subscription information.

[0052] The above PCF (161) is an NF that manages operator policy information for providing services in a 5G system.

[0053] A UE (user equipment, terminal) (101) can access a 5G core network through a base station (5G RAN, radio access network, base station, BS, 103). Meanwhile, an N3IWF (N3 interworking function) (not shown) may exist for cases where the UE (101) communicates through non-3GPP access. In the case of non-3GPP access, session management is controlled by the UE (101), non-3GPP access, N3IWF, and SMF (121), and for mobility management, control may be performed through the UE (101), non-3GPP access, N3IWF, and AMF (111).

[0054] In a 5G or NR system, entities that perform mobility management and session management are separated into AMF (111) and SMF (121). Meanwhile, a 5G or NR system is being considered for a stand-alone (SA) deployment structure that performs communication only with 5G or NR entities, and a non-stand-alone (NSA) deployment structure that uses 4G entities and 5G or NR entities together.

[0055] As shown in Fig. 1, when a UE (101) communicates with a network, control is performed by a base station (103), and deployment may be possible in which a 5G entity of a core network is used. In this case, mobility management between the UE (101) and the AMF (111) and session management between the UE (101) and the SMF (121) may be performed in the NAS (non-access stratum) layer, which is layer 3.

[0056] The communication network on which this disclosure is based assumes a 5G or 4G LTE network, but the same concept can be applied to other systems within a range that can be understood by a person with ordinary technical skills.

[0057] The 3GPP standard has standardized the 5G network system architecture and procedures. Mobile carriers can offer various services on 5G networks. To provide each service, mobile carriers must satisfy different service requirements (e.g., latency, communication range, data rate, bandwidth, reliability, etc.). To achieve this, mobile carriers can configure network slices and allocate network resources appropriate for specific services, either by network slice or by set of network slices. Network resources can refer to network functions (NFs), logical resources provided by NFs, or radio resource allocations from base stations.

[0058] For example, a mobile carrier can configure network slice A to provide mobile broadband services, network slice B to provide vehicle communication services, and network slice C to provide IoT services. In other words, 5G networks can efficiently provide relevant services to terminals through network slices specialized for each service's characteristics.

[0059] The present disclosure relates to a method and device for supporting a terminal performing data communication using a network slice, and, in a case where a terminal roams in communication using a network slice, to a method and device for selecting a slice related to an application that the terminal wishes to use and a network providing the slice.

[0060] FIG. 2 is a flowchart illustrating an embodiment for enabling network slice support and communication in a 5G network according to an embodiment of the present disclosure.

[0061] The embodiment illustrated in FIG. 2 is about the operation of the network and the UE (101) when the terminal (UE) (101) is in the home network (HPLMN, home PLMN).

[0062] Referring to FIG. 2, at step 201, the UE (101) can transmit a registration request message to the AMF (111).

[0063] At this time, the information element transmitted and included in the registration request message may include an indication for a slice change or an indication for a state change of the terminal (101). The role of this indication is to notify the network to support an update of the state or slice information of the terminal (101), so that the network can update the state of the terminal (101) when a situation such as when the terminal (101) is roaming occurs.

[0064] Or, if this information is available and a slice-related policy update of the terminal (101) is required, the network can transmit slice-related policy update information or slice-related configuration update information to the UE (101).

[0065] At step 203, AMF (111) can send a registration accept message to UE (101).

[0066] At this time, the information transmitted in the registration accept message, i.e., the information element, may include at least one of slice information, information about candidate PLMNs (public land mobile networks) that provide the slice, and information about access technology supported by the PLMN. For example, when there is slice #1 that provides application #1, PLMNs that can provide slice #1 may be PLMN #1 and PLMN #2. In this case, the registration accept message may include information such as information about the slice #1, information about PLMN #1 and PLMN #2 that can provide slice #1, and be transmitted to the UE (101). For example, when there is slice #2 that provides application #2, PLMNs that can provide slice #2 may be PLMN #2 and PLMN #3. In this case, the registration accept message may include information such as information about the slice #2 and information about PLMN #2 and PLMN #3 that can provide the slice #2, and may be transmitted to the UE (101). Meanwhile, information about the access technology that can provide the corresponding service may also be included in the registration accept message or transmitted to the UE (101) as separate information.

[0067] Or in another embodiment, the information transmitted in the registration accept message, i.e., the information element, may include at least one of PLMN information, information on (candidate) slices provided by the PLMN, and information on access technology supported by the PLMN. For example, when there is PLMN #1, slices provided by PLMN #1 may be slice #1 and slice #2. In this case, the registration accept message may include information on PLMN #1, and information on slice #1 and slice #2 provided by PLMN #1, and may be transmitted to the UE (101). In addition, the access technology information provided by PLMN #1 may also be included in the registration accept message or transmitted to the UE (101) as separate information. In addition, for example, slice #1 may support both application #1 and application #2.

[0068] In steps 211 and 213, PCF (161) can transmit policy information to UE (101) via AMF (111).

[0069] At this time, the information included in the policy information transmitted, i.e., the information element, may include at least one of slice information, information about candidate PLMNs providing the slice, and information about the access technology supported by the PLMN. For example, if there is slice #1 providing application #1, PLMNs that can provide slice #1 may be PLMN #1 and PLMN #2. In this case, the policy information may include information such as information about the slice #1, information about PLMN #1 and PLMN #2 that can provide slice #1, and may be transmitted to the terminal (101). For example, if there is slice #2 providing application #2, PLMNs that can provide slice #2 may be PLMN #2 and PLMN #3. In this case, the policy information may include information such as information about the slice #2, information about PLMN #2 and PLMN #3 that can provide slice #2, and may be transmitted to the terminal (101). Meanwhile, information on access technology that can provide the service may also be included in the policy information or transmitted to the UE (101) as separate information.

[0070] Or in another embodiment, the information transmitted included in the policy information, i.e., the information element, may include at least one of PLMN information, information on slices provided by the PLMN, and information on access technology supported by the PLMN. For example, when there is PLMN #1, slices provided by PLMN #1 may be slice #1 and slice #2. In this case, the policy information may include information on PLMN #1, and information on slice #1 and slice #2 provided by PLMN #1, and may be transmitted to the terminal (101). In addition, access technology information provided by PLMN #1 may also be included in the policy information or transmitted to the UE (101) as separate information. In addition, for example, slice #1 may support both application #1 and application #2.

[0071] At step 221, the UE (101) can select a slice.

[0072] UE (101) can select a slice that provides a service of an application supported by UE (101).

[0073] At step 223, the UE (101) can set the priority of the slice.

[0074] When there are multiple slices providing applications, UE (101) can set the priority of the slices.

[0075] At step 225, the UE (101) can select a PLMN by considering the priority of the slice.

[0076] The UE (101) can select a PLMN by referring to the priority between slices set in step 223 above.

[0077] Meanwhile, depending on the information transmitted to the UE (101) from the network (AMF (111) or PCF (161) etc.) and received by the UE (101), the method by which the UE (101) selects the PLMN in step 225 may be different.

[0078] Case 1) When slice information and candidate PLMN information are transmitted to the UE (101).

[0079] The information element transmitted from the network to the UE (101) may include slice information, information about candidate PLMNs providing the slice, and information about access technology supported by the PLMN. For example, if there is slice #1 providing application #1, information such as information about slice #1 and information indicating that PLMNs capable of providing slice #1 are PLMN #1 and PLMN #2 may be transmitted to the UE (101). For example, if there is slice #2 providing application #2, information such as information about slice #2 and information indicating that PLMNs capable of providing slice #2 are PLMN #2 and PLMN #3 may be transmitted to the UE (101). Meanwhile, information about access technology capable of providing the corresponding service may also be transmitted to the UE (101).

[0080] In this case, the UE (101) that received case 1 can select PLMNs that provide slices that provide applications that the UE (101) wants to receive by assigning weights or priorities to PLMNs that provide slices.

[0081] For example, if PLMNs that can provide slice #1 are PLMN #1 and PLMN #2, and PLMNs that can provide slice #2 are PLMN #2 and PLMN #3, then PLMN #2 can have a higher priority than other PLMNs because it provides slice #1 and slice #2.

[0082] Or as another example,

[0083] Case 2) When information on candidate slices provided for PLMNs is transmitted to the UE (101).

[0084] The information element transmitted from the network to the UE (101) may include PLMN information, information about slices provided by the PLMN, and information about access technologies supported by the PLMN. For example, when there is PLMN #1, information about PLMN #1 and information indicating that the slices provided by PLMN #1 are slice #1 and slice #2, etc., may be transmitted to the UE (101). In addition, information about the access technology provided by PLMN #1 may also be transmitted to the UE (101). In addition, for example, slice #1 may support both application #1 and application #2.

[0085] In this case, the UE (101) that received case 2 can select a PLMN that has a lot of information about the slices that the UE (101) is trying to select.

[0086] For example, if the slices provided by PLMN #3 are slice #1, slice #2, and slice #3, which are more than the slices provided by PLMN #1 (slice #1, slice #2), PLMN #3 may have a higher priority than PLMN #1.

[0087] Case 3)

[0088] Or, 1) the UE (101) receives the priority or weight for each slice or PLMN, and 2) if there is a slice with a high priority among the requested slices, the UE (101) can select the PLMN providing the slice with the highest priority.

[0089] For example, if slice #1 has a higher weight than other slices #2 and #3, the PLMNs providing slice #1 (e.g., PLMN #1) may have a higher priority than the other PLMNs.

[0090] That is, if application #1 or user or the terminal user must use slice #1 with the highest priority, the PLMN that provides slice #1, which corresponds to a case where the slice has a high priority, may have a higher priority than other PLMNs.

[0091] At step 281, the UE (101) can transmit a registration request message to the AMF (111-3) through the base station (103-03) corresponding to the VPLMN (visited PLMN).

[0092] In process 283, the UE (101) can receive a registration accept message from the AMF (111-3) of the VPLMN (via the base station (103-03)).

[0093] FIG. 3A and FIG. 3B are flowcharts illustrating an embodiment for enabling network slice support and communication in a 5G network according to an embodiment of the present disclosure.

[0094] The embodiments illustrated in FIGS. 3a and 3b relate to the operation of a UE in a VPLMN and are examples of registration accept.

[0095] And, the embodiments illustrated in FIGS. 3a and 3b are examples of candidate PLMNs per slice.

[0096] Referring to FIGS. 3a and 3b, at step 301, the UE (101) can transmit a registration request message to the AMF (111).

[0097] At this time, the information transmitted in the registration request message, i.e., the information element, may include an indication of a slice change or an indication of a state change of the terminal (101). The role of this indication is to notify the network to support an update of the state or slice information of the terminal (101), so that the network can update the state of the terminal (101) when a situation such as when the terminal (101) is roaming occurs.

[0098] Or, if this information is available and a slice-related policy update of the terminal (101) is required, the network can transmit slice-related policy update information or slice-related configuration update information to the UE (101).

[0099] At step 303, AMF (111) can send a registration accept message to UE (101).

[0100] At this time, the information transmitted in the registration accept message, i.e., the information element, may include at least one of slice information, information about candidate PLMNs providing the slice, and information about access technology supported by the PLMN. For example, if there is slice #1 providing application #1, PLMNs that can provide slice #1 may be PLMN #1 and PLMN #2. In this case, the registration accept message may include information such as information about the slice #1, information about PLMN #1 and PLMN #2 that can provide slice #1, and may be transmitted to the UE (101). For example, if there is slice #2 providing application #2, PLMNs that can provide slice #2 may be PLMN #2 and PLMN #3. In this case, the registration accept message may include information such as information about the slice #2, information about PLMN #2 and PLMN #3 that can provide slice #2, and may be transmitted to the UE (101). Meanwhile, information on access technology that can provide the service may also be included in the registration accept message or transmitted to the UE (101) as separate information.

[0101] In steps 311 and 313, PCF (161) can transmit policy information to UE (101) via AMF (111).

[0102] At this time, the information included in the policy information transmitted, i.e., the information element, may include at least one of slice information, information about candidate PLMNs providing the slice, information about access technology supported by the PLMN, priority information, etc. For example, when there is slice #1 providing application #1, PLMNs that can provide slice #1 may be PLMN #1 and PLMN #2. In this case, the policy information may include information such as information about the slice #1, information about PLMN #1 and PLMN #2 that can provide slice #1, and may be transmitted to the terminal (101). For example, when there is slice #2 providing application #2, PLMNs that can provide slice #2 may be PLMN #2 and PLMN #3. In this case, the policy information may include information such as information about the slice #2, information about PLMN #2 and PLMN #3 that can provide slice #2, and may be transmitted to the terminal (101). Meanwhile, information on access technology capable of providing the service and / or priority information may also be included in the policy information or transmitted to the UE (101) as separate information.

[0103] At step 321, the UE (101) can select a slice.

[0104] UE (101) can select a slice that provides a service of an application supported by UE (101).

[0105] At step 323, the UE (101) can set the priority of the slice.

[0106] When there are multiple slices providing applications, UE (101) can set the priority of the slices.

[0107] At step 325, the UE (101) can select a PLMN by considering the priority of the slice.

[0108] The UE (101) can select a PLMN by referring to the priority between slices set in step 323 above.

[0109] Meanwhile, depending on the information transmitted to the UE (101) from the network (AMF (111) or PCF (161) etc.) and received by the UE (101), the method by which the UE (101) selects the PLMN in step 325 may be different.

[0110] Case 1) When slice information and candidate PLMN information are transmitted to the UE (101).

[0111] Information transmitted from the network to the UE (101), i.e., information elements, may include slice information, information about candidate PLMNs providing the slice, and information about access technology supported by the PLMN. For example, if there is slice #1 providing application #1, information such as information about slice #1 and information indicating that PLMNs capable of providing slice #1 are PLMN #1 and PLMN #2 may be transmitted to the UE (101). For example, if there is slice #2 providing application #2, information such as information about slice #2 and information indicating that PLMNs capable of providing slice #2 are PLMN #2 and PLMN #3 may be transmitted to the UE (101). Meanwhile, information about access technology capable of providing the corresponding service may also be transmitted to the UE (101).

[0112] In this case, the UE (101) that received case 1 can select PLMNs that provide slices that provide applications that the UE (101) wants to receive by assigning weights or priorities to PLMNs that provide slices.

[0113] For example, if PLMNs that can provide slice #1 are PLMN #1 and PLMN #2, and PLMNs that can provide slice #2 are PLMN #2 and PLMN #3, then PLMN #2 can have a higher priority than other PLMNs because it provides slice #1 and slice #2.

[0114] Or as another example,

[0115] Case 2) When information on candidate slices provided for PLMNs is transmitted to the UE (101).

[0116] The information element transmitted from the network to the UE (101) may include PLMN information, information about slices provided by the PLMN, and information about access technologies supported by the PLMN. For example, when there is PLMN #1, information about PLMN #1 and information indicating that the slices provided by PLMN #1 are slice #1 and slice #2, etc., may be transmitted to the UE (101). In addition, information about the access technology provided by PLMN #1 may also be transmitted to the UE (101). In addition, for example, slice #1 may support both application #1 and application #2.

[0117] In this case, the UE (101) that received case 2 can select a PLMN that has a lot of information about the slices that the UE (101) is trying to select.

[0118] For example, if the slices provided by PLMN #3 are slice #1, slice #2, and slice #3, which are more than the slices provided by PLMN #1 (slice #1, slice #2), PLMN #3 may have a higher priority than PLMN #1.

[0119] Case 3)

[0120] Or, 1) priority or weight is received by the UE (101) for each slice or PLMN, and 2) if there is a slice with a high priority among the requested slices, the UE (101) can select the PLMN providing the slice with the highest priority.

[0121] For example, if slice #1 has a higher weight than other slices #2 and #3, the PLMNs providing slice #1 (e.g., PLMN #1) may have a higher priority than the other PLMNs.

[0122] That is, if application #1 or user or the terminal user must use slice #1 with the highest priority, the PLMN that provides slice #1, which corresponds to a case where the slice has a high priority, may have a higher priority than other PLMNs.

[0123] In the embodiment related to FIGS. 3A and 3B, the UE (101) may receive at least one of information about candidate PLMNs per slice, for example, slice information, information about candidate PLMNs providing the slice, information about access technology supported by the PLMN, priority information, etc., at step 303 or step 313. Accordingly, similar to case 1, the UE (101) may select slices that provide applications to be provided by assigning weights or priorities to PLMNs that provide them in duplicate. Alternatively, according to case 3, if there is a slice with a high priority among the requested slices, the UE (101) may select the PLMN providing the slice with the highest priority.

[0124] At step 331, the UE (101) can transmit a registration request message to the AMF (111-2) of the VPLMN.

[0125] At step 333, AMF (111-2) can send a registration accept message to UE (101).

[0126] At step 335, the UE (101) can communicate with a network corresponding to the VPLMN (base station (103-02), AMF (111-2), SMF (121-2), UPF (131-2), PCF (161-2), etc.).

[0127] At step 337, the PCF (161) can transmit policy information to the UE (101). According to an embodiment, the PCF (161) belonging to the HPLMN can transmit the policy information to the UE (101) through the PCF (161-2) belonging to the VPLMN and through the AMF (111-2) belonging to the VPLMN.

[0128] At this time, the information element included in the policy information transmitted may include at least one of slice information, information about candidate PLMNs providing the slice, information about access technology supported by the PLMN, priority information, etc. For example, if there is slice #1 providing application #1, PLMNs that can provide slice #1 may be PLMN #1 and PLMN #2. In this case, the policy information may include information such as information about the slice #1, information about PLMN #1 and PLMN #2 that can provide slice #1, and may be transmitted to the terminal (101). For example, if there is slice #2 providing application #2, PLMNs that can provide slice #2 may be PLMN #2 and PLMN #3. In this case, the policy information may include information such as information about the slice #2, information about PLMN #2 and PLMN #3 that can provide slice #2, and may be transmitted to the terminal (101). Meanwhile, information on access technology capable of providing the service and / or priority information may also be included in the policy information or transmitted to the UE (101) as separate information.

[0129] At step 381, the UE (101) can transmit a registration request message to the AMF (111-3) through the base station (103-03) corresponding to the VPLMN (VPLMN).

[0130] At step 383, the UE (101) can receive a registration accept message from the AMF (111-3) of the VPLMN (via the base station (103-03)).

[0131] FIGS. 4A and 4B are flowcharts illustrating an embodiment for enabling network slice support and communication in a 5G network according to an embodiment of the present disclosure.

[0132] The embodiments illustrated in FIGS. 4A and 4B are examples of registration acceptance. Furthermore, the embodiments illustrated in FIGS. 4A and 4B are examples of candidate slices per PLMN.

[0133] At step 401, the UE (101) can transmit a registration request message to the AMF (111).

[0134] At this time, the information element transmitted and included in the registration request message may include an indication of a slice change or an indication of a state change of the terminal (101). The role of this indication is to notify the network to support an update of the state or slice information of the terminal (101), so that the network can update the state of the terminal (101) when a situation such as when the terminal (101) is roaming occurs.

[0135] Or, if this information is available and a slice-related policy update of the terminal (101) is required, the network can transmit slice-related policy update information or slice-related configuration update information to the UE (101).

[0136] At step 403, AMF (111) can send a registration accept message to UE (101).

[0137] At this time, the information transmitted in the registration accept message, i.e., the information element, may include at least one of PLMN information, information on (candidate) slices provided by the PLMN, and information on access technology supported by the PLMN. For example, if there is PLMN #1, slices provided by PLMN #1 may be slice #1 and slice #2. In this case, the registration accept message may include information on PLMN #1, and information on slice #1 and slice #2 provided by PLMN #1, and may be transmitted to the terminal (101). In addition, the access technology information provided by PLMN #1 may also be included in the registration accept message or transmitted to the UE (101) as separate information. In addition, for example, slice #1 may support both application #1 and application #2.

[0138] In steps 411 and 413, PCF (161) can transmit policy information to UE (101) via AMF (111).

[0139] At this time, the information element transmitted and included in the policy information may include at least one of PLMN information, information on slices provided by the PLMN, information on access technology supported by the PLMN, priority information, etc. For example, when there is PLMN #1, slices provided by PLMN #1 may be slice #1 and slice #2. In this case, the policy information may include information on PLMN #1, and information on slice #1 and slice #2 provided by PLMN #1, and may be transmitted to UE (101). In addition, access technology information and / or priority information provided by PLMN #1 may also be included in the policy information or transmitted to UE (101) as separate information. In addition, for example, slice #1 may support both application #1 and application #2.

[0140] At step 421, the UE (101) can select a slice.

[0141] UE (101) can select a slice that provides a service of an application supported by UE (101).

[0142] At step 423, the UE (101) can set the priority of the slice.

[0143] When there are multiple slices providing applications, UE (101) can set the priority of the slices.

[0144] At step 425, the UE (101) can select a PLMN by considering the priority of the slice.

[0145] The UE (101) can select a PLMN by referring to the priority between slices set in step 423 above.

[0146] Depending on the information transmitted to the UE (101) from the network (AMF (111) or PCF (161) etc.) and received by the UE (101), the method by which the UE (101) selects the PLMN in step 325 may vary.

[0147] Case 1) When slice information and candidate PLMN information are transmitted to the UE (101).

[0148] Information transmitted from the network to the UE (101), i.e., information elements, may include slice information, information about candidate PLMNs providing the slice, and information about access technology supported by the PLMN. For example, if there is slice #1 providing application #1, information about slice #1 and information indicating that PLMNs capable of providing slice #1 are PLMN #1 and PLMN #2, etc. may be transmitted to the UE (101). For example, if there is slice #2 providing application #2, information about slice #2 and information indicating that PLMNs capable of providing slice #2 are PLMN #2 and PLMN #3, etc. may be transmitted to the UE (101). Meanwhile, information about access technology capable of providing the corresponding service may also be transmitted to the UE (101).

[0149] In this case, the UE (101) that received case 1 can select PLMNs that provide slices that provide applications that the UE (101) wants to receive by assigning weights or priorities to PLMNs that provide slices.

[0150] For example, if the PLMNs that can provide slice #1 are PLMN #1 and PLMN #2, and the PLMNs that can provide slice #2 are PLMN #2 and PLMN #3, then PLMN #2 can have a higher priority than the other PLMNs because it provides slice #1 and slice #2.

[0151] Or as another example,

[0152] Case 2) When information on candidate slices provided for PLMNs is transmitted to the UE (101).

[0153] The information element transmitted from the network to the UE (101) may include PLMN information, information about slices provided by the PLMN, and information about access technologies supported by the PLMN. For example, when there is PLMN #1, information about PLMN #1 and information indicating that the slices provided by PLMN #1 are slice #1 and slice #2, etc., may be transmitted to the UE (101). In addition, information about the access technology provided by PLMN #1 may also be transmitted to the UE (101). In addition, for example, slice #1 may support both application #1 and application #2.

[0154] In this case, the UE (101) that received case 2 can select a PLMN that has a lot of information about the slices that the UE (101) is trying to select.

[0155] For example, if the slices provided by PLMN #3 are slice #1, slice #2, and slice #3, which are more than the slices provided by PLMN #1 (slice #1, slice #2), PLMN #3 may have a higher priority than PLMN #1.

[0156] Case 3)

[0157] Or, 1) priority or weight is received by the UE (101) for each slice or PLMN, and 2) if there is a slice with a high priority among the requested slices, the UE (101) can select the PLMN providing the slice with the highest priority.

[0158] For example, if slice #1 has a higher weight than other slices #2 and #3, the PLMNs providing slice #1 (e.g., PLMN #1) may have a higher priority than the other PLMNs.

[0159] That is, if application #1 or user or the terminal user must use slice #1 with the highest priority, the PLMN that provides slice #1, which corresponds to a case where the slice has a high priority, may have a higher priority than other PLMNs.

[0160] In the embodiment related to FIGS. 4A and 4B, the UE (101) may receive at least one of information about candidate slices per PLMN, for example, PLMN information, information about slices provided by the PLMN, information about access technology supported by the PLMN, priority information, etc., at step 403 or step 413. Accordingly, similar to case 2, the UE (101) may select a PLMN having a large amount of information about slices to be selected. Alternatively, according to case 3, if there is a slice with a high priority among the requested slices, the UE (101) may select the PLMN providing the slice with the highest priority.

[0161] At step 431, the UE (101) can transmit a registration request message to the AMF (111-2) of the VPLMN.

[0162] At step 433, AMF (111-2) can send a registration accept message to UE (101).

[0163] At step 435, the UE (101) can communicate with a network corresponding to the VPLMN (base station (103-02), AMF (111-2), SMF (121-2), UPF (131-2), PCF (161-2), etc.).

[0164] At step 437, the PCF (161) can transmit policy information to the UE (101). According to an embodiment, the PCF (161) belonging to the HPLMN can transmit the policy information to the UE (101) through the PCF (161-2) belonging to the VPLMN and through the AMF (111-2) belonging to the VPLMN.

[0165] At this time, the information element included in the policy information transmitted may include at least one of PLMN information, information on slices provided by the PLMN, information on access technology supported by the PLMN, priority information, etc. For example, if there is PLMN #1, the slices provided by PLMN #1 may be slice #1 and slice #2. In this case, the policy information may include information on PLMN #1, and information on slice #1 and slice #2 provided by PLMN #1, and may be transmitted to the UE (101). In addition, access technology information and / or priority information provided by the PLMN #1 may also be included in the policy information or transmitted to the UE (101) as separate information. In addition, for example, slice #1 may support both application #1 and application #2.

[0166] At step 481, the UE (101) can transmit a registration request message to the AMF (111-3) through the base station (103-03) corresponding to the VPLMN (VPLMN).

[0167] At step 483, the UE (101) can receive a registration accept message from the AMF (111-3) of the VPLMN (via the base station (103-03)).

[0168] FIG. 5A and FIG. 5B are flowcharts illustrating an embodiment for enabling network slice support and communication in a 5G network according to an embodiment of the present disclosure.

[0169] The embodiments illustrated in FIGS. 5a and 5b are examples of configuration commands.

[0170] Referring to FIGS. 5a and 5b, at step 501, the UE (101) can transmit a registration request message to the AMF (111).

[0171] At this time, the information element transmitted and included in the registration request message may include an indication of a slice change or an indication of a state change of the terminal (101). The role of this indication is to notify the network to support an update of the state or slice information of the terminal (101), so that the network can update the state of the terminal (101) when a situation occurs, such as when the terminal (101) is roaming.

[0172] Or, if this information is available and a slice-related policy update of the terminal (101) is required, the network can transmit slice-related policy update information or slice-related configuration update information to the UE (101).

[0173] At step 503, AMF (111) can send a registration accept message to UE (101).

[0174] At this time, the information transmitted in the registration accept message, i.e., the information element, may include at least one of slice information, information about candidate PLMNs providing the slice, and information about access technology supported by the PLMN. For example, if there is slice #1 providing application #1, PLMNs that can provide slice #1 may be PLMN #1 and PLMN #2. In this case, the registration accept message may include information such as information about the slice #1, information about PLMN #1 and PLMN #2 that can provide slice #1, and may be transmitted to the UE (101). For example, if there is slice #2 providing application #2, PLMNs that can provide slice #2 may be PLMN #2 and PLMN #3. In this case, the registration accept message may include information such as information about the slice #2, information about PLMN #2 and PLMN #3 that can provide slice #2, and may be transmitted to the UE (101). Meanwhile, information on access technology that can provide the service may also be included in the registration accept message or transmitted to the UE (101) as separate information.

[0175] Or in another embodiment, the information transmitted in the registration accept message, i.e., the information element, may include at least one of PLMN information, information on slices provided by the PLMN, and information on access technology supported by the PLMN. For example, when there is PLMN #1, the slices provided by PLMN #1 may be slice #1 and slice #2. In this case, the registration accept message may include information on PLMN #1, and information on slice #1 and slice #2 provided by PLMN #1, and may be transmitted to the UE (101). In addition, the access technology information provided by PLMN #1 may also be included in the registration accept message or transmitted to the UE (101) as separate information. In addition, for example, slice #1 may support both application #1 and application #2.

[0176] At step 511, the UDM (151) can transmit candidate slices and priority related information per PLMN to the AMF (111) (via an update message).

[0177] At step 513, AMF (111) can transmit information received from UDM (151) to UE (101) through a configuration update command message.

[0178] At this time, the information element transmitted by the UDM (151) to the AMF (111) or the information element included in the configuration update command message transmitted by the AMF (111) to the UE (101) may include at least one line of slice information, information on candidate PLMNs providing the slice, information on access technology supported by the PLMN, priority information, etc. For example, when there is slice #1 providing application #1, the PLMNs that can provide slice #1 may be PLMN #1 and PLMN #2. In this case, the information element may be transmitted including information on the slice #1, and information on PLMN #1 and PLMN #2 that can provide the slice #1. For example, when there is slice #2 providing application #2, the PLMNs that can provide slice #2 may be PLMN #2 and PLMN #3. In this case, the information element may be transmitted including information about the slice #1 and information about PLMN #1 and PLMN #2 that can provide the slice #1. Meanwhile, information about the access technology that can provide the service and / or priority information may also be transmitted.

[0179] Or as another example,

[0180] At this time, the information element transmitted by the UDM (151) to the AMF (111) or the information element included in the configuration update command message transmitted by the AMF (111) to the UE (101) may include at least one line of PLMN information, information on slices provided by the PLMN, information on access technology supported by the PLMN, priority information, etc. For example, when there is PLMN #1, the slices provided by PLMN #1 may be slice #1 and slice #2. In this case, the information element may include and transmit information such as information on the slice #1 and information on PLMN #1 and PLMN #2 that can provide the slice #1. In addition, access technology information and / or priority information provided by the PLMN #1 may also be transmitted together. In addition, for example, slice #1 may support both application #1 and application #2.

[0181] At step 521, the UE (101) can select a slice.

[0182] UE (101) can select a slice that provides a service of an application supported by UE (101).

[0183] At step 523, the UE (101) can set the priority of the slice.

[0184] When there are multiple slices providing applications, UE (101) can set the priority of the slices.

[0185] At step 525, the UE (101) can select a PLMN by considering the priority of the slice.

[0186] The UE (101) can select a PLMN by referring to the priority between slices set in step 523 above.

[0187] The method by which the UE (101) selects a PLMN in step 525 may vary depending on the information transmitted to the UE (101) from the network (AMF (111) or UDM (151) etc.) and received by the UE (101).

[0188] Case 1) When slice information and candidate PLMN information are transmitted to the UE (101).

[0189] The information element transmitted from the network to the UE (101) may include slice information, information about candidate PLMNs providing the slice, and information about access technology supported by the PLMN. For example, if there is slice #1 providing application #1, information such as information about slice #1 and information indicating that PLMNs capable of providing slice #1 are PLMN #1 and PLMN #2 may be transmitted to the UE (101). For example, if there is slice #2 providing application #2, information such as information about slice #2 and information indicating that PLMNs capable of providing slice #2 are PLMN #2 and PLMN #3 may be transmitted to the UE (101). Meanwhile, information about access technology capable of providing the corresponding service may also be transmitted to the UE (101).

[0190] In this case, the UE (101) that received case 1 can select PLMNs that provide slices that provide applications that the UE (101) wants to receive by assigning weights or priorities to PLMNs that provide slices.

[0191] For example, if PLMNs that can provide slice #1 are PLMN #1 and PLMN #2, and PLMNs that can provide slice #2 are PLMN #2 and PLMN #3, then PLMN #2 can have a higher priority than other PLMNs because it provides slice #1 and slice #2.

[0192] Or as another example,

[0193] Case 2) When information on candidate slices provided for PLMNs is transmitted to the UE (101).

[0194] The information element transmitted from the network to the UE (101) may include PLMN information, information about slices provided by the PLMN, and information about access technologies supported by the PLMN. For example, when there is PLMN #1, information about PLMN #1 and information indicating that the slices provided by PLMN #1 are slice #1 and slice #2, etc., may be transmitted to the UE (101). In addition, information about the access technology provided by PLMN #1 may also be transmitted to the UE (101). In addition, for example, slice #1 may support both application #1 and application #2.

[0195] In this case, the UE (101) that received case 2 can select a PLMN that has a lot of information about the slices that the UE (101) is trying to select.

[0196] For example, if the slices provided by PLMN #3 are slice #1, slice #2, and slice #3, which are more than the slices provided by PLMN #1 (slice #1, slice #2), PLMN #3 may have a higher priority than PLMN #1.

[0197] Case 3)

[0198] Or, 1) priority or weight is received by the UE (101) for each slice or PLMN, and 2) if there is a slice with a high priority among the requested slices, the UE (101) can select the PLMN providing the slice with the highest priority.

[0199] For example, if slice #1 has a higher weight than other slices #2 and #3, the PLMNs providing slice #1 (e.g., PLMN #1) may have a higher priority than the other PLMNs.

[0200] That is, if application #1 or user or the terminal user must use slice #1 with the highest priority, the PLMN that provides slice #1, which corresponds to a case where the slice has a high priority, may have a higher priority than other PLMNs.

[0201] At step 531, the UE (101) can transmit a registration request message to the AMF (111-2) of the VPLMN.

[0202] At step 533, AMF (111-2) can send a registration accept message to UE (101).

[0203] At step 535, the UE (101) can communicate with a network corresponding to the VPLMN (base station (103-02), AMF (111-2), SMF (121-2), UPF (131-2), PCF (161-2), etc.).

[0204] In step 537, the UDM (151) and the AMF (111) can update the PLMN, slices, and priority-related information for selecting a slice of the UE (101) through a configuration update command. That is, in step 537-1, the UDM (151) can send a message to the AMF (111), in step 537-3, the AMF (111) (of the HPLMN) can send a message to the AMF (111-2) (of the VPLMN), and in step 537-5, the AMF (111-2) (of the VPLMN) can send a message to the UE (101) for updating the PLMN, slices, and priority-related information for selecting a slice of the UE (101).

[0205] At this time, the information element transmitted may include at least one of slice information, information about candidate PLMNs providing the slice, information about access technology supported by the PLMN, and priority information. For example, if there is slice #1 providing application #1, PLMNs that can provide slice #1 may be PLMN #1 and PLMN #2. In this case, the information element may be transmitted including information about the slice #1, information about PLMN #1 and PLMN #2 that can provide the slice #1, and the like. For example, if there is slice #2 providing application #2, PLMNs that can provide slice #2 may be PLMN #2 and PLMN #3. In this case, the information element may be transmitted including information about the slice #2, information about PLMN #2 and PLMN #3 that can provide the slice #2, and the like. Meanwhile, information about the access technology that can provide the corresponding service and / or priority information may also be transmitted including information about the information element.

[0206] Or in another embodiment, the information element transmitted at this time may include at least one of PLMN information, information about slices provided by the PLMN, information about access technology supported by the PLMN, priority information, etc. For example, if there is PLMN #1, the slices provided by PLMN #1 may be slice #1 and slice #2. In this case, the information element may include and be transmitted information about PLMN #1, and information about slice #1 and slice #2 provided by PLMN #1. In addition, access technology information and / or priority information provided by PLMN #1 may also be included in the information element and be transmitted. In addition, for example, slice #1 may support both application #1 and application #2.

[0207] At step 581, the UE (101) can transmit a registration request message to the AMF (111-3) through the base station (103-03) corresponding to the VPLMN (VPLMN).

[0208] At step 583, the UE (101) can receive a registration accept message from the AMF (111-3) through the base station (103-03) corresponding to the VPLMN (VPLMN).

[0209] FIG. 6A and FIG. 6B are flowcharts illustrating an embodiment for enabling network slice support and communication in a 5G network according to an embodiment of the present disclosure.

[0210] The embodiments illustrated in FIGS. 6A and 6B are examples of registration rejects.

[0211] Referring to FIGS. 6a and 6b, at step 601, the UE (101) can transmit a registration request message to the AMF (111).

[0212] At this time, the information element transmitted and included in the registration request message may include an indication of a slice change or an indication of a state change of the terminal (101). The role of this indication is to notify the network to support an update of the state or slice information of the terminal (101), so that the network can update the state of the terminal (101) when a situation occurs, such as when the terminal (101) is roaming.

[0213] Or, if this information is available and a slice-related policy update of the terminal (101) is required, the network can transmit slice-related policy update information or slice-related configuration update information to the UE (101).

[0214] At step 603, AMF (111) can send a registration accept message to UE (101).

[0215] At this time, the information element transmitted in the registration accept message may include at least one of slice information, information about candidate PLMNs providing the slice, and information about access technology supported by the PLMN. For example, if there is slice #1 providing application #1, PLMNs that can provide slice #1 may be PLMN #1 and PLMN #2. In this case, the registration accept message may include information such as information about the slice #1, information about PLMN #1 and PLMN #2 that can provide slice #1, and may be transmitted to the UE (101). For example, if there is slice #2 providing application #2, PLMNs that can provide slice #2 may be PLMN #2 and PLMN #3. In this case, the registration accept message may include information such as information about the slice #2, information about PLMN #2 and PLMN #3 that can provide slice #2, and may be transmitted to the UE (101). Meanwhile, information on access technology that can provide the service may also be included in the registration accept message or transmitted to the UE (101) as separate information.

[0216] Or, as another embodiment, the information element transmitted in the registration accept message may include at least one of PLMN information, information on slices provided by the PLMN, and information on access technology supported by the PLMN. For example, when there is PLMN #1, slices provided by PLMN #1 may be slice #1 and slice #2. In this case, the registration accept message may include information on PLMN #1, and information on slice #1 and slice #2 provided by PLMN #1, and may be transmitted to the UE (101). In addition, information on the access technology provided by PLMN #1 may also be included in the registration accept message or transmitted to the UE (101) as separate information. In addition, for example, slice #1 may support both application #1 and application #2.

[0217] In steps 611 and 613, PCF (161) can transmit policy information to UE (101) via AMF (111).

[0218] At this time, the information element included in the policy information transmitted may include at least one of slice information, information on candidate PLMNs providing the slice, information on access technology supported by the PLMN, priority information, etc. For example, when there is slice #1 providing application #1, PLMNs that can provide slice #1 may be PLMN #1 and PLMN #2. In this case, the policy information may include information such as information on the slice #1, information on PLMN #1 and PLMN #2 that can provide slice #1, and may be transmitted to the terminal (101). For example, when there is slice #2 providing application #2, PLMNs that can provide slice #2 may be PLMN #2 and PLMN #3. In this case, the policy information may include information such as information on the slice #2, information on PLMN #2 and PLMN #3 that can provide slice #2, and may be transmitted to the terminal (101). Meanwhile, information on access technology capable of providing the service and / or priority information may also be included in the policy information or transmitted to the UE (101) as separate information.

[0219] Or in another embodiment, the information element transmitted by being included in the policy information may include at least one of PLMN information, information on slices provided by the PLMN, information on access technology supported by the PLMN, priority information, etc. For example, when there is PLMN #1, slices provided by PLMN #1 may be slice #1 and slice #2. In this case, the policy information may include information on PLMN #1, and information on slice #1 and slice #2 provided by PLMN #1, and may be transmitted to the UE (101). In addition, access technology information and / or priority information provided by PLMN #1 may also be included in the policy information or transmitted to the UE (101) as separate information. In addition, for example, slice #1 may support both application #1 and application #2.

[0220] In step 621, the UE (101) can select a PLMN. In selecting this PLMN, the UE (101) can select a PLMN that supports roaming of the UE (101) by considering the PLMN and access technology.

[0221] At step 631, the UE (101) can transmit a registration request message to the AMF (111-2) of the VPLMN.

[0222] At step 633, the AMF (111-2) may transmit a registration reject message to the UE (101). At this time, the registration reject message transmitted to the UE (101) may include information indicating that the corresponding slice is not serviced in relation to the application in the corresponding PLMN, for example, a not allowed slice cause number (information).

[0223] In addition, the information element transmitted in the registration reject message may include at least one of slice information, information about candidate PLMNs providing the slice, and information about access technology supported by the PLMN. For example, if there is slice #1 providing application #1, PLMNs that can provide slice #1 may be PLMN #1 and PLMN #2. In this case, the registration reject message may include information such as information about the slice #1, information about PLMN #1 and PLMN #2 that can provide slice #1, and may be transmitted to the UE (101). For example, if there is slice #2 providing application #2, PLMNs that can provide slice #2 may be PLMN #2 and PLMN #3. In this case, the registration reject message may include information such as information about the slice #2, information about PLMN #2 and PLMN #3 that can provide slice #2, and may be transmitted to the UE (101). Meanwhile, information on access technology that can provide the service may also be included in the registration reject message or transmitted to the UE (101) as separate information.

[0224] Or as another embodiment, the information element transmitted in the registration reject message may include at least one of PLMN information, information about slices provided by the PLMN, and information about access technology supported by the PLMN. For example, if there is PLMN #1, slices provided by PLMN #1 may be slice #1 and slice #2. In this case, the registration reject message may include and be transmitted information about PLMN #1, slice #1 and slice #2 provided by PLMN #1. In addition, information about the access technology provided by PLMN #1 may also be included in the registration reject message or transmitted to the UE (101) as separate information. In addition, for example, slice #1 may support both application #1 and application #2.

[0225] At step 635, the UE (101) can communicate with the network.

[0226] At step 637, the PCF (161) can transmit policy information to the UE (101). According to an embodiment, the PCF (161) belonging to the HPLMN can transmit the policy information to the UE (101) through the PCF (161-2) belonging to the VPLMN and through the AMF (111-2) belonging to the VPLMN.

[0227] At this time, the information element included in the policy information transmitted may include at least one of slice information, information about candidate PLMNs providing the slice, information about access technology supported by the PLMN, priority information, etc. For example, when there is slice #1 providing application #1, PLMNs that can provide slice #1 may be PLMN #1 and PLMN #2. In this case, the policy information may include information about the slice #1, information about PLMN #1 and PLMN #2 that can provide slice #1, etc., and may be transmitted to the terminal (101). For example, when there is slice #2 providing application #2, PLMNs that can provide slice #2 may be PLMN #2 and PLMN #3. In this case, the policy information may include information about the slice #2, information about PLMN #2 and PLMN #3 that can provide slice #2, etc., and may be transmitted to the terminal (101). Meanwhile, information on access technology capable of providing the service and / or priority information may also be included in the policy information or transmitted to the UE (101) as separate information.

[0228] Or in another embodiment, the information element included in the transmitted policy information may include at least one of PLMN information, information on slices provided by the PLMN, information on access technology supported by the PLMN, priority information, etc. For example, when there is PLMN #1, slices provided by PLMN #1 may be slice #1 and slice #2. In this case, the policy information may include information on PLMN #1, and information on slice #1 and slice #2 provided by PLMN #1, and may be transmitted to the UE (101). In addition, access technology information and / or priority information provided by PLMN #1 may also be included in the policy information or transmitted to the UE (101) as separate information. In addition, for example, slice #1 may support both application #1 and application #2.

[0229] At step 641, the UE (101) can select a slice.

[0230] UE (101) can select a slice that provides a service of an application supported by UE (101).

[0231] At step 643, the UE (101) can set the priority of the slice.

[0232] When there are multiple slices providing applications, UE (101) can set the priority of the slices.

[0233] At step 645, the UE (101) can select a PLMN by considering the priority of the slice.

[0234] The UE (101) can select a PLMN by referring to the priority between slices set in step 643 above.

[0235] Depending on the information transmitted to the UE (101) from the network (AMF (111) or PCF (161) etc.) and received by the UE (101), the method by which the UE (101) selects the PLMN in step 645 may vary.

[0236] Case 1) When slice information and candidate PLMN information are transmitted to the UE (101).

[0237] The information element transmitted from the network to the UE (101) may include slice information, information about candidate PLMNs providing the slice, and information about access technology supported by the PLMN. For example, if there is slice #1 providing application #1, information such as information about slice #1 and information indicating that PLMNs capable of providing slice #1 are PLMN #1 and PLMN #2 may be transmitted to the UE (101). For example, if there is slice #2 providing application #2, information such as information about slice #2 and information indicating that PLMNs capable of providing slice #2 are PLMN #2 and PLMN #3 may be transmitted to the UE (101). Meanwhile, information about access technology capable of providing the corresponding service may also be transmitted to the UE (101).

[0238] In this case, the UE (101) that received case 1 can select PLMNs that provide slices that provide applications that the UE (101) wants to receive by assigning weights or priorities to PLMNs that provide slices.

[0239] For example, if PLMNs that can provide slice #1 are PLMN #1 and PLMN #2, and PLMNs that can provide slice #2 are PLMN #2 and PLMN #3, then PLMN #2 can have a higher priority than other PLMNs because it provides slice #1 and slice #2.

[0240] Or as another example,

[0241] Case 2) When information on candidate slices provided for PLMNs is transmitted to the UE (101).

[0242] The information element transmitted from the network to the UE (101) may include PLMN information, information about slices provided by the PLMN, and information about access technologies supported by the PLMN. For example, when there is PLMN #1, information about PLMN #1 and information indicating that the slices provided by PLMN #1 are slice #1 and slice #2, etc., may be transmitted to the UE (101). In addition, information about the access technology provided by PLMN #1 may also be transmitted to the UE (101). In addition, for example, slice #1 may support both application #1 and application #2.

[0243] In this case, the UE (101) that received case 2 can select a PLMN that has a lot of information about the slices that the UE (101) is trying to select.

[0244] For example, if the slices provided by PLMN #3 are slice #1, slice #2, and slice #3, which are more than the slices provided by PLMN #1 (slice #1, slice #2), PLMN #3 may have a higher priority than PLMN #1.

[0245] Case 3)

[0246] Or, 1) priority or weight is received by the UE (101) for each slice or PLMN, and 2) if there is a slice with a high priority among the requested slices, the UE (101) can select the PLMN providing the slice with the highest priority.

[0247] For example, if slice #1 has a higher weight than other slices #2 and #3, the PLMNs providing slice #1 (e.g., PLMN #1) may have a higher priority than the other PLMNs.

[0248] That is, if application #1 or user or the terminal user must use slice #1 with the highest priority, the PLMN that provides slice #1, which corresponds to a case where the slice has a high priority, may have a higher priority than other PLMNs.

[0249] At step 681, the UE (101) can transmit a registration request message to the AMF (111-3) through the base station (103-03) corresponding to the VPLMN (VPLMN).

[0250] At step 683, the UE (101) can receive a registration accept message from the VPLMN.

[0251] FIG. 7 is a diagram showing the configuration of a terminal according to an embodiment of the present disclosure.

[0252] Referring to FIG. 7, the terminal of the present disclosure may include a transceiver (710), a memory (720), and a control unit (processor) (730). The processor (730), transceiver (710), and memory (720) of the terminal may operate according to the communication method of the terminal described above. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the processor (730), transceiver (710), and memory (720) may be implemented in the form of a single chip.

[0253] The transceiver (710) is a general term for the terminal's receiver and transmitter, and can transmit and receive signals with a base station or network entity. The signals transmitted and received with the base station may include control information and data. To this end, the transceiver (710) may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-converts the received signal. However, this is only one embodiment of the transceiver (710), and the components of the transceiver (710) are not limited to the RF transmitter and RF receiver.

[0254] Additionally, the transceiver (710) may include a wired or wireless transceiver and may include various configurations for transmitting and receiving signals.

[0255] In addition, the transceiver (710) can receive a signal through a wireless channel and output it to the processor (730), and transmit the signal output from the processor (730) through the wireless channel.

[0256] In addition, the transceiver (710) can receive a communication signal and output it to the processor, and transmit the signal output from the processor to a network entity via a wired or wireless network.

[0257] The memory (720) can store programs and data necessary for the operation of the terminal. In addition, the memory (720) can store control information or data included in signals acquired from the terminal. The memory (720) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD.

[0258] The processor (730) can control a series of processes so that the terminal can operate according to the embodiments of the present disclosure described above. The processor (730) may include at least one processor. For example, the processor (730) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs.

[0259] FIG. 8 is a diagram illustrating a configuration of a network entity according to an embodiment of the present disclosure.

[0260] Referring to FIG. 8, a network entity of the present disclosure may include a transceiver (810), a memory (820), and a control unit (processor) (830). The processor (830), the transceiver (810), and the memory (820) of the network entity may operate according to the communication method of the network entity described above. However, the components of the network entity are not limited to the examples described above. For example, the network entity may include more or fewer components than the components described above. In addition, the processor (830), the transceiver (810), and the memory (820) may be implemented in the form of a single chip.

[0261] A network entity may include any of the network functions (NFs) described above, such as AMF, SMF, PCF, NEF (Network Exposure Function), UDM, and UPF. In addition, a network entity may also include a base station.

[0262] The transceiver (810) is a general term for the receiving unit and the transmitting unit of a network entity, and can transmit and receive signals with a terminal or other network entities. At this time, the transmitted and received signals may include control information and data. To this end, the transceiver (810) may be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-converts the received signal. However, this is only one embodiment of the transceiver (810), and the components of the transceiver (810) are not limited to the RF transmitter and RF receiver. The transceiver (810) may include wired and wireless transceivers, and may include various configurations for transmitting and receiving signals.

[0263] Additionally, the transceiver (810) can receive a signal through a communication channel (e.g., a wireless channel) and output the signal to the processor (830), and transmit the signal output from the processor (830) through the communication channel.

[0264] In addition, the transceiver (810) can receive a communication signal and output it to the processor, and transmit the signal output from the processor to a terminal or other network entity via a wired or wireless network.

[0265] The memory (820) can store programs and data necessary for the operation of the network entity. Furthermore, the memory (820) can store control information or data included in signals acquired from the network entity. The memory (820) can be configured as a storage medium, such as a ROM, a RAM, a hard disk, a CD-ROM, a DVD, or a combination of storage media.

[0266] The processor (830) may control a series of processes to enable a network entity to operate according to the embodiments of the present disclosure described above. The processor (830) may include at least one processor. The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

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

[0268] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc-ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in memories formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.

[0269] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), a 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 via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

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

[0271] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.

Claims

1. A method performed by a terminal of a wireless communication system, A step of transmitting a first message associated with a change of a slice to an access and mobility management function (AMF) of a home public land mobile network (HPLMN); Receiving a second message from the AMF of the HPLMN, the second message including information about at least one slice and information about at least one PLMN providing the at least one slice; A step of transmitting a registration request message to the AMF of the first PLMN; A step of receiving a registration rejection message from the AMF of the first PLMN, the AMF indicating that the slice requested by the terminal is not allowed in the first PLMN; A step of selecting a slice based on the above registration rejection message; a step of selecting a second PLMN providing the selected slice; and A method comprising the step of transmitting a registration request message to an AMF of the selected second PLMN.

2. In paragraph 1, A method, characterized in that the registration rejection message includes information about at least one slice and information about at least one PLMN associated with the at least one slice.

3. In the first paragraph, the step of selecting the slice comprises: A method further comprising the step of receiving a policy from a policy control function (PCF), the policy comprising information about at least one slice and information about at least one PLMN providing each of the at least one slice.

4. In paragraph 1, The second message further includes information regarding the priority of the at least one slice, A method characterized in that the slice is selected based on information regarding the priority of at least one slice.

5. In paragraph 1, A method characterized in that, when there are multiple PLMNs providing the selected slice, the second PLMN is selected by giving priority to a PLMN that provides slices that overlap with the applications that the terminal wishes to receive.

6. In paragraph 1, A method characterized in that, when there are multiple PLMNs providing the selected slice, the second PLMN is selected by giving priority to a PLMN providing a greater number of slices.

7. In paragraph 1, A method, characterized in that the second message includes information of at least one PLMN and information of at least one slice provided by the at least one PLMN.

8. In the terminal of a wireless communication system, Transmitter and receiver; and A terminal including a control unit which transmits a first message associated with a change of a slice to an AMF (access and mobility management function) of a home public land mobile network (HPLMN) through the transceiver, receives a second message including information on at least one slice and information on at least one PLMN providing the at least one slice from the AMF of the HPLMN through the transceiver, transmits a registration request message to the AMF of a first PLMN through the transceiver, receives a registration rejection message from the AMF of the first PLMN through the transceiver, indicating that the slice requested by the terminal in the first PLMN is not allowed, selects a slice based on the registration rejection message, selects a second PLMN providing the selected slice, and transmits a registration request message to the AMF of the selected second PLMN through the transceiver.

9. In paragraph 8, A terminal characterized in that the above registration rejection message includes information about at least one slice and information about at least one PLMN associated with the at least one slice.

10. In the 8th paragraph, the control unit, A terminal characterized in that the transceiver receives a policy from a policy control function (PCF) through the transceiver, the policy including information about at least one slice and information about at least one PLMN providing each of the at least one slice.

11. In paragraph 8, The second message further includes information regarding the priority of the at least one slice, A terminal characterized in that the slice is selected based on information regarding the priority of at least one slice.

12. In paragraph 8, A terminal characterized in that, when there are multiple PLMNs providing the selected slice, the second PLMN is selected by giving priority to a PLMN that provides slices that overlap with the applications that the terminal wishes to receive.

13. In paragraph 8, A terminal characterized in that, when there are multiple PLMNs providing the selected slice, the second PLMN is selected by giving priority to a PLMN providing a greater number of slices.

14. In paragraph 8, A terminal, characterized in that the second message includes information of at least one PLMN and information of at least one slice provided by the at least one PLMN.

Images