KR20230155933A - Method and apparatus for supporting priority of network slice in wireless communication system - Google Patents

Abstract

The present disclosure includes the steps of transmitting a registration request message to a base station; The registration request message includes network slice access stratum (AS) group (NSAG) support information, and the registration request message is delivered to an access and mobility management function (AMF) through a base station, and is transmitted to each network slice. Receiving a registration accept message including NSAG information related to priority from the base station through the AMF; The NSAG information includes a method to be performed by the terminal determined based on the NSAG support message.

Description

Method and apparatus for supporting priority of network slices in a wireless communication system {METHOD AND APPARATUS FOR SUPPORTING PRIORITY OF NETWORK SLICE IN WIRELESS COMMUNICATION SYSTEM}

This disclosure relates to a method and apparatus for supporting network slice groups and priorities in a wireless communication system.

5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and includes sub-6 GHz ('Sub 6GHz') bands such as 3.5 gigahertz (3.5 GHz) as well as millimeter wave (mm) bands such as 28 GHz and 39 GHz. It is also possible to implement it in the ultra-high frequency band ('Above 6GHz') called Wave. In addition, in the case of 6G mobile communication technology, which is called the system of Beyond 5G, Terra is working to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low delay time that is reduced to one-tenth. Implementation in Terahertz bands (e.g., 95 GHz to 3 THz) is being considered.

In the early days of 5G mobile communication technology, there were concerns about ultra-wideband services (enhanced Mobile BroadBand, eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). With the goal of satisfying service support and performance requirements, efficient use of ultra-high frequency resources, including beamforming and massive array multiple input/output (Massive MIMO) to alleviate radio wave path loss in ultra-high frequency bands and increase radio transmission distance. Various numerology support (multiple subcarrier interval operation, etc.) and dynamic operation of slot format, initial access technology to support multi-beam transmission and broadband, definition and operation of BWP (Band-Width Part), large capacity New channel coding methods such as LDPC (Low Density Parity Check) codes for data transmission and Polar Code for highly reliable transmission of control information, L2 pre-processing, and dedicated services specialized for specific services. Standardization of network slicing, etc., which provides networks, has been carried out.

Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology, considering the services that 5G mobile communication technology was intended to support, based on the vehicle's own location and status information. V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience, and NR-U (New Radio Unlicensed), which aims to operate a system that meets 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 the terrestrial network is impossible, positioning, etc. Physical layer standardization for technology is in progress.

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

When this 5G mobile communication system is commercialized, an explosive increase in connected devices will be connected to the communication network. Accordingly, it is expected that strengthening the functions and performance of the 5G mobile communication system and integrated operation of connected devices will be necessary. To this end, eXtended Reality (XR) and Artificial Intelligence are designed to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR). , AI) and machine learning (ML), new research will be conducted on 5G performance improvement and complexity reduction, AI service support, metaverse service support, and drone communication.

In addition, the development of these 5G mobile communication systems includes new waveforms, full dimensional MIMO (FD-MIMO), and array antennas to ensure coverage in the terahertz band of 6G mobile communication technology. , multi-antenna transmission technology such as Large Scale Antenna, metamaterial-based lens and antenna to improve coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum), RIS ( In addition to Reconfigurable Intelligent Surface technology, Full Duplex technology, satellite, and AI (Artificial Intelligence) to improve the frequency efficiency of 6G mobile communication technology and system network are utilized from the design stage and end-to-end. -to-End) Development of AI-based communication technology that realizes system optimization by internalizing AI support functions, and next-generation distributed computing technology that realizes services of complexity beyond the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could be the basis for .

As various services can be provided as described above and with the development of mobile communication systems, a method to effectively provide these services is required, and in particular, a method to provide a method for efficient integrated access and control of backhaul nodes is required. It is being demanded.

The disclosed embodiment seeks to provide an apparatus and method that can effectively provide services in a wireless communication system.

According to an embodiment of the present disclosure, a method performed by a terminal includes the steps of transmitting a registration request message to a base station; The registration request message includes network slice access stratum (AS) group (NSAG) support information, and the registration request message is delivered to an access and mobility management function (AMF) through a base station, and is transmitted to each network slice. Receiving a registration accept message including NSAG information related to priority from the base station through the AMF; The NSAG information may include a method determined based on the NSAG support message.

The disclosed embodiment provides an apparatus and method that can effectively provide services in a mobile communication system.

The effects that can be obtained from the present disclosure are not limited to the effects mentioned in the various embodiments, and other effects not mentioned will be clearly understood by those skilled in the art from the description below. It could be.

Figure 1 shows a method of providing network slice AS (access stratum) group (NSAG) information in a terminal registration procedure in a wireless communication system according to an embodiment of the present disclosure.
Figure 2 shows a method of determining slice priority or slice group priority through UDM in a terminal registration procedure in a wireless communication system according to an embodiment of the present disclosure.
Figure 3 is a block diagram showing the structure of a terminal according to an embodiment of the present disclosure.
Figure 4 is a block diagram showing the structure of a base station according to an embodiment of the present disclosure.
Figure 5 is a block diagram showing the structure of a network entity according to an embodiment of the present disclosure.

In the 3GPP 5G system, network slice group priority and mapping information between network slices and network slice groups are provided for slice-based cell reselection of the terminal. Meanwhile, when there are TAs using different mapping rules, in order for the UE to reselect a cell in the TAs using different mapping rules, the mapping information between network slices and network slice groups in the TAs using different mapping rules is required. must be provided separately. Meanwhile, since it is inefficient to provide mapping information between network slices and network slice groups for TAs that use different mapping rules, it is necessary to determine in what cases mapping information between network slices and network slice groups will be provided.

In addition, network slice priority must be determined by considering policy information about network slices for existing terminals, but there is currently no such method. Lastly, there is a need for home network operators to be able to control network slice priorities for cell reselection for each subscriber even in roaming situations.

This disclosure presents a method for solving the above problems.

Hereinafter, the operating principle of the present disclosure will be described in detail with reference to the attached drawings. In the following description of the present disclosure, if a detailed description of a related known function or configuration is determined to unnecessarily obscure the gist of the present disclosure, the detailed description will be omitted. In addition, the terms described below are terms defined in consideration of the functions in the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification.

For the same reason, some components are exaggerated, omitted, or schematically shown in the accompanying drawings. Additionally, the size of each component does not entirely reflect its actual size. In each drawing, identical or corresponding components are assigned the same reference numbers.

The advantages and features of the present disclosure and methods for achieving them will become clear by referring to the embodiments described in detail below along with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms, and the present embodiments are merely intended to ensure that the disclosure is complete and to provide common knowledge in the technical field to which the present disclosure pertains. It is provided to fully inform those who have the scope of the disclosure, and the disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout the specification.

At this time, it will be understood that each block of the processing flow diagrams and combinations of the flow diagram diagrams can be performed by computer program instructions. These computer program instructions can be mounted on a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment, so that the instructions performed through the processor of the computer or other programmable data processing equipment are described in the flow chart block(s). It creates the means to perform functions. These computer program instructions may also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular manner, so that the computer-usable or computer-readable memory It is also possible to produce manufactured items containing instruction means that perform the functions described in the flowchart block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a process that is executed by the computer, thereby generating a process that is executed by the computer or other programmable data processing equipment. Instructions that perform processing equipment may also provide steps for executing the functions described in the flow diagram block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). Additionally, it should be noted that in some alternative execution examples it is possible for the functions mentioned in the blocks to occur out of order. For example, it is possible for two blocks shown in succession to be performed substantially at the same time, or it is possible for the blocks to be performed in reverse order depending on their functions.

At this time, the term '~unit' used in this embodiment refers to software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and '~unit' refers to what roles. Perform. However, '~part' is not limited to software or hardware. The '~ part' may be configured to reside in an addressable storage medium and may be configured to reproduce on one or more processors. Therefore, as an example, '~ part' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, 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 may be further separated into additional components and 'parts'. Additionally, components and 'parts' may be implemented to regenerate one or more CPUs within a device or a secure multimedia card. Additionally, in an embodiment, '~ part' may include one or more processors.

In the following description of the present disclosure, if a detailed description of a related known function or configuration is determined to unnecessarily obscure the gist of the present disclosure, the detailed description will be omitted. Hereinafter, embodiments of the present disclosure will be described with reference to the attached drawings.

Terms used in the following description to identify a connection node, a term referring to network entities, a term referring to messages, a term referring to an interface between network objects, and a term referring to various types of identification information. The following are examples for convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meaning may be used.

Terms used in the present disclosure are merely used to describe specific embodiments and may not be intended to limit the scope of other embodiments. Singular expressions may include plural expressions, unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as generally understood by a person of ordinary skill in the technical field described in this disclosure. Among the terms used in this disclosure, terms defined in general dictionaries may be interpreted to have the same or similar meaning as the meaning they have in the context of related technology, and unless clearly defined in this disclosure, have an ideal or excessively formal meaning. It is not interpreted as In some cases, even terms defined in the present disclosure cannot be interpreted to exclude embodiments of the present disclosure.

In various embodiments of the present disclosure described below, a hardware approach method is explained as an example. However, since various embodiments of the present disclosure include technology using both hardware and software, the various embodiments of the present disclosure do not exclude software-based approaches.

For convenience, this disclosure uses terms and names defined in the LTE and NR standards, which are the most recent standards defined by the 3rd Generation Partnership Project (3GPP) organization among currently existing communication standards. However, the present disclosure is not limited by the above terms and names, and can be equally applied to systems complying with other standards. In particular, the present disclosure is applicable to 3GPP NR (5th generation mobile communication standard). Additionally, embodiments of the present disclosure can be applied to other communication systems with similar technical background or channel types. Additionally, the embodiments of the present disclosure may be applied to other communication systems through some modifications without significantly departing from the scope of the present disclosure at the discretion of a person with skilled technical knowledge.

In the following description, terms referring to signals, terms referring to channels, terms referring to control information, terms referring to network entities, terms referring to device components, etc. are used for convenience of explanation. This is exemplified. Accordingly, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meaning may be used.

In addition, the present disclosure describes various embodiments using terms used in some communication standards (eg, 3rd Generation Partnership Project (3GPP)), but this is only an example for explanation. Various embodiments of the present disclosure can be easily modified and applied to other communication systems.

The 5G mobile communication network consists of 5G UE (user equipment, terminal), 5G RAN (radio access network, base station, gNB (5g nodeB), eNB (evolved nodeB, etc.), and 5G core network. The 5G core network includes an access and mobility management function (AMF) that provides UE mobility management function, a session management function (SMF) that provides a session management function, a user plane function (UPF) that performs a data transmission role, and a policy control function. PCF (policy control function) that provides, UDM (unified data management) that provides data management functions such as subscriber data and policy control data, and UDR (unified data repository) that stores data of various network functions such as UDM. It consists of network functions such as:

In the 5G system, network slicing refers to a technology and structure that enables multiple virtualized, independent logical networks in one physical network. To satisfy the specialized requirements of services/applications, network operators provide services by configuring a virtual end-to-end network called a network slice. At this time, the network slice is identified by an identifier called S-NSSAI (single-network slice selection assistance information). The network transmits a set of slices (e.g. allowed NSSAI(s)) allowed to the UE in a UE registration procedure (e.g. UE registration procedure), and the UE transmits one S-NSSAI (i.e. network slice) of these. Application data is transmitted and received through a PDU (protocol data unit) session created through .

In the 5G system, a base station is responsible for one or more TAs (Tracking Area, a unit defined to track the location of a terminal in the 5G system), and different frequencies and network slices can be supported for each TA or cell within the TA. The base station can broadcast network slice information supported by each TA to the terminal, and the terminal can determine which network slice is supported by each TA based on the network slice information supported by each TA. At this time, the slice information for each TA and cell that the base station broadcasts may include identifier (i.e., Slice group id) information for the slice group to which the S-NSSAI for each slice is mapped instead of the S-NSSAI for each slice. The terminal can determine which slice groups are supported for each TA. For example, the terminal can identify slice groups supported by cells within the TA for each TA. In addition, the terminal can determine which S-NSSAIs are supported for each TA based on the mapping relationship information between the S-NSSAI and slice group id received from AMF through NAS (Non-Access Stratum). Additionally, according to an embodiment of the present disclosure, NAS may be a communication protocol between UE and AMF. Additionally, according to an embodiment of the present disclosure, the terminal can determine the S-NSSAIs supported by cells within the TA for each TA based on the mapping relationship information between the S-NSSAI and slice group ID.

During cell re-selection, which is a procedure for selecting a more suitable cell, the UE can make a decision based on the priority value for each S-NSSAI or slice group ID received from the NAS. Additionally, according to an embodiment of the present disclosure, the terminal can determine the cell based on slice-related information broadcast from the base station. For example, if a network operator wants to move a terminal to a cell where a specific slice is supported, high priority can be given to a slice or slice group related to a cell where a specific slice is supported.

5G base stations have mapping between slice group id and S-NSSAI set on a TA basis. Therefore, different mapping rules between slice group ID and S-NSSAI can be applied for each TA. For example, in different TAs, the same slice group id may be an identifier representing different S-NSSAI. The terminal may receive mapping relationship information between the S-NSSAI and slice group ID for some TAs (e.g., TAs belonging to the Registration Area (RA)) from the AMF through the NAS during the network registration procedure. At this time, if there are TAs that use different mapping rules for the slices for which mapping is to be provided, the different mapping relationship information in the TAs that use different mapping rules and the TAs that use different mapping rules are shared together. It can be transmitted including. If the terminal moves to a TA other than the RA received in the last network registration procedure, it can perform the network registration procedure again and receive mapping information between slice group ID and S-NSSAI for new TAs.

Meanwhile, in order to support cell re-selection even when the UE moves to a TA adjacent to an RA with different matching rules, the UE establishes a link between the slice group ID for the TA adjacent to the RA with different matching rules and the S-NSSAI. It must be possible to receive mapping information. This disclosure presents a method for this.

The priority for each network slice or network slice group must be determined so as not to violate the network operator's policy. Additionally, the priority for each network slice or network slice group needs to be considered along with determining other policy control information for the network slice. For example, other policy control information for a network slice may be UE Route Policy (URSP) information. For example, URSP may be information containing rules on which network slice the traffic provided to the terminal should be transmitted. Accordingly, the PCF (Policy Control Function), a network function (NF) that is located in the network where the terminal is located and manages policy information for the network where the terminal is located, must be able to support the priority verification function for each network slice or slice group. do. For example, the network where the terminal is located may be a serving network.

Meanwhile, there may be cases where a home network operator wants to control the priority of each network slice or network slice group for each subscriber. For example, if multiple subscribers want to access a specific network slice, a higher priority value is provided to subscribers using a high rate plan, thereby giving subscribers using a high rate plan priority for using a specific network slice. can do. Accordingly, UDM (Unified Data Management), an NF that is located in the terminal's home network (i.e., home network) and stores and manages subscriber information for the terminal located in the home network, is configured to manage each network slice or slice group of the terminal located in the home network. It must be able to support the ability to control priority decisions. In addition, according to an embodiment of the present disclosure, when a home network operator provides priority information for each network slice or slice group in the home network to a terminal roaming in the visited network, the home network Priority information for each network slice or slice group in the home network must be converted into priority information for each network slice identifier or network slice group identifier supported by the visited network and provided to the terminal. According to an embodiment of the present disclosure, the visited network may be a visited network in which a roaming agreement on network slice priority has been reached between operators.

In providing network slice group priority and mapping information between network slices and network slice groups for the terminal's slice-based cell reselection in the 3GPP 5G system, it prevents the terminal from referring to incorrect mapping information and ensures that the network operator's policy is efficient. It allows the home network operator to control the network slice priority for cell reselection for each subscriber even in roaming situations.

Figure 1 shows a method of providing NSAG (network slice AS (access stratum) group) information in a terminal registration procedure in a wireless communication system according to an embodiment of the present disclosure. NSAG information is information including mapping relationship information between slice group identifiers and S-NSSAI for slices and priority information to be used for cell re-selection for slices or slice group(s) to which slices are mapped.

Referring to FIG. 1, in step 101, the terminal (UE) may transmit an AN message (AN parameter, registration request) to the base station (RAN). At this time, the registration request message includes a UE identifier (subscription concealed identifier (SUCI), 5G-globally unique temporary identity (5G-GUTI), or permanent equipment identifier (PEI), etc.), requested NSSAI, and UE mobility management (MM) core network. At least one of capabilities, etc. may be included. If the UE supports network slice group and network slice priority for cell re-selection, the UE may include Support of NSAG in the UE MM core network capability.

According to an embodiment of the present disclosure, when the terminal supporting NSAG determines that slice group mapping needs to be updated or when the terminal supporting NSAG determines that slice priority needs to be updated, the terminal transmits a registration request message. It may perform a registration procedure and may also include an indication requesting NSAG. According to an embodiment of the present disclosure, when the terminal determines that slice group mapping needs to be updated, it may correspond to a case where the terminal receives an unknown slice group ID from the base station. When receiving an indication requesting NSAG, the AMF may include NSAG information in the information transmitted to the terminal or may include information including an instruction to disable slice-based cell re-selection to the terminal.

In step 102, the RAN may select the AMF based on information in the AN message received from the UE. RAN can deliver an N2 message (N2 parameters, registration request) to the selected AMF. N2 parameters may include selected PLMN ID, UE location information, UE context request, etc. At this time, the N2 message may include the RAN ID.

At step 103, the necessary steps in the UE registration procedure may be performed. According to an embodiment of the present disclosure, if the 5GMM Core Network Capability provided by the terminal in step 1 includes information indicating that NSAG is supported, the AMF may store the fact that the terminal supports NSAG in the terminal's UE Context information. In addition, if there is no UE Context for the terminal, the AMF determines the previous AMF of the terminal based on the 5G-GUTI received in step 1 and sends a UE Context request message including the identifier of the terminal to the previous AMF to request information about the terminal. UE Context can be received. The received UE Context may include one or more of the following: whether the UE supports NSAG, priority information about the slice or slice group provided to the UE, and mapping information between slice group id and S-NSSAI.

In step 104, the AMF may determine the RA (Registration Area), which is an area for managing the mobility of the UE, and Allowed NSSAI, which is information on slices allowed within the RA. Additionally, if the UE needs to update the Configured NSSAI, which is information about slices currently available in the network, the Configured NSSAI can be determined.

If the 5GMM Core Network Capability provided by the terminal in step 101 includes information indicating support for NSAG, AMF provides mapping information between S-NSSAI and slice group ID for some or all of the slices in the Configured NSSAI, slice or slice group. NSAG information including priority information can be determined.

According to an embodiment of the present disclosure, AMF can operate in the following two ways to solve the case where external TAs adjacent to the RA border use different mapping rules between S-NSSAI and slice group ID. :

- If the AMF confirms that a TA outside the RA adjacent to the boundary of the RA uses a mapping rule between different S-NSSAIs and slice group ids, the AMF provides a mapping rule between different S-NSSAIs and slice group ids to the UE. Identifier information for TAs using rules and mapping relationship information between S-NSSAIs and slice group ids for TAs using mapping rules between different S-NSSAIs and slice group ids can be included in the information to be transmitted to the terminal. Information to be transmitted to the terminal may be NSAG information for TA boundary. When AMF does not know the mapping relationship information between S-NSSAI and slice group id for a TA that uses mapping rules between different S-NSSAI and slice group id, it provides different S-NSSAI and slice group id information to the Network Slice Selection Function (NSSF). After requesting and receiving mapping relationship information between S-NSSAI and slice group id for TA using mapping rules between slice group ids, NSAG information for TA boundary can be determined.

- The RA can be configured so that an external TA adjacent to the RA boundary has the same mapping rule as the mapping rule between S-NSSAI and slice group id within the RA.

Additionally, according to an embodiment of the present disclosure, AMF can provide information (NSAG forbidden area) about TA(s) on which slice-based cell re-selection should not be performed.

In step 105, the AMF may request the PCF to select or verify the priority value for the slice or slice group within the NSAG information, NSAG information for TA boundary determined in step 104. For this purpose, AMF can transmit NSAG information and NSAG information for TA boundary in the request message sent to PCF. At this time, AMF can only provide priority information for each slice among NSAG information and NSAG information for TA boundary information.

Alternatively, in step 104, when the NSAG priority or slice priority for the UE is newly determined and a change occurs, the AMF allows the new NSAG priority or slice priority for the UE to be considered when creating the UE policy for the UE, or creates a new NSAG priority for the UE. In order for the UE policy to be appropriately updated considering NSAG priority or slice priority, the NSAG priority or slice priority information and UE ID determined in step 104 can be notified to the PCF through Npcf_UEPolicyControl Create Request or Npcf_UEPolicyControl Update Request. If the UE is roaming, the NSAG priority or slice priority information and UE ID determined in step 104 may be transmitted to the H-PCF through the V-PCF. In step 106, if the message from the AMF in step 105 includes priority information for each slice corresponding to NSAG information, NSAG information for TA boundary or NSAG information, NSAG information for TA boundary, priority for each slice or slice group The ranking value can be determined. At this time, the PCF can consider the predetermined URSP rule and the network operator's policy.

Alternatively, the PCF receives the Npcf_UEPolicyControl Create Request in step 105, and when NSAG priority or slice priority is included in the Npcf_UEPolicyControl Create Request message, if there is no UE Policy yet, NSAG priority or slice priority is considered when creating a new UE Policy. UE Policy can be created. After creating a UE Policy, the created UE Policy can be transmitted to the UE through AMF. According to an embodiment of the present disclosure, NSAG priority may be priority information for each slice group. According to an embodiment of the present disclosure, slice priority may be priority information for each slice. According to an embodiment of the present disclosure, the UE Policy is information transmitted to the UE and may include matching rules between traffic and slices. If the terminal is roaming, H-PCF can transmit the UE Policy created through V-PCF and AMF to the terminal.

The PCF receives the Npcf_UEPolicyControl Update Request message in step 105, and if the Npcf_UEPolicyControl Update Request message includes NSAG priority or slice priority, and a UE Policy exists, whether UE policy update is necessary based on the received NSAG priority or slice priority. can be judged. If the PCF determines that UE policy update is necessary based on the NSAG priority or slice priority received by the PCF, it can calculate a new UE policy and transmit the updated UE Policy to the UE through AMF. If the terminal is roaming, H-PCF can transmit the updated UE Policy to the terminal through V-PCF and AMF.

In step 107, the PCF may include information about the priority value for each slice or slice group determined in step 106 in the response message transmitted to the AMF.

At step 108, the remaining terminal registration procedures may be performed.

In step 109, the AMF may include a registration accept message in the N2 message and transmit it to the RAN.

According to an embodiment of the present disclosure, when the AMF determines NSAG information, NSAG information for TA boundary, and NSAG forbidden area in step 104, the registration accept message transmitted by the AMF to the terminal includes NSAG information, NSAG information for TA boundary, NSAG May include forbidden area information.

In step 110, the RAN may transmit a registration accept message to the UE within the message received from the AMF in step 8.

When the UE receives NSAG information for TA boundary, and the UE moves to the RA boundary and receives slice group ids supported by cells in the TA included in the NSAG information for TA boundary information, a slice corresponding to the received slice group id ( s) can be known. For example, when receiving slice group IDs, the UE can know the slice(s) corresponding to the received slice group ID through information included in the NSAG information for TA boundary. The UE may perform cell re-selection based on the slice(s) corresponding to the received slice group id.

When the UE receives an NSAG forbidden area, slice-based cell re-selection is not performed on TAs included in the NSAG forbidden area. In other words, cell re-selection may not be performed considering slice group IDs broadcast from TAs included in the NSAG forbidden area.

Figure 2 shows a method of determining slice priority or slice group priority through UDM in a terminal registration procedure in a wireless communication system according to an embodiment of the present disclosure.

Referring to FIG. 2, in step 201, the terminal (UE) may transmit an AN message (AN parameter, registration request) to the base station (RAN). At this time, the registration request message includes a UE identifier (subscription concealed identifier (SUCI), 5G-globally unique temporary identity (5G-GUTI), or permanent equipment identifier (PEI), etc.), requested NSSAI, and UE mobility management (MM) core network. At least one of capabilities, etc. may be included. If the UE supports network slice group and network slice priority for cell re-selection, the UE may include Support of NSAG in the UE MM core network capability.

In step 202, the RAN may select the AMF based on information in the AN message received from the UE. RAN can deliver an N2 message (N2 parameters, registration request) to the selected AMF. N2 parameters may include selected PLMN ID, UE location information, UE context request, etc. At this time, the N2 message may include the RAN ID.

In step 203, the AMF may request subscriber information of the terminal by including the terminal's identifier and an identifier for the requested information in a message transmitted to the UDM. At this time, if the terminal supports NSAG, the AMF may include an identifier requesting slice priority information in the UDM.

In step 204, the UDM may include the terminal identifier of the message received from the AMF in step 203 and subscriber information for the requested information in a response message sent to the AMF. The response message that transmits the terminal identifier of the message received from AMF and subscriber information for the requested information to AMF may include the following information:

Subscribed slice information (S-NSSAIs), slice priority information for each slice within a subscribed slice (slice priority for Subscribed S-NSSAIs) (here, priority information may be provided for each slice or slice group), NSAG forbidden information .

NSAG forbidden information can be one of the following: an indicator that prohibits slice-based cell re-selection of a terminal, an indicator that prohibits slice-based cell re-selection for a roaming terminal, and an indicator that prohibits cell re-selection in a specific geographic location. there is.

In step 205, the AMF may not provide NSAG information to the terminal if NSAG forbidden information exists in the information received in step 204 and the NSAG forbidden information information indicates an indicator prohibiting slice-based cell re-selection of the terminal. there is. If the NSAG forbidden information information is an indicator that prohibits slice-based cell re-selection for a roaming terminal, AMF may not provide NSAG information to the roaming terminal. If the NSAG forbidden information information is an indicator that prohibits slice-based cell re-selection in a specific geographical location, the AMF may provide the UE with TA information that slice-based cell re-selection is prohibited along with NSAG information.

Meanwhile, if the information received in step 204 does not include NSAG forbidden information, the AMF provides NSAG information including slice priority information for cell re-selection to be provided to the UE based on the information received from the UDM in step 204. Calculate.

At this time, AMF may request NSSF to determine NSAG information, and the following information may be included in the message requesting NSSF:

Slice priority for Subscribed S-NSSAIs, Subscribed S-NSSAIs, NSAG information request indicator received from UDM (this may be information indicating that the terminal supports NSAG)

If NSAG information request indicator and slice priority for Subscribed S-NSSAIs are included, NSSF determines whether to use slice priority for Subscribed S-NSSAIs based on operator policy. If the terminal is roaming, the NSSF determines whether to use slice priority for Subscribed S-NSSAIs according to the agreement between the home network operator and the visited network operator.

The response message sent by NSSF to AMF may include:

NSAG information, Configured NSSAI, Mapping of Configured NSSAI

NSAG information is information that includes slice priority information for each slice or slice group determined by NSSF and mapping information between the corresponding slice group id and S-NSSAI. When the terminal is roaming, slice identifiers in NSAG information consist of slice identifiers of the visited network. Therefore, when NSSF determines that the terminal is roaming, it can provide Configured NSSAI and Mapping of Configured NSSAI. Mapping of Configured NSSAI is information indicating the mapping relationship between slice identifiers (i.e., visited network slice identifiers) included in the Configured NSSAI and Subscribed S-NSSAIs (i.e., home network identifiers).

Meanwhile, AMF can directly calculate NSAG information using slice priority for Subscribed S-NSSAIs and Subscribed S-NSSAIs received from UDM without requesting NSSF.

At step 206. The AMF may request the PCF to select or verify the priority value for the slice or slice group within the NSAG information determined in step 205. For this purpose, AMF can transmit NSAG information in the request message sent to PCF. At this time, AMF may only provide priority information for each slice within NSAG information.

Alternatively, in step 205, when the NSAG priority or slice priority for the UE is newly determined and a change occurs, the AMF allows the new NSAG priority or slice priority for the UE to be considered when creating the UE policy for the UE, or creates a new NSAG priority for the UE. In order for the UE policy to be appropriately updated considering NSAG priority or slice priority, the NSAG priority or slice priority information and UE ID determined in step 205 can be notified to the PCF through Npcf_UEPolicyControl Create Request or Npcf_UEPolicyControl Update Request. If the UE is roaming, the NSAG priority or slice priority information and UE ID determined in step 205 may be transmitted to the H-PCF through the V-PCF.

In step 207, the PCF may determine a priority value for each slice or slice group when the message from the AMF in step 206 includes NSAG information or priority information for each slice. At this time, the PCF can consider the predetermined URSP rule and the network operator's policy.

Alternatively, the PCF receives the Npcf_UEPolicyControl Create Request message in step 206, and if the Npcf_UEPolicyControl Create Request message includes NSAG priority or slice priority, and if there is no UE Policy yet, NSAG priority or slice priority is considered when creating a new UE Policy. You can create a UE Policy by doing this. After creating a UE Policy, the created UE Policy can be transmitted to the UE through AMF. According to an embodiment of the present disclosure, NSAG priority may be priority information for each slice group. According to an embodiment of the present disclosure, slice priority may be priority information for each slice. According to an embodiment of the present disclosure, the UE Policy is information transmitted to the UE and may include matching rules between traffic and slices. If the terminal is roaming, H-PCF can transmit the UE Policy created through V-PCF and AMF to the terminal.

The PCF receives the Npcf_UEPolicyControl Update Request message in step 206, and if the Npcf_UEPolicyControl Update Request message includes NSAG priority or slice priority, and a UE Policy exists, whether UE policy update is necessary based on the received NSAG priority or slice priority. can be judged. If the PCF determines that UE policy update is necessary based on the NSAG priority or slice priority received by the PCF, it can calculate a new UE policy and transmit the updated UE Policy to the UE through MF. If the terminal is roaming, H-PCF can transmit the updated UE Policy to the terminal through V-PCF and AMF.

In step 208, the PCF may include information about the priority value for each slice or slice group determined in step 207 in the response message transmitted to the AMF.

At step 209, the remaining terminal registration procedures can be performed.

In step 210, the AMF may include a registration accept message in the N2 message and transmit it to the RAN. According to an embodiment of the present disclosure, when the AMF determines NSAG information in step 205, the AMF may include the NSAG information in the registration accept message transmitted to the terminal. According to an embodiment of the present disclosure, when the AMF determines NSAG information, Configured NSSAI, and Mapping of Configured NSSAI in step 205, the registration accept message transmitted to the terminal may include NSAG information, Configured NSSAI, and Mapping of Configured NSSAI information. there is.

In step 211, the RAN may transmit a registration accept message to the UE within the message received from the AMF in step 210.

Figure 3 is a block diagram showing the structure of a terminal (UE) according to an embodiment of the present disclosure.

As shown in FIG. 3, the terminal of the present disclosure may include a processor 320, a transceiver 300, and a memory 310. 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 aforementioned components. In addition, the processor 320, the transceiver 300, and the memory 310 may be implemented in the form of a single chip.

According to an embodiment of the present disclosure, the processor 320 can control a series of processes in which the terminal can operate according to the above-described embodiment of the present disclosure. For example, the processor 320 may control components of the terminal to perform a method to support priority of a network slice according to the above-described embodiments. The processor 320 may control the components of the terminal to perform the above-described embodiments of the present disclosure by executing a program stored in the memory 310. Additionally, the processor 620 may be an Application Processor (AP), a Communication Processor (CP), a circuit, an application-specific circuit, or at least one processor.

According to an embodiment of the present disclosure, the transceiver 300 can transmit and receive signals with a network entity, another terminal, or a base station. Signals transmitted and received from network entities, other terminals, or base stations may include control information and data. The transceiver 300 may be comprised of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. However, this is only an example of the transceiver 300, and the components of the transceiver 300 are not limited to the RF transmitter and RF receiver. Additionally, the transceiver 300 may receive a signal through a wireless channel, output it to the processor 320, and transmit the signal output from the processor 320 through a wireless channel.

According to one embodiment of the present disclosure, the memory 310 may store programs and data necessary for operation of the terminal. Additionally, the memory 310 may store control information or data included in signals transmitted and received by the terminal. The memory 310 may be composed of a storage medium such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Additionally, there may be multiple memories 310. Additionally, according to one embodiment, the memory 310 may store a program for performing a method to support the priority of a network slice according to the above-described embodiments.

Figure 4 is a block diagram showing the structure of a base station according to an embodiment of the present disclosure.

As shown in FIG. 4, the base station of the present disclosure may include a processor 420, a transceiver 400, and a memory 410. However, the components of the base station are not limited to the above examples. For example, a base station may include more or fewer components than those described above. In addition, the processor 420, the transceiver 400, and the memory 410 may be implemented in the form of a single chip.

According to an embodiment of the present disclosure, the processor 420 can control a series of processes by which the base station can operate according to the above-described embodiment of the present disclosure. For example, the processor 420 may control components of the base station to perform a method to support priority of a network slice according to the above-described embodiments. The processor 420 may control the components of the base station to perform the above-described embodiments of the present disclosure by executing a program stored in the memory 410. Additionally, the processor 420 may be at least one processor.

According to an embodiment of the present disclosure, the transceiver 400 can transmit and receive signals with a network entity, another base station, or a terminal. Signals transmitted and received from network entities, other base stations, or terminals may include control information and data. The transceiver 400 may be comprised of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. However, this is only an example of the transceiver 400, and the components of the transceiver 400 are not limited to the RF transmitter and RF receiver. Additionally, the transceiver 400 may receive a signal through a wireless channel and output it to the processor 420, and transmit the signal output from the processor 420 through a wireless channel.

According to one embodiment of the present disclosure, the memory 410 may store programs and data necessary for the operation of the base station. Additionally, the memory 410 may store control information or data included in signals transmitted and received by the base station. The memory 410 may be composed of a storage medium such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Additionally, there may be multiple memories 410. Additionally, according to one embodiment, the memory 410 may store a program for performing a method to support the priority of a network slice according to the above-described embodiments.

Figure 5 is a block diagram showing the structure of a network entity according to an embodiment of the present disclosure.

As shown in FIG. 5, the network entity of the present disclosure may include a processor 520, a transceiver 500, and a memory 510. However, the components of the network entity are not limited to the examples described above. For example, a network entity may include more or fewer components than those described above. In addition, the processor 520, the transceiver 500, and the memory 510 may be implemented in the form of a single chip.

According to an embodiment of the present disclosure, the processor 520 may control a series of processes in which the NF may operate according to the above-described embodiment of the present disclosure. For example, the processor 520 may control components of a network entity to perform a method to support priority of a network slice according to the above-described embodiments. The processor 520 may control components of the network entity so that the above-described embodiments of the present disclosure are performed by executing a program stored in the memory 510. Additionally, the processor 520 may be at least one processor.

According to an embodiment of the present disclosure, the transceiver 500 can transmit and receive signals with other network entities, base stations, or terminals. Signals transmitted and received with other network entities or terminals may include control information and data. The transceiver 500 may be comprised of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that amplifies the received signal with low noise and down-converts the frequency. However, this is only an example of the transceiver 500, and the components of the transceiver 500 are not limited to the RF transmitter and RF receiver. Additionally, the transceiver 500 may receive a signal through a wired or wireless channel and output it to the processor 520, and transmit the signal output from the processor 520 through a wired or wireless channel.

According to one embodiment of the present disclosure, the memory 510 may store programs and data necessary for the operation of a network entity. Additionally, the memory 510 may store control information or data included in signals transmitted and received by a network entity. The memory 510 may be composed of a storage medium such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. Additionally, there may be multiple memories 510. Additionally, according to one embodiment, the memory 510 may store a program for performing a method for supporting the priority of a network slice according to the above-described embodiments.

According to an embodiment of the present disclosure, a method performed by a terminal includes the steps of transmitting a registration request message to a base station; The registration request message includes network slice access stratum (AS) group (NSAG) support information, and the registration request message is delivered to an access and mobility management function (AMF) through a base station, and is transmitted to each network slice. Receiving a registration accept message including NSAG information related to priority from the base station through the AMF; The NSAG information may include a method determined based on the NSAG support message.

Methods according to 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.

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

These programs (software modules, software) include random access memory, non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (EEPROM: Electrically Erasable Programmable Read Only Memory), magnetic disc storage device, Compact Disc-ROM (CD-ROM: Compact Disc-ROM), Digital Versatile Discs (DVDs), or other types of It can be stored in an optical storage device or magnetic cassette. Alternatively, it may be stored in a memory consisting of a combination of some or all of these. Additionally, a plurality of each configuration memory may be included.

In addition, the program can be accessed through a communication network such as the Internet, Intranet, LAN (Local Area Network), WLAN (Wide LAN), or SAN (Storage Area Network), or a combination of these. It may be stored in an attachable storage device that can be accessed. This storage device can be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communications network may be connected to the device performing embodiments of the present disclosure.

In the specific embodiments of the present disclosure described above, elements included in the present disclosure are expressed in singular or plural numbers depending on the specific embodiment presented. However, 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, and even components expressed in plural may be composed of singular or singular. Even expressed components may be composed of plural elements.

Meanwhile, the embodiments of the present disclosure disclosed in the specification and drawings are merely provided as specific examples to easily explain the technical content of the present disclosure and aid understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is obvious to those skilled in the art that other modifications based on the technical idea of the present disclosure can be implemented. Additionally, each of the above embodiments can be operated in combination with each other as needed. For example, a base station and a terminal may be operated by combining parts of one embodiment of the present disclosure and another embodiment. Additionally, the embodiments of the present disclosure can be applied to other communication systems, and other modifications based on the technical idea of the embodiments may also be implemented.

Claims (1)

In the way the terminal performs,
Transmitting a registration request message to the base station; The registration request message includes network slice access stratum (AS) group (NSAG) support information, and the registration request message is transmitted to an access and mobility management function (AMF) through a base station,
Receiving a registration accept message including NSAG information related to the priority of each network slice from the base station through the AMF;
A method wherein the NSAG information is determined based on the NSAG support message.

Images