Terminals, network nodes, and communication methods

Abstract

To provide a time-limited network slice service in a communication system. [Solution] The terminal includes a transmitting unit that sends a registration request to the core network, a receiving unit that receives a registration permission from the core network which includes information identifying the network slice and an effectiveness timer value associated with the network slice, and a control unit that, upon receiving the information identifying the network slice and the effectiveness timer value, starts a timer that sets the effectiveness timer value, and the control unit utilizes the network slice until the timer expires.

Description

Technical Field

[0001] The present invention relates to a terminal, a network node, and a communication method in a communication system.

Background Art

[0002] In 3GPP (registered trademark) (3rd Generation Partnership Project), in order to achieve further increase in system capacity, further increase in data transmission speed, further reduction in latency in a radio section, etc., a radio communication method called 5G or NR (New Radio) (hereinafter, this radio communication method is referred to as "5G" or "NR") is being studied. In 5G, various radio technologies are being studied in order to meet the requirement of achieving a throughput of 10 Gbps or more and reducing the latency in the radio section to 1 ms or less.

[0003] In NR, a network architecture including a 5GC (5G Core Network) corresponding to the EPC (Evolved Packet Core), which is the core network in the network architecture of LTE (Long Term Evolution), and an NG-RAN (Next Generation - Radio Access Network) corresponding to the E-UTRAN (Evolved Universal Terrestrial Radio Access Network), which is the RAN (Radio Access Network) in the network architecture of LTE, is being studied (for example, Non-Patent Document 1 and Non-Patent Document 2).

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Non-Patent Document 2

[0005] Network slices are operated within 5GC to allow telecommunications carriers to provide services to users. The implementation of limited-lifetime network slice services is being considered. However, the detailed operation of the network and terminals for operating limited-life network slices has not been defined.

[0006] This invention has been made in view of the above points, and aims to provide a time-limited network slice service in a communication system. [Means for solving the problem]

[0007] According to the disclosed technology, the system includes a transmitting unit that transmits a registration request to a core network, a receiving unit that receives a registration authorization from the core network, which includes information identifying a network slice and an effectiveness timer value associated with the network slice, and a control unit that, upon receiving the information identifying the network slice and the effectiveness timer value, starts a timer that sets the effectiveness timer value, wherein the control unit provides terminals that utilize the network slice until the timer expires. [Effects of the Invention]

[0008] According to the disclosed technology, a time-limited network slice service can be provided in a communication system. [Brief explanation of the drawing]

[0009] [Figure 1] This is a diagram illustrating an example of a communication system. [Figure 2] This diagram illustrates an example of a communication system in a roaming environment. [Figure 3] This is a sequence diagram illustrating an example (1) of the operation related to network slicing in an embodiment of the present invention. [Figure 4] This is a flowchart illustrating an example of terminal operation related to network slicing in an embodiment of the present invention (1-1). [Figure 5] This is a flowchart illustrating an example of terminal operation related to network slicing in an embodiment of the present invention (1-2). [Figure 6] This is a flowchart illustrating examples of terminal operations related to network slicing in embodiments of the present invention (1-3). [Figure 7] This is a flowchart illustrating examples of terminal operations related to network slicing in embodiments of the present invention (1-4). [Figure 8] This is a flowchart illustrating examples (1-5) of terminal operations related to network slicing in embodiments of the present invention. [Figure 9] This is a flowchart illustrating an example of network operation related to network slicing in an embodiment of the present invention (1-1). [Figure 10] This is a flowchart illustrating an example of network operation related to network slicing in an embodiment of the present invention (1-2). [Figure 11] This is a flowchart illustrating examples of network operations related to network slicing in embodiments of the present invention (1-3). [Figure 12] This is a flowchart illustrating examples of network operations related to network slicing in embodiments of the present invention (1-4). [Figure 13] This is a flowchart illustrating examples of network operations related to network slicing in embodiments of the present invention (1-5). [Figure 14] This is a flowchart illustrating examples of network operations related to network slicing in embodiments of the present invention (1-6). [Figure 15] This is a sequence diagram for explaining an example (2) of operations related to network slices in an embodiment of the present invention. [Figure 16] This is a flowchart for explaining an example (2-1) of terminal operations related to network slices in an embodiment of the present invention. [Figure 17A] This is a flowchart for explaining an example (2-2) of terminal operations related to network slices when receiving a Configured NSSAI in an embodiment of the present invention. [Figure 17B] This is a flowchart for explaining an example (2-2) of terminal operations related to network slices when receiving an Allowed NSSAI in an embodiment of the present invention. [Figure 17C] This is a flowchart for explaining an example (2-2) of terminal operations related to network slices when receiving a Conditional Allowed NSSAI in an embodiment of the present invention. [Figure 17D] This is a flowchart for explaining an example (2-2) of terminal operations related to network slices when receiving a setting update command with a registration request set in an embodiment of the present invention. [Figure 18] This is a flowchart for explaining an example (2-3) of terminal operations related to network slices in an embodiment of the present invention. [Figure 19] This is a flowchart for explaining an example (2-4) of terminal operations related to network slices in an embodiment of the present invention. [Figure 20] This is a flowchart for explaining an example (2-1) of network operations related to network slices in an embodiment of the present invention. [Figure 21] This is a flowchart for explaining an example (2-2) of network operations related to network slices in an embodiment of the present invention. [Figure 22] This is a flowchart for explaining an example (2-3) of network operations related to network slices in an embodiment of the present invention. [Figure 23] This is a sequence diagram illustrating an example (3) of the operation related to network slicing in an embodiment of the present invention. [Figure 24] This is a flowchart illustrating an example of terminal operation related to network slicing in an embodiment of the present invention (3-1). [Figure 25] This is a flowchart illustrating an example of terminal operation related to network slicing in an embodiment of the present invention (3-2). [Figure 26] This figure shows an example of the functional configuration of the base station 10 in an embodiment of the present invention. [Figure 27] This figure shows an example of the functional configuration of terminal 20 in an embodiment of the present invention. [Figure 28] This figure shows an example of the hardware configuration of the base station 10 and terminal 20 in an embodiment of the present invention. [Figure 29] This figure shows an example of the configuration of a vehicle 2001 in an embodiment of the present invention. [Modes for carrying out the invention]

[0010] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.

[0011] In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE, but are not limited to existing LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and LTE-Advanced and later methods (e.g., NR), or wireless LAN (Local Area Network), unless otherwise specified.

[0012] Furthermore, in the embodiments of the present invention, "configuring" wireless parameters may mean that predetermined values ​​are pre-configured, or that wireless parameters notified from the network node 30 or terminal 20 are configured.

[0013] Figure 1 is a diagram illustrating an example of a communication system. As shown in Figure 1, the communication system consists of a terminal 20 (UE) and multiple network nodes 30. Hereafter, one network node 30 will be assigned to each function, however, one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0014] The RAN (Radio Access Network) is a network node 30 having radio access functionality, which may include a base station 10, and is connected to the UE, AMF (Access and Mobility Management Function), and UPF (User plane function). The AMF is a network node 30 having functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 interconnected with the DN (Data Network) and having functions such as a PDU (Protocol Data Unit) session point to the outside, packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and DN constitute a network slice. In the wireless communication network in the embodiment of the present invention, multiple network slices may be constructed.

[0015] AMF is connected to UE, RAN, SMF (Session Management function), NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function), and AF (Application Function). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0016] SMF is a network node 30 that has functions such as session management, IP (Internet Protocol) address allocation and management for UEs, DHCP (Dynamic Host Configuration Protocol) functionality, ARP (Address Resolution Protocol) proxy, and roaming functionality. NEF is a network node 30 that has the function of notifying other NFs (Network Functions) of capabilities and events. NSSF is a network node 30 that has functions such as selecting the network slice to which the UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which the UE connects. PCF is a network node 30 that has the function of controlling network policy. AF is a network node 30 that has the function of controlling application servers. NRF is a network node 30 that has the function of discovering NF instances that provide services. UDM is a network node 30 that manages subscriber data and authentication data. UDM is connected to UDR (User Data Repository) which holds the said data.

[0017] Figure 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Figure 2, the network consists of a terminal 20 (UE) and multiple network nodes 30. Hereafter, one network node 30 will be assumed to correspond to each function, however, one network node 30 may implement multiple functions, or multiple network nodes 30 may implement one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0018] The RAN is a network node 30 with wireless access capabilities and is connected to the UE, AMF, and UPF. The AMF is a network node 30 with functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 interconnected with the DN and has functions such as external PDU session point, packet routing and forwarding, and user plane QoS handling. The UPF and DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, multiple network slices are constructed.

[0019] AMF is connected to UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0020] SMF is a network node 30 with functions such as session management, UE IP address assignment and management, DHCP functionality, ARP proxy, and roaming functionality. NEF is a network node 30 with the function of notifying other NFs of capabilities and events. NSSF is a network node 30 with functions such as selecting the network slice to which the UE connects, determining the allowed NSSAI, determining the NSSAI to be configured, and determining the AMF set to which the UE connects. PCF is a network node 30 with the function of performing network policy control. AF is a network node 30 with the function of controlling the application server. NRF is a network node 30 with the function of discovering NF instances that provide services. SEPP is an opaque proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). vSEPP shown in Figure 2 is SEPP in the visited network, and hSEPP is SEPP in the home network.

[0021] As shown in Figure 2, the UE is in a roaming environment connected to the RAN and AMF in the VPLMN (Visited PLMN). The VPLMN and HPLMN (Home PLMN) are connected via vSEPP and hSEPP. The UE can communicate with the HPLMN's UDM, for example, via the VPLMN's AMF.

[0022] Here, network slices are operated within 5GC for telecommunications carriers to provide services to users. The implementation of limited-lifetime network slice services is being considered. However, the detailed operation of the network and terminals for operating limited-lifetime network slices was not defined.

[0023] Therefore, the following describes methods for providing time-limited network slice services in communication systems. Methods for realizing time-limited network slices include timer-based methods and URSP (UE Route Selection Policy) methods.

[0024] When implementing time-limited network slices on a timer basis, it is expected that timers will be associated with the network slice information. For example, the UE may receive an S-NSSAI (Single - NSSAI) that identifies the time-limited network slice as a Configured NSSAI from the core network during the registration procedure, pre-configuration, or configuration update command (CONFIGURATION UPDATE COMMAND).

[0025] The configuration update command may also include information about alternative network slices that the network notifies the UE of when the timer for a time-limited network slice expires. For example, when the timer associated with an S-NSSAI representing a particular time-limited network slice expires, the command may include information indicating alternative S-NSSAI(s) representing that time-limited network slice. The network node that includes this alternative network slice information may be an AMF, a UDM, or an NSSF. However, the network node that includes this alternative network slice information is not limited to these.

[0026] For the sake of simplicity, in the following explanation, 5GS mobility management messages or 5GS session management messages may be referred to as NAS messages. Furthermore, 5GS mobility management messages may be REGISTRATION REQUEST messages or UL NAS TRANSPORT messages. Similarly, 5GS session management messages may be PDU SESSION ESTABLISHMENT REQUEST messages.

[0027] Figure 3 is a sequence diagram illustrating an example (1) of the operation related to a network slice in an embodiment of the present invention. In step S11, the AMF30A sends a Registration Accept to the UE20. The Registration Accept includes the Configured NSSAI and its associated timer T1. In the following step S12, the UE20 stores the Configured NSSAI in the NSSAI storage. Note that the Configured NSSAI and its associated timer T1 may be set in the UE by a pre-configuration or configuration update command, rather than by the Registration Accept message. Note that timer T1 may be a timer value.

[0028] In the following step S13, UE20 sends Registration Complete to AMF30A. In the following steps S14a and S14b, UE20 and AMF30A start Timer T1. In the following step S15, UE20 and AMF30A use the network slice identified by Configured NSSAI until Timer T1 expires.

[0029] Here, the timing of the timer count start in steps S14a and S14b may be determined. Also, in steps S14a and S14b, the behavior when S-NSSAI is NSSAA dependent (subject to NSSAA (Network Slice-Specific Authentication and Authorization)) may be determined. Also, the behavior of the timer count according to the timer value may be determined. In addition, when the timer expires, instead of just terminating the network slice, an alternative network slice may be notified. When an alternative network slice is notified, simultaneous registration requests from multiple UEs to that alternative network slice may be avoided. Also, the behavior when a new timer value is received while the timer is running may be determined. Also, the operation after the timer count expires may be determined. Also, the behavior of the wireless network when the time-limited network slice expires may be determined.

[0030] Figure 4 is a flowchart illustrating an example of terminal operation related to a network slice in an embodiment of the present invention (1-1). In step S101, UE20 receives a Configured NSSAI (S-NSSAI) and its associated timer T1. Note that the Configured NSSAI (S-NSSAI(s)) and its associated timer T1 may be received or set by a registration procedure, pre-configuration, or configuration update command. In the following step S102, UE20 starts timer T1.

[0031] In step S103, if timer T1 has not expired, UE20 may send a NAS message, or if it receives a new timer T2 associated with the S-NSSAI, it may stop timer T1 and start timer T2.

[0032] In step S104, if timer T1 expires, UE20 may suppress the transmission of NAS messages using the S-NSSAI associated with timer T1, remove the S-NSSAI from the Allowed NSSAI if it is stored as an Allowed NSSAI, or move the S-NSSAI to the Rejected NSSAI in the NSSAI storage if it is stored as an Allowed NSSAI. Note that a NAS message using an S-NSSAI may be a NAS message that includes the S-NSSAI in question.

[0033] Figure 5 is a flowchart illustrating an example (1-2) of terminal operation related to a network slice in an embodiment of the present invention. In step S111, UE20 receives a Configured NSSAI (S-NSSAI) and its associated timer T1. Note that the Configured NSSAI (S-NSSAI(s)) and its associated timer T1 may be received or set by a registration procedure, pre-configuration, or configuration update command. At this time, UE20 does not need to start timer T1. In the following step S112, UE20 receives an Allowed NSSAI. Note that the Allowed NSSAI may be received or set by a registration procedure or configuration update command.

[0034] In step S113, if the S-NSSAI from the Configured NSSAI is an Allowed NSSAI, the UE20 may store the S-NSSAI in the Allowed NSSAI section of the NSSAI storage and start Timer T1. Alternatively, if the time from the time the Configured NSSAI is received to the time the Allowed NSSAI is received or the S-NSSAI is stored in the Allowed NSSAI section of the NSSAI storage is t, the UE20 may set the starting value of Timer T1 to t1-t. Furthermore, if t1-t<0, the UE20 may not count Timer T1, may remove the S-NSSAI from the Allowed NSSAI section, or may move the S-NSSAI to the Rejected NSSAI section of the NSSAI storage.

[0035] In step S114, if timer T1 has not expired, UE20 may send a NAS message, or if it receives a new timer T2 associated with the S-NSSAI, it may stop timer T1 and start timer T2.

[0036] In step S115, if timer T1 expires, UE20 may suppress the transmission of NAS messages using the S-NSSAI associated with timer T1, remove the S-NSSAI from the Allowed NSSAI if it is stored as an Allowed NSSAI, or move the S-NSSAI to the Rejected NSSAI in the NSSAI storage if it is stored as an Allowed NSSAI. Note that a NAS message using an S-NSSAI may be a NAS message that includes the S-NSSAI in question.

[0037] Figure 6 is a flowchart illustrating an example (1-3) of terminal operation related to a network slice in an embodiment of the present invention. In step S121, UE20 receives the Configured NSSAI (S-NSSAI) and its associated timer T1. The Configured NSSAI (S-NSSAI(s)) and its associated timer T1 may be received or set by a registration procedure, pre-configuration, or configuration update command.

[0038] In step S122, if the timer value of timer T1 is "0" or "Deactivated", UE20 may ignore timer T1, or if it is counting, it may stop the timer and assume that the time-limited nature of the network slice identified by the S-NSSAI has been eliminated, stopped, or released. Also, if the timer value of timer T1 is "Activated", UE20 may restart the count of timer T1, or if there is a timer that has stopped counting, it may set the remaining timer value obtained by subtracting the elapsed time from the time it was stopped to the timer and start counting, or if there is a timer that has stopped counting, it may set the remaining timer value at the time it was stopped to the timer and start counting. Furthermore, if the timer value of timer T1 is a number other than 0, UE20 may perform the operation shown in Figure 4 or Figure 5.

[0039] Figure 7 is a flowchart illustrating an example (1-4) of terminal operation related to a network slice in an embodiment of the present invention. In step S131, UE20 receives a Configured NSSAI (S-NSSAI) and its associated timer T1. The Configured NSSAI (S-NSSAI(s)) and its associated timer T1 may be received or set by a registration procedure, pre-configuration, or configuration update command.

[0040] In step S132, if timer T1 is associated with one or more S-NSSAIs, UE20 may associate timer T1 with multiple S-NSSAIs simultaneously and start counting timer T1. Also, for example, if timer T1 is specified as "all" rather than being associated with a specific S-NSSAI, timer T1 may be associated with all S-NSSAIs included in the Configured NSSAI, setting the same timer value.

[0041] Figure 8 is a flowchart illustrating an example (1-5) of terminal operation related to a network slice in an embodiment of the present invention. In step S141, UE20 receives a Configured NSSAI (S-NSSAI) and its associated timer T1. The Configured NSSAI (S-NSSAI(s)) and its associated timer T1 may be received or set by a registration procedure, pre-configuration, or configuration update command. In the following step S142, UE20 starts timer T1. In the following step S143, timer T1 expires. In the following step S144, UE20 sends a NAS message using default NSSAI to the core network.

[0042] Figure 9 is a flowchart illustrating an example of network operation related to a network slice in an embodiment of the present invention (1-1). In step S1001, if multiple S-NSSAIs can identify one network slice (identified by NSI), and if a time limit (with an expiration date setting) is set for that network slice, the timer associated with that network slice expires. This timer may be the network start timer, and if there are multiple UEs connected to the network using that network slice, the timer count may start with a different timer value for each UE.

[0043] In the following step S1002, the AMF30A sends a new Configured NSSAI to the UE, deleting all S-NSSAIs that identify the network slice registered in the subscriber information of the UE20. If there are multiple UEs connected to the network using the network slice, the timing of sending the new Configured NSSAI to the UEs may be based on timers with different timer values ​​for each UE. By using timers with different timer values ​​for each UE, a new Configured NSSAI can be sent to each UE at different times when the timer expires.

[0044] By sending a new Configured NSSAI at different times for each UE, it is possible to prevent signal congestion caused by, for example, multiple UEs simultaneously making registration requests using the new Configured NSSAI.

[0045] Figure 10 is a flowchart illustrating an example (1-2) of network operation related to a network slice in an embodiment of the present invention. In step S1011, if multiple S-NSSAIs can identify one network slice (identified by an NSI (Network Slice Instance)), and if a time limit (with an expiration date setting) is set for the S-NSSAI, the timer associated with the S-NSSAI expires. This timer may be the network start timer, and if there are multiple UEs connected to the network using the S-NSSAI, the timer count may start with a different timer value for each UE.

[0046] In the subsequent step S1012, the AMF30A sends a notification to the UE designating the S-NSSAI as a Rejected NSSAI, and a Configured NSSAI or Allowed NSSAI containing an alternative S-NSSAI for the network slice identified by the S-NSSAI. If there are multiple UEs connected to the network using the S-NSSAI, the timing of sending the alternative S-NSSAI to the UEs may be based on timers with different timer values ​​for each UE. By starting timers with different timer values ​​for each UE, alternative S-NSSAIs can be sent to the UEs at different times for each UE when their timers expire.

[0047] By sending alternative S-NSSAI at different times for each UE, signal congestion caused by multiple UEs simultaneously making registration requests using the same alternative S-NSSAI can be prevented.

[0048] Figure 11 is a flowchart illustrating an example (1-3) of network operation related to a network slice in an embodiment of the present invention. In step S1021, if one S-NSSAI can identify multiple network slices (identified by NSI), and if a time limit (with an expiration date setting) is set for the network slice, the timer associated with that network slice expires.

[0049] In the subsequent step S1022, the AMF30A sends a notification designating the S-NSSAI as a Rejected NSSAI. Furthermore, it updates the mapping between the network slices held in the core network and the S-NSSAI. For example, it may demap the S-NSSAI from network slices whose timers have expired and switch to mapping it to network slices whose timers have not expired.

[0050] Figure 12 is a flowchart illustrating an example (1-4) of network operation related to network slices in an embodiment of the present invention. In step S1031, if one S-NSSAI can identify multiple network slices (identified by NSI), and if a time limit (with an expiration date setting) is set for the S-NSSAI, the timer associated with the S-NSSAI expires. This timer may be the network start timer, and if there are multiple UEs connected to the network using the S-NSSAI, the timer count may start with a different timer value for each UE.

[0051] In the subsequent step S1032, the AMF30A sends a new Configured NSSAI to the UE, deleting the S-NSSAI that identifies the network slice registered in the UE's subscriber information. If there are multiple UEs connected to the network using the S-NSSAI, the timing of sending the new Configured NSSAI to the UEs may be based on timers with different timer values ​​for each UE. By using timers with different timer values ​​for each UE, a new Configured NSSAI can be sent to each UE at different times when the timer expires.

[0052] By sending a new Configured NSSAI at different times for each UE, it is possible to prevent signal congestion caused by, for example, multiple UEs simultaneously making registration requests using the new Configured NSSAI.

[0053] Figure 13 is a flowchart illustrating an example (1-5) of network operation related to network slices in an embodiment of the present invention. In step S1041, cells #A, #B, and #C are set in a certain TA, and network slices identified by S-NSSAI#1 and S-NSSAI#2 are set in the TA. Wireless resources are allocated to S-NSSAI#1 and S-NSSAI#2 in cells #A and #B either as Prioritized or Dedicated. Wireless resources are allocated to S-NSSAI#1 and S-NSSAI#2 in cell #C as Shared.

[0054] In the following step S1042, when the time-limited network slice identified by S-NSSAI#2 is terminated, the wireless network receives a notification or information regarding the termination of the time-limited network slice identified by S-NSSAI#2 from the core network or management function. In the following step S1043, based on the notification or information, the wireless network decides on the allocation of wireless resources. For example, S-NSSAI#2 may be removed from the shared wireless resource usage in cell #C. The management function may be a function that performs service management and / or orchestration.

[0055] More specifically, the allocation of preferred / exclusive or shared radio resources managed by the RRM (radio resource management) policy may be based on a member list (rRMPolicyMemberList). The member list may include PLMNid and / or S-NSSAI, and the member list may be associated with preferred / exclusive or shared resource allocation groups. Here, when the network slice indicated by S-NSSAI#2 is released, S-NSSAI#2, which is associated with the shared resource allocation group of the RRM policy, may be removed from the RRM policy's member list in cell #C. Note that the management of the RRM policy described above may be performed by a management function that manages the radio network, or by the radio network itself.

[0056] Figure 14 is a flowchart illustrating an example (1-6) of network operation related to network slices in an embodiment of the present invention. In step S1051, cells #A, #B, and #C are set in a certain TA, and network slices identified by S-NSSAI#1 and S-NSSAI#2 are set in the TA. Wireless resources are allocated to S-NSSAI#1 and S-NSSAI#2 in cells #A and #B either as priority or dedicated. In cell #C, S-NSSAI#1 and S-NSSAI#2 are allocated wireless resources on a shared basis.

[0057] In the following step S1052, when the time-limited network slice identified by S-NSSAI#2 is terminated, the core network sends a notification or information regarding the termination of the time-limited network slice identified by S-NSSAI#2 to the management function. In the following step S1053, based on the notification or information, the management function determines the allocation of wireless resources. For example, S-NSSAI#2 may be removed from the shared wireless resource usage in cell #C. The management function may be a function that performs service management and / or orchestration.

[0058] More specifically, the allocation of preferred / exclusive or shared wireless resources managed by the RRM policy may be based on a member list (rRMPolicyMemberList). The member list includes PLMNid and / or S-NSSAI, and the member list may be associated with preferred / exclusive or shared resource allocation groups. Here, when the network slice indicated by S-NSSAI#2 is released, S-NSSAI#2, which is associated with the shared resource allocation group of the RRM policy, may be removed from the RRM policy's member list in cell #C. After the member list is updated, the management function may configure the wireless resources of the wireless network based on the RRM policy.

[0059] Figure 15 is a sequence diagram illustrating an example (2) of the operation related to a network slice in an embodiment of the present invention. In step S21, UE20 sends a Registration Request to AMF30A. In the following step S22, AMF30A sends a Registration Accept to UE20, which includes one or more Conditional S-NSSAIs and associated validity timers as Conditionally Allowed NSSAIs. For the sake of simplicity, here we refer to it as a Conditional "Allowed" NSSAI, but whether it is Allowed (whether use is permitted) is based on the associated conditions. Also, "conditional" may mean that it can be used if the conditions are met. Furthermore, the conditions may indicate whether the network slice is available or unavailable at a specific time (or time frame). Note that the Conditional Allowed NSSAI and associated validity timers may be set in the UE by pre-configuration or configuration update commands, rather than in the Registration Accept message.

[0060] Here, several implementation examples of conditionally allowed NSSAI can be considered. For example, a conditionally allowed NSSAI could be an Extended Allowed NSSAI, a PendingNSSAI, or a dedicated NSSAI that holds S-NSSAIs with conditions attached, which are neither Allowed NSSAI, PendingNSSAI, nor RejectedNSSAI.

[0061] In the following step S23, when UE20 receives an Allowed NSSAI that includes an effectiveness timer for an S-NSSAI corresponding to a temporary network slice, it starts the effectiveness timer. In the following step S24, when the effectiveness timer expires, UE20 removes the S-NSSAI from the Allowed NSSAI list and releases the PDU session associated with the S-NSSAI.

[0062] Here, the UE behavior when a conditionally allowed NSSAI is received may be determined. Also, the activation behavior for the timer count may be determined according to the timer value. Also, the behavior when a new timer value is received while the timer is active may be determined. Also, the behavior after the timer count expires may be determined. Also, the wireless network behavior when a time-limited network slice expires may be determined.

[0063] Figure 16 is a flowchart illustrating an example of terminal operation related to a network slice in an embodiment of the present invention (2-1). In step S201, the UE20 receives an S-NSSAI identifying a time-limited network slice from the core network as a conditionally allowed NSSAI. Furthermore, a timer indicating time-limited or validity may be associated with the S-NSSAI.

[0064] Furthermore, the S-NSSAI received by UE20 as a conditionally allowed NSSAI does not necessarily have to be received as part of an Allowed NSSAI IE (Information Element). For example, UE20 may receive a dedicated IE that contains a conditionally allowed NSSAI S-NSSAI, which is different from the Allowed NSSAI IE. This dedicated IE may contain one or more conditional S-NSSAIs and may also have associated timers indicating time-limited or valid status.

[0065] The S-NSSAI of a conditionally allowed NSSAI received by UE20 may be an HPLMN S-NSSAI. For example, in a roaming scenario, the S-NSSAI to which a timer is associated may not be an Allowed NSSAI (serving S-NSSAI), but rather one or more mapped S-NSSAIs (HPLMN S-NSSAIs) of the conditionally allowed NSSAI. Furthermore, in a roaming scenario, a dedicated IE containing the conditionally allowed NSSAI may consist of a combination of the Allowed NSSAI and / or one or more mapped S-NSSAIs (HPLMN S-NSSAIs) of the Allowed NSSAI and timers associated with those one or more mapped S-NSSAIs.

[0066] Furthermore, in a roaming scenario, if there are multiple mapped S-NSSAIs (HPLMN S-NSSAIs) for one conditionally allowed NSSAI (one conditionally allowed S-NSSAI), and the time constraints of these multiple mapped S-NSSAIs are the same, the core network may configure a dedicated IE by associating the multiple mapped S-NSSAIs with one timer. Furthermore, in a roaming scenario, if there are multiple mapped S-NSSAIs (HPLMN S-NSSAIs) for one conditionally allowed NSSAI (one conditionally allowed S-NSSAI), and the time constraints of one or more of these mapped S-NSSAIs are different, the core network may configure a dedicated IE by associating the mapped S-NSSAI with each timer.

[0067] In the following step S202, UE20 starts the timer. In step S203, if the timer has not expired, UE20 may send a NAS message, or if it receives a new timer associated with the S-NSSAI, it may stop the timer and start a new timer. In step S204, if the validity timer has expired, UE20 may suppress the sending of the NAS message.

[0068] Figure 17A is a flowchart illustrating an example of terminal operation related to a network slice when a Configured NSSAI is received in an embodiment of the present invention (2-2). In the operation shown in Figure 17A, the S-NSSAI may be held or stored in the NSSAI storage.

[0069] In step S211A, UE20 holds the conditionally allowed NSSAI in NSSAI storage.

[0070] In step S212A, when UE20 receives a new Configured NSSAI, if one or more S-NSSAIs that it holds as conditionally allowed NSSAIs are included in the received Configured NSSAI, it may remove those one or more S-NSSAIs from the conditionally allowed NSSAIs. At the same time, it may also remove the timers associated with those one or more S-NSSAIs.

[0071] Figure 17B is a flowchart illustrating an example (2-2) of terminal operation related to network slices when an Allowed NSSAI is received in an embodiment of the present invention. In the operation shown in Figure 17B, the S-NSSAI may be held or stored in NSSAI storage.

[0072] In step S211B, UE20 holds the conditionally allowed NSSAI in NSSAI storage. Furthermore, UE20 holds one or more conditionally allowed S-NSSAIs included in the conditionally allowed NSSAI as allowed NSSAIs.

[0073] In step S212B, UE20 may keep one or more S-NSSAIs held as conditionally allowed NSSAIs in NSSAI storage until the timer associated with them expires. Upon the expiration of the timer, UE20 may remove the one or more conditionally allowed S-NSSAIs from the allowed NSSAIs.

[0074] Figure 17C is a flowchart illustrating an example (2-2) of terminal operation related to a network slice when a conditionally allowed NSSAI is received in an embodiment of the present invention. In the operation shown in Figure 17C, the S-NSSAI may be held or stored in the NSSAI storage.

[0075] In step S211C, UE20 holds the conditionally allowed NSSAI in NSSAI storage. Furthermore, UE20 receives one or more new conditionally allowed NSSAIs and the timers associated with those conditionally allowed NSSAIs.

[0076] In step S212C, UE20 may replace all (any) conditional Allowed NSSAIs it holds with the conditional Allowed NSSAIs it has received. More specifically, UE20 may replace all (any) conditional Allowed NSSAIs of the PLMN, SNPN (Standalone Non-Public Network), or equivalent PLMN to which UE20 is connected with the conditional Allowed NSSAIs of the PLMN, SNPN (Standalone Non-Public Network), or equivalent PLMN (equivalent) to which UE20 is connected.

[0077] In step S213C, UE20 may delete all (any) timers associated with the conditionally allowed NSSAI that was replaced in step S212C. Furthermore, UE20 may retain the timers associated with the received conditionally allowed NSSAI.

[0078] Figure 17D is a flowchart illustrating an example of terminal operation (2-2) related to a network slice that receives a configuration update command with a registration request set in an embodiment of the present invention. In the operation shown in Figure 17D, S-NSSAI may be held or stored in NSSAI storage.

[0079] In step S211D, UE20 holds a conditional Allowed NSSAI and a timer associated with that conditional Allowed NSSAI.

[0080] In step S212D, UE20 receives a configuration update command. If the Configuration update indication IE included in the configuration update command is set to "registration requested" but does not contain any configuration update information regarding network slices, UE20 may delete all (any) conditional Allowed NSSAIs and the timers associated with those conditional Allowed NSSAIs.

[0081] Figure 18 is a flowchart illustrating an example (2-3) of terminal operation related to a network slice in an embodiment of the present invention. In step S221, the UE20 receives an S-NSSAI identifying a time-limited network slice from the core network as a conditionally allowed NSSAI. Furthermore, an effectiveness timer may be associated with the S-NSSAI.

[0082] In step S222, UE20 may ignore the validity timer if its timer value is "0" or "Deactivated," or if it is counting, it may stop the validity timer and assume that the timed nature of the network slice identified by the S-NSSAI has been eliminated, stopped, or released. Furthermore, if the validity timer's timer value is "Activated," UE20 may restart the validity timer's count, or if there is a validity timer that has stopped counting, it may set the validity timer to the remaining timer value obtained by subtracting the elapsed time since it stopped, and start counting, or if there is a validity timer that has stopped counting, it may set the validity timer to the remaining timer value at the time it stopped, and start counting. Additionally, if the validity timer's timer value is a number other than 0, UE20 may perform the actions shown in Figure 16 or Figures 17A-17D.

[0083] Figure 19 is a flowchart illustrating an example (2-4) of terminal operation related to a network slice in an embodiment of the present invention. In step S231, the UE20 receives an S-NSSAI identifying a time-limited network slice from the core network as a conditionally allowed NSSAI. Furthermore, an effectiveness timer may be associated with the S-NSSAI.

[0084] In the following step S232, UE20 starts the validity timer. In the following step S233, the validity timer expires. In the following step S234, UE20 sends a NAS message using default NSSAI to the core network. Note that default S-NSSAI does not need to have a timer associated with a time-limited network slice. Note that the behavior of UE20 when a timer associated with a time-limited network slice expires is not limited to this.

[0085] Figure 20 is a flowchart illustrating an example of network operation related to network slices in an embodiment of the present invention (2-1). In step S2001, if AMF30A does not receive from UE20 an indication of UE20's ability to support the time-limited network slice utilization function in the registration request, AMF30A may perform one or more of the operations shown in 1)-4) below.

[0086] 1) Do not allow the use of time-limited network slices in UE20. 2) Do not notify the UE20 of the S-NSSAI that identifies the time-limited network slice as an Allowed NSSAI. 3) Do not notify the UE20 of the S-NSSAI that identifies the time-limited network slice as a Rejected NSSAI. 4) Do not notify the UE20 of the S-NSSAI that identifies the time-limited network slice as a Configured NSSAI.

[0087] Furthermore, if AMF30A receives a registration request from UE20 indicating its capability to support the use of time-limited network slices, it will allow the UE to use the time-limited network slices.

[0088] Here, notification to the UE may be made in response to a registration request (registration permission) or in a configuration update command. Note that the operation shown in Figure 20 represents the behavior when UE20 supports this capability in the use of a time-limited network slice as an option for operator network operation, and does not indicate that UE's support for this capability is mandatory in all cases when using a time-limited network slice.

[0089] Figure 21 is a flowchart illustrating an example of network operation related to network slices in an embodiment of the present invention (2-2). In step S2011, cells #A, #B, and #C are set in a certain TA, and network slices identified by S-NSSAI#1 and S-NSSAI#2 are set in the TA. Wireless resources are allocated to S-NSSAI#1 and S-NSSAI#2 in cells #A and #B either as priority or dedicated. Wireless resources are allocated to S-NSSAI#1 and S-NSSAI#2 in cell #C as shared.

[0090] In step S2012, when the time-limited network slice identified by S-NSSAI#2 is terminated, the wireless network receives notification or information regarding the termination of the time-limited network slice identified by S-NSSAI#2 from the core network or management function. The management function may be a function that manages and / or orchestrates services.

[0091] In step S2013, based on the notification or information, the wireless network determines the allocation of wireless resources. For example, S-NSSAI#2 may be removed from the shared wireless resource usage in cell #C.

[0092] More specifically, the allocation of preferred / exclusive or shared wireless resources managed by the RRM policy may be based on a member list (rRMPolicyMemberList). The member list may include PLMNid and / or S-NSSAI, and the member list may be associated with preferred / exclusive or shared resource allocation groups. Here, when the network slice indicated by S-NSSAI#2 is released, S-NSSAI#2, which is associated with the shared resource allocation group of the RRM policy, may be removed from the RRM policy member list in cell #C. Note that the management of the RRM policy described above may be performed by a management function that manages the wireless network, or by the wireless network itself.

[0093] Figure 22 is a flowchart illustrating an example (2-3) of network operation related to network slices in an embodiment of the present invention. In step S2021, cells #A, #B, and #C are set in a certain TA, and network slices identified by S-NSSAI#1 and S-NSSAI#2 are set in the TA. Wireless resources are allocated to S-NSSAI#1 and S-NSSAI#2 in cells #A and #B either as Prioritized or Dedicated. Wireless resources are allocated to S-NSSAI#1 and S-NSSAI#2 in cell #C as Shared.

[0094] In step S2022, when a time-limited network slice identified by S-NSSAI#2 is terminated, the core network sends a notification or information regarding the termination of the time-limited network slice identified by S-NSSAI#2 to the management function. The management function may be a function that manages and / or orchestrates services.

[0095] In step S2023, the management function determines the allocation of wireless resources based on the notification or information. For example, S-NSSAI#2 may be removed from the shared wireless resource usage in cell #C.

[0096] More specifically, the allocation of preferred / exclusive or shared wireless resources managed by the RRM policy may be based on a member list (rRMPolicyMemberList). The member list includes PLMNid and / or S-NSSAI, and the member list may be associated with preferred / exclusive or shared resource allocation groups. Here, when the network slice indicated by S-NSSAI#2 is released, S-NSSAI#2, which is associated with the shared resource allocation group of the RRM policy, may be removed from the RRM policy's member list in cell #C. After the member list is updated, the management function may configure the wireless resources of the wireless network based on the RRM policy.

[0097] Figure 23 is a sequence diagram illustrating an example (3) of the operation related to network slicing in an embodiment of the present invention. In step S31, UE20 makes a decision on whether to perform the PDU session establishment procedure based on URSP (UE Route Selection Policy). If the decision is true, the process proceeds to step S32 and the PDU session establishment procedure is performed. If the decision is false, the PDU session establishment procedure is not performed.

[0098] When using URSP's Time Window to determine whether to perform the above PDU session establishment procedure, it was difficult to use URSP's Time Window for both time-limited network slices and normal traffic control because there is only one Time Window per network slice. Therefore, it is acceptable to set multiple Time Windows for a single network slice.

[0099] Figure 24 is a flowchart illustrating an example of terminal operation related to network slicing in an embodiment of the present invention (3-1). In step S301, UE20 determines the truth value of the Slice Validation Indication of the URSP's RSD (Route Selection Descriptor). If the Slice Validation Indication is true, the process proceeds to step S302; otherwise, it proceeds to step S303.

[0100] In step S302, UE20 determines whether the current time falls within the time window of the Route Selection Validation Criteria. If it is within the time window (YES in S302), it proceeds to step S303; if it is outside the time window (NO in S302), it terminates the flow. In step S303, UE20 sends a PDU session establishment request to the network.

[0101] Furthermore, the UE20 performing the operation shown in Figure 24 may perform the PDU session establishment procedure determination during the PDU session establishment procedure, or when the validity of the rules defined by URSP changes, or it may continuously monitor changes in the validity of the rules defined by URSP.

[0102] More specifically, when UE20 sends a PDU session establishment request to the core network, it checks the Time Window information of the Route Selection Validation Criteria if the Slice Validation Indication of the URSP's RSD is true. The Time Window information consists of information indicating the start time and stop time (for convenience, the period from the start time to the stop time is called the time window). If the time at which UE20 sends the PDU session establishment request falls within the Time Window, it may send the PDU session establishment request.

[0103] Furthermore, if the current time exceeds the time window specified by the Route Selection Validation Criteria Time Window information of the URSP's RSD, UE20 may pre-determine that the PDU session establishment procedure should not be performed. In other words, UE20 may recognize that the validity of the rules set by URSP has changed because the time window specified by the Route Selection Validation Criteria Time Window information of the URSP's RSD has exceeded, and pre-determine that the PDU session establishment procedure should not be performed. UE20, having determined that the PDU session establishment procedure should not be performed, may also notify higher layers that a PDU session cannot be established using that network slice.

[0104] Furthermore, the UE may monitor at any time whether the current time has passed the time window specified by the Route Selection Validation Criteria Time Window information of the URSP's RSD. If, during monitoring at any time, the current time has passed the time window specified by the Route Selection Validation Criteria Time Window information of the URSP's RSD, the UE may pre-determine that the PDU session establishment procedure should be performed as false. If the UE20 determines that the PDU session establishment procedure should be performed as false, it may notify the upper layer that a PDU session cannot be established using that network slice.

[0105] Figure 25 is a flowchart illustrating an example of terminal operation related to network slicing in an embodiment of the present invention (3-2). In step S311, UE20 determines whether the current time is within the time window of the Slice Selection Validation Criteria of the URSP's RSD. If it is within the time window (YES in S311), the process proceeds to step S312; if it is outside the time window (NO in S311), the flow terminates. In step S312, UE20 sends a PDU session establishment request to the network.

[0106] Furthermore, the UE20 performing the operation shown in Figure 25 may perform the PDU session establishment procedure determination during the PDU session establishment procedure, or when the validity of the rules defined by URSP changes, or it may continuously monitor changes in the validity of the rules defined by URSP.

[0107] More specifically, when UE20 sends a PDU session establishment request to the core network, it checks the Time Window information of the Slice Selection Validation Criteria in the URSP's RSD. The Time Window information consists of information indicating the start time and stop time (for convenience, the period from the start time to the stop time is called the time window). If the time at which UE20 sends the PDU session establishment request falls within the Time Window time window, it may send the PDU session establishment request. The Slice Selection Validation Criteria may be information set in URSP separately from the Route Selection Validation Criteria. The Slice Selection Validation Criteria contains Time Window information and may be used, for example, to determine whether a PDU session establishment procedure using a time-limited network slice is being performed.

[0108] Furthermore, if the current time has passed the time window specified by the Time Window information of the Slice Selection Validation Criteria in the URSP's RSD, UE20 may pre-determine that the PDU session establishment procedure should not be performed. In other words, UE20 may recognize that the validity of the rules set by URSP has changed because the time window specified by the Time Window information of the Slice Selection Validation Criteria in the URSP's RSD has passed, and pre-determine that the PDU session establishment procedure should not be performed. UE20, having determined that the PDU session establishment procedure should not be performed, may also notify higher layers that a PDU session cannot be established using that network slice.

[0109] Furthermore, the UE may, at any time, monitor whether the current time has passed the time window specified by the Time Window information of the URSP's RSD's Slice Selection Validation Criteria. If, during monitoring at any time, the current time has passed the time window specified by the URSP's RSD's Slice Selection Validation Criteria's Time Window information, the UE may pre-determine that the PDU session establishment procedure should be performed as false. The UE, having determined that the PDU session establishment procedure should be performed as false, may notify the upper layer that a PDU session cannot be established using that network slice.

[0110] URSP is a policy used by the UE to determine how traffic is routed. For example, UE20 may check the URSP when establishing a new PDU session, or it may check the URSP for routing an already established PDU session. The URSP may include the Time Window information mentioned above.

[0111] In the embodiments described above, the core network can provide time-limited network slices to the UE based on a timer or URSP.

[0112] In other words, it is possible to provide a time-limited network slice service in a communication system.

[0113] (Device configuration) Next, we will describe an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processes and operations described above. The base station 10, network node 30, and terminal 20 include the functions to perform the embodiments described above. However, the base station 10, network node 30, and terminal 20 may each have only some of the functions in the embodiments.

[0114] <Base station 10 and network node 30> Figure 26 is a diagram showing an example of the functional configuration of the base station 10. As shown in Figure 26, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 26 is merely an example. The functional classifications and names of the functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions on the system architecture may be composed of multiple network nodes 30 separated by function.

[0115] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 or other network node 30 and transmitting the signal by wire or wireless. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 or other network node 30 and obtaining information from the received signal, for example, information from a higher layer.

[0116] The configuration unit 130 stores pre-configured configuration information and various configuration information to be transmitted to the terminal 20 in a storage device, and reads it from the storage device as needed. The contents of the configuration information include, for example, settings related to network slices.

[0117] The control unit 140 performs processing related to network slicing in the network, as described in the embodiment. The control unit 140 also performs processing related to communication with the terminal 20. The signal transmission function of the control unit 140 may be included in the transmission unit 110, and the signal reception function of the control unit 140 may be included in the reception unit 120.

[0118] <Terminal 20> Figure 27 is a diagram showing an example of the functional configuration of terminal 20. As shown in Figure 27, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 27 is merely an example. Any functional classification and functional unit names are acceptable as long as they enable the operation according to the embodiment of the present invention.

[0119] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals or reference signals transmitted from the network node 30.

[0120] The configuration unit 230 stores various configuration information received from the network node 30 by the receiving unit 220 in its storage device and reads it from the storage device as needed. The configuration unit 230 also stores pre-configured configuration information. The content of the configuration information includes, for example, settings related to network slices.

[0121] The control unit 240 performs processing related to connection control to the network and network slices, as described in the embodiment. The signal transmission function in the control unit 240 may be included in the transmission unit 210, and the signal reception function in the control unit 240 may be included in the reception unit 220.

[0122] (Hardware configuration) The block diagrams (Figures 26 and 27) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the one or more devices with software.

[0123] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. As mentioned above, the method of implementation is not particularly limited.

[0124] For example, the network node 30, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 28 is a diagram showing an example of the hardware configuration of a base station 10 and terminal 20 according to one embodiment of the present disclosure. The network node 30 may have a hardware configuration similar to that of the base station 10. The base station 10 and terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0125] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured to omit some of the devices.

[0126] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of the reading and writing of data in the storage device 1002 and auxiliary storage device 1003.

[0127] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0128] Furthermore, the processor 1001 reads programs (program code), software modules, or data, etc., from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes a computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 26 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 27 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunications line.

[0129] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of this disclosure.

[0130] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0131] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include high-frequency switches, duplexers, filters, frequency synthesizers, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmit / receive antenna, amplifier section, transmit / receive section, transmission path interface, etc., may be implemented by the communication device 1004. The transmit / receive section may be implemented with physically or logically separated transmitting and receiving sections.

[0132] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0133] Furthermore, each device, such as the processor 1001 and the storage device 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0134] Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0135] Figure 29 shows an example of the configuration of vehicle 2001. As shown in Figure 29, vehicle 2001 comprises a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0136] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

[0137] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0138] Signals from various sensors 2021-2029 include current signals from current sensor 2021 which senses motor current, front and rear wheel rotation speed signals obtained by rotation speed sensor 2022, front and rear wheel air pressure signals obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal depression signals obtained by accelerator pedal sensor 2029, brake pedal depression signals obtained by brake pedal sensor 2026, shift lever operation signals obtained by shift lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0139] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Services Unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0140] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0141] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via its communication port 2033 to the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001.

[0142] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0143] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above input.

[0144] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in memory 2032, which is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0145] (Summary of the embodiments) As described above, according to an embodiment of the present invention, a terminal is provided which includes a receiving unit that receives information identifying a network slice and a timer value associated with the network slice from the core network, and a control unit that, upon receiving the information identifying the network slice and the timer value, starts a timer that sets the timer value, and the control unit, upon the expiration of the timer, suppresses the transmission of a NAS (Non-Access Stratum) message to the core network using the information identifying the network slice.

[0146] With the above configuration, the core network can provide time-limited network slices to the UE based on a timer or URSP. In other words, it can provide time-limited network slice services in a communication system.

[0147] If the control unit receives another timer value associated with the same network slice as the network slice while the timer is operating, it may stop the timer and start a timer that sets the other timer value. With this configuration, the core network can provide time-limited network slices to the UE based on the timer or URSP.

[0148] The receiving unit may further receive information identifying an authorized network slice, which includes information identifying the network slice, and the control unit may start a timer that sets a value obtained by subtracting the elapsed time from the time the information identifying the network slice and the timer value were received to the time the information identifying the authorized network slice was received from the timer value. With this configuration, the core network can provide a time-limited network slice to the UE based on the timer or URSP.

[0149] When the timer expires, the receiving unit receives information identifying a network slice to replace the network slice, and the control unit may use the replacement network slice to perform a registration request procedure. With this configuration, the core network can provide time-limited network slices to the UE based on the timer or URSP.

[0150] The control unit may determine whether the current time is included in the time frame contained in the information for routing traffic, and if the current time is included in the time frame, it may execute a PDU (Protocol Data Unit) session establishment procedure. With this configuration, the core network can provide time-limited network slices to the UE based on a timer or URSP.

[0151] Furthermore, according to an embodiment of the present invention, a network node is provided which includes a transmitting unit that transmits information identifying a network slice and a timer value associated with the network slice to a terminal, and a control unit that, when it transmits the information identifying the network slice and the timer value, starts a timer that sets the timer value, and when the timer expires, the transmitting unit transmits information identifying a network slice to replace the network slice and a timer value associated with the replacement network slice to the terminal at different timings for each terminal.

[0152] With the above configuration, the core network can provide time-limited network slices to the UE based on a timer or URSP. In other words, it can provide time-limited network slice services in a communication system.

[0153] (Supplement to the embodiment) While embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. Regarding the processing procedures described in the embodiments, the order of processing may be changed as long as it does not contradict each other. For the convenience of explaining the processing, the network node 30 and terminal 20 have been described using a functional block diagram, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of the network node 30 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0154] Furthermore, the notification of information is not limited to the embodiments / models described herein and may be carried out by other methods. For example, the notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0155] Each aspect / embodiment described in this disclosure may be applied to at least one of the following systems: LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

[0156] Each aspect / embodiment described in this disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), and IEEE This may apply to at least one system utilizing 802.20, UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. It may also apply to a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G).

[0157] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0158] In this specification, specific operations performed by network node 30 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having network node 30, it is clear that various operations performed for communication with terminal 20 can be performed by network node 30 and at least one other network node (for example, MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides network node 30, the other network node may be a combination of multiple other network nodes (for example, MME and S-GW).

[0159] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0160] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0161] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0162] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0163] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0164] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0165] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0166] The terms “system” and “network” as used in this disclosure are interchangeable.

[0167] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or corresponding other information. For example, wireless resources may be indicated by an index.

[0168] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0169] In this disclosure, terms such as "base station (BS)", "wireless base station", "base station equipment", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0170] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0171] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform information-based control or operation.

[0172] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0173] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0174] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0175] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything)). In this case, the terminals 20 may have the functions that the network node 30 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to inter-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0176] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

[0177] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in a table, database, or other data structure), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0178] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0179] The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard.

[0180] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0181] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

[0182] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0183] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0184] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0185] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0186] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0187] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0188] <Note> The embodiments described above can also be further described as follows (see addendum).

[0189] (Note 1) A receiving unit that receives information identifying a network slice and a timer value associated with the network slice from the core network, The system includes information identifying the network slice and a control unit that, upon receiving the timer value, starts a timer that sets the timer value. The control unit is a terminal that, when the timer expires, suppresses the transmission of NAS (Non-Access Stratum) messages to the core network using information that identifies the network slice.

[0190] (Note 2) The terminal described in Appendix 1, which, when the control unit receives another timer value associated with the same network slice as the network slice while the timer is operating, stops the timer and starts a timer to set the other timer value.

[0191] (Note 3) The receiving unit further receives information identifying an authorized network slice, which includes information identifying the network slice. The control unit is a terminal as described in Appendix 1, which starts a timer that sets a value obtained by subtracting the elapsed time from the time it receives the information identifying the network slice and the timer value to the time it receives the information identifying the permitted network slice from the timer value.

[0192] (Note 4) When the timer expires, the receiving unit receives information identifying a network slice to replace the network slice. The control unit is the terminal described in Appendix 1 that executes the registration request procedure using the alternative network slice.

[0193] (Note 5) The control unit determines whether the current time is included in the time frame included in the information for routing traffic, and if the current time is included in the time frame, the terminal described in Appendix 1 executes the PDU (Protocol Data Unit) session establishment procedure.

[0194] (Note 6) A transmission unit that transmits information identifying a network slice and a timer value associated with the network slice to a terminal, The system includes a control unit that, upon receiving information identifying the network slice and the timer value, starts a timer that sets the timer value, The transmitting unit is a network node that, when the timer expires, transmits to the terminal information identifying a network slice to replace the network slice and a timer value associated with the replacement network slice at different timings for each terminal. [Explanation of Symbols]

[0195] 10 base station 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 devices 210 Transmitter 220 Receiver 230 Setting section 240 Control Unit 30 network nodes 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive Unit 2003 Steering Department 2004 Accelerator pedal 2005 Brake pedal 2006 Shift Lever 2007 Front Wheel 2008 Rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 Rotation speed sensor 2023 Pneumatic Sensor 2024 Vehicle Speed ​​Sensor 2025 Accelerometer 2026 Brake Pedal Sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driver Support Systems Department 2031 Microprocessor 2032 memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

1. A transmission unit that sends registration requests to the core network, A receiving unit that receives registration permission from the core network, which includes information identifying a network slice and an effectiveness timer value associated with the network slice. The system includes a control unit that, upon receiving information identifying the network slice and the effectiveness timer value, starts a timer that sets the effectiveness timer value, The control unit controls the terminals that utilize the network slice until the timer expires.

2. A receiving unit that receives registration requests from the terminal, A transmission unit that transmits registration permission to the terminal, including information identifying a network slice and an effectiveness timer value associated with the network slice, The system includes a control unit that, upon receiving information identifying the network slice and the effectiveness timer value, starts a timer that sets the effectiveness timer value, The control unit is a network node that allows the terminal to use the network slice until the timer expires.

3. The transmitting unit transmits a configuration update to the terminal, which includes information identifying the network slice and the validity timer value. When the control unit transmits information identifying the network slice and the validity timer value, it starts the timer that sets the validity timer value. The network node according to claim 2, wherein the control unit permits the terminal to use the network slice until the timer expires.

4. In the case of a roaming scenario, the transmitting unit transmits a registration request or configuration update to the terminal, which includes information identifying the mapped network slice of HPLMN (Home Public Land Mobile Network) and the validity timer value. When the control unit transmits information identifying the network slice and the validity timer value, it starts the timer that sets the validity timer value. The network node according to claim 2, wherein the control unit permits the terminal to use the network slice until the timer expires.

5. If the receiving unit does not receive a registration request from the terminal that includes the ability to support a time-limited network slice utilization function, the control unit shall not transmit to the terminal a registration permission that includes information identifying the network slice to which the validity timer value is associated as a set S-NSSAI (Single-Network Slice Selection Assistance Information).

6. The procedure for sending a registration request to the core network, A procedure for receiving registration permission from the core network, which includes information identifying a network slice and an effectiveness timer value associated with the network slice, When information identifying the network slice and the validity timer value are received, a procedure for starting a timer to set the validity timer value, A communication method in which a terminal performs the procedure for using the network slice until the timer expires.

Images