Network node, method and program using network node

Abstract

To control network control network slice selection.SOLUTION: A network node includes a controller configured to store configuration data defining whether to allow switching of a network slice, determine whether to switch the network slice on the basis of the configuration data, and switch the network slice from a first network slice to a second network slice in response to the determination.SELECTED DRAWING: Figure 10

Description

[Technical Field]

[0001] The present disclosure relates to a network node, a method by the network node, and a program, and in particular to a network node, a method by the network node, and a program for controlling network slice switching. [Background technology]

[0002] The Third Generation Partnership Project (3GPP (registered trademark)) defines network slicing, a technology that virtually divides a network and controls traffic at a fine granularity for each application by implementing bandwidth restrictions and priority control.

[0003] A virtually divided network is called a network slice, and an identifier called S-NSSAI (Single-Network Slice Selection Assistance Information) is assigned to the network slice. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TS 23.501 V18.4.0 (2023-12) Summary of the Invention [Problem to be solved by the invention]

[0005] Non-Patent Document 1 describes network slice replacement. In network slice replacement, a specific network slice is switched to an alternative network slice. Network slice replacement is triggered by the S-NSSAI corresponding to the network slice before the switch becoming unavailable or congestion occurring in the network slice before the switch.

[0006] In network slice replacement, an alternative network slice is selected by the network. In other words, network slice replacement can be said to correspond to network controlled network slice selection.

[0007] Non-Patent Document 1 only describes that network slice replacement is performed in the above-mentioned cases, but does not describe controlling network slice selection by network control.

[0008] The present disclosure provides a technique for controlling network-controlled network slice selection based on pre-configured configuration data. [Means for solving the problem]

[0009] In order to achieve the above object, a network node according to an embodiment is a network node including a control unit, and the control unit is configured to store configuration data defining whether or not to allow switching of a network slice, determine whether or not to switch the network slice based on the configuration data, and switch the network slice from a first network slice to a second network slice in accordance with the determination.

[0010] Further, a method according to an embodiment is a method executed by a network node, and includes storing configuration data defining whether or not to allow switching of a network slice, determining whether or not to switch the network slice based on the configuration data, and switching the network slice from a first network slice to a second network slice in accordance with the determination.

[0011] According to the above configuration, it is possible to control the switching of network slices in accordance with configuration data that defines whether or not the switching of network slices is permitted. Note that the above configuration may achieve other effects instead of or in addition to the above effect. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is a diagram illustrating a configuration of a communication system according to a first embodiment. [Figure 2] FIG. 2 is a block diagram showing the physical configuration of a network node according to the first embodiment. [Figure 3] FIG. 2 is a block diagram showing the logical configuration of a network node according to the first embodiment. [Figure 4] 2 is a block diagram showing the physical configuration of the terminal device according to the first embodiment. FIG. [Figure 5] 2 is a block diagram showing the logical configuration of a terminal device according to the first embodiment. FIG. [Figure 6] FIG. 1 is a diagram illustrating an overview of a network slice according to a first embodiment. [Figure 7] 4 is a flowchart showing a registration procedure according to the first embodiment. [Figure 8] 10 is a flowchart showing the procedure for switching network slices according to the first embodiment. [Figure 9] A diagram showing network-controlled network slice selection-related subscription data in the first embodiment. [Figure 10]1 is a flowchart showing a procedure for performing network slice selection according to the first embodiment. [Figure 11] 1 is a flowchart showing a procedure for performing network slice selection according to the first embodiment. [Figure 12] A diagram showing network-controlled network slice selection-related subscription data in the second embodiment. [Figure 13] 10 is a flowchart showing the procedure for performing network slice selection according to the second embodiment. [Figure 14] 10 is a flowchart showing the procedure for performing network slice selection according to the second embodiment. [Figure 15] 10 is a flowchart showing the procedure for performing network slice selection according to the third embodiment. [Figure 16] 10 is a flowchart showing the procedure for performing network slice selection according to the fourth embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. In this specification and drawings, elements that can be similarly described will be designated by the same reference numerals, and redundant description will be omitted.

[0014] The embodiments described below are merely examples of configurations that can realize the present invention. Each of the following embodiments can be modified or changed as appropriate depending on the configuration of the device to which the present invention is applied and various conditions. Not all of the combinations of elements included in each of the following embodiments are necessarily essential for realizing the present invention, and some of the elements can be omitted as appropriate. Therefore, the scope of the present invention is not limited to the configurations described in each of the following embodiments. As long as there are no mutual contradictions, configurations that combine multiple configurations described in the following embodiments can also be adopted.

[0015] 1. First embodiment 1.1 Communication Systems The configuration of a communication system 1 according to an embodiment will be described with reference to Fig. 1. As shown in Fig. 1, the communication system 1 includes a network node 10, a terminal apparatus (Terminal Apparatus) 20, and a RAN node (Base Station Apparatus) 30. The network node 10 is connected to a data network (DN) 40. The DN 40 includes a network such as the Internet. The communication system 1 is configured in accordance with predetermined technical specifications (TS). For example, the communication system 1 may comply with technical specifications defined by 3GPP (e.g., 5G, 5G Advanced, 6G, etc.).

[0016] In the communication system 1, for example, in accordance with the 5G NR specification, communication is performed between each of the network nodes 10 described below. Also, communication is performed between the terminal device 20, the RAN node 30, and the network node 10. The section between the terminal device 20 and the RAN node 30 is a wireless section.

[0017] The network node 10 constitutes a core network. The network node 10 includes an Access and Mobility Management Function (AMF) 10a, a User Plane Function (UPF) 10b, a Unified Data Management (UDM) / Unified Data Repository (UDR) 10c, an Application Function (AF) 10d, a Network Slice Selection Function (NSSF) 10e, a Session Management Function (SMF) 10f, and a Policy Control Function (PCF) 10g.

[0018] The network nodes 10 are not limited to network nodes such as the AMF 10a described above, but may include other network nodes that are defined or will be defined in the 3GPP technical specifications. Also, some of the network nodes 10, such as the AF 10d, do not necessarily constitute a core network. Such network nodes 10 are located outside the communication system 1 and communicate with network nodes 10 within the communication system 1 through the DN 40.

[0019] In the communication system 1, a user plane where user data is transmitted and received and a control plane where control data is transmitted and received are configured separately. That is, the communication system 1 supports C / U separation. The user plane is called the U-plane, and the control plane is called the C-plane.

[0020] The terminal device 20 may be a device that wirelessly communicates with the RAN node 30, and may be, for example, user equipment (UE) that operates in accordance with the 3GPP 5G NR specifications. The terminal device 20 may also be any other device that is or will be defined in the 3GPP technical specifications.

[0021] The terminal device 20 may be, for example, a mobile phone terminal such as a smartphone, a tablet terminal, a laptop PC, a communication module, a communication card, or an IoT device such as a surveillance camera or a robot. The terminal device 20 may be a vehicle (e.g., a car, a train, etc.) or a device provided therein. The terminal device 20 may be a transport vehicle other than a vehicle (e.g., a ship, an airplane, etc.) or a device provided therein. The terminal device 20 may be a sensor or a device provided therein. The terminal device 20 may also be referred to as a terminal, a mobile station, a mobile terminal, a mobile device, a mobile unit, a subscriber station, a subscriber terminal, a subscriber device, a subscriber unit, a wireless station, a wireless terminal, a wireless device, a wireless unit, a remote station, a remote terminal, a remote device, a remote unit, or the like. The terminal device 20 may be a device adapted to one or more of enhanced Mobile Broadband (eMBB), Ultra-Reliable and Low Latency Communications (URLLC), and Massive Machine Type Communications (mMTC).

[0022] The RAN node 30 forms a radio access network (RAN) and manages at least one cell. A cell constitutes the smallest unit of a communication area. For example, one cell belongs to one frequency (e.g., carrier frequency) and is composed of one component carrier. The term "cell" may refer to wireless communication resources and may also refer to a communication target of the terminal device 20. The RAN node 30 wirelessly communicates with the terminal device 20 located in its own cell in the U-plane and C-plane. In other words, the RAN node 30 terminates the U-plane protocol and C-plane protocol for the terminal device 20.

[0023] The RAN node 30 communicates with the network node 10 in the U-plane and the C-plane. More specifically, the RAN node 30 connects to the AMF 10a via an NG-C interface (not shown) in the C-plane, and connects to the UPF 10b via an NG-U interface (not shown) in the U-plane.

[0024] The RAN node 30 may be, for example, a gNB that provides a U-plane and a C-plane conforming to the 3GPP 5G NR specifications to the terminal device 20 and connects to the 3GPP 5GC (5G Core Network). Alternatively, the RAN node 30 may be any other device that is specified or will be specified in the 3GPP technical specifications.

[0025] Next, the physical configuration of the network node 10 will be described with reference to Fig. 2. As shown in Fig. 2, the network node 10 includes, as hardware elements, a processor 101, a memory 102, and a transceiver 103. The above-mentioned elements provided in the network node 10 are connected to each other by an internal bus. Note that the network node 10 may include hardware elements other than the elements shown in Fig. 2.

[0026] The processor 101 is a computing element that realizes various functions of the network node 10. The processor 101 may be a system-on-a-chip (SoC) that includes elements such as a central processing unit (CPU), a graphics processing unit (GPU), and a memory controller.

[0027] The memory 102 is configured by at least one storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk drive (HDD), or a solid state drive (SSD). The memory 102 is an element that temporarily or permanently stores programs and data used to execute various processes in the network node 10. The programs include one or more instructions for operating the network node 10. The processor 101 implements the functions of the network node 10 by loading and executing the programs stored in the memory 102 in the memory 102 and / or a system memory (not shown).

[0028] The transceiver 103 transmits and receives signals to and from other network nodes 10 and RAN nodes 30 .

[0029] Next, the logical configuration of the network node 10 will be described with reference to Fig. 3. As shown in Fig. 3, the network node 10 includes, as functional blocks, a control unit 110 and a communication unit 120. The communication unit 120 includes at least one transmission unit 111 and at least one reception unit 122.

[0030] The control unit 110 may include at least one processor 101 and at least one memory 102. In other words, the control unit 110 may be realized by the processor 101 and the memory 102. The control unit 110 executes various control processes in the network node 10. For example, the control unit 110 controls communication with other nodes (e.g., other network nodes 10 and RAN node 30) via the communication unit 120. That is, the control unit 110 controls transmission and reception of data / information / messages via the communication unit 120.

[0031] The communication unit 120 includes the transceiver 103. In other words, the communication unit 120 is realized by the transceiver 103. The communication unit 120 communicates with other network nodes 10 and RAN nodes 30 by transmitting and receiving signals to and from the other network nodes 10 and RAN nodes 30.

[0032] The control unit 110 operates to execute various processes of the network node 10 of this embodiment.

[0033] Next, the physical configuration of the terminal device 20 will be described with reference to Fig. 4. As shown in Fig. 4, the terminal device 20 includes, as hardware elements, a processor 201, a memory 202, an input / output interface 203, a transceiver 204, and an antenna 205. The above elements provided in the terminal device 20 are connected to each other by an internal bus. Note that the terminal device 20 may have hardware elements other than the elements shown in Fig. 4.

[0034] The processor 201 is a computing element that realizes various functions of the terminal device 20. The processor 201 may be a CPU, and may further include other processors such as a GPU.

[0035] The memory 202 is composed of at least one storage medium such as a RAM. The memory 202 is an element that temporarily or permanently stores programs and data used to execute various processes in the terminal device 20. The programs include one or more instructions for operating the terminal device 20. The processor 201 implements the functions of the terminal device 20 by loading the programs stored in the memory 202 into the memory 202 and / or a system memory (not shown) and executing them.

[0036] The input / output interface 203 is an interface that accepts operations on the terminal device 20 and supplies them to the processor 201, and also presents various information to the user. The input / output interface 203 is, for example, a touch panel.

[0037] The transceiver 204 is a circuit that performs various signal processing to realize wireless communication, and includes a baseband processor and an RF circuit. The transceiver 204 transmits and receives wireless signals to and from the RAN node 30 via an antenna 205.

[0038] Next, the logical configuration of the terminal device 20 will be described with reference to Fig. 5. As shown in Fig. 5, the terminal device 20 includes, as functional blocks, a control unit 210 and a communication unit 220. The communication unit 220 includes at least one transmission unit 121 and at least one reception unit 122.

[0039] The control unit 210 may include at least one processor 201 and at least one memory 202. In other words, the control unit 210 may be realized by the processor 201 and the memory 202. The control unit 210 executes various control processes in the terminal device 20. For example, the control unit 210 controls wireless communication with the RAN node 30 via the communication unit 220. That is, the control unit 210 controls transmission and reception of data / information / messages via the communication unit 220.

[0040] The communication unit 220 includes a transceiver 204 and an antenna 205. In other words, the communication unit 220 is realized by the transceiver and the antenna 205. The communication unit 220 wirelessly communicates with the RAN node 30 by transmitting and receiving radio signals to and from the RAN node 30.

[0041] The control unit 210 operates to execute various processes of the terminal device 20 of this embodiment.

[0042] 1.2 Network Slicing Next, an overview of network slices will be described with reference to Fig. 6. Each network slice is established by virtually dividing the network so that a terminal device 20 can communicate with a DN 40 via a RAN node 30 and a network node (UPF) 10. In a network slice, data is conveyed by establishing a protocol data unit (PDU) session between the terminal device 20 and the network node 10.

[0043] As shown in Figure 6, multiple network slices are established between the terminal device 20 and the network node 10. Each of the network slices is identified by an S-NSSAI.

[0044] The data format of the S-NSSAI includes a slice / service type (SST) and a slice differentiator (SD).

[0045] SST specifies the use of network slices and includes standard SST and individual SST. Standard SST specifies eMBB, URLLC, Massive Internet of Things (MIoT), Vehicle to X (V2X), and High Performance Machine Type Communication (HMTC). Individual SST specifies use that can be freely set by operators. SD is an identifier for separating multiple network slices in the same SST.

[0046] 1.3 Network Slice Registration The terminal device 20 holds an S-NSSAI applicable within a Public Land Mobile Network (PLMN). This S-NSSAI is called a Configured S-NSSAI. The terminal device 20 registers the S-NSSAI by executing a registration request to the AMF 10a. An overview of the registration procedure will be described with reference to FIG. 7.

[0047] The terminal device 20 transmits a registration request message to the RAN node 30 (step S701). The registration request message includes an S-NSSAI. This S-NSSAI is called a Requested S-NSSAI.

[0048] Next, the RAN node 30 selects an AMF 10a based on the Requested S-NSSAI and transmits a registration request message to the selected AMF 10a (step S702).

[0049] Next, the AMF 10a selects a UDM / UDR 10c and registers the S-NSSAI in the selected UDM / UDR 10c (step S703). This S-NSSAI is called a Subscribed S-NSSAI. The Subscribed S-NSSAI is stored in the UDM / UDR 10c as subscription data.

[0050] Next, the AMF 10a notifies the terminal device 20 of the registered S-NSSAI (step S704). This S-NSSAI is called an Allowed S-NSSAI.

[0051] In this way, the terminal device 20 can establish a PDU session corresponding to the network slice with the UPF 10b and communicate with the DN 40 through the established PDU session.

[0052] 1.4 Network Control Network Slice Selection Non-Patent Document 1 describes network slice replacement, in which a specific network slice is switched to an alternative network slice. Network slice replacement is triggered by the S-NSSAI corresponding to the network slice before the switch becoming unavailable or congestion occurring in the network slice before the switch.

[0053] Switching a network slice refers to disconnecting the PDU session of the network slice currently being used by the terminal device 20, selecting an alternative network slice, and establishing a new PDU session for the alternative network slice. Hereinafter, the currently used network slice will be referred to as the "first network slice," and the alternative network slice will be referred to as the "second network slice."

[0054] For example, a case may be considered in which AF 10d requests to switch the network slice to meet the service requirements for an application it manages. In such a case, for example, NSSF 10e selects a second network slice in response to a request from AF 10d. Then, SMF 10f disconnects the PDU session for the first network slice and establishes a PDU session for the second network slice. In this way, the network slice is switched from the first network slice to the second network slice. An example of a procedure for switching the network slice will be described with reference to FIG. 8.

[0055] The AF 10d transmits a network slice replacement request (Network Slice Switch Request) to the NSSF 10e / SMF 10f (step S801).

[0056] Next, the NSSF 10e selects a second network slice (step S802). This selection is performed by selecting one of the S-NSSAIs registered in the UDM / UDR 10c.

[0057] Next, SMF 10f disconnects the PDU session established with the first network slice (step S803). Next, SMF 10f establishes a PDU session with the second network slice selected in step S802 (step S804). In this way, the network slice is switched from the first network slice to the second network slice.

[0058] In both the case described with reference to FIG. 8 and the network slice replacement described in Non-Patent Document 1, a second network slice is selected by the network. Such network slice selection is referred to herein as network-controlled network slice selection. Note that triggers for performing network-controlled network slice selection include a request from AF 10d and the unavailability of S-NSSAI, but these are merely examples. Network-controlled network slice selection may also be performed in response to an event such as the occurrence of an emergency.

[0059] Since the network-controlled network slice selection disconnects the PDU session established for the first network slice, it will have some impact on the terminal device 20 using the first network slice. The technology described in Non-Patent Document 1 does not take into consideration the impact on the terminal device 20 of the network slice replacement.

[0060] For example, the number of users of a service that uses a specific network slice may suddenly increase, causing congestion in that network slice. In such a case, the application providing the service may request switching to another network slice, even if it tolerates a temporary network interruption caused by disconnecting the PDU session. On the other hand, some terminal devices 20 may not tolerate a temporary network interruption. The technology described in Non-Patent Document 1 does not take such a case into consideration at all.

[0061] In this embodiment, network-controlled network slice selection is controlled based on preset configuration data. The configuration data is configured by adding a new data type to subscription data. In this embodiment, the terms "network slice selection," "network-controlled network slice selection," and "network slice switching" are used interchangeably.

[0062] A network node such as the NSSF10e refers to the subscription data to determine whether to perform network-controlled network slice selection. Referring to Figure 9, data types added to the subscription data will be described.

[0063] The newly added data type to the subscription data is data for controlling network-controlled network slice selection. As shown in Figure 9, the data type is, for example, Network Controlled Network Slicing Selection Related Subscription Data.

[0064] The network controlled network slicing selection related subscription data includes three data fields: the first data field is a network controlled network slicing selection allowed flag, the second data field is a service impact description, and the third data field is demanded service requirements.

[0065] The network-controlled network slice selection permission flag indicates whether it is permitted to perform network-controlled network slice selection. The network-controlled network slice selection permission flag may have values ​​such as "0: permitted" and "1: denied".

[0066] The service impact description indicates the acceptable (unacceptable) service impacts caused by switching the network slice. The service impact description may have values ​​such as "1: relaxed QoS parameters are not allowed" and "2: ssc mode 2 is allowed." "1: relaxed QoS parameters are not allowed" indicates that it is allowed to select only a second network slice that provides a Quality of Service (QoS) equivalent to that of the first network slice. "2: ssc mode 2 is allowed" indicates that it is allowed to perform network-controlled network slice selection only when the Session and Service Continuity (SSC) mode of the PDU session is 2.

[0067] The requested service requirement indicates a service requirement requested for the second network slice. The requested service requirement indicates, for example, a QoS value requested for each QoS parameter. The technical specifications defined by 3GPP define the QoS parameters shown in Table 1. The requested service requirement may have a combination of a value indicating a type of QoS parameter and a value indicating a corresponding QoS value, such as "1: packet delay budget" and "10 (ms)". [Table 1]

[0068] The data structure of the network-controlled network slice selection-related subscription data is merely an example, and data structures other than those described may be adopted. In particular, the service impact description described with reference to FIG. 9 is merely an example, and the service impact description may include specific numerical values ​​of the allowable service impact for the QoS parameters shown in Table 1.

[0069] Network-controlled network slice selection-related subscription data is stored together with the Subscribed S-NSSAI as subscription data when it is stored in the UDM / UDR 10c. That is, data for controlling the network-controlled network slice selection shown in FIG. 9 is stored in the UDM / UDR 10c for each terminal device 20 or each group of terminal devices 20. The subscription data is registered and managed for each terminal device 20. Alternatively, the subscription data may be registered and managed for each network slice or for each combination of a terminal device 20 and a network slice.

[0070] Next, an example of a procedure for performing network-controlled network slice selection according to this embodiment will be described with reference to FIG. 10. In this embodiment, it is assumed that network-controlled network slice selection is performed in response to a request from AF10d. In the process shown in FIG. 10, whether or not to perform network-controlled network slice selection is determined based only on the network-controlled network slice selection permission flag included in the subscription data. Hereinafter, in the figure, the network slice is referred to as "NW-S."

[0071] The AF 10d transmits a network slice switching request to the PCF 10g (step S1001). The network slice switching request includes at least an S-NSSAI for the first network slice used by the AF 10d and an ID (UE-ID) of the terminal device 20. It may also include an S-NSSAI for the second network slice.

[0072] Next, the PCF 10g acquires the subscription data stored in the UDM / UDR 10c based on the UE-ID included in the network slice switching request. Then, the PCF 10g determines whether to perform network slice selection for the terminal device 20 that recorded the subscription data based on the value of the network-controlled network slice selection allowance flag included in the subscription data (step S1002). This determination is made based on whether the value of the network-controlled network slice selection allowance flag is "0: allow" or "1: deny." Note that the subscription data may be acquired based on the S-NSSAI for the first network slice instead of the UE-ID. Alternatively, the subscription data may be acquired based on a combination of the UE-ID and the S-NSSAI for the first network slice.

[0073] If it is determined in step S1002 that the network slice selection is not to be performed, the PCF 10g transmits a message indicating that the network slice selection is not to be performed to the AF 10d (step S1003). In this case, the process illustrated in FIG. 10 ends.

[0074] If it is determined in step S1002 that network slice selection is to be performed, the PCF 10g instructs the NSSF 10e to select a second network slice (step S1004).

[0075] In step S1005, the NSSF 10e selects a second network slice by selecting an S-NSSAI from the S-NSSAIs registered in the UDM / UDR 10c.

[0076] Next, the SMF 10f disconnects the PDU session established for the first network slice (step S1006). The PDU session established for the first network slice refers to the PDU session established for the terminal device 20 managed by the AF 10d that requested switching the network slice.

[0077] Next, the SMF 10f establishes a PDU session for the second network slice selected in step S1005 (step S1007). The PDU session is established for the terminal device 20 whose PDU session was disconnected in step S1006.

[0078] The above-mentioned procedure for disconnecting and establishing a PDU session is performed by the NSSF 10e, AMF 10a, and SMF 10f in cooperation with each other according to the existing network slice replacement procedure. This is also the case in other embodiments described later. In this manner, a network-controlled network slice selection is performed, and the network slice is switched from the first network slice to the second network slice.

[0079] Next, another example of a procedure for performing network-controlled network slice selection according to this embodiment will be described with reference to Figure 11. In the process shown in Figure 11, in addition to the process shown in Figure 10, whether or not to perform network-controlled network slice selection is determined based on the service impact description and / or requested service requirements included in the subscription data. Hereinafter, service impact will be abbreviated as "SI" in the figure.

[0080] The AF 10d transmits a network slice switching request to the PCF 10g / NSSF 10e (step S1101). The network slice switching request includes at least an S-NSSAI for the first network slice used by the AF 10d and the UE-ID of the terminal device 20. It may also include an S-NSSAI for the second network slice.

[0081] Next, the PCF 10g / NSSF 10e acquires the subscription data stored in the UDM / UDR 10c based on the UE-ID included in the network slice switching request. Then, the PCF 10g determines whether to perform network slice selection for the terminal device 20 that recorded the subscription data based on the value of the network control network slice selection permission flag included in the subscription data (step S1102). Note that the subscription data may be acquired based on the S-NSSAI for the first network slice instead of the UE-ID. Alternatively, the subscription data may be acquired based on a combination of the UE-ID and the S-NSSAI for the first network slice.

[0082] If it is determined in step S1102 that the network slice selection is not to be performed, the PCF 10g / NSSF 10e transmits a message indicating that the network slice selection is not to be performed to the AF 10d (step S1103). In this case, the process illustrated in FIG. 11 ends.

[0083] If it is determined in step S1102 that network slice selection is to be performed, the PCF 10g / NSSF10e determines whether or not to allow the service impact according to the value of the service impact description included in the subscription data, and determines whether or not to perform network slice selection (step S1104). For example, if the service impact description indicates "2: ssc mode 2 is allowed," the PCF 10g / NSSF10e determines to perform network slice selection only if the SSC mode of the PDU session is 2. Then, the PCF 10g / NSSF10e selects a second network slice.

[0084] Furthermore, in the determination in step S1104, the PCF 10g / NSSF 10e may discover a second network slice that allows the service impact indicated by the value of the service impact description. For example, if the service impact description indicates "1: relaxed QoS parameters are not allowed," the PCF 10g / NSSF 10e discovers a second network slice that provides a QoS equivalent to the QoS of the first network slice. This discovery is performed by selecting an S-NSSAI from the S-NSSAIs registered in the UDM / UDR 10c.

[0085] To find a second network slice that provides a QoS equivalent to that of the first network slice, QoS values ​​corresponding to the QoS provided by each of the network slices may be stored in the UDM / UDR 10c. The QoS values ​​may be stored as a QoS list in association with an S-NSSAI for each network slice for the QoS parameters shown in Table 1. Table 2 shows an example of the QoS list. [Table 2]

[0086] By storing the QoS list in the UDM / UDR 10c, a second network slice that provides a QoS equivalent to that of the first network slice can be appropriately discovered. Also, by storing the QoS list in the UDM / UDR 10c, the above discovery can be performed at a detailed QoS level.

[0087] By storing the QoS list, the service impact description can have a value indicating, for example, "3: packet delay budget within 10 ms is allowed" in addition to the above example. If the service impact description indicates "3: packet delay budget within 10 ms is allowed", a second network slice that provides a packet delay budget within 10 milliseconds is discovered.

[0088] Furthermore, by storing the QoS list, the service impact description can have a value indicating, for example, "4: packet delay budget within 10 ms after replacement is allowed" in addition to the above example. If the service impact description indicates "4: packet delay budget within 10 ms after replacement is allowed", a second network slice is discovered in which the difference between the packet delay budget provided by the first network slice and the packet delay budget provided by the second network slice is within 10 milliseconds.

[0089] In the determination in step S1104, in addition to or instead of the service impact description, the PCF 10g / NSSF10e may find a second network slice that satisfies the values ​​of the requested service requirements included in the subscription data. For example, if the requested service requirements indicate "1: packet delay budget" and "10 (ms)", the PCF 10g / NSSF10e finds a second network slice that satisfies the service requirements.

[0090] The service impact description indicates the numerical value and / or conditions of the acceptable impact of the service impact caused by switching to the second network slice. The requested service requirement indicates the numerical value and / or conditions of the requested service requirement. The PCF 10g / NSSF 10e finds the second network slice by referring to the QoS list based on any of the numerical value and / or conditions.

[0091] If it is determined in step S1104 that the network slice selection is not to be performed, the PCF 10g / NSSF 10e transmits a message indicating that the network slice selection is not to be performed to the AF 10d (step S1105). In this case, the process illustrated in FIG. 11 ends.

[0092] If it is determined in step S1104 that network slice selection is to be performed, the PCF 10g / NSSF 10e selects a second network slice (step S1106).

[0093] Next, the SMF 10f disconnects the PDU session established for the first network slice (step S1107). The PDU session established for the first network slice refers to the PDU session established for the terminal device 20 managed by the AF 10d that requested switching the network slice.

[0094] Next, SMF 10f establishes a PDU session for the second network slice selected in step S1106 (step S1108). The PDU session is established for the terminal device 20 whose PDU session was disconnected in step S1107. In this way, network-controlled network slice selection is performed, and the network slice is switched from the first network slice to the second network slice.

[0095] In this embodiment, an example in which a new data type is added to subscription data has been described. However, the new data type is not limited to subscription data and may be added to application data or other data. The application data is data stored in the UDM / UDR 10c by the AF 10d. In this case, it is determined whether to perform network-controlled network slice selection for each application, and service impact and / or service requirements are determined.

[0096] That is, configuration data for controlling network slice selection may be stored in a data management system / repository used in the core network, such as UDM / UDR10c. The configuration data may be stored for each terminal device 20 or each group of terminal devices 20. In this case, the configuration data is stored as subscription data. The configuration data may also be stored for each application. In this case, the configuration data is stored as application data.

[0097] Further, the configuration data may be stored for each network slice, where it is determined whether to perform network-controlled network slice selection for each network slice, and service impact and / or service requirements are determined. Still further, the configuration data may be stored for each DNN, where it is determined whether to perform network-controlled network slice selection for each DNN, and service impact and / or service requirements are determined.

[0098] As described above, the first embodiment has been described. In the first embodiment, whether or not to perform network-controlled network slice selection is controlled according to configuration data set by a terminal device, an application, a network slice, and / or a DNN that uses the network slice.

[0099] According to the first embodiment, whether to perform network-controlled network slice selection is determined taking into account the impact on terminal devices, applications, network slices, and / or DNNs.

[0100] In the first embodiment, the PCF 10g determines whether to perform network slice selection, but the PCF 10g is the entity that performs this determination. The procedure described in the first embodiment is performed by one or more of the network nodes 10.

[0101] 2. Second embodiment Next, a second embodiment will be described. In the second embodiment, whether to perform network control network slice selection is determined based on the procedure described in the first embodiment, and the use of the network slice is taken into consideration in the determination.

[0102] As described above, the data format of the S-NSSAI includes an SST and an SD. The SST specifies the use of the network slice. The SD is an identifier for separating multiple network slices in the same SST.

[0103] In the second embodiment, whether to perform network-controlled network slice selection is determined for each use of the network slice. With reference to Figure 12, the data types to be added to the subscription data will be described.

[0104] 12 shows network control network slice selection-related subscription data according to the second embodiment. The network control network slice selection-related subscription data shown in FIG. 12 corresponds to the network control network slice selection-related subscription data shown in FIG.

[0105] As shown in Figure 12, the network control network slice selection allowance flag, service impact description, and requested service requirements are specified for each network slice application. Note that the three data fields are the same as the data fields described with reference to Figure 9, so detailed description will be omitted.

[0106] Data fields such as the network-controlled network slice selection permission flag shown in Figure 12 are defined corresponding to the SST in the S-NSSAI. The SST includes a standard SST and an individual SST.

[0107] Next, an example of a procedure for performing network control network slice selection according to the second embodiment will be described with reference to Figure 13. In the second embodiment, network control network slice selection is also performed in response to a request from AF 10d. In the process shown in Figure 13, whether or not to perform network control network slice selection is determined based only on the network control network slice selection permission flag included in the subscription data.

[0108] The AF 10d transmits a network slice switching request to the PCF 10g (step S1301). The network slice switching request includes at least an S-NSSAI for the first network slice used by the AF 10d and the UE-ID of the terminal device 20. It may also include an S-NSSAI for the second network slice.

[0109] Next, the PCF 10g acquires the subscription data stored in the UDM / UDR 10c based on the UE-ID included in the network slice switching request. Then, the PCF 10g determines whether to perform network slice selection for the terminal device 20 that recorded the subscription data, based on the value of the network-controlled network slice selection allowance flag corresponding to the SST in the S-NSSAI (step S1302). This determination is made based on whether the value of the network-controlled network slice selection allowance flag is "0: allow" or "1: deny." Note that the subscription data may be acquired based on the S-NSSAI for the first network slice instead of the UE-ID. Alternatively, the subscription data may be acquired based on a combination of the UE-ID and the S-NSSAI for the first network slice.

[0110] If it is determined in step S1302 that the network slice selection is not to be performed, the PCF 10g transmits a message indicating that the network slice selection is not to be performed to the AF 10d (step S1303). In this case, the process illustrated in FIG. 10 ends.

[0111] If it is determined in step S1302 that network slice selection is to be performed, the PCF 10g instructs the NSSF 10e to select a second network slice (step S1304).

[0112] In step S1305, the NSSF 10e selects a second network slice by selecting an S-NSSAI from the S-NSSAIs registered in the UDM / UDR 10c.

[0113] Next, the SMF 10f disconnects the PDU session established for the first network slice (step S1306). The PDU session established for the first network slice refers to the PDU session established for the terminal device 20 managed by the AF 10d that requested switching the network slice.

[0114] Next, SMF 10f establishes a PDU session for the second network slice selected in step S1305 (step S1307). The PDU session is established for the terminal device 20 whose PDU session was disconnected in step S1306. In this way, network-controlled network slice selection is performed based on the definition of each network slice usage, and the network slice is switched from the first network slice to the second network slice.

[0115] Next, another example of the procedure for performing network-controlled network slice selection according to the second embodiment will be described with reference to Fig. 14. In the process shown in Fig. 14, in addition to the process shown in Fig. 13, whether to perform network-controlled network slice selection is determined based on the service impact description and / or requested service requirements included in the subscription data.

[0116] The AF 10d transmits a network slice switching request to the PCF 10g / NSSF 10e (step S1401). The network slice switching request includes at least an S-NSSAI for the first network slice used by the AF 10d and the UE-ID of the terminal device 20. The network slice switching request may also include an S-NSSAI for the second network slice.

[0117] Next, the PCF 10g / NSSF 10e acquires the subscription data stored in the UDM / UDR 10c based on the UE-ID included in the network slice switching request. Then, the PCF 10g determines whether to perform network slice selection for the terminal device 20 that recorded the subscription data based on the value of the network control network slice selection permission flag corresponding to the SST in the S-NSSAI (step S1402). Note that the subscription data may be acquired based on the S-NSSAI for the first network slice instead of the UE-ID. Alternatively, the subscription data may be acquired based on a combination of the UE-ID and the S-NSSAI for the first network slice.

[0118] If it is determined in step S1402 that the network slice selection is not to be performed, the PCF 10g / NSSF 10e transmits a message indicating that the network slice selection is not to be performed to the AF 10d (step S1403). In this case, the process illustrated in FIG. 14 ends.

[0119] If it is determined in step S1402 that network slice selection is to be performed, the PCF 10g / NSSF10e determines whether to tolerate the service impact according to the value of the service impact description corresponding to the SST in the S-NSSAI, and determines whether to perform network slice selection (step S1404). In addition, in the determination in step S1404, the PCF 10g / NSSF10e may select a second network slice that tolerates the service impact indicated by the value of the service impact description.

[0120] In determining in step S1404, in addition to or instead of the service impact description, the PCF 10g / NSSF 10e may select a second network slice that satisfies the value of the requested service requirement corresponding to the SST in the S-NSSAI.

[0121] If it is determined in step S1404 that the network slice selection is not to be performed, the PCF 10g / NSSF 10e transmits a message indicating that the network slice selection is not to be performed to the AF 10d (step S1405). In this case, the process illustrated in FIG. 14 ends.

[0122] If it is determined in step S1404 that network slice selection is to be performed, the PCF 10g / NSSF 10e selects a second network slice (step S1406).

[0123] Next, the SMF 10f disconnects the PDU session established for the first network slice (step S1407). The PDU session established for the first network slice refers to the PDU session established for the terminal device 20 managed by the AF 10d that requested switching the network slice.

[0124] Next, SMF 10f establishes a PDU session for the second network slice selected in step S1406 (step S1408). The PDU session is established for the terminal device 20 whose PDU session was disconnected in step S1407. In this way, network-controlled network slice selection is performed based on the definition of each network slice usage, and the network slice is switched from the first network slice to the second network slice.

[0125] As described above, the second embodiment has been described. In the second embodiment, whether or not to perform network control network slice selection is controlled according to configuration data set for each use of the network slice.

[0126] According to the second embodiment, whether to perform network-controlled network slice selection is determined in accordance with the application of the network slice, taking into account the impact on the terminal device, application, network slice, and / or DNN.

[0127] 3. Third embodiment Next, a third embodiment will be described. In the first and second embodiments, examples have been described in which a second network slice that tolerates the service impact indicated by the value of the service impact description and a second network slice that satisfies the value of the requested service requirement are selected. In the third embodiment, network slice selection is repeated until a second network slice that tolerates the service impact indicated by the value of the service impact description is found.

[0128] Another example of the procedure for performing network-controlled network slice selection according to the third embodiment will be described with reference to Figure 15. In the third embodiment, it is assumed that network-controlled network slice selection is also performed by a request from the AF 10d. In the process shown in Figure 15, a network slice is selected based on the service impact description and / or requested service requirements included in the subscription data. This selection is performed by selecting one of the S-NSSAIs from the S-NSSAIs registered in the UDM / UDR 10c.

[0129] The AF 10d transmits a network slice switching request to the PCF 10g / NSSF 10e (step S1501). The network slice switching request includes at least an S-NSSAI for the first network slice used by the AF 10d and the UE-ID of the terminal device 20. The network slice switching request may also include an S-NSSAI for the second network slice.

[0130] Next, the PCF 10g / NSSF 10e acquires the subscription data stored in the UDM / UDR 10c based on the UE-ID included in the network slice switching request. Then, the PCF 10g determines whether to perform network slice selection for the terminal device 20 that recorded the subscription data based on the value of the network control network slice selection permission flag included in the subscription data (step S1502). Note that the subscription data may be acquired based on the S-NSSAI for the first network slice instead of the UE-ID. Alternatively, the subscription data may be acquired based on a combination of the UE-ID and the S-NSSAI for the first network slice.

[0131] If it is determined in step S1502 that the network slice selection is not to be performed, the PCF 10g / NSSF 10e transmits a message indicating that the network slice selection is not to be performed to the AF 10d (step S1503). In this case, the process illustrated in FIG. 15 ends.

[0132] If it is determined in step S1502 that network slice selection is to be performed, the PCF 10g / NSSF10e selects a network slice as the second network slice, and then determines whether the selected network slice is a network slice that allows the service impact indicated by the value of the service impact description included in the subscription data (step S1504).

[0133] As described above, the UDM / UDR 10c stores QoS values ​​for each network slice as a QoS list. The PCF 10g / NSSF 10e can refer to the QoS list based on the selected S-NSSAI and determine whether the network slice corresponding to the selected S-NSSAI is a network slice that tolerates service impact.

[0134] In the determination in step S1504, the PCF 10g / NSSF 10e may determine whether the selected network slice is a network slice that satisfies the value of the requested service requirements included in the subscription data.

[0135] If the result of the determination in step S1504 is that the selected network slice is not a network slice that tolerates the service impact / satisfies the requested service requirements, the process of step S1504 is repeated until it is determined that the selected network slice is a network slice that tolerates the service impact / satisfies the requested service requirements.

[0136] The process of step S1504 may be repeated a preset number of times. The preset number of times may be stored in the UDM / UDR 10c, similar to the network control network slice selection permission flag.

[0137] If the result of the determination in step S1504 is that the selected network slice is a network slice that tolerates the service impact / satisfies the requested service requirements, the PCF 10g / NSSF 10e selects the determined network slice as the second network slice (step S1505).

[0138] Next, the SMF 10f disconnects the PDU session established for the first network slice (step S1506). The PDU session established for the first network slice refers to the PDU session established for the terminal device 20 managed by the AF 10d that requested switching the network slice.

[0139] Next, SMF 10f establishes a PDU session for the second network slice selected in step S1505 (step S1507). The PDU session is established for the terminal device 20 whose PDU session was disconnected in step S1506. In this way, network-controlled network slice selection is performed, and the network slice is switched from the first network slice to the second network slice.

[0140] As described in the second embodiment, the network-controlled network slice selection permission flag in step S1503 may be defined for each use of the network slice. Similarly, the service impact description and requested service requirements in step S1503 may also be defined for each use of the network slice.

[0141] As described above, the third embodiment has been described. In the third embodiment, network slice selection is repeated until a network slice that tolerates service impact / satisfies requested service requirements is found.

[0142] According to the third embodiment, the possibility of switching to a network slice that can tolerate service impact / meets requested service requirements is increased.

[0143] 4. Fourth embodiment Next, a fourth embodiment will be described. Whether to perform network control network slice selection is determined based on the procedures described in the first to third embodiments, and the determination takes into account the case where the second network slice is in use.

[0144] An example of a procedure for performing network control network slice selection according to the fourth embodiment will be described with reference to Figure 16. In the fourth embodiment, network control network slice selection is also performed in response to a request from AF 10d. In the process shown in Figure 14, whether or not to perform network control network slice selection is determined based only on the network control network slice selection permission flag included in the subscription data.

[0145] The AF 10d transmits a network slice switching request to the PCF 10g (step S1601). The network slice switching request includes at least an S-NSSAI for the first network slice used by the AF 10d and the UE-ID of the terminal device 20. It may also include an S-NSSAI for the second network slice.

[0146] Next, the PCF 10g acquires the subscription data stored in the UDM / UDR 10c based on the UE-ID included in the network slice switching request. Then, the PCF 10g determines whether to perform network slice selection for the terminal device 20 that recorded the subscription data, based on the value of the network-controlled network slice selection allowance flag included in the subscription data (step S1602). This determination is made based on whether the value of the network-controlled network slice selection allowance flag is "0: allow" or "1: deny." Note that the subscription data may be acquired based on the S-NSSAI for the first network slice instead of the UE-ID. Alternatively, the subscription data may be acquired based on a combination of the UE-ID and the S-NSSAI for the first network slice.

[0147] If it is determined in step S1602 that the network slice selection is not to be performed, the PCF 10g transmits a message indicating that the network slice selection is not to be performed to the AF 10d (step S1603). In this case, the process illustrated in FIG. 16 ends.

[0148] If it is determined in step S1602 that network slice selection is to be performed, the PCF 10g instructs the NSSF 10e to select a second network slice (step S1604).

[0149] In step S1605, the NSSF 10e selects a second network slice by selecting an S-NSSAI from the S-NSSAIs registered in the UDM / UDR 10c.

[0150] Next, the PCF 10g acquires the subscription data stored in the UDM / UDR 10c based on the UE-ID. Then, the PCF 10g determines whether to perform network slice selection for the terminal device 20 that recorded the subscription data, based on the value of the network-controlled network slice selection allowance flag included in the subscription data (step S1606). This determination is made based on whether the value of the network-controlled network slice selection allowance flag is "0: allow" or "1: deny." Note that, in step S1606, the subscription data may be acquired based on the S-NSSAI selected in step S1605, instead of the UE-ID. Alternatively, the subscription data may be acquired based on a combination of the UE-ID and the selected S-NSSAI.

[0151] If it is determined in step S1606 that the network slice selection is not to be performed, the PCF 10g transmits a message indicating that the network slice selection is not to be performed to the AF 10d (step S1607). In this case, the process illustrated in FIG. 16 ends.

[0152] If it is determined in step S1606 that network slice selection is to be performed, SMF 10f disconnects the PDU session established for the first network slice (step S1608). The PDU session established for the first network slice refers to the PDU session established for the terminal device 20 managed by AF 10d that requested the network slice to be switched.

[0153] Next, SMF 10f establishes a PDU session for the second network slice selected in step S1605 (step S1609). The PDU session is established for the terminal device 20 whose PDU session was disconnected in step S1608. In this way, network-controlled network slice selection is performed based on the definition of each network slice usage, and the network slice is switched from the first network slice to the second network slice.

[0154] The determination in step S1606 may be based on the service impact description and / or the requested service requirements included in the subscription data. The network-controlled network slice selection allowance flag in step S1606 may be defined for each use of the network slice. Similarly, the service impact description and the requested service requirements may also be defined for each use of the network slice.

[0155] The fourth embodiment has been described above. In the fourth embodiment, whether or not to perform network slice selection is controlled according to configuration data set by a terminal device using a second network slice. The configuration data may be defined for each application, network slice, and / or DNN.

[0156] According to the fourth embodiment, when a terminal device or the like is using the second network slice to be switched to, the decision as to whether to perform network control network slice selection is made taking into consideration the impact on the terminal device or the like.

[0157] 5. Variations Although the embodiments for carrying out the present invention have been described above, the present invention is not limited to the above-described embodiments. It is to be understood that the above-described embodiments are merely examples and that various modifications are possible.

[0158] The words, phrases, and other expressions used in the above embodiments are merely examples and may be replaced with substantially identical or similar expressions. In particular, since the technology according to the above embodiments relates to technical specifications, the expressions in the above embodiments may be replaced with substantially identical or similar expressions in technical specifications (e.g., technical specifications cited in this specification).

[0159] The information transmitted and received in the above embodiment may be contained in the same or a different message or element already described in the technical specifications, or may be contained in a newly defined message or element. The information transmitted and received in the above embodiment may be transmitted and received using a different layer and / or a different channel than those in the above embodiment.

[0160] The means and / or functions provided by the devices described in the above embodiments can be provided by software recorded in a tangible memory device and a computer that executes the software, software alone, hardware alone, or a combination thereof. For example, if any of the above devices is provided by electronic circuits that are hardware, it can be provided by digital circuits including a large number of logic circuits, or analog circuits.

[0161] The device described in the above embodiment executes a program stored in a non-transitory tangible storage medium, and the execution of the program results in the execution of a method corresponding to the program.

[0162] 6. Notes Some or all of the above embodiments and modified examples may be described as, but are not limited to, the following notes. Hereinafter, a relationship is expressed in which a note that is subordinate to multiple notes is subordinate to another note that is subordinate to multiple notes. All of the following subordinate relationships of notes are included in the above embodiments.

[0163] (Appendix 1) A network node including a controller, The control unit storing configuration data defining whether or not to allow switching of the network slice; Determine whether to switch the network slice based on the configuration data; Switching the network slice from a first network slice to a second network slice in response to the determination. A network node that is configured to:

[0164] (Appendix 2) The network node of Supplementary Note 1, wherein the configuration data includes data regarding acceptable / unacceptable service impacts caused by switching the network slice.

[0165] (Appendix 3) 3. A network node as described in Supplementary Note 2, wherein the data on service impact includes data on acceptable service impact for QoS parameters.

[0166] (Appendix 4) The network node according to claim 2 or 3, wherein the control unit is further configured to select, based on the configuration data, a network slice that tolerates the service impact as the second network slice.

[0167] (Appendix 5) A network node described in any one of Supplementary Notes 1 to 4, wherein the configuration data includes data regarding service requirements requested from the second network slice.

[0168] (Appendix 6) A network node as described in Supplementary Note 5, wherein the data on service requirements includes data on service requirements requested from the second network slice for QoS parameters.

[0169] (Appendix 7) The network node of claim 5 or 6, wherein the control unit is further configured to select a network slice that satisfies the service requirements as the second network slice based on the configuration data.

[0170] (Appendix 8) A network node described in any one of Supplementary Notes 1 to 7, wherein the configuration data is stored as subscription data together with an S-NSSAI corresponding to the first network slice.

[0171] (Appendix 9) 8. The network node of claim 1, wherein the configuration data is stored on a per-application basis.

[0172] (Appendix 10) 8. A network node according to any one of Supplementary Notes 1 to 7, wherein the configuration data is stored per network slice.

[0173] (Appendix 11) 8. The network node of claim 1, wherein the configuration data is stored per DNN.

[0174] (Appendix 12) A network node described in any one of Supplementary Notes 1 to 11, wherein the configuration data is stored for each use of the network slice.

[0175] (Appendix 13) The network node of Supplementary Note 12, wherein the control unit is further configured to determine whether to switch the network slice based on the configuration data in accordance with the use of the first network slice.

[0176] (Appendix 14) The network node of Supplementary Note 13, wherein the control unit is further configured to determine the use from an S-NSSAI corresponding to the first network slice.

[0177] (Appendix 15) The network node of Supplementary Note 4, wherein the control unit is further configured to select a network slice that tolerates the service impact as the second network slice by selecting one of the registered S-NSSAIs.

[0178] (Appendix 16) The network node of claim 15, wherein the control unit repeats selecting the S-NSSAI until it finds a network slice that tolerates the service impact.

[0179] (Appendix 17) The network node of Supplementary Note 7, wherein the control unit is further configured to select a network slice that satisfies the service requirements as the second network slice by selecting one of the registered S-NSSAIs.

[0180] (Appendix 18) The network node of Supplementary Note 17, wherein the control unit repeats selecting the S-NSSAI until it finds a network slice that satisfies the service requirements.

[0181] (Appendix 19) The network node of any one of Supplementary Notes 1 to 18, wherein the control unit is further configured to determine whether to switch the network slice based on configuration data for the first network slice, and to determine whether to switch the network slice based on configuration data for the second network slice.

[0182] (Appendix 20) 1. A method performed by a network node, comprising: Storing configuration data that defines whether or not to allow switching of the network slice; Determining whether to switch the network slice based on the configuration data; Switching the network slice from a first network slice to a second network slice in response to the determination; A method comprising:

[0183] (Appendix 21) When executed, the processor in the network node Storing configuration data that defines whether or not to allow switching of the network slice; Determining whether to switch the network slice based on the configuration data; Switching the network slice from a first network slice to a second network slice in response to the determination; A program that executes.

[0184] (Appendix 22) When executed, the processor in the network node Storing configuration data that defines whether or not to allow switching of the network slice; Determining whether to switch the network slice based on the configuration data; Switching the network slice from a first network slice to a second network slice in response to the determination; A computer-readable non-transitory tangible recording medium storing a program for executing the above.

[0185] (Appendix 23) A terminal device including a control unit and a communication unit, The control unit is configured to register configuration data defining whether or not to allow switching of the network slice in the network node; The configuration data is used by the network node to determine whether to switch the network slice; The communication unit is configured to communicate with a data network using a second network slice switched from the first network slice in response to the determination. Terminal device.

[0186] The disclosures of the above prior art documents and references are incorporated herein by reference. [Explanation of symbols]

[0187] 10 network node, 101 processor, 102 memory, 103 transceiver, 110 control unit, 120 communication unit, 20 terminal device, 201 processor, 202 memory, 203 input / output interface, 204 transceiver, 205 antenna, 210 control unit, 220 communication unit, 30 RAN node, 40 DN

Claims

1. A network node including a controller, The control unit storing configuration data defining whether or not to allow switching of the network slice; Determine whether to switch the network slice based on the configuration data; Switching the network slice from a first network slice to a second network slice in response to the determination. A network node that is configured to:

2. The network node according to claim 1 , wherein the configuration data includes data on acceptable / unacceptable service impacts caused by switching the network slice.

3. 3. The network node of claim 2, wherein the data on service impact includes data on acceptable service impact for QoS parameters.

4. The network node according to claim 2 , wherein the control unit is further configured to select, based on the configuration data, a network slice that tolerates the service impact as the second network slice.

5. The network node of claim 1 , wherein the configuration data includes data regarding service requirements requested from the second network slice.

6. The network node according to claim 5 , wherein the data on service requirements includes data on service requirements requested of the second network slice for QoS parameters.

7. The network node according to claim 5 , wherein the control unit is further configured to select, based on the configuration data, a network slice that satisfies the service requirements as the second network slice.

8. The network node of claim 1, wherein the configuration data is stored as subscription data together with an S-NSSAI corresponding to the first network slice.

9. The network node of claim 1 , wherein the configuration data is stored on a per-application basis.

10. The network node of claim 1 , wherein the configuration data is stored per network slice.

11. The network node of claim 1 , wherein the configuration data is stored for each DNN.

12. The network node of claim 1 , wherein the configuration data is stored for each use of a network slice.

13. The network node according to claim 12, wherein the control unit is further configured to determine whether to switch the network slice based on the configuration data in accordance with an application of the first network slice.

14. 1. A method performed by a network node, comprising: Storing configuration data that defines whether or not to allow switching of the network slice; Determining whether to switch the network slice based on the configuration data; Switching the network slice from a first network slice to a second network slice in response to the determination; A method comprising:

15. When executed, the processor in the network node Storing configuration data that defines whether or not to allow switching of the network slice; Determining whether to switch the network slice based on the configuration data; Switching the network slice from a first network slice to a second network slice in response to the determination; A program that executes.

Images