KR20200091308A - Apparatus and method for supporting network slices interworking in wireless communication system - Google Patents

Abstract

The present invention relates to a 5thgeneration (5G) or pre-5G communication system for supporting a data transmission rate higher than a 4thgeneration (4G) communication system such as long-term evolution (LTE). According to various embodiments of the present invention, a method of operating a core network device in a wireless communication system includes the following steps of: receiving a session creation request message; transmitting an Nudm_SDM_Get request message; receiving an Nudm_SDM_Get response message including information about a subscription slice to which a terminal has subscribed; comparing the subscription slice information to slice information which can be provided by the core network device; selecting slice information to be transmitted to the terminal based on the result of the comparison; and transmitting the selected slice information to the terminal.

Description

A device and method for providing interworking of a network slice in a wireless communication system{APPARATUS AND METHOD FOR SUPPORTING NETWORK SLICES INTERWORKING IN WIRELESS COMMUNICATION SYSTEM}

The disclosure generally relates to a wireless communication system, and more particularly, to an apparatus and method for providing network slicing in a wireless communication system.

4G (4 ^th generation) to meet the traffic demand in the radio data communication system increases since the commercialization trend, efforts to develop improved 5G (5 ^th generation) communication system, or pre-5G communication system have been made. For this reason, the 5G communication system or the pre-5G communication system is called a 4G network (Beyond 4G Network) communication system or a Long Term Evolution (LTE) system (Post LTE) system.

To achieve high data rates, 5G communication systems are being considered for implementation in the ultra-high frequency (mmWave) band (eg, 60 gigahertz (60 GHz) band). In order to mitigate the path loss of radio waves in the ultra-high frequency band and increase the transmission distance of radio waves, in 5G communication systems, beamforming, massive array multiple input/output (massive MIMO), full dimensional multiple input/output (FD-MIMO) ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed.

In addition, in order to improve the network of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud RAN), an ultra-dense network ), Device to Device communication (D2D), wireless backhaul, mobile network, cooperative communication, coordinated multi-points (CoMP), and interference cancellation ) And other technologies are being developed.

In addition, in 5G system, advanced coding modulation (Advanced Coding Modulation, ACM) hybrid frequency shift keying and quadrature amplitude modulation (FQAM) and sliding window superposition coding (SWSC) and advanced access technology, FBMC (Filter Bank Multi Carrier) ), NOMA (Non Orthogonal Multiple Access), and SCMA (Sparse Code Multiple Access).

Meanwhile, the Internet is evolving from a human-centered connection network in which humans generate and consume information, to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. The Internet of Everything (IoE) technology, which combines big data processing technology through connection with cloud servers, etc. to IoT technology, is also emerging. In order to implement IoT, technical elements such as sensing technology, wired/wireless communication and network infrastructure, service interface technology, and security technology are required, and recently, a sensor network for connection between objects, a machine to machine (Machine to Machine) , M2M), and MTC (Machine Type Communication). In the IoT environment, an intelligent IT (Internet Technology) service that collects and analyzes data generated from connected objects to create new values in human life can be provided. IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliance, high-tech medical service through convergence and complex between existing IT (information technology) technology and various industries. It can be applied to.

Accordingly, various attempts have been made to apply a 5G communication system to an IoT network. For example, 5G communication technology such as sensor network, machine to machine (M2M), and MTC (Machine Type Communication) are implemented by techniques such as beamforming, MIMO, and array antenna. It is. It may be said that the application of cloud radio access network (cloud RAN) as the big data processing technology described above is an example of 5G technology and IoT technology convergence.

As it is possible to provide various services according to the above-mentioned and the development of a mobile communication system, a method for effectively providing these services is required.

Based on the discussion as described above, the present disclosure provides a method and apparatus for interworking between an EPS network system and a 5G network system structure that provides a network slicing function in a wireless communication system.

According to various embodiments of the present disclosure, a method of operating a core network device in a wireless communication system includes a process of receiving a session creation request message, a process of transmitting a Nudm_SDM_Get request message, and a Nudm_SDM_Get response message including subscription slice information subscribed to by a terminal. Receiving process, comparing the subscription slice information with slice information that can be provided by the core network device, selecting slice information to be transmitted to the terminal based on the comparison result, and selecting the slice information. It may include a process of transmitting to the terminal.

According to various embodiments of the present disclosure, a core network device of a wireless communication system includes a communication unit, a storage unit, and at least one processor coupled with the communication unit and the storage unit, which performs communication with other devices in the core network, wherein At least one processor receives a session creation request message through the communication unit, transmits a Nudm_SDM_Get request message through the communication unit, receives a Nudm_SDM_Get response message including subscription slice information subscribed to by the terminal through the communication unit, and the Subscription slice information and slice information that can be provided by the core network device are compared, based on the comparison result, slice information to be transmitted to the terminal is selected, and the selected slice information can be transmitted to the terminal through the communication unit have.

According to various embodiments of the present disclosure, a method of operating a core network device in a wireless communication system in a wireless communication system includes a process of receiving a session creation request message, a process of transmitting a Nudm_SDM_Get request message, and subscription slice information subscribed to by the terminal. The process of receiving the Nudm_SDM_Get response message, transmitting the Nnssf_NSSelection_Get request message including the subscription slice information and the PLMN ID included in the ID of the terminal, mapped slice information used in VPLMN mapped to the subscription slice information Receiving an Nnssf_NSSelection_Get response message, comparing the mapped slice information with slice information that can be provided by the core network device, and selecting slice information to be transmitted to the terminal based on the comparison result , Transmitting the selected slice information to the terminal.

According to various embodiments of the present disclosure, in a wireless communication system, a core network device of a wireless communication system includes a communication unit, a storage unit, and at least one processor coupled with the communication unit and the storage unit to perform communication with other devices in the core network. Including, the at least one processor receives a session creation request message through the communication unit, sends a Nudm_SDM_Get request message through the communication unit, Nudm_SDM_Get response message including the subscription slice information to which the terminal subscribes through the communication unit A Nnssf_NSSelection_Get request message including the subscription slice information and the PLMN ID included in the ID of the terminal is transmitted through the communication unit, and the mapped slice is mapped to the subscription slice information and used in the VPLMN through the communication unit. Receives an Nnssf_NSSelection_Get response message including information, compares the mapped slice information with slice information that can be provided by the core network device, selects slice information to be transmitted to the terminal based on the comparison result, and The selected slice information may be transmitted to the terminal through a communication unit.

The apparatus and method according to various embodiments of the present disclosure provide an interworking method between an EPS network system and a 5G network system structure that provides a network slicing function, thereby effectively providing a service in a mobile communication system.

The effects obtainable in the present disclosure are not limited to the above-mentioned effects, and other effects not mentioned may be clearly understood by those skilled in the art from the description below. will be.

1 illustrates a 5G network slice interworking structure (non-roaming) according to some embodiments of the present disclosure.
2 illustrates a network slice interworking configuration (Non-roaming) according to some embodiments of the present disclosure.
3 illustrates a network slice interworking configuration diagram (Local breakout roaming) according to some embodiments of the present disclosure.
4 illustrates a network slice interworking configuration diagram (Home-routed roaming) according to some embodiments of the present disclosure.
5 illustrates SMF+PGW-C operation for network slice interworking support according to some embodiments of the present disclosure.
6 illustrates SMF+PGW-C operation for network slice interworking support according to some embodiments of the present disclosure.
7 illustrates a configuration of a base station in a wireless communication system according to various embodiments of the present disclosure.
8 illustrates a configuration of a terminal in a wireless communication system according to various embodiments of the present disclosure.
9 illustrates a configuration of a core network device in a wireless communication system according to various embodiments of the present disclosure.
10 illustrates a 5G network registration procedure of a terminal according to various embodiments of the present disclosure.

Terms used in the present disclosure are only 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 commonly understood by a person skilled in the art described in the present disclosure. Among the terms used in the present disclosure, terms defined in the general dictionary may be interpreted as meanings identical or similar to meanings in the context of the related art, and are ideally or excessively formal meanings unless explicitly defined in the present disclosure. Is not interpreted as In some cases, even terms defined in the present disclosure cannot be interpreted to exclude embodiments of the present disclosure.

Various embodiments of the present disclosure described below describe a hardware approach as an example. However, since various embodiments of the present disclosure include technology that uses both hardware and software, various embodiments of the present disclosure do not exclude a software-based approach.

Hereinafter, the present disclosure relates to an apparatus and method for providing interworking of a network slice in a wireless communication system. Specifically, the present disclosure describes a technique for interworking between an EPS network system and a 5G network system structure that provides a network slicing function in a wireless communication system.

The terms used in the following description, the terms referring to the channel, the terms referring to the control information, the terms referring to the network objects (network entities), the terms referring to the components of the device, and the like for convenience of description It is illustrated. Therefore, the present disclosure is not limited to the terms described below, and other terms having equivalent technical meanings 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 in other communication systems.

The 3GPP standard standardized the 5G network system architecture and procedures. Mobile operators can provide a variety of services in 5G networks. In order to provide each service, the mobile communication service provider needs to satisfy different service requirements for each service (for example, latency, communication range, data rate, bandwidth, reliability, etc.). To this end, a mobile communication operator may configure a network slice and allocate network resources suitable for a specific service for each network slice or for each set of network slices. The network resource may mean NF (Network Function) or logical resource provided by NF or radio resource allocation of the base station.

For example, a mobile communication provider may configure network slice A for mobile broadband service provision, network slice B for vehicle communication service provision, and network slice C for IoT service provision. That is, in this way, in the 5G network, the corresponding service can be provided on a network slice specialized for the characteristics of each service. S-NSSAI (Single-Network Slice Selection Assistance Information) defined in 3GPP may be used as a classifier for classifying network slices.

Mobile operators can operate 5G networks and EPS (or LTE) networks together. The mobile communication terminal can access the 5G network and use the service to move to the EPS network. Alternatively, the mobile communication terminal can access the EPS network and use the service to move to the 5G network.

In the present disclosure, an interworking method between an EPS network system and a 5G network system structure providing a network slice function is defined. 1, 2, and 3 show an interworking structure of 5GS (5G system) and Evolved Packet System (EPS).

In addition, the present disclosure defines a network operation and a terminal operation to establish a session connection in EPS so that a terminal using a communication service can seamlessly use the service even when moving to 5GS.

1 shows an interworking structure of 5GS and EPS in a non-roaming situation. 5GS may be composed of NR (New Radio) base station 150, AMF (145), SMF (120), UPF (125), PCF (115), UDM (110). EPS may be composed of E-UTRA base station 140, MME 135, SGW 130, PGW-U 125, PGW-C 120, PCRF 115, HSS 110. UGS 110 of 5GS and HSS 110 of EPS may be configured as one combo node. The 5GS SMF 120 and the EPS PGW-C 120 may be configured as one combo node. The UDM+HSS 110 node may store subscriber information of the terminal. The UPF 125 of 5GS and the PGW-U 125 of EPS may be configured as one combo node. The terminal 155 may access the MME 135 of the EPS through the E-UTRA base station 140 to use the EPS network service. In addition, the terminal 155 may access the 5MF AMF 145 through the NR base station 150 to use the 5GS network service.

Figure 2 shows the interworking structure of 5GS and EPS in the Local Breakout roaming situation. As described in FIG. 1, the terminal 260 may access the MME 240 of the EPS through the E-UTRA base station 245 and use the EPS network service. In addition, the terminal 260 may access the 5MF AMF 250 through the NR base station 255 to use the 5GS network service. In the 5GS and EPS interworking structure in Local Breakout roaming, the SMF+PGW-C (225) node may be located in a VPLMN (Visited PLMN).

3 shows an interworking structure of 5GS and EPS in a home-routed roaming situation. As described in FIG. 1, the terminal 370 may access the MME 335 of the EPS through the E-UTRA base station 340 to use the EPS network service. In addition, the terminal 370 may access the 5MF AMF 360 through the NR base station 365 to use the 5GS network service. In the 5GS and EPS interworking structure in home-routed roaming, the SMF+PGW-C 320 node may be located in the HPLMN (Home PLMN).

4 illustrates a procedure for a terminal 410 to establish a PDN connection in EPS according to an embodiment of the present invention. The terminal 410 may access the MME 420 through the E-UTRA base station 415 to exchange signaling messages with the PGW-C 430 located in the EPS and establish a PDN connection. When the PDN connection establishment is completed, the terminal 410 may transmit uplink data to the PGW-U 435 or receive downlink data from the PGW-U 435.

Step 1: The terminal 410 may transmit a PDN connectivity request message to the MME 420 to establish a PDN connection. The PDN connection request message may be transmitted to the MME 420 through the E-UTRA base station 415.

Step 2: Upon receiving the PDN connection request message in step 1, the MME 420 may transmit a session creation request message to the S-GW 425.

Step 3: Upon receiving the session creation request message in step 2, the S-GW 425 may transmit a session creation request message to the SMF+PGW-C 430.

Step 4: In step 3, the SMF+PGW-C 430 receiving the session creation request message can perform the PCF+PCRF 440 and IP-CAN session establishment or modification procedure.

Step 5: In step 3, the SMF+PGW-C 430 receiving the session creation request message may transmit the Nudm_SDM_Get request message to the UDM+HSS 445. The Nudm_SDM_Get request message may include a key type that can access the data type of the subscriber information requested and the data type of the subscriber information. According to an embodiment of the present invention, as a data type of subscriber information to be requested, " slice selection subscription data (Slice Selection Subscription data) " may be included, and a key to access the data type of the subscriber information, the terminal ID is "SUPI " May be included.

Step 6: In step 5, the UDM+HSS 445 receiving the Nudm_SDM_Get request message, if the Nudm_SDM_Get request message includes the " slice selection subscriber data " parameter, the network slice subscription information of the terminal corresponding to the received terminal ID SUPI Can be found in the database (UDR). According to an embodiment of the present invention, the network slice subscription information may be composed of one or more S-NSSAI(s), and may be referred to as subscribed S-NSSAIs. The UDM+HSS 445, which finds the subscription slice of the UE corresponding to the received SUPI, may return a Nudm_SDM_Get response message to the SMF+PGW-C 430. The Nudm_SDM_Get response message may include “subscribed S-NSSAIs” information of the terminal corresponding to the SUPI. The "subscribed S-NSSAIs" may include one or more default S-NSSAIs. For the description of the present invention, the "subscription slice" can be described as an example as follows.

Subscribed S-NSSAIs: {S-NSSAI 1, S-NSSAI 2, S-NSSAI 3(default)}

The terminal 410 is subscribed to three slices, and it can be assumed that S-NSSAI 3 is the basic slice.

When the PLMN ID included in the terminal ID SUPI and the PLMN ID in which the SMF+PGW-C 430 is located coincide (that is, corresponds to the embodiment of FIG. 1 and the embodiment of FIG. 3), a Nudm_SDM_Get response message is sent. The received SMF+PGW-C 430 may perform the SMF+PGW-C 430 operation for the SMF+PGW-C 430 to select the S-NSSAI, as shown in FIG. 5.

Referring to FIG. 5, SMF+PGW-C 430 that has received (520) Nudm_SDM_Get response message corresponds to Nudm_SDM_Get response message that S-NSSAI that SMF+PGW-C 430 can provide in step 6 It may be checked whether it is included in the included "subscribed slices (subscribed S-NSSAIs)" (525).

If there is no S-NSSAI that SMF+PGW-C 430 can provide (530) or one or more S-NSSAI that SMF+PGW-C 430 can provide, the "subscribe slice received in step 6" If there is no S-NSSAI matching "530", SMF+PGW-C 430 selects a default slice (default S-NSSAI) among the "subscription slices" received in step 6, or no S-NSSAI. You may not choose.

If there is one S-NSSAI that can be provided by SMF+PGW-C 430 and the S-NSSAI is included in the "subscription slice" received in step 6 (535) or SMF+PGW-C 430 If there is one S-NSSAI that matches the "subscription slice" received in step 6 among two or more S-NSSAIs that can be provided (535), SMF+PGW-C (430) is SMF+PGW-C (430) You can choose one S-NSSAI included in the "subscription slice" while being able to provide it.

When there are two or more S-NSSAIs that SMF+PGW-C 430 can provide, and two or more S-NSSAIs are included in the "subscription slice" (540), SMF+PGW-C 430 Based on the operator policy set in SMF+PGW-C (430), SMF+PGW-C (430) can provide and select one of two or more S-NSSAI included in the "subscription slice" S-NSSAI Can.

When the PLMN ID included in the terminal ID SUPI and the PLMN ID where the SMF+PGW-C 430 is located coincide (that is, corresponding to the embodiment of FIG. 1 and the embodiment of FIG. 3), process 7 and process 8 may not be performed.

When the PLMN ID included in the terminal ID SUPI and the PLMN ID where the SMF+PGW-C 430 is located do not match (that is, in the case of the embodiment of FIG. 2), steps 7 and 8 may be performed. have.

Step 7: In step 6, the SMF+PGW-C 430 receiving the Nudm_SDM_Get response message may transmit the Nnssf_NSSelection_Get request message to the NSSF 450. The Nnssf_NSSelection_Get request message may include “PLMN ID” included in SUPI, which is the terminal ID, and “subscribed S-NSSAIs” of the terminal received from UDM+HSS 445 in step 6. The “PLMN ID” included in the SUPI may indicate the HPLMN of the terminal. The "subscription slice" may indicate slice information used in the HPLMN of the terminal.

Step 8: The NSSF 450 receiving the Nnssf_NSSelection_Get request message in Step 7 is mapped to "subscribed S-NSSAIs" included in the request message and used by the VPLMN "mapped S-NSSAIs" ". For the description of the present invention, the "subscription slice" and the "mapped slice" can be described, for example, as follows.

Subscribed S-NSSAIs: {S-NSSAI 1, S-NSSAI 2, S-NSSAI 3(default)}

Mapped S-NSSAIs: {(S-NSSAI 1, S-NSSAI a), (S-NSSAI 2, S-NSSAI b), (S-NSSAI 3, S-NSSAI c)}

The S-NSSAI included in the "subscription slice" may be configured with a slice value (eg, S-NSSAI 1) used in the HPLMN of the terminal. The S-NSSAI included in the "mapped slice" is mapped to the slice value used in the HPLMN of the terminal (for example, S-NSSAI 1) and the slice value used in the VPLMN (for example, S-NSSAI a) ) (For example, (S-NSSAI 1, S-NSSAI a)).

The NSSF 450 may return an Nnssf_NSSelection_Get response message to the SMF+PGW-C 430. The Nnssf_NSSelection_Get response message may include “mapped slice” information.

The SMF+PGW-C 430 receiving the Nnssf_NSSelection_Get response message performs the SMF+PGW-C 430 operation for the SMF+PGW-C 430 to select the S-NSSAI, as shown in FIG. 6. Can.

Referring to FIG. 6, the SMF+PGW-C 430 receiving the 620 Nnssf_NSSelection_Get response message provides the SMF+PGW-C 430 using the “ mapped slice ” information included in the Nnssf_NSSelection_Get response message. It can be confirmed whether the S-NSSAI is included in the "subscribed slices (subscribed S-NSSAIs)" included in the Nudm_SDM_Get response message received in step 6 (625). For the above operation, the SMF_PGW-C 430 may interpret “subscription slice” information using the received “mapped slice” information.

That is, for example, if the slice provided by SMF+PGW-C 430 is S-NSSAI a, SMF+PGW-C 430 receives the received “mapped S-NSSAIs” information. It can be seen that S-NSSAI 1 mapped to S-NSSAI a, which is a slice provided by SMF+PGW-C 430, is included in "subscribed S-NSSAIs".

Subscribed S-NSSAIs: { S-NSSAI 1 , S-NSSAI 2, S-NSSAI 3(default)}

Mapped S-NSSAIs: {( S-NSSAI 1, S-NSSAI a ), (S-NSSAI 2, S-NSSAI b), (S-NSSAI 3, S-NSSAI c)}

In addition, for example, when the slice provided by SMF+PGW-C 430 is S-NSSAI d, SMF+PGW-C 430 uses the received “mapped slice” information to “join slice” It can be seen that S-NSSAI d, which is a slice provided by SMF+PGW-C 430, is not included in.

Subscribed S-NSSAIs: {S-NSSAI 1, S-NSSAI 2, S-NSSAI 3(default)}

Mapped S-NSSAIs: {(S-NSSAI 1, S-NSSAI a), (S-NSSAI 2, S-NSSAI b), (S-NSSAI 3, S-NSSAI c)}

In addition, for example, if the slices provided by SMF+PGW-C 430 are S-NSSAI a and S-NSSAI d, SMF+PGW-C 430 uses the received “mapped slice” information. Thus, it can be seen that S-NSSAI a was included among the slices provided by SMF+PGW-C 430 in the "subscription slice", but S-NSSAI d was not included.

Subscribed S-NSSAIs: { S-NSSAI 1 , S-NSSAI 2, S-NSSAI 3(default)}

Mapped S-NSSAIs: {( S-NSSAI 1, S-NSSAI a ), (S-NSSAI 2, S-NSSAI b), (S-NSSAI 3, S-NSSAI c)}

In addition, for example, if the slices provided by SMF+PGW-C 430 are S-NSSAI a and S-NSSAI c, SMF+PGW-C 430 receives the "mapped slice" information received as follows. It can be seen that S-NSSAI a and S-NSSAI c provided by SMF+PGW-C 430 are included in the "subscription slice" by using.

Subscribed S-NSSAIs: { S-NSSAI 1 , S-NSSAI 2, S-NSSAI 3(default) }

Mapped S-NSSAIs: {( S-NSSAI 1, S-NSSAI a ), (S-NSSAI 2, S-NSSAI b), (S-NSSAI 3, S-NSSAI c) }

If there is no S-NSSAI that SMF+PGW-C 430 can provide (630) or one or more S-NSSAI that SMF+PGW-C 430 can provide (e.g., S-NSSAI d ) If there is no S-NSSAI that matches the "subscription slice" received in step 6 (630), SMF+PGW-C 430 is the default slice (default S-NSSAI) among the "subscription slices" received in step 6 ) Or no S-NSSAI.

One S-NSSAI that can be provided by the SMF+PGW-C 430 (eg, S-NSSAI a) is included in the "subscription slice" received by the corresponding S-NSSAI in step 6 (for example, S-NSSAI a mapped to S-NSSAI 1) if (635) or two or more S-NSSAI that SMF+PGW-C 430 can provide (e.g., S-NSSAI a and S-NSSAI d ), there is one S-NSSAI that matches the "subscription slice" received in step 6 (for example, S-NSSAI 1 mapped to S-NSSAI a, S-NSSAI of HPLMN mapped to S-NSSAI d) In case 635, SMF+PGW-C 430 may select one S-NSSAI included in the "subscription slice" while being provided by SMF+PGW-C 430.

If there are two or more S-NSSAIs that SMF+PGW-C 430 can provide, and two or more of them are included in the "subscription slice" (640), SMF+PGW-C 430 Based on the operator policy set in SMF+PGW-C (430), SMF+PGW-C (430) can provide and select one of two or more S-NSSAI included in the "subscription slice" S-NSSAI Can.

Step 9: SMF+PGW-C 430 receiving the Nudm_SDM_Get response message in Step 6 (corresponding to the embodiment of Figure 1 or the embodiment of Figure 3) or SMF+PGW- receiving the Nnssf_NSSelection_Get response message in Step 8 C 430 (corresponding to the case of the embodiment of FIG. 2) may transmit a Create Session response message to the S-GW 425.

In the session creation response message, slice information selected through the procedure of FIG. 5 or 6 may be included in the form of PCO (545, 645). Various methods of slice information included in the session creation response message may exist. The slice information included in the session creation response message may be transmitted to the terminal 410 through steps 10, 11, and 12.

In addition, SMF+PGW-C 430 UDM the S-NSSAI, the slice information selected through the procedure of FIG. 5 or 6, and PDN connection information (eg, PDN connection ID, etc.) supported by the S-NSSAI. Can be stored in +HSS 445.

The following describes an example of slice information included in a session creation response message according to an embodiment of the present invention in the case of local breakout roaming (that is, in the case of the embodiment of FIG. 2). For description of the embodiment of the present invention, it is assumed that SMF+PGW-C 430 selects S-NSSAI 1 by performing the operation of FIG. 6 as follows.

Subscribed S-NSSAIs: { S-NSSAI 1 , S-NSSAI 2, S-NSSAI 3(default)}

Mapped S-NSSAIs: {( S-NSSAI 1, S-NSSAI a ), (S-NSSAI 2, S-NSSAI b), (S-NSSAI 3, S-NSSAI c)}

[LB Embodiment 1]: SMF+PGW-C 430 according to an embodiment of the present invention is mapped to S-NSSAI 1 selected in a session creation response message, and S-NSSAI a used in VPLMN and The S-NSSAI a may include a PCO (protocol configuration options). The PCO may include a PLMN ID in which S-NSSAI a is used, that is, a VPLMN ID.

Create Session Response msg: {??, PCO(S-NSSAI a) }

[LB Embodiment 2]: Alternatively, SMF+PGW-C 430 is mapped to S-NSSAI 1 selected in the session creation response message and includes S-NSSAI a used in VPLMN and mapping information corresponding thereto in PCO format can do. The PCO may include a PLMN ID in which S-NSSAI a is used, that is, a VPLMN ID.

Create Session Response msg: {??, PCO(S-NSSAI a, (S-NSSAI 1, S-NSSAI a)) }}

or

Create Session Response msg: {??, PCO((S-NSSAI 1, S-NSSAI a)) }

[LB Embodiment 3]: Alternatively, the SMF+PGW-C 430 may include the S-NSSAI 1 selected in the session creation response message in the form of PCO. The PCO may include a PLMN ID in which S-NSSAI 1 is used, that is, an HPLMN ID.

Create Session Response msg: {??, PCO(S-NSSAI 1) }

[LB Embodiment 4]: Alternatively, the SMF+PGW-C 430 may include S-NSSAI 1 selected in the session creation response message and mapping information corresponding thereto in PCO format. The PCO may include a PLMN ID in which S-NSSAI 1 is used, that is, an HPLMN ID and a PLMN ID in which S-NSSAI a is used, that is, a VPLMN ID.

Create Session Response msg: {??, PCO(S-NSSAI 1, (S-NSSAI 1, S-NSSAI a)) }}

or

Create Session Response msg: {??, PCO((S-NSSAI 1, S-NSSAI a)) }

[LB Embodiment 5]: Alternatively, the SMF+PGW-C 430 may not include the slice information selected in the session creation response message.

Create Session Response msg: {??}

The following describes an example of slice information included in a session creation response message according to an embodiment of the present invention in the case of Home-Routed roaming (that is, corresponding to the embodiment of FIG. 3 ). For the description of the embodiment of the present invention, it is assumed that SMF+PGW-C 430 selects S-NSSAI 1 by performing the operation of FIG. 5 as follows.

Subscribed S-NSSAIs: { S-NSSAI 1 , S-NSSAI 2, S-NSSAI 3(default)}

[HR Embodiment 1]: The SMF+PGW-C 430 according to an embodiment of the present invention may include S-NSSAI 1 selected in the Create Session response message in PCO form. The PCO may include a PLMN ID in which S-NSSAI 1 is used, that is, an HPLMN ID.

Create Session Response msg: {??, PCO(S-NSSAI 1) }

[HR Embodiment 2]: Alternatively, the SMF+PGW-C 430 may not include the slice information selected in the Create Session response message.

Create Session Response msg: {??}

Step 10: In step 9, the S-GW 425 receiving the session creation response message may transmit the session creation response message to the MME 420. The session creation response message transmitted by the S-GW 425 to the MME 420 may include slice information included in the session creation response message received in step 9.

Step 11: The MME 420 receiving the session creation response message in step 10 may transmit a Bearer Setup request message or a "Downlink NAS transport with PDN Connectivity Accept" message to the E-UTRA base station 415. The message transmitted by the MME 420 to the E-UTRA base station 415 may include slice information included in the session creation response message received in step 10.

Step 12: In step 11, the E-UTRA base station 415 receiving the Bearer Setup request message or the "Downlink NAS transport with PDN Connectivity Accept" message sends an RRC connection reconfiguration message or RRC Direct Transfer to the terminal 410 You can send a message. The message transmitted by the E-UTRA base station 415 to the terminal 410 may include slice information included in the message received in step 11.

Upon receiving the RRC connection reconfiguration message or the RRC Direct Transfer message, the terminal 410 may store S-NSSAI, which is slice information included in the message, and a PLMN ID using the S-NSSAI. The slice information may be included in the message in the form of PCO.

Step 13: In step 12, the terminal 410 receiving the RRC connection reconfiguration message may transmit an RRC connection reconfiguration complete message to the E-UTRA base station 415.

Step 14: In step 13, the E-UTRA base station 415 receiving the RRC connection reconfiguration complete message may transmit a Bearer Setup response message to the MME 420.

Step 15: In step 12, the terminal 410 receiving the RRC Direct Transfer message can transmit a Direct Transfer message to the E-UTRA base station 415.

Step 16: In step 15, the E-UTRA base station 415 receiving the Direct Transfer message can transmit a PDN Connectivity Complete message to the MME 420.

As illustrated in FIG. 4, the terminal according to an embodiment of the present invention may access the EPS network to establish a PDN connection and transmit and receive data. The terminal can move to the 5GS network, where the terminal can provide the 5GS network with PDN connection related information established in the EPS network. 10 illustrates a process in which a terminal moves to a 5G network and performs a registration procedure according to an embodiment of the present invention. In more detail, the terminals 260, 370, and 1010 may move to 5GS and send a registration request message to the AMFs 250, 360, and 1020. The registration request message may include information related to PDN connection established in the EPS network. The PDN connection-related information may include Requested NSSAI, which is slice information requested by the terminal, and other slice information (eg, PLMN ID, indication, mapping information, etc. in which S-NSSAI included in Requested NSSAI is used). The Requested NSSAI may consist of one or more S-NSSAI. The Registration Request message may be transmitted to the AMF 250, 360, 1020 via NG-RAN (255, 365, 1015). Various methods of PDN connection-related information included in the Registration Request message may exist.

Hereinafter, in the case of Local Breakout roaming (that is, corresponding to the embodiment of FIG. 2), an example of a method of providing PDN connection-related information established in EPS according to an embodiment of the present invention to a 5GS network will be described.

According to an embodiment, in the case of [LB Embodiment 1] in Step 9 of FIG. 4, the terminals 260 and 1010 according to the embodiment of the present invention pass through the NG-RANs 255 and 1015 and AMFs 250 and 1020 The Registration Request message sent to) may include the S-NSSAI a received in step 12 of FIG. 4 as the Requested NSSAI, and the PLMN ID, that is, the VPLMN ID , in which the S-NSSAI a is used.

According to an embodiment, in the case of [LB Embodiment 2] in Step 9 of FIG. 4, the terminals 260 and 1010 according to the embodiment of the present invention pass through the NG-RANs 255 and 1015 to AMFs 250 and 1020 The Registration Request message sent to) may include S-NSSAI a received in step 12 of FIG. 4 as the requested NSSAI, and mapping information (S-NSSAI 1, S-NSSAI a) corresponding to the S-NSSAI a and the A PLMN ID in which S-NSSAI a is used, that is, a VPLMN ID may be included.

If the AMF (250, 1020) according to the embodiments of [LB Embodiment 1] and [LB Embodiment 2] contains information allocated by EPS in a terminal ID (eg, 5G-GUTI or GUTI or SUPI) Alternatively, if the VPLMN ID is included in the received Registration Request message, it can be seen that the Requested NSSAI included in the Registration Request received from the terminal is composed of S-NSSAI values used in the VPLMN.

According to an embodiment, in the case of [LB Embodiment 3] in Step 9 of FIG. 4, the terminals 260 and 1010 according to the embodiment of the present invention pass through the NG-RANs 255 and 1015 to AMFs 250 and 1020 The Registration Request message sent to) may include the S-NSSAI 1 received in step 12 of FIG. 4 as the requested NSSAI, and may include the PLMN ID used in the S-NSSAI 1, that is, the HPLMN ID .

According to an embodiment, in the case of [LB Embodiment 4] in Step 9 of FIG. 4, the terminals 260 and 1010 according to the embodiment of the present invention pass through the NG-RANs 255 and 1015 to AMFs 250 and 1020 The Registration Request message sent to) may include S-NSSAI 1 received in step 12 of FIG. 4 as the requested NSSAI, and mapping information (S-NSSAI 1, S-NSSAI a) corresponding to the S-NSSAI 1 and the PLMN ID in which S-NSSAI 1 is used, that is, HPLMN ID may be included.

If the AMF (250, 1020) according to the embodiments of [LB Embodiment 3] and [LB Embodiment 4] contains information allocated by EPS in the terminal ID (eg, 5G-GUTI or GUTI or SUPI) Or, if the HPLMN ID is included in the received Registration Request message, it can be seen that the Requested NSSAI included in the Registration Request received from the terminal is composed of S-NSSAI values used in the HPLMN.

According to an embodiment, in the case of [LB Embodiment 5] of Step 9 of FIG. 4, the terminals 260 and 1010 according to the embodiment of the present invention pass through the NG-RANs 255 and 1015 to AMFs 250 and 1020 The Registration Request message sent to) may not include slice-related information. That is, the Requested NSSAI may not be included in the Registration Request message.

The AMF (250, 1020) according to the embodiment of [LB Embodiment 5], if the terminal ID (for example, 5G-GUTI or GUTI or SUPI) includes information allocated from the EPS, the terminal has moved in the EPS It can be seen that it is a terminal. AMF (250, 1020) may obtain the PDN connection information set by the terminal in the EPS from the UDM (210, 1030) and S-NSSAI information supported by the PDN connection. The AMF (250, 1020) may include the S-NSSAI supported by the PDN connection obtained from the UDMs (210, 1030) in the Registration Accept message sent to the terminal in the Allowed NSSAI.

Hereinafter, in the case of Home-Routed roaming (that is, corresponding to the embodiment of FIG. 3), an example of a method of providing PDN connection-related information established in EPS according to an embodiment of the present invention to a 5GS network will be described.

According to an embodiment, in the case of [HR Embodiment 1] of Step 9 of FIG. 4, the terminals 370 and 1010 according to the embodiment of the present invention pass through the NG-RANs 365 and 1015 and AMFs 360 and 1020 The Registration Request message sent to) may include S-NSSAI 1 received in step 12 of FIG. 4 as the requested NSSAI . When S-NSSAI 1 is included in the Registration Request message, the PDU session status of S-NSSAI 1 may be included in the Registration Request message.

According to an embodiment, in the case of [HR Embodiment 1] of Step 9 of FIG. 4, the terminals 370 and 1010 according to the embodiment of the present invention pass through the NG-RANs 365 and 1015 and AMFs 360 and 1020 The Registration Request message sent to) may include S-NSSAI 1 received in step 12 of FIG. 4 as a requested NSSAI, and may include an indication that the S-NSSAI 1 is a value used in HPLMN . When S-NSSAI 1 is included in the Registration Request message, the PDU session status of S-NSSAI 1 may be included in the Registration Request message.

According to an embodiment, in the case of [HR Embodiment 1] of Step 9 of FIG. 4, the terminals 370 and 1010 according to the embodiment of the present invention pass through the NG-RANs 365 and 1015 and AMFs 360 and 1020 The Registration Request message sent to) may include S-NSSAI 1 received in step 12 of FIG. 4 as a Requested NSSAI, and may include a PLMN ID in which the S-NSSAI 1 is used, that is, an HPLMN ID . When S-NSSAI 1 is included in the Registration Request message, the PDU session status of S-NSSAI 1 may be included in the Registration Request message.

If the AMF (360, 1020) according to the embodiment of [HR Embodiment 1] includes information allocated by the EPS in the terminal ID (eg, 5G-GUTI or GUTI or SUPI), or the received Registration Request message If the HPLMN ID is included in, or if the indication indicating the HPLMN value is included in the received registration request message, the requested NSSAI included in the registration request received from the terminal is configured with the S-NSSAI value used in the HPLMN. Able to know.

The AMF (360, 1020) may obtain the "subscribed slice (subscribed S-NSSAIs)" information of the terminal corresponding to the terminal ID from the UDM (310, 1030) in step 5 (1055) of FIG. The AMFs 360 and 1020 may compare Requested NSSAI received from the terminal 1010 and subscription slice information obtained from the UDM. If the S-NSSAI included in the requested NSSAI is also included in the subscription slice information, process 6 (1060) of FIG. 10 may be performed. Alternatively, without performing step 5 (1055) of FIG. 10, step 6 (1060) may be performed immediately. In addition, in step 6 (1060) of FIG. 10, the AMF (360, 1020) may send an NSSelection_Get request message to the NSSF 1025. In the NSSelection_Get request message, the subscription slice information of the terminal, the PLMN ID (ie, HPLMN ID) included in the terminal ID (for example, SUPI), and the HPLMN S-NSSAI value of the terminal receiving the session from the terminal (invention of the present invention) According to an embodiment of the present invention, S-NSSAI 1), may include the Requested NSSAI received from the terminal.

The NSSF 1025 is a VPLMN mapped with an HPLMN S-NSSAI value (eg, an HPLMN S-NSSAI value included in the Requested NSSAI) received from the AMF (360, 1020) (i.e., the serving PLMN the UE is currently connected to). VPLMN S-NSSAI can be used. The NSSF 1025 may determine Allowed NSSAI based on the subscription slice information of the terminal, the VPLMN S-NSSAI value determined by the NSSF, and the Requested NSSAI value. The Allowed NSSAI may be configured with one or more VPLMN S-NSSAI values available in the serving PLMN the UE is currently connected to. The NSSF 1025 may return the NSSelection_Get response message to the AMF 360, 1020. The NSSelection_Get response message may include Allowed NSSAI determined by NSSF and mapping information (Mapping Of Allowed NSSAI) corresponding thereto. Upon receiving the NSSelection_Get response message, the AMFs 360 and 1020 may return a Registration Accept message to the terminal 1010 in steps 7 (1065) and 8 (1070) of FIG. 10. The Registration Accept message may include Allowed NSSAI and Mapping Of Allowed NSSAI received from NSSF. Upon receiving the Registration Accept message, the terminal 1010 stores Allowed NSSAI and mapping information (Mapping Of Allowed NSSAI) included in the Registration Accept message, and manages (creates/modifies/deletes) the PDU session in the current Registration Area, and data It can be used to send and receive.

According to an embodiment, in the case of [HR Embodiment 1] of Step 9 of FIG. 4, the terminals 370 and 1010 according to the embodiment of the present invention pass through the NG-RANs 365 and 1015 and AMFs 360 and 1020 Request Requested NSSAI is not included in the Registration Request message sent to ), or the S-NSSAI value in Requested NSSAI can be set as unknown. In addition, the registration request message may include mapping information (S-NSSAI 1, unknown) . That is, the UE includes the S-NSSAI 1 received in step 12 of FIG. 4 as the HPLMN S-NSSAI value of the mapping information, and the VPLMN S-NSSAI value is set to unknown or does not include any value ( empty). When S-NSSAI 1 is included in the Registration Request message, the PDU session status of S-NSSAI 1 may be included in the Registration Request message.

The AMF (360, 1020) according to the embodiment of [HR Embodiment 1] is the "subscribed slice (subscribed S-NSSAIs ) of the terminal corresponding to the terminal ID from the UDM (310, 1030) in step 5 (1055) of FIG. )" information. AMF (360, 1020) may compare the S-NSSAI value used in the HPLMN received from the terminal and the subscription slice information obtained from the UDM. If the HPLMN S-NSSAI value received from the terminal is also included in the subscription slice information, process 6 (1060) of FIG. 10 may be performed. Alternatively, process 6(1060) may be performed without performing process 5(1055) of FIG. 10. AMF (360, 1020) may send an NSSelection_Get request message to NSSF (1025) (1055). In the NSSelection_Get request message, the subscription slice information of the terminal, the PLMN ID (ie, HPLMN ID) included in the terminal ID (eg, SUPI), the mapping information received from the terminal, and the HPLMN that the terminal received from the terminal establishes a session S-NSSAI value (according to an embodiment of the present invention, S-NSSAI 1), may include a Requested NSSAI received from the terminal.

NSSF 1025 is mapped to the HPLMN S-NSSAI value received from the AMF (360, 1020) (for example, the HPLMN S-NSSAI value included in the mapping information or the HPLMN S-NSSAI value that the terminal has a session with). The VPLMN S-NSSAI value usable in the VPLMN (ie, the serving PLMN the UE is currently connected to) may be determined. The NSSF 1025 may determine the allowed NSSAI based on the subscription slice information of the UE, the HPLMN S-NSSAI value included in the mapping information, the VPLMN S-NSSAI value determined by the NSSF, and the requested NSSAI value. The Allowed NSSAI may be configured with one or more VPLMN S-NSSAI values available in the serving PLMN the UE is currently connected to. The NSSF 1025 may return the NSSelection_Get response message to the AMFs 360 and 1020. The NSSelection_Get response message may include Allowed NSSAI determined by NSSF and mapping information (Mapping Of Allowed NSSAI) corresponding thereto. Upon receiving the NSSelection_Get response message, the AMF 1020 may return the Registration Accept message to the terminal 1010 in steps 7 (1065) and 8 (1070) of FIG. 10. The Registration Accept message may include Allowed NSSAI and mapping information (Mapping Of Allowed NSSAI) received from NSSF. Upon receiving the Registration Accept message, the terminal 1010 stores Allowed NSSAI and mapping information (Mapping Of Allowed NSSAI) included in the Registration Accept message, and manages (creates/modifies/deletes) the PDU session in the current Registration Area, data It can be used to send and receive.

According to an embodiment, in the case of [HR embodiment 2] in step 9 of FIG. 4, the terminals 370 and 1010 according to the embodiment of the present invention pass through the NG-RANs 365 and 1015 and AMFs 360 and 1020 The Registration Request message sent to) may not include slice-related information. That is, the Requested NSSAI may not be included in the Registration Request message.

AMF (360, 1020) according to the embodiment of [HR embodiment 2] is the terminal ID (for example, 5G-GUTI or GUTI or SUPI), if the information assigned in the EPS is included, the terminal has been moved in the EPS You can see that The AMF (360, 1020) may obtain the PDN connection information set by the UE in the EPS and the S-NSSAI information supported by the PDN connection from the UDM (1030). The AMF (360, 1020) may include the S-NSSAI supported by the PDN connection obtained from the UDMs (310, 1030) in the Registration Accept message sent to the terminals (370, 1010) in the Allowed NSSAI.

According to another embodiment of the present invention, an operation of determining Allowed NSSAI and Mapping of Allowed NSSAI may be performed in AMF 1020 rather than NSSF 1025. That is, process 6 (1060) of FIG. 10 may be processed as an AMF internal operation.

The terminal according to an embodiment of the present invention may store slice information in the form of PCO included in the message received in step 12 of FIG. 4 in the terminal. The slice information in the form of PCO received by the terminal may be a "S-NSSAI" value connected to a PDN connection, a " PLMN ID " or a "mapped slice" information in which the corresponding S-NSSAI is used. The UE compares the received slice information and slice policy information previously stored in the UE (eg, UE Route Selection Policy (URSP), Network Slice Selection Policy (NSSP), UE local policy, etc.), and determines whether the information matches. can do. Table 1 below shows an example of slice policy information stored in the terminal.

Application identifier Slice identifier (S-NSSAI) Application id #1 S-NSSAI 1 Application id #2 S-NSSAI 2 Application id #3 S-NSSAI 1, S-NSSAI 2 Matching all S-NSSAI 3

The slice policy information stored in the terminal includes an application installed in the terminal and slice information to be used to use each application. For example, in the case of Application id#1 of the terminal, it may be serviced using S-NSSAI 1. The terminal that wants to use Application id#1 can access the 5G network and perform the registration procedure. During the registration procedure, the terminal may transmit a registration request message to the network, and the registration request message may include slice information (S-NSSAI) to be used by the terminal in the form of a requested NSSAI. During the registration procedure, the terminal may receive Allowed NSSAI, which is slice information that the terminal can use by accessing the network from the network. When the UE transmits a PDU session establishment request message for Application id#1 using the Allowed NSSAI and slice policy information, the terminal may include S-NSSAI 1.

When the PCO received by the terminal includes the HPLMN ID as the "S-NSSAI" value (eg, S-NSSAI 1) and the "PLMN ID" in which the corresponding S-NSSAI is used, the terminal slice information stored in the terminal By using the terminal to access the EPS to create a PDN connection, it is possible to check the slice information mapped with the application being used.

If the application currently being used by the terminal is application id#1, the slice identified based on the slice policy information stored in the terminal may be S-NSSAI 1. In this case, it may be determined that the slice (S-NSSAI 1) checked based on the slice policy information stored in the terminal and the slice information (S-NSSAI 1) received by the PCO match. When generating the requested NSSAI and mapping information (Mapping of Requested NSSAI) in step 1 1035 of FIG. 10, the terminal may include the S-NSSAI 1 in the requested NSSAI or mapping information.

Or, if the application currently being used by the terminal is application id#2, the slice identified based on the slice policy information stored in the terminal may be S-NSSAI 2. In this case, it can be determined that the slice (S-NSSAI 2) checked based on the slice policy information stored in the terminal and the slice information (S-NSSAI 1) received by the PCO are inconsistent. When generating the requested NSSAI and mapping information (Mapping of Requested NSSAI) in step 1 1035 of FIG. 10, the UE may include the S-NSSAI 1 and S-NSSAI 2 in the requested NSSAI or mapping information.

VPLMN ID and "mapped slice information" as "S-NSSAI" value (for example, S-NSSAI a) and "PLMN ID" in which the corresponding S-NSSAI is used in the PCO received by the terminal (for example, { When S-NSSAI 1, S-NSSAI a}) is included, the terminal can check the slice information mapped to the application being used by generating the PDN connection by accessing the EPS using the slice policy information stored in the terminal. .

If the application currently being used by the terminal is application id#1, the slice identified based on the slice policy information stored in the terminal may be S-NSSAI 1. In this case, it can be determined that the slice (S-NSSAI 1) checked based on the slice policy information stored in the terminal matches the slice information ({S-NSSAI 1, S-NSSAI a}) received by the PCO. When generating the requested NSSAI and mapping information (Mapping of Requested NSSAI) in step 1 (1035) of FIG. 10, the terminal may include the S-NSSAI a in the requested NSSAI, and {S-NSSAI 1, S-NSSAI a} may be included in the mapping information.

Or, if the application currently being used by the terminal is application id#2, the slice identified based on the slice policy information stored in the terminal may be S-NSSAI 2. In this case, it may be determined that the slice (S-NSSAI 2) checked based on the slice policy information stored in the terminal and the slice information ({S-NSSAI 1, S-NSSAI a}) received by the PCO are inconsistent. When generating the requested NSSAI and mapping information (Mapping of Requested NSSAI) in step 1 (1035) of FIG. 10, the terminal may include the S-NSSAI a and the unknown indication in the Requested NSSAI, {S-NSSAI 1, S-NSSAI a} and {S-NSSAI 2, unknown (or empty)} may be included in the mapping information.

Referring to FIG. 10, in step 2 1040, the terminal 1010 may transmit a registration request message to the base station 1015 in order for the terminal to register with the communication system. In step 4 1050, the base station 1015 may transmit a registration request message to the AMF 1020 to be accessed.

The registration request message transmitted in steps 2 and 4 ((1040, 1050)) may include request slice information (Requested NSSAI) to be used after the terminal 1010 registers with the communication system. The request slice information is set slice information Based on (Configured NSSAI), the UE 1010 may determine in step 1 1035. The request slice information and the setup slice information may be composed of one or more S-NSSAI.

In step 5 1055, the AMF 1020 receiving the registration request message 1050 may acquire terminal subscription information from the UDM 1030. The terminal subscription information may include subscription slice information (subscribed S-NSSAIs) of the terminal 1010.

In step 6 (1060), the AMF (1020) is the request slice information received from the terminal 1010 in step 4 (1050), the subscription slice information received from the UDM (1030) in step 5 (1055) and the terminal (1010) After the terminal 1010 registers with the communication system based on the slice information available at the current location, the allowed slice information (Allowed NSSAI) may be determined.

Alternatively, in step 6 (1060), the AMF (1020) may request the NSSF 1025 to determine the permission slice information. To this end, the AMF 1020 requests the NSSF 1025 to request slice information received from the terminal 1010 in step 4 (1050) and subscription slice information and terminal 1010 received from the UDM 1030 in step 5 (1055). Can provide current location information. The NSSF 1025 determines available slice information (Allowed NSSAI) after the terminal 1010 registers with the communication system based on the information received from the AMF 1020 and slice information available at the current location of the terminal 1010. Can. The NSSF 1025 may return the permission slice information to the AMF 1020.

At this time, if there is no slice available after the UE registers with the communication system, the AMF 1020 to NSSF 1025 are for slices included in the request slice information received from the UE 1010 in step 4 (1050). Rejected slice information (rejected S-NSSAIs) may be generated, and allow slice information may be configured in various ways as follows.

According to one or more embodiments, the AMF 1020 or NSSF 1025 checks the subscription slice information of the terminal 1010, and if the subscription slice information includes a default slice (default S-NSSAI(s)) If present, the AMF 1020 or NSSF 1025 may include a default slice in the allowed slice information (Allowed NSSAI). According to an embodiment, if the default slice is not included in the subscription slice information, the AMF 1020 or NSSF 1025 does not set the subscription slice information to empty or does not send the subscription slice information to the terminal 1010 Can decide.

According to one or more embodiments, the AMF 1020 or NSSF 1025 may set subscription slice information to empty.

According to one or more embodiments, the AMF 1020 or NSSF 1025 may decide not to send subscription slice information to the terminal 1010.

In step 6 (1060), the AMF 1020, which has determined the allowed slice information and the rejected slice information (or obtained from NSSF 1025), sends a registration permission message to the terminal 1035 in step 7 (1065). At least one of the permission slice information and the reject slice information may be included. The registration permission message of the process 7 (1065) may be transmitted to the terminal 1010 in the process 8 (1070) via the base station 1015.

In step 8 (1070), the terminal 1010 receiving the registration permission message may check the permission slice information and/or rejection slice information included in the registration permission message, and perform the following operations.

According to one or more embodiments, if only the rejection slice information is included in the registration permission message received in step 8 (1070) and the permission slice information is not included, the terminal 1010 determines whether the terminal is in steps 1, 2, and 4 It can be seen that all request slices requested to the network are rejected through (1035, 1040, and 1050). Accordingly, the terminal 1010 may not request a PDU session until it receives permission slice information from the network. Alternatively, the terminal 1010 may not include slice information (S-NSSAI) when requesting a PDU session until it receives permission slice information from the network. The network (eg, SMF or AMF) that has received the PDU session request message that does not include the slice information (S-NSSAI) selects a default slice (default S-NSSAI) based on the subscription information of the terminal 1010 A PDU session can be created.

According to one or more embodiments, when the rejection slice information is included in the registration permission message received in step 8 (1070) and the permission slice information is set to empty, the terminal 1010 processes the terminal. It can be seen through 1, 2, and 4 (1035, 1040, and 1050) that all request slices requested to the network are rejected. Accordingly, the terminal 1010 may not request a PDU session until it receives permission slice information from the network. Alternatively, the terminal 1010 may not include slice information (S-NSSAI) when requesting a PDU session until it receives permission slice information from the network. The network (eg, SMF or AMF) that has received the PDU session request message that does not include the slice information (S-NSSAI) selects a default slice (default S-NSSAI) based on the subscription information of the terminal 1010 A PDU session can be created.

According to one or more embodiments, the reject slice information in the registration permission message received in step 8 (1070) is the request slice requested by the terminal 1010 to the network through steps 1, 2 and 4 (1035, 1040 and 1050) If it includes all (that is, all request slices of the terminal have been rejected), and the slice information (S-NSSAIs) is included in the allowed slice information, the terminal 1010 is the process 1, 2 and 4 (1035, 1040) And 1050), it can be seen that all request slices requested to the network have been rejected. In addition, the terminal 1010 may use the permission slice information received by the terminal 1010 in step 8 (1070) for requesting a PDU session until new permission slice information is received from the network. According to an embodiment of the present disclosure, when requesting a PDU session, the UE 1010 may include slice information (S-NSSAI) of the allowed slice information received in step 8 (1070) in the PDU session request message.

7 illustrates a configuration of a base station in a wireless communication system according to various embodiments of the present disclosure. The configuration illustrated in FIG. 7 may be understood as a configuration of the base stations 140, 245, and 340 of EPS or the base stations 150, 255, 365 of 5GS. The terms'??','??', and the like used below refer to a unit that processes at least one function or operation, which may be implemented by hardware or software, or a combination of hardware and software.

Referring to FIG. 7, the base station includes a wireless communication unit 710, a backhaul communication unit 720, a storage unit 730, and a control unit 740.

The wireless communication unit 710 performs functions for transmitting and receiving signals through a wireless channel. For example, the wireless communication unit 710 performs a conversion function between a baseband signal and a bit stream according to a physical layer standard of the system. For example, during data transmission, the wireless communication unit 710 generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the wireless communication unit 710 restores the received bit stream through demodulation and decoding of the baseband signal.

In addition, the wireless communication unit 710 up-converts the baseband signal to a radio frequency (RF) band signal, transmits it through an antenna, and downconverts the RF band signal received through the antenna to a baseband signal. To this end, the wireless communication unit 710 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), and an analog to digital converter (ADC). Also, the wireless communication unit 710 may include a plurality of transmission/reception paths. Furthermore, the wireless communication unit 710 may include at least one antenna array composed of a plurality of antenna elements.

In terms of hardware, the wireless communication unit 710 may be composed of a digital unit (digital unit) and an analog unit (analog unit), the analog unit is a plurality of sub-units (sub-units) according to the operating power, operating frequency, etc. It can be composed of. The digital unit may be implemented with at least one processor (eg, a digital signal processor (DSP)).

The wireless communication unit 710 transmits and receives signals as described above. Accordingly, all or part of the wireless communication unit 710 may be referred to as a'transmitter', a'receiver', or a'transceiver'. In addition, in the following description, transmission and reception performed through a wireless channel are used in a sense including processing performed as described above by the wireless communication unit 710.

The backhaul communication unit 720 provides an interface for communicating with other nodes in the 5GS network or EPS network. That is, the backhaul communication unit 720 converts a bit stream transmitted from a base station to another node, for example, another access node, another base station, an upper node, a core network, into a physical signal, and converts a physical signal received from another node. Convert to bit string.

The storage unit 730 stores data such as a basic program, an application program, and setting information for the operation of the base station. The storage unit 730 may be configured as a volatile memory, a nonvolatile memory, or a combination of a volatile memory and a nonvolatile memory. In addition, the storage unit 730 provides stored data at the request of the control unit 740.

The control unit 740 controls overall operations of the base station. For example, the control unit 740 transmits and receives signals through the wireless communication unit 710 or through the backhaul communication unit 720. In addition, the control unit 740 writes and reads data in the storage unit 730. In addition, the control unit 740 may perform functions of a protocol stack required by a communication standard. According to another implementation, the protocol stack may be included in the wireless communication unit 710. To this end, the control unit 740 may include at least one processor. According to various embodiments, the control unit 740 may include functions for network slicing interworking. Here, the functions for network slicing interworking are instruction sets or codes stored in the storage unit 730, or are at least temporarily stored instructions/codes stored in the control unit 740 or storage spaces storing instructions/codes, Alternatively, it may be a part of circuitry constituting the control unit 740.

According to various embodiments, the control unit 740 receives a Bearer Setup request message including slice information or a Downlink NAS transport with PDN Connectivity Accept message for network slicing interworking, and an RRC connection reconfiguration message that may include slice information, or The RRC Direct Transfer message may be controlled to be transmitted to the terminal, and, for example, the controller 740 may control the base station to perform operations according to the various embodiments described above.

8 illustrates a configuration of a terminal in a wireless communication system according to various embodiments of the present disclosure. The configuration illustrated in FIG. 8 may be understood as the configuration of the terminals 155, 260, 370. The terms'??','??', and the like used below refer to a unit that processes at least one function or operation, which may be implemented by hardware or software, or a combination of hardware and software.

Referring to FIG. 8, the terminal includes a communication unit 810, a storage unit 820, and a control unit 830.

The communication unit 810 performs functions for transmitting and receiving signals through a wireless channel. For example, the communication unit 810 performs a conversion function between a baseband signal and a bit stream according to a physical layer standard of the system. For example, during data transmission, the communication unit 810 generates complex symbols by encoding and modulating a transmission bit string. In addition, upon receiving data, the communication unit 810 restores the received bit stream through demodulation and decoding of the baseband signal. In addition, the communication unit 810 upconverts the baseband signal to an RF band signal, transmits it through an antenna, and downconverts the RF band signal received through the antenna to a baseband signal. For example, the communication unit 810 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC.

Also, the communication unit 810 may include a plurality of transmission/reception paths. Furthermore, the communication unit 810 may include at least one antenna array composed of a plurality of antenna elements. In terms of hardware, the communication unit 810 may be composed of digital circuits and analog circuits (eg, radio frequency integrated circuit (RFIC)). Here, the digital circuit and the analog circuit may be implemented in one package. Also, the communication unit 810 may include a plurality of RF chains. Furthermore, the communication unit 810 may perform beamforming.

In addition, the communication unit 810 may include different communication modules to process signals of different frequency bands. Furthermore, the communication unit 810 may include a plurality of communication modules to support a plurality of different wireless access technologies. For example, different wireless access technologies include Bluetooth low energy (BLE), Wi-Fi (Wireless Fidelity), WiGig (WiFi Gigabyte), cellular networks (eg Long Term Evolution (LTE), 5G network, etc.) Also, different frequency bands may include a super high frequency (SHF) band (eg, 2.5 GHz, 5 Ghz) and a millimeter wave (eg, 60 GHz) band.

The communication unit 810 transmits and receives signals as described above. Accordingly, all or part of the communication unit 810 may be referred to as a'transmission unit', a'reception unit', or a'transmission and reception unit'. In addition, in the following description, transmission and reception performed through a wireless channel are used in a sense including processing performed as described above by the communication unit 810.

The storage unit 820 stores data such as a basic program, an application program, and setting information for the operation of the terminal. The storage unit 820 may be configured of volatile memory, nonvolatile memory, or a combination of volatile memory and nonvolatile memory. And the storage unit 820 provides the stored data at the request of the control unit 830.

The control unit 830 controls overall operations of the terminal. For example, the control unit 830 transmits and receives signals through the communication unit 810. In addition, the control unit 830 writes and reads data in the storage unit 820. In addition, the control unit 830 may perform functions of the protocol stack required by the communication standard. To this end, the control unit 830 may include at least one processor or a micro processor, or may be a part of the processor. Also, a part of the communication unit 810 and the control unit 830 may be referred to as a communication processor (CP). According to various embodiments, the control unit 830 may include a function for supporting network slicing. Here, the function for supporting network slicing is a set of instructions or codes stored in the storage unit 830, or at least temporarily a storage space storing instructions/codes or instructions/codes residing in the control unit 830, Alternatively, it may be a part of circuitry constituting the control unit 830.

According to various embodiments, the control unit 830 may establish a PDN connection while the UE accesses the MME 420 through the E-UTRA base station 415 to exchange signaling messages with the PGW-C 430 located in the EPS. Control, and when the PDN connection establishment is completed, the terminal 410 may send uplink data to the PGW-U 435 or receive downlink data from the PGW-U 435. Can be controlled. In particular, the control unit 830 may receive an RRC connection reconfiguration message or an RRC Direct Transfer message from the base station, and store the slice information included in the message, S-NSSAI and PLMN ID using the S-NSSAI. For example, the control unit 830 may control the terminal to perform operations according to various embodiments described above.

9 illustrates a configuration of a core network object in a wireless communication system according to various embodiments of the present disclosure. The configuration illustrated in FIG. 9 includes HSS+UDM (110, 210, 310), PCF+PCRF (115, 215, 220, 315), SMF+PGW-C (120, 225, 320), UPF of FIGS. +PGW-U (125, 230, 325), SGW (130, 235, 330), MME (135, 240, 335), AMF (145, 250, 360), UPF (355), v-SMF (350) , It can be understood as a configuration of a device having at least one function of vPCF 345. The terms'??','??', and the like used below refer to a unit that processes at least one function or operation, which may be implemented by hardware or software, or a combination of hardware and software.

Referring to FIG. 9, the core network object includes a communication unit 910, a storage unit 920, and a control unit 930.

The communication unit 910 provides an interface for performing communication with other devices in the network. That is, the communication unit 910 converts a bit stream transmitted from the core network object to another device into a physical signal, and converts a physical signal received from another device into a bit stream. That is, the communication unit 910 may transmit and receive signals. Accordingly, the communication unit 910 may be referred to as a modem, a transmitter, a receiver, or a transceiver. At this time, the communication unit 910 allows the core network object to communicate with other devices or systems through a backhaul connection (for example, a wired backhaul or a wireless backhaul) or a network.

The storage unit 920 stores data such as a basic program, an application program, and configuration information for the operation of the core network object. The storage unit 920 may be configured of volatile memory, nonvolatile memory, or a combination of volatile memory and nonvolatile memory. Then, the storage unit 920 provides the stored data at the request of the control unit 930.

The control unit 930 controls overall operations of the core network object. For example, the control unit 930 transmits and receives signals through the communication unit 910. In addition, the control unit 930 writes and reads data in the storage unit 920. To this end, the control unit 930 may include at least one processor. According to various embodiments, the control unit 930 may include a function for supporting network slicing. Here, the function for supporting network slicing is implemented by a set of instructions or codes stored in the storage unit 920, and at least temporarily stores instructions/codes or instructions/codes stored in the controller 930. It may be a space or a part of circuitry constituting the control unit 930.

According to various embodiments, the controller 930 receives a session creation request message, transmits a Nudm_SDM_Get request message, receives a Nudm_SDM_Get response message, and receives S received by subscribed S-NNSAIs and SMF-PGW-C itself -Comparing the NSSAI information, and selecting the S-NSSAI to be used, and controlling the function to transmit to the terminal by including it in the session creation response message, the control unit 930 is the core network object according to the various embodiments described above You can control to perform the actions.

The methods according to the embodiments described in the claims or the specification of the disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented in software, a computer readable storage medium storing 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. The one or more programs include instructions that cause an electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.

Such programs (software modules, software) include random access memory, non-volatile memory including flash memory, read only memory (ROM), and electrically erasable programmable ROM. (electrically erasable programmable read only memory, EEPROM), magnetic disc storage device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs) or other forms It can be stored in an optical storage device, a magnetic cassette. Or, it may be stored in a memory composed of a combination of some or all of them. Also, a plurality of configuration memories may be included.

In addition, the program may be through a communication network composed of a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WAN), or a storage area network (SAN), or a combination thereof. It can be stored in an attachable storage device that can be accessed. Such a storage device can access a device performing an embodiment of the present disclosure through an external port. In addition, a separate storage device on the communication network may access a device performing an embodiment of the present disclosure.

In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in singular or plural according to the specific embodiments presented. However, the singular or plural expressions are appropriately selected for the situation presented for convenience of description, and the present disclosure is not limited to the singular or plural components, and even the components expressed in plural are composed of singular or expressed in singular. Even the configured components may be configured in plural.

On the other hand, in the detailed description of the present disclosure, specific embodiments have been described, but various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be determined not only by the scope of claims to be described later, but also by the scope and equivalents of the claims.

Claims (16)

In the method of operating the core network device in a wireless communication system,
Receiving a session creation request message;
Sending a Nudm_SDM_Get request message;
Receiving a Nudm_SDM_Get response message including subscription slice information subscribed to by the terminal;
Comparing the subscription slice information with slice information that can be provided by the core network device;
Selecting slice information to be transmitted to the terminal based on the comparison result;
And transmitting the selected slice information to the terminal.
According to claim 1, Based on the comparison result, the process of selecting slice information to be transmitted to the terminal,
If there is no slice that can be provided by the core network device or if there is no slice that matches the received subscription slice among one or more slices that can be provided by the core network device, the default slice of the received subscription slice is A method that involves selecting or selecting no slices.
According to claim 1, Based on the comparison result, the process of selecting slice information to be transmitted to the terminal,
If there is one slice that the core network device can provide and the corresponding slice is included in the received subscription slice, or among two or more slices that the core network device can provide, a slice matching the received subscription slice In the case of one, a method of selecting one slice included in the received subscription slice while being provided by the core network device.
According to claim 1, Based on the comparison result, the process of selecting slice information to be transmitted to the terminal,
If there are two or more slices that can be provided by the core network device, and two or more of the slices are included in the received subscription slice, the received subscription while being able to be provided by the core network device based on a set operator policy And selecting one of two or more slices included in the slice.
In the core network device of the wireless communication system,
A communication unit performing communication with other devices in the core network;
Storage unit;
And at least one processor coupled to the communication unit and the storage unit,
The at least one processor
A session creation request message is received through the communication unit,
A Nudm_SDM_Get request message is transmitted through the communication unit,
A Nudm_SDM_Get response message including subscription slice information subscribed to by the terminal is received through the communication unit,
Compare the slice information and the slice information that can be provided by the core network device,
Based on the comparison result, slice information to be transmitted to the terminal is selected,
A core network device that transmits the selected slice information to the terminal through the communication unit.
The method of claim 5, wherein the at least one processor,
As a result of comparing the slice information that can be provided by the core network device with the subscription slice information, when there is no slice that can be provided by the core network device or one or more slices that the core network device can provide, If there is no slice matching the received subscription slice, a core network device is selected from among the received subscription slices or no slice is selected.
The method of claim 5, wherein the at least one processor,
As a result of comparing the subscription slice information and slice information that can be provided by the core network device, when there is one slice that can be provided by the core network device and the corresponding slice is included in the received subscription slice or the core network A core network that selects one slice included in the received subscription slice while being provided by the core network device when one of the two or more slices that can be provided by the device matches the received subscription slice. Device.
The method of claim 5, wherein the at least one processor,
As a result of comparing the slice information that can be provided by the core network device and the subscription slice information, there are two or more slices that can be provided by the core network device, and two or more of the slices are included in the received subscription slice. If possible, a core network device that selects one of two or more slices included in the received subscription slice while being provided by the core network device based on a set operator policy.
In the method of operating the core network device in a wireless communication system,
Receiving a session creation request message;
Sending a Nudm_SDM_Get request message;
Receiving a Nudm_SDM_Get response message including subscription slice information subscribed to by the terminal;
Transmitting an Nnssf_NSSelection_Get request message including the subscription slice information and a PLMN ID included in the ID of the terminal;
Receiving an Nnssf_NSSelection_Get response message that includes mapped slice information mapped to the subscription slice information and used by the VPLMN;
Comparing the mapped slice information with slice information that can be provided by the core network device;
Selecting slice information to be transmitted to the terminal based on the comparison result;
And transmitting the selected slice information to the terminal.
10. The method of claim 9, Based on the comparison result, the process of selecting slice information to be transmitted to the terminal,
If there is no slice that can be provided by the core network device or there is no slice that matches the received mapped slice among one or more slices that can be provided by the core network device, the received mapped slice is the default A method that involves selecting a slice or selecting no slices.
According to claim 1, Based on the comparison result, the process of selecting slice information to be transmitted to the terminal,
When the core network device can provide one slice and the corresponding slice is included in the received mapped slice, or the two or more slices that the core network device can provide match the received mapped slice And if there is only one slice, selecting a slice included in the received mapped slice while being provided by the core network device.
According to claim 1, Based on the comparison result, the process of selecting slice information to be transmitted to the terminal,
When there are two or more slices that can be provided by the core network device, and two or more of the slices are included in the received mapped slice, the core network device can provide the core network device and receive the received message based on a set operator policy. And selecting one of two or more slices included in the mapped slice.
In the core network device of the wireless communication system,
A communication unit performing communication with other devices in the core network;
Storage unit;
And at least one processor coupled to the communication unit and the storage unit,
The at least one processor
A session creation request message is received through the communication unit,
A Nudm_SDM_Get request message is transmitted through the communication unit,
A Nudm_SDM_Get response message including subscription slice information subscribed to by the terminal is received through the communication unit,
The Nnssf_NSSelection_Get request message including the subscription slice information and the PLMN ID included in the ID of the terminal is transmitted through the communication unit,
The Nnssf_NSSelection_Get response message including the mapped slice information used in the VPLMN is mapped to the subscription slice information through the communication unit, and is received.
Compare the slice information mapped to the slice information that can be provided by the core network device,
Based on the comparison result, slice information to be transmitted to the terminal is selected,
A core network device that transmits the selected slice information to the terminal through the communication unit.
The method of claim 13, wherein the at least one processor,
As a result of comparing the mapped slice information and slice information that can be provided by the core network device, when there is no slice that can be provided by the core network device or one or more slices that can be provided by the core network device If there is no slice matching the received mapped slice, a core network device is selected from among the received mapped slices or no slice is selected.
The method of claim 13, wherein the at least one processor,
As a result of comparing the mapped slice information and slice information that can be provided by the core network device, when there is one slice that can be provided by the core network device and the corresponding slice is included in the received mapped slice, or If there is one slice matching the received mapped slice among two or more slices that the core network device can provide, one slice included in the received mapped slice while being provided by the core network device is Core network device of choice.
The method of claim 13, wherein the at least one processor,
As a result of comparing the mapped slice information with slice information that can be provided by the core network device, there are two or more slices that can be provided by the core network device, and two or more slices of the slices are received by the mapped slice. If included in the core network device to select one of the two or more slices included in the received mapped slice while being provided by the core network device based on the established operator policy.

Images