JP7342954B2 - Communication method, core network node, and wireless terminal - Google Patents

Description

The present disclosure relates to a wireless terminal, a core network node, and a control method.

The telecommunications industry is working on a new generation of networks called fifth generation (5G) networks. Activities are being initiated at multiple research and standards organizations to develop 5G networks that serve multiple vertical service providers and serve a wide variety of terminals. In particular, the 3rd Generation Partnership Project (3GPP) is studying next-generation communication technology and system architecture for a 5G network, which is a next-generation mobile communication system. In particular, 3GPP is specifying 5GS (5G System) as a system for realizing a 5G mobile communication system. The specifications of 5GS are disclosed in, for example, Non-Patent Document 1, Non-Patent Document 2, and Non-Patent Document 3.

For example, one of the main features of 5GS is the specification of network slicing technology.

A network slice is a logical collection of network functions and resources that implement a communication service in a specific use case. Network slicing is a process of dividing one physical network into multiple slices.

Non-Patent Document 1 describes a process in which a wireless terminal (UE; User Equipment) uses S-NSSAI (Single Network Slice Selection Assistance information).

S-NSSAI may be configured with SST (Slice/Service type) and SD (Slice Differentiator). Furthermore, S-NSSAI may be configured only with SST. Note that the SST may indicate a function or service aspect of a network slice, and the SD may be complementary information used to identify network slices indicated by the same SST.

A network slice instance is a network slice that includes a control plane (c-plane; cp) function and a user plane (u-plane; up) function as described in Non-Patent Document 1. This is the actual situation.

Regarding the relationship between S-NSSAIs and network slice instances, a plurality of different S-NSSAIs may be associated with one network slice instance. Further, one S-NSSAI may be associated with one network slice instance, or may be associated with a plurality of different network slice instances. The network selects an appropriate network slice instance using S-NSSAI or the like. The network slice instance selection function is described in Section 5.15 of Non-Patent Document 1. The network slice instance selected here provides network slice-specific services to the UE.

NSSAI (Network Slice Selection Assistance Information) is a collection of S-NSSAI. Furthermore, there are five types of NSSAI: Configured NSSAI, Rejected NSSAI, Allowed NSSAI, Requested NSSAI, and Subscribed NSSAI.

Requested NSSAI includes one or more S-NSSAIs that the UE sends to the network. Allowed NSSAI includes one or more S-NSSAIs that the network allows use. Rejected NSSAI includes S-NSSAIs that the network has refused to use, and each S-NSSAI included in Rejected NSSAI is associated with a cause value. The Configured NSSAI includes one or more S-NSSAIs that are indicated to the UE as being applicable to one or more PLMNs (Public land mobile networks). Subscribed NSSAI includes S-NSSAI based on subscriber information that a UE has subscribed for use of a certain PLMN.

Furthermore, in 3GPP, studies are underway on network slice-specific authentication and authorization functions. Details of authentication and authorization procedures specific to network slices are described in Section 5.15 of Non-Patent Document 1. As described in Non-Patent Document 1, the network slice-specific authentication and authorization procedure is activated by the network, and the network ultimately notifies the UE of the network slice-specific authentication and authorization results. .

3GPP TS 23.501 V16.1.0 (2019-06) 3GPP TS 23.502 V16.1.1 (2019-06) 3GPP TS 24.501 V16.1.0 (2019-06)

In 3GPP, studies are underway on authentication and authorization functions specific to network slices. However, it is not clear how the UE (User Equipment) and the network operate when the network becomes abnormal while performing authentication and authorization procedures specific to network slices. Note that an abnormal state may be a state in which the execution of an authentication and authorization procedure specific to a network slice has been started, but the execution of the procedure is delayed. Alternatively, the abnormal state may be a state in which, although execution of an authentication and authorization procedure specific to a network slice has been started, signals between devices necessary for the procedure are lost. Alternatively, an abnormal state may be a state in which authentication and authorization procedures specific to a network slice are not activated even though they are required to be executed.

In this case, the network has no way to notify the UE of the network's semi-normal state, so the UE cannot know that the network has become semi-normal. Thus, for example, a problem may arise where the UE waits indefinitely for the initiation and/or completion of network slice-specific authentication and authorization procedures from the network. In other words, the UE and network that support the authentication and authorization procedure functions specialized for network slices will no longer be able to provide services using the authentication and authorization functions specialized for network slices.

The present disclosure has been made in view of these circumstances, and its purpose is to solve or at least alleviate the problem that the UE cannot know that a semi-normal state is occurring in the network. Including.

In one aspect of the present disclosure, the wireless terminal receives a registration permission message that includes at least one information indicating that an authentication and authorization procedure specified for a first network slice is pending. and a control unit that starts a timer for determining that the network slice specified authentication and authorization procedure is semi-normal based on reception of the registration permission message.

In one aspect of the present disclosure, the core network node sends a registration permission message to the wireless terminal that includes at least one information indicating that an authentication and authorization procedure specified for a first network slice is pending. and a control unit that starts a timer for determining that the authentication and authorization procedures specified for network slices are semi-normal based on the transmission of the registration permission message. .

According to the present disclosure, the UE can know that semi-normality is occurring in the network.

FIG. 3 is a schematic configuration diagram of a UE according to each aspect. FIG. 3 is a schematic configuration diagram of an AMF according to each embodiment. FIG. 3 is a configuration diagram of a UE according to each aspect. FIG. 3 is an AMF configuration diagram according to each embodiment. It is a figure which shows the initial procedure which is a premise of each aspect. FIG. 6 is a diagram illustrating network slice-specific authentication and authorization procedures according to each aspect. FIG. 3 is a diagram showing a reconnection procedure using S-NSSAI according to the first aspect. FIG. 3 is a diagram showing a reconnection procedure using S-NSSAI according to the first aspect. FIG. 3 is a diagram showing a reconnection procedure using S-NSSAI according to the first aspect. FIG. 7 is a diagram showing a reconnection procedure using S-NSSAI according to a second embodiment. FIG. 7 is a diagram showing a reconnection procedure using S-NSSAI according to a second embodiment. FIG. 7 is a diagram showing a reconnection procedure using S-NSSAI according to a second embodiment. FIG. 7 is a diagram showing a reconnection procedure using S-NSSAI according to a third aspect. FIG. 7 is a diagram showing a reconnection procedure using S-NSSAI according to a third aspect. FIG. 7 is a diagram showing a reconnection procedure using S-NSSAI according to a third aspect. FIG. 12 is a diagram showing a reconnection procedure using S-NSSAI when spanning AMFs according to a fourth aspect.

(Mobile communication system according to the present disclosure)
A mobile communication system according to the present disclosure will be described with reference to FIGS. 1 to 6.

FIG. 1 is a diagram showing an example of a device configuration of a UE. UE 10 may be a computer device whose processor operates by executing a program stored in memory. The UE 10 may be, for example, a mobile phone terminal, a smartphone terminal, or a tablet terminal. Further, the UE 10 may be an IoT (Internet of Things) terminal or an MTC (Machine Type Communication) terminal.

The UE 10 includes a communication section 11 and a control section 12. The communication unit 11 and the control unit 12 may be software or modules whose processing is executed by a processor executing a program stored in a memory. Alternatively, the communication unit 11 and the control unit 12 may be hardware such as a circuit or a chip.

The communication unit 11 is a functional unit that allows the UE 10 to connect to an access network and connect to the core network via the access network. In other words, the UE 10 can transmit and receive user data and/or control information to and from the access network and/or the core network via the communication unit 11.

The control unit 12 is a functional unit for controlling the UE 10, and realizes various processes of the entire UE 10 by reading and executing various information and programs stored in the memory.

Details of a configuration example of the UE 10, which will be explained in each aspect below, will be described using FIG. 3.

FIG. 3 is a block diagram showing a configuration example of the UE 10. A Radio Frequency (RF) transceiver 1101 performs analog RF signal processing for communicating with Non-3GPP access such as WLAN, eNB (evolved NodeB), or gNB (next generation NodeB). Analog RF signal processing performed by RF transceiver 1101 includes frequency upconversion, frequency downconversion, and amplification. RF transceiver 1101 is coupled with antenna 1102 and baseband processor 1103. That is, RF transceiver 1101 receives modulation symbol data from baseband processor 1103, generates a transmit RF signal, and provides the transmit RF signal to antenna 1102. The modulation symbol data may be OFDM (Orthogonal Frequency Division Multiplexing) symbol data. Further, RF transceiver 1101 generates a baseband reception signal based on the reception RF signal received by antenna 1102, and supplies this to baseband processor 1103. Furthermore, the UE 10 may also communicate using wired media. In this case, Radio Frequency (RF) transceiver 1101 is not connected to antenna 1102 and operates as an adapter for communicating with wired media.

The baseband processor 1103 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. Digital baseband signal processing includes (a) data compression/decompression, (b) data segmentation/concatenation, and (c) transmission format (transmission frame) generation/decomposition. Digital baseband signal processing includes (d) channel encoding/decoding. Digital baseband signal processing includes (e) modulation (symbol mapping)/demodulation, and (f) generation of OFDM symbol data (baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT). On the other hand, control plane processing includes communication management of layer 1 (e.g., transmission power control) and layer 2 (e.g., radio resource management, and hybrid automatic repeat request (HARQ) processing). Control plane processing includes Layer 3 (e.g., signaling for attach, mobility, and call management) communication management.

For example, in the case of LTE (Long Term Evolution) and LTE-Advanced, digital baseband signal processing by baseband processor 1103 may include a Packet Data Convergence Protocol (PDCP) layer. Digital baseband signal processing may include Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer signal processing. Further, the control plane processing by the baseband processor 1103 may include processing of a Non-Access Stratum (NAS) protocol, a Radio Resource Control (RRC) protocol, and a MAC CE (Control Element).

The baseband processor 1103 may include a modem processor (e.g., Digital Signal Processor (DSP)) that performs digital baseband signal processing. The baseband processor 1103 may include a protocol stack processor that performs control plane processing. The protocol stack processor may be, for example, a Central Processing Unit (CPU) or a Micro Processing Unit (MPU). In this case, the protocol stack processor that performs control plane processing may be shared with the application processor 1104, which will be described later.

Application processor 1104 is also referred to as a CPU, MPU, microprocessor, or processor core. Application processor 1104 may include multiple processors (multiple processor cores). Application processor 1104 executes a system software program (Operating System (OS)) read from memory 1106 or a memory not shown. The application processor realizes various functions of the UE 10 by executing various application programs. The application program may be, for example, a telephone call application, a web browser, a mailer, a camera operation application, or a music playback application.

In some implementations, baseband processor 1103 and application processor 1104 may be integrated on one chip, as shown by the dashed line (1105) in FIG. 3. In other words, the baseband processor 1103 and the application processor 1104 may be implemented as one System on Chip (SoC) device 1105. An SoC device is sometimes called a system Large Scale Integration (LSI) or chipset.

Memory 1106 is volatile memory or non-volatile memory or a combination thereof. Memory 1106 may include multiple physically independent memory devices. Volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof. Non-volatile memory is masked Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or a hard disk drive. or non-volatile memory is any combination thereof. For example, memory 1106 may include external memory devices accessible from baseband processor 1103, application processor 1104, and SoC 1105. Memory 1106 may include embedded memory devices integrated within baseband processor 1103, within application processor 1104, or within SoC 1105. Memory 1106 may include memory within a Universal Integrated Circuit Card (UICC).

Memory 1106 may store software modules (computer programs) that include instructions and data for processing by UE 10 as described in the aspects above. In some implementations, baseband processor 1103 or application processor 1104 may be configured to retrieve and execute such software modules from memory 1106 to perform processing for UE 10 as described in aspects below.

FIG. 2 shows an example of the device configuration of the AMF (Access and Mobility management Function) 30. AMF 30 includes a communication section 31 and a control section 32. The communication unit 31 and the control unit 32 may be software or modules whose processing is executed by a processor executing a program stored in a memory. Alternatively, the communication section 31 and the control section 32 may be hardware such as a circuit or a chip.

The communication unit 31 is a functional unit for connecting the AMF 30 to a core network device included in an access network or a core network. In other words, the AMF 30 can transmit and receive user data and/or control information to and from the core network device included in the access network and/or the core network via the communication unit 31.

The control unit 32 is a functional unit for controlling the AMF 30, and realizes various processes of the entire AMF 30 by reading and executing various information and programs stored in the memory.

With reference to FIG. 4, details of a configuration example of the AMF 30, which will be explained in multiple aspects below, will be described.

FIG. 4 is a block diagram showing a configuration example of the AMF 30. Referring to FIG. 4, AMF 30 includes a network interface 1201, a processor 1202, and a memory 1203. Network interface 1201 is used to communicate with other network node devices that make up the communication system. Network interface 1201 may include, for example, a network interface card (NIC) compliant with the IEEE 802.3 series.

The processor 1202 reads software (computer program) from the memory 1203 and executes it, thereby performing the processing of the AMF 30 explained using the sequence diagram in the above embodiment. The processor 1202 may be, for example, a microprocessor, an MPU (Micro Processing Unit), or a CPU (Central Processing Unit). Processor 1202 may include multiple processors.

Memory 1203 is configured by a combination of volatile memory and nonvolatile memory. Memory 1203 may include storage located remotely from processor 1202. In this case, processor 1202 may access memory 1203 via an I/O interface (not shown).

In the example of FIG. 4, memory 1203 is used to store software modules. The processor 1202 reads out and executes these software module groups from the memory 1203, thereby being able to perform the processing of the AMF 30, which will be described in later aspects.

As described using FIG. 4, each of the processors included in the AMF 30 executes one or more programs including a group of instructions for causing a computer to perform the algorithm described using the drawings.

In the examples above, the program may be stored and provided to the computer using various types of non-transitory computer readable media. Non-transitory computer-readable media includes various types of tangible storage media. Examples of non-transitory computer-readable media include magnetic recording media (eg, floppy disks, magnetic tape, hard disk drives), magneto-optical recording media (eg, magneto-optical disks). Furthermore, examples of non-transitory computer-readable media include CD-ROM (Read Only Memory), CD-R, and CD-R/W. Further examples of non-transitory computer readable media include semiconductor memory. Semiconductor memories include, for example, mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, and RAM (Random Access Memory). The program may also be provided to the computer on various types of transitory computer readable media. Examples of transitory computer-readable media include electrical signals, optical signals, and electromagnetic waves. The temporary computer-readable medium can provide the program to the computer via wired communication channels, such as electrical wires and fiber optics, or wireless communication channels.

Examples of procedures related to each aspect will be explained below, but before that, main terms and information will be explained. Note that the information in each aspect may be information included in messages sent and received between the UE and AMF, information held within the UE, or information held within the core network. It may be information.

The core network refers to at least some of AMF 30, SMF (Session Management Function) 40, UPF (User Plane Function) 50, UDM (Unified Data Management) 60, and AAA (Authentication, Authorization, and Accounting) 70. , core network, or core network device. That is, the fact that the core network sends and receives messages and/or executes procedures means that devices within the core network send and receive messages and/or execute procedures.

The access network is a wireless network that connects the UE and the core network. The access network may be a 3GPP network or a non-3GPP network. The 3GPP network may be the NG-(R)AN 20, which refers to at least a portion of the gNB 21 and the ng-eNB 22, and may also be referred to as the NG-(R)AN or the NG-(R)AN device. In other words, the fact that NG-(R)AN sends and receives messages and/or executes procedures means that devices within NG-(R)AN send and receive messages and/or execute procedures. Note that the gNB may be a gNB having an NR (New Radio) function that configures NG-(R)AN. The ng-eNB 22 may be an eNB having an E-UTRA (Evolved Universal Terrestrial Radio Access) function that configures the NG-(R)AN.

N1 mode is a UE mode that allows access to the core network via the access network. Further, the N1 mode may be a UE mode in which messages can be sent and received using the N1 interface.

S1 mode is a UE mode in which messages can be sent and received using the S1 interface. Note that the S1 interface may be composed of an S1-MME interface and an S1-U interface.

The core network manages the location of the UE using a set of adjacent cells called a tracking area (TA) as a unit. A tracking area is identified by a Tracking Area Identifier (TAI).

A tracking area list (also referred to as a TA list) is a list that includes one or more TAs. Also, a set of one or more TAs is sometimes expressed as a registration area (RA).

The first network slice information may be the Requested NSSAI or the NSSAI sent by the UE during a registration procedure. The UE may include the first network slice information in an initial registration, mobility registration update, or periodic registration update message.

The first support information is information or capability information indicating whether the UE supports a network slice-specific authentication and authorization procedure. good. The UE may include the first supporting information in an initial registration, mobility registration update, or periodic registration update message.

Here, the authentication and authorization procedure specific to a network slice may be an authentication and authorization procedure required for each network slice.

The second network slice information may be the Allowed NSSAI or the NSSAI available in the current registration area of the UE. The NSSAI available at the location (current registration area) of the UE may be notified from the core network. The core network may include the second network slice information in a registration accept message, a configuration update command (UE configuration information update command control signal or control message), or a DL (Downlink) NAS transport message. may be included in

The third network slice information may be Rejected NSSAI, or may be one or more S-NSSAIs rejected by the core network. The core network may include the third network slice information in a registration accept message, a registration reject message, a de-registration request message, or a configuration update command (UE configuration information update). (command control signal or control message), or may be included in a DL NAS transport message. Rejected NSSAI may be a list in which one or more S-NSSAIs rejected by the core network are associated with rejection reason values for the S-NSSAIs. The third network slice information may be an NSSAI including an S-NSSAI having a predetermined cause value (reason value or rejection reason value). This predetermined cause value may be at least one of a first reason value to a fourth reason value described later.

The first reason value may be a cause value (reason value or rejection reason value) associated with each S-NSSAI included in the third network slice information. Note that the first reason value may be a reason value indicating pending. Alternatively, the first reason value may be a reason value indicating that an authentication and authorization procedure specific to a network slice is being executed, is being executed, or is scheduled to be executed. In each aspect, the first reason value may be expressed as a "reason value indicating pending" for the sake of explanation. In some cases, when multiple S-NSSAIs are set in the third network slice information, the first reason value may be associated with each S-NSSAI, or the first reason value may be associated with each S-NSSAI, or the first reason value may be associated with each S-NSSAI, or the first reason value may be associated with each S-NSSAI. It may also be associated with the network slice information (Rejected NSSAI) of No. 3. For the S-NSSAI to which the reason value is associated, the UE shall not operate until the network slice-specific authentication and authorization procedures are successful, or the terminal power is turned on/off, or the USIM (Universal Subscriber Identity Module) is inserted or removed. Until then, transmission of a registration request (initial registration request, mobility registration update, or periodic registration update) using the S-NSSAI may be suppressed. Note that the authentication and authorization procedure specific to a network slice is successful when the UE receives an EAP (Extensible Authentication Protocol) success from the core network. The core network may include the first reason value in a registration accept message, a registration reject message, a de-registration request message, or a configuration update command (UE configuration information update command). control signal or control message), or may be included in a DL NAS transport message.

The second reason value may be a cause value (or a reason for rejection value) associated with each S-NSSAI included in the third network slice information. Note that the second reason value may be a reason value indicating success or failure. Further, the second reason value may be a reason value indicating that the procedure was successful as a result of executing the authentication and authorization procedure specific to the network slice. It is sometimes expressed as "reason value indicating (success)". Further, the second reason value may be a reason value indicating that the procedure has failed as a result of executing the authentication and authorization procedure specific to the network slice, and in each aspect, " It is sometimes expressed as "reason value indicating failure". In some cases, if multiple S-NSSAIs are set in the third network slice information, the second reason value may be associated with each S-NSSAI, or a second reason value may be associated with each S-NSSAI, or a second reason value may be associated with each S-NSSAI, or a second reason value may be associated with each S-NSSAI. It may be associated with No. 3 network slice information (Rejected NSSAI). The UE 10 may maintain the association between the reason value and the third network slice information until the terminal power is turned on/off or the USIM (Universal Subscriber Identity Module) is inserted or removed. Additionally, if the second reason value is a reason value indicating failure, the UE 10 uses the relevant S-NSSAI until the terminal power is turned on/off or the USIM (Universal Subscriber Identity Module) is inserted or removed. Transmission of a registration request (initial registration request, mobility registration update, or periodic registration update) may be suppressed. The core network may include the second reason value in the registration accept message, in the registration reject message, in the de-registration request message, or in the configuration update command (UE configuration information update command). control signal or control message), or may be included in a DL NAS transport message.

The third reason value may be a cause value (reason value or rejection reason value) associated with each S-NSSAI included in the third network slice information. Note that the third reason value may be a reason value indicating "S-NSSAI not available in the current PLMN" described in Section 9.11.3.46 of Non-Patent Document 3. Here, the reason value indicating "S-NSSAI not available in the current PLMN" is the reason value indicating that the S-NSSAI is not available in the PLMN (Public land mobile network) that the UE is accessing. It's good. That is, when the UE 10 moves to another PLMN, the UE 10 may be able to reconnect (registration request) using the S-NSSAI. In some cases, if multiple S-NSSAIs are set in the third network slice information, the third reason value may be associated with each S-NSSAI, and the third reason value may be associated with a Rejected value indicating a collection of S-NSSAIs. May be associated with NSSAI. Note that the UE 10 may maintain the association between the reason value and the third network slice information until the terminal power is turned on/off or the USIM (Universal Subscriber Identity Module) is inserted or removed. The core network may include the third reason value in the registration accept message, in the registration reject message, in the de-registration request message, or in the configuration update command (UE configuration information update command). control signal or control message), or may be included in a DL NAS transport message.

The fourth reason value may be a cause value (reason value or rejection reason value) associated with each S-NSSAI included in the third network slice information. Note that the fourth reason value may be a reason value indicating "S-NSSAI not available in the current registration area" described in Section 9.11.3.46 of Non-Patent Document 3. Here, the reason value indicating "S-NSSAI not available in the current registration area" may be a reason value indicating that the S-NSSAI is not available in the registration area where the UE is located. That is, when the UE 10 moves to another RA, the UE 10 may be able to reconnect (registration request) using the S-NSSAI. In some cases, if multiple S-NSSAIs are set in the third network slice information, the fourth reason value may be associated with each S-NSSAI, or a fourth reason value may be associated with each S-NSSAI, or a fourth reason value may be associated with each S-NSSAI, or a fourth reason value may be associated with each S-NSSAI. It may be associated with No. 3 network slice information (Rejected NSSAI). Note that the UE 10 may maintain the association between the reason value and the third network slice information until the terminal power is turned on/off or the USIM (Universal Subscriber Identity Module) is inserted or removed. The core network may include the fourth reason value in the registration accept message, in the registration reject message, in the de-registration request message, or in the configuration update command (UE configuration information update command). control signal or control message), or may be included in a DL NAS transport message.

The first timer information may be a timer value set to timer 1. Here, timer 1 indicates that the UE requests a registration request (registration request message is an initial registration request, or a mobility registration update, It may be a timer that manages (sends or suppresses sending) messages (or periodic registration update). That is, the timer 1 may be a timer that manages (transmits or suppresses transmission) reconnection (transmission/retransmission of a registration request) using a pending S-NSSAI. In some cases, timer 1 may be a timer that waits for receiving an EAP identity request (a control signal or message in which the core network requests an EAP identity from the UE), an EAP success, or an EAP failure. It may be a timer that waits for the reception of a control signal or message indicating the completion of EAP authentication, or a configuration update command that triggers the acquisition of new slice information. ) may also be a timer that waits for the reception of. Furthermore, the timer 1 may be a timer for determining whether or not the network is abnormal while performing authentication and authorization procedures specific to network slices. The core network may include the first timer information in the registration accept message or in the registration reject message.

The fourth network slice information may be Configured NSSAI. The core network may include the fourth network slice information in the registration accept message, in the configuration update command (UE configuration information update command control signal or control message), or in the DL NAS transport message. Good too.

The second network slice information may be information indicating that there is no S-NSSAI available in the location where the UE is (current registration area), or may be an empty Allowed NSSAI. good. The second network slice information in this case will also be referred to as fifth network slice information hereinafter. The core network may include the fifth network slice information in the registration accept message or in the registration reject message.

The first instruction information may be instruction information that the core network transmits when prompting or requesting the UE to perform a registration procedure. Note that the core network may include the first instruction information in a configuration update command (UE configuration information update command control signal or control message), in a de-registration request message, or in a registration reject message. may be included in

An example of an initial procedure (hereinafter sometimes referred to as the main procedure) that is a premise for each aspect will be described using FIG. 5. This procedure example includes a registration procedure.

The example procedure contained in FIG. 5 is described in detail as follows.

Step (1) The UE 10 transmits the first network slice information (Requested NSSAI) and the first support information to the access network (for example, NG-(R)AN 20) on the N1 interface (S0501). Specifically, the UE 10 transmits an RRC (Radio Resource Control) message including a registration request message to the access network. Here, the registration request message may be an initial registration request, a mobility registration update, or a periodic registration update.

Step (2) The access network selects the AMF 30 to which the registration request message is to be sent, based on the registration request message included in the RRC message (S0502). That is, the access network may select the AMF 30 based on the information included in the RRC message.

Step (3) The access network transmits or transparently transfers a registration request message to the selected AMF 30 (S0503). At this time, the registration request may include first network slice information (Requested NSSAI) and first support information. Note that messages regarding the registration procedure that are transmitted and received on the N1 interface between the UE 10 and the AMF 30 are messages that are processed at the NAS (Non-Access-Stratum) layer. Further, the NAS layer is a layer above the RRC layer between the UE 10 and the NG-(R)AN 20.

Step (4) The AMF 30 receives the registration request message and executes the registration procedure described in Section 4.2.2 of Non-Patent Document 2 (S0504).

Here, as described in Section 5.15 of Non-Patent Document 1, the AMF 30 converts one or more S-NSSAIs into second network slice information ( Allowed NSSAI) (S0504). In some instances, if the registration request message received in step (1) includes the first support information, the AMF 30 is subject to network slice-specific authentication and authorization. Set S-NSSAI as the third network slice information (Rejected NSSAI). Note that the S-NSSAI set in the third network slice information does not have to be the S-NSSAI itself that is subject to network slice-specific authentication and authorization in HPLMN (Home PLMN). The S-NSSAI set in the third network slice information is the S-NSSAI provided by the serving PLMN that is mapped to the S-NSSAI that is subject to network slice-specific authentication and authorization in HPLMN. It's okay. Here, the AMF 30 determines or specifies the S-NSSAI that is subject to network slice-specific authentication and authorization based on the subscriber information. That is, during the registration procedure described in Section 4.2.2 of Non-Patent Document 1 mentioned above, the AMF 30 performs authentication and authorization specific to network slices based on the subscriber information (S504) received from the UDM 60. Determine or identify the S-NSSAI that is subject to.

Step (5) The AMF 30 updates the PDU (Protocol Data Unit) Session information to the SMF 40 when the AMF 30 is updated. (S0505)

In some cases, if the RRC message including the registration request message received in step (1) does not include the first network slice information (Requested NSSAI), or if the first network slice information (Requested NSSAI) is If the requested S-NSSAI is not included in the first network slice information (Requested NSSAI), the AMF 30 determines which S-NSSAI is subject to network slice-specific authentication and authorization based on the subscriber information. may be specified. Specifically, in this case, the AMF 30 determines whether one or more default S-NSSAIs set in the subscriber information (S0504) obtained from the UDM 60 are subject to network slice-specific authentication and authorization. Determine. If default S-NSSAIs are targeted for authentication and authorization specific to network slices, the AMF 30 determines these S-NSSAIs as targets for authentication and authorization specific to network slices.

In a certain case, if all S-NSSAIs included in the first network slice information (Requested NSSAI) received in step (1) are subject to network slice-specific authentication and authorization, AMF30 may set the fifth network slice information as an empty Allowed NSSAI. In other words, nothing need be set in Allowed NSSAI as the fifth network slice information.

In some cases, if the RRC message including the registration request message received in step (1) does not include the first network slice information (Requested NSSAI), and all defaults set in the subscriber information If the S-NSSAI is subject to network slice-specific authentication and authorization, the AMF 30 may set the fifth network slice information as an empty Allowed NSSAI. In other words, nothing need be set in Allowed NSSAI as the fifth network slice information.

In some cases, all the S-NSSAIs included in the first network slice information (Requested NSSAI) received in step (1) are the set of S-NSSAIs recorded in the subscriber information (Subscribed NSSAI). does not match, and all default S-NSSAIs set in the subscriber information are subject to network slice-specific authentication and authorization, the AMF30 uses the fifth network slice information as the fifth network slice information. You may also set an empty Allowed NSSAI. In other words, nothing need be set in Allowed NSSAI as the fifth network slice information.

Step (6) The AMF 30 sets one or more S-NSSAIs that are subject to network slice-specific authentication and authorization as third network slice information (Rejected NSSAI), and sets the third network slice information (Rejected NSSAI). and transmits a registration accept message including either the second network slice information, the third network slice information, or the fifth network slice information to the UE 10 on the N1 interface (S0506).

Note that the one or more S-NSSAIs included in the third network slice information (Rejected NSSAI) are not the S-NSSAIs themselves that are subject to network slice-specific authentication and authorization in HPLMN. Good too. One or more S-NSSAIs included in the third network slice information (Rejected NSSAI) are provided by the Serving PLMN that is mapped to the S-NSSAI that is subject to network slice-specific authentication and authorization in HPLMN. It may also be S-NSSAI.

Step (7) The UE 10 recognizes and retains the contents of the various information acquired in the registration accept message. For example, the UE 10 may recognize and hold the second network slice information or the fifth network slice information as Allowed NSSAI. The UE 10 may recognize and retain the third network slice information as Rejected NSSAI.

Then, based on the reception of the registration accept message, the UE 10 transmits a registration complete message on the N1 interface (S0507).

The initial procedure is thus completed, and the network slice-specific authentication and authorization procedure shown in FIG. 6 is performed (first state). The first state is a state in which the initial procedure shown in FIG. 5 has been completed, and is a state in which authentication and authorization procedures specific to network slices are awaited.

Examples of authentication and authorization procedures (hereinafter sometimes referred to as "this procedure") specific to network slices according to each aspect will be described using FIG. 6. This procedure example includes a network slice-specific authentication and authorization procedure.

Step (1) The AMF 30 performs the registration procedure after the registration procedure is completed (after sending the registration accept, or after the registration complete After receiving a message or establishing a 5GMM (5GS Mobility Management) context), the start of a Network Slice-Specific Authentication and Authorization procedure may be triggered (S0601).

At this time, the AMF 30 determines the processing status of the S-NSSAI that has been determined to be the target of authentication and authorization specific to the network slice and the authentication and authorization procedure specific to the network slice described in step (4) of the registration procedure above. may be associated and retained. In other words, the AMF 30 uses UE context information (UE context information) to collect state information indicating for which S-NSSAI the authentication and authorization procedures specific to network slices are being executed, are being executed, or are scheduled to be executed. It may be kept as . The status information may be information indicating that the network slice-specific authentication and authorization procedure for the S-NSSAI is pending, success, or failure.

Based on this state information, the AMF 30 may determine the trigger for starting the Network Slice-Specific Authentication and Authorization procedure or for which S-NSSAI the Network Slice-Specific Authentication and Authorization procedure should be executed. For example, if the UE context information includes status information indicating that the network slice-specific authentication and authorization procedure for a specific S-NSSAI has been successful, the AMF30 may not perform or may skip the Network Slice-Specific Authentication and Authorization procedure for the S-NSSAI.

Steps (2, 3) The AMF 30 executes the Network Slice-Specific Authentication and Authorization procedure using EAP described in Section 4.2.9.2 of Non-Patent Document 2 (S0602 and S0603).

Step (4) After the AMF 30 notifies the UE of the execution result (EAP success or EAP failure) of the Network Slice-Specific Authentication and Authorization procedure (S0604), the AMF 30 is configured as described in Section 4.2.9 of Non-Patent Document 2. A configuration update command may be sent towards the UE as described in Section 2. Specifically, when setting new second network slice information or fifth network slice information (Allowed NSSAI) to the UE, or when setting new third network slice information (Rejected NSSAI) to the UE, or , when the serving AMF changes to another different AMF, the AMF 30 may send a configuration update command to the UE for each access type. Note that the access type indicates the type of access network, and may mean a 3GPP network or a non-3GPP network.

So far, examples of initial procedures and authentication and authorization procedures specific to network slices, which are the premises of each aspect, have been described. In each aspect of this disclosure, based on the above premise, we will consider various problem scenarios in which services using authentication and authorization functions specialized for network slices cannot be provided, and divide the aspects into optimal solutions for each problem scenario. The solution is explained as follows.

(First aspect)
FIG. 7 is a diagram for explaining the first aspect.

In this aspect, after executing steps S0501 to S0505 in FIG. 5, the UE 10 receives the third network slice information including the S-NSSAI associated with the first reason value instead of the process in step S0506. , regarding scenarios where network slice-specific authentication and authorization procedures are pending. The UE 10 supports a network slice-specific authentication and authorization procedure. Here, waiting for the authentication and authorization procedure specific to a network slice means that the UE 10 waits for the pending procedure indicated by the first reason value after receiving the registration accept, after sending the registration complete message, or after establishing the 5GMM context. This is a state in which one or more S-NSSAIs associated with a reason value indicating (pending) are held. Specifically, waiting for network slice-specific authentication and authorization procedures means not receiving an EAP identity request, or not receiving an EAP success, or not receiving an EAP failure, or not receiving new slice information. It may also mean that a message that triggers acquisition (configuration update command or de-registration request) has not been received, or a message that sets new slice information (DL NAS transport) has not been received.

The solution described here allows the UE 10 to: It manages the sending of a registration request (initial registration request, mobility registration update, or periodic registration update) using S-NSSAI associated with the first reason value (reason value indicating pending). be. Note that managing transmission may mean managing the behavior of transmitting and the behavior of suppressing transmission, and the behavior of transmitting is sometimes expressed as re-attempt (reconnection).

The steps shown in FIG. 7 are explained in detail as follows.

Step (1) After executing the processes of steps S0501 to S0505 in FIG. Receive information (S0701). The reception of the first timer information may be performed due to the UE 10 transmitting a registration complete message to the AMF 30. If the timer 1 and/or the first timer value is set in the UE 10 in advance, the first timer information may not be received.

At this time, the UE 10 may hold one or more S-NSSAIs indicated by the third network slice information in association with the first reason value (reason value indicating pending). In addition, after sending the registration accept message to the UE 10 or after receiving the registration complete message from the UE 10, the AMF 30 also sends one or more S-NSSAIs indicated by the third network slice information to the first reason value ( (reason value indicating pending) may be stored as UE context information. The AMF 30 associates the first timer information with one or more S-NSSAIs indicated by the third network slice information and/or the first reason value (reason value indicating pending) as UE context information. You can keep it.

Step (2) The UE 10 implements the first processing example (S0702). In the first processing example, the UE 10 may implement one or more of the first to third behavior examples. The first processing example is a behavior (first (behavior example), behavior until the timer 1 expires or stops (second behavior example), and behavior when the timer 1 expires or stops (third behavior example).

The first behavior example in this aspect may be a behavior in which the UE 10 sets a timer value indicated by the first timer information or a value previously set in the UE 10 to the timer 1 and starts the timer 1. . Note that starting the timer 1 here may mean starting the timer's count. Further, the timer value set in advance in the UE 10 may be set in the UE 10 so as to be used when the UE 10 is located in an HPLMN or an equivalent PLMN.

The UE 10 starts timer 1 in units of one or more S-NSSAIs associated with the first reason value (reason value indicating pending) in the third network slice information (Rejected NSSAI). Alternatively, it may be activated in units of at least one of S-NSSAI, SIM (Subscriber Identity Module), UE, and PLMN, or a combination thereof. In other words, the first timer information including the timer value of timer 1 is one of the third network slice information (Rejected NSSAI) that is associated with the first reason value (reason value indicating pending). It may be set in units of the above S-NSSAIs, or it may be set in units of at least one of S-NSSAIs, SIMs, UEs, and PLMNs, or in units of combinations thereof. For example, the UE 10 starts timer 1 in units of one or more S-NSSAIs associated with the first reason value (reason value indicating pending) among the third network slice information (Rejected NSSAI). Timer 1 may be started for each SIM, Timer 1 may be started for each UE, or Timer 1 may be started for each PLMN. For example, the UE 10 uses a timer for each combination of one or more S-NSSAI and PLMN associated with the first reason value (reason value indicating pending) in the third network slice information (Rejected NSSAI). 1, or it may be set for each combination of one or more S-NSSAI and SIM associated with the first reason value (reason value indicating pending), or the first Timer 1 may be started for each UE and one or more S-NSSAIs associated with a reason value of 1 (a reason value indicating pending). For example, the UE 10 may start timer 1 for each combination of SIM and PLMN, or may start timer 1 for each combination of UE and PLMN. For example, the UE 10 selects one or more S-NSSAIs associated with the first reason value (reason value indicating pending) among the third network slice information (Rejected NSSAI), and the combination of the UE and PLMN. Timer 1 may be started, and one or more S-NSSAI and SIM associated with the first reason value (reason value indicating pending) among the third network slice information (Rejected NSSAI) Timer 1 may be started for each combination of SIM, UE, and PLMN, or may be started for each combination of SIM, UE, and PLMN. For example, the UE 10 selects one or more combinations of S-NSSAI, SIM, UE, and PLMN that are associated with the first reason value (reason value indicating pending) among the third network slice information (Rejected NSSAI). Timer 1 may be started in units.

Note that if there are two or more S-NSSAIs associated with the first reason value (reason value indicating pending), the first timer information includes the timer value of the single S-NSSAI and the first reason value. (reason value indicating pending) and the number of S-NSSAIs associated with it.

In the first behavior example in this aspect, the UE 10 may repeat the operation of restarting the timer 1 N times each time the timer 1 expires. The numerical value N of N times, which is the number of repeated operations, may be a value determined based on configuration data held by the UE 10. Alternatively, the number N of N times is set in the registration accept message, registration reject message, configuration update command (UE configuration information update command control signal or control message) transmitted from the AMF 30, or DL NAS transport message, and the AMF 30 The numerical value N may be set in the UE 10 by transmitting the message to the UE 10. In this case, a second behavior example described below may be activated until the timer 1 is activated N times and expires, and a third behavior example described below may be activated after the timer 1 is activated N times and expires.

As a second behavior example in this aspect, until the activated timer 1 stops or expires, the UE 10 selects the first reason value (pending ( One or more S-NSSAIs associated with one or more S-NSSAIs (reason values indicating pending), or associated with the first reason value (reason values indicating pending) of the third network slice information (Rejected NSSAI) It may also include a behavior of suppressing the transmission of a registration request (initial registration request, mobility registration update, or periodic registration update) using the S-NSSAI of the serving PLMN to which one or more S-NSSAIs are mapped.

In the second behavior example in this aspect, until the activated timer 1 stops or expires, the UE 10 receives a reason value indicating pending from the third network slice information (Rejected NSSAI). or one or more S-NSSAIs associated with the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI). The emergency registration request may be transmitted using the S-NSSAI of the serving PLMN to which the PLMN is mapped, regardless of the third network slice information (Rejected NSSAI).

In the second behavior example in this aspect, the UE 10 selects one or more S- The S-NSSAI of the serving PLMN to which one or more S-NSSAIs associated with the first reason value (reason value indicating pending) of the NSSAI or the third network slice information (Rejected NSSAI) is mapped. When the network slice-specific authentication and authorization procedures for the NSSAI are completed, the S-NSSAI may be deleted from the third network slice information (Rejected NSSAI). The UE 10 may manage the S-NSSAI deleted from the third network slice information as second network slice information (Allowed NSSAI). Furthermore, the UE 10 may start a service using the S-NSSAI managed as the second network slice information (Allowed NSSAI).

As a third behavior example in this aspect, when the activated timer 1 stops or expires, the UE 10 sets the first reason value (a reason value indicating pending) and/or the third network slice. It may include a behavior of updating at least one of the information of one or more S-NSSAI corresponding to the information (Rejected NSSAI).

Specifically, the UE 10 may implement the following first procedure example as a third behavior example.

In this embodiment, when the activated timer 1 stops or expires, the UE 10 transmits the first reason value (reason value indicating pending) and the third network slice information (Rejected NSSAI) held by the UE 10. ) may be disassociated from one or more S-NSSAIs corresponding to the S-NSSAI. Here, canceling the association between the first reason value (reason value indicating pending) and one or more S-NSSAI corresponding to the third network slice information (Rejected NSSAI) means that the UE 10 holds Regarding one or more S-NSSAIs corresponding to the third network slice information (Rejected NSSAI) and the first reason value (reason value indicating pending), ) may mean deleting the reason value (reason value indicating failure), or may mean rewriting it with a second reason value (reason value indicating failure). At this time, the UE 10 may rewrite the message to the second reason value (a reason value indicating failure) without transmitting or receiving messages with the core network and/or the access network (locally). Note that deleting the first reason value (a reason value indicating pending) may mean that no reason value is associated with the one or more S-NSSAIs.

In some cases, the UE 10 may implement the following second procedure example, which is different from the first procedure example, as a third behavior example.

In this embodiment, when the activated timer 1 stops or expires, the UE 10 receives the first reason value (indicating pending) of the third network slice information (Rejected NSSAI) held by the UE 10. One or more S-NSSAIs associated with a reason value) may be deleted. Here, deleting one or more S-NSSAIs associated with the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) means that the UE retains the S-NSSAI. Delete both the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) and one or more S-NSSAIs associated with that reason value. It may mean that

In some cases, the UE 10 may implement the following third procedure example, which is different from the first to second procedure examples, as a third behavior example.

When the activated timer 1 stops or expires, the UE 10 selects one or more of the third network slice information (Rejected NSSAI) associated with the first reason value (reason value indicating pending). If the UE 10 holds only the S-NSSAI, the UE 10 may reset the third network slice information (Rejected NSSAI) held by the UE 10. Here, resetting the third network slice information (Rejected NSSAI) may mean deleting all the third network slice information (Rejected NSSAI) held by the UE.

FIG. 8 shows the reconnection procedure using the S-NSSAI associated with the first reason value (reason value indicating pending), which is performed after the first processing example of this aspect. FIG.

In some cases, the UE 10 may implement the following first example procedure.

Specifically, after implementing the first processing example, the UE 10 selects one of the third network slice information (Rejected NSSAI) that is associated with the first reason value (reason value indicating pending). One or more S-NSSAIs, or one or more S-NSSAIs associated with the first reason value (reason value indicating pending) out of the third network slice information (Rejected NSSAI), are mapped. A registration request (initial registration request, mobility registration update, or periodic registration update) message may be sent to the AMF 30 using the S-NSSAI provided by the serving PLMN (S0801).

In some cases, the UE 10 may implement the following second example procedure.

Specifically, when the activated timer 1 stops or expires as shown in FIG. A registration request (initial registration request, mobility registration update, or periodic registration update) message that does not use one or more S-NSSAIs that is associated with network slice information (Rejected NSSAI) may be transmitted to the AMF 30 (S0801). Specifically, in the second procedure example, the third network slice information (Requested NSSAI) set in the registration request (initial registration request, mobility registration update, or periodic registration update) message is Among the slice information (Rejected NSSAI), one or more S-NSSAIs associated with the reason value indicating pending should not be set. Alternatively, the UE 10 may send one slice that is already associated with the third network slice information (Rejected NSSAI) and is in a pending state in a registration request (initial registration request, mobility registration update, or periodic registration update) message. The above S-NSSAI may be set as an individual information element and transmitted to the AMF 30. The AMF 30 may initiate O&M (Operation and Maintenance), such as checking the normality of authentication and authorization procedures specific to network slices, for the S-NSSAI received as an individual information element. Note that among the third network slice information (Rejected NSSAI), one or more S-NSSAIs that were associated with the first reason value (reason value indicating pending) are the same as those in the first processing example. As explained in the first procedure example of the third behavior example, one or more associated reason values are deleted or replaced with a second reason value (a reason value indicating failure). It may be S-NSSAI of

The AMF 30 receives a registration request message that does not use one or more S-NSSAIs that is associated with the first reason value (reason value indicating pending) among the third network slice information (Rejected NSSAI). do. Next, when setting the new second network slice information (Allowed NSSAI) to the UE, the AMF 30 sets the second network slice information in the registration accept message and sets the new third network slice information (Rejected NSSAI). When configuring the UE, set the third network slice information and second reason value (reason value indicating failure) in the registration accept message, and send the new fourth network slice information (Configured NSSAI) to the UE. When setting, the fourth network slice information may be set in the registration accept message, and the registration accept message including this information may be transmitted to the UE 10 (S0802).

Note that the UE 10 determines the reason for being associated with one or more S-NSSAI associated with the third network slice information (Rejected NSSAI) based on the first procedure example of the third behavior example of the first processing example. Even if the value is deleted or rewritten to the second reason value (reason value indicating failure), the AMF 30 replaces the reason value associated with the relevant S-NSSAI as UE Context information with the first reason value. (reason value indicating pending). That is, the reason value recognized by the AMF 30 may be different from the reason value associated with one or more S-NSSAIs associated with the third network slice information (Rejected NSSAI) recognized by the UE 10. The reason value recognized by the AMF 30 is associated with one or more S-NSSAIs associated with the third network slice information (Rejected NSSAI).

Here, a case will be described in which the second network slice information is included in the registration accept message. One or more S-NSSAIs included in the second network slice information and the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) held by the UE 10 When one or more associated S-NSSAIs match, the UE 10 may delete the matching one or more S-NSSAIs from the third network slice information (Rejected NSSAI). The UE 10 transmits a registration request (initial registration request, mobility registration update, or periodic registration update) message to the AMF 30 using one or more S-NSSAIs deleted from the third network slice information (Rejected NSSAI). (S0803)

For example, it is assumed that the UE 10 holds S-NSSAI #1 as the S-NSSAI corresponding to the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. At this time, if the UE 10 receives a registration accept message including S-NSSAI#1 as the second network slice information, the UE 10 selects the S-NSSAI that it holds as the S-NSSAI corresponding to the third network slice information (Rejected NSSAI). Delete #1. Furthermore, the UE 10 may transmit a registration request (initial registration request, mobility registration update, or periodic registration update) message using S-NSSAI#1 to the AMF 30 (S0803).

A certain case will be described in which the third network slice information and the second reason value are included in the registration accept message. One or more S-NSSAIs included in the third network slice information and the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) held by the UE 10 When the one or more associated S-NSSAIs match, the UE 10 may rewrite the reason value associated with the matched one or more S-NSSAIs to the reason value indicated by the second reason value. Here, the reason value indicated by the second reason value may be a reason value indicating failure.

For example, it is assumed that the UE 10 holds S-NSSAI #1 as the S-NSSAI corresponding to the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. At this time, if the UE 10 receives a registration accept message including S-NSSAI#1 as the S-NSSAI corresponding to the third network slice information and the second reason value (reason value indicating failure), the UE 10 Even if the reason value associated with S-NSSAI #1 held as the S-NSSAI corresponding to the third network slice information (Rejected NSSAI) is rewritten to the second reason value (reason value indicating failure) good.

In some cases, for example, if the fourth network slice information includes Configured NSSAI, the UE 10 may delete the third network slice information (Rejected NSSAI) that it holds. That is, the UE 10 may reset the held third network slice information (Rejected NSSAI) by receiving the fourth network slice information (Configured NSSAI). In some cases, the UE 10 sends a registration request (initial registration request, or mobility registration update, or periodic registration update) message to the AMF 30 using one or more S-NSSAIs associated with the fourth network slice information (Configured NSSAI). It may be sent (S0803). The fourth network slice information set by the UE 10 includes the first reason value (indicating pending) for authentication and authorization specific to network slices in the third network slice information (Rejected NSSAI). One or more S-NSSAIs associated with the reason value) may be included. That is, in step S0803, the UE 10 selects the first reason value (indicating pending) for authentication and authorization specific to the network slice that was included in the reset third network slice information (Rejected NSSAI). A registration request (initial registration request, mobility registration update, or periodic registration update) message can be sent to the AMF 30 using one or more S-NSSAIs associated with the reason value.

For example, it is assumed that the UE 10 holds S-NSSAI#1 and S-NSSAI#2 as S-NSSAIs corresponding to the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. A fourth reason value (a reason value indicating "S-NSSAI not available in the current registration area") described in Non-Patent Document 3 is associated with S-NSSAI#2. At this time, if a registration accept message including the fourth network slice information (Configured NSSAI) is received, the UE 10 selects S-NSSAI#1, which is held as the S-NSSAI corresponding to the third network slice information (Rejected NSSAI). and S-NSSAI#2, or the third network slice information (Rejected NSSAI) itself held by the UE 10 may be deleted. For example, if S-NSSAI#1 is included in the fourth network slice information (Configured NSSAI), the UE 10 uses S-NSSAI#1 included in the fourth network slice information (Configured NSSAI). A registered registration request (initial registration request, mobility registration update, or periodic registration update) message may be sent to the AMF 30.

In some cases, the UE 10 may implement the following third example procedure.

Specifically, when the activated timer 1 stops or expires as shown in FIG. A registration request (initial registration request, mobility registration update, or periodic registration update) message using the S-NSSAI associated with the reason value shown) may be transmitted to the AMF 30 (S0901). Note that among the third network slice information (Rejected NSSAI), one or more S-NSSAIs that were associated with the first reason value (reason value indicating pending) are the same as those in the first processing example. As explained in the first procedure of the third behavior example, one or more S whose associated reason value has been deleted or rewritten with a second reason value (a reason value indicating failure) -Can be NSSAI.

The AMF 30 receives a registration request message using one or more S-NSSAIs associated with the first reason value (reason value indicating pending) among the third network slice information (Rejected NSSAI). do. Next, when setting the new second network slice information (Allowed NSSAI) to the UE, the AMF 30 sets the second network slice information in the registration accept message and sets the new third network slice information (Rejected NSSAI). When setting the UE, the third network slice information and the second reason value are set in the registration accept message, and when setting the new fourth network slice information (Configured NSSAI) in the UE, the fourth network slice information and the second reason value are set in the registration accept message. network slice information may be set, and a registration accept message including these information may be transmitted to the UE 10 (S0902).

Note that the reason why the UE 10 is associated with one or more S-NSSAIs corresponding to the third network slice information (Rejected NSSAI) based on the first procedure example of the third behavior example of the first processing example Even if the value is deleted or rewritten to the second reason value (reason value indicating failure), the AMF 30 determines that the reason value associated with the S-NSSAI as UE Context information is the first reason value. (reason value indicating pending). In other words, the reason value associated with one or more S-NSSAI of the third network slice information (Rejected NSSAI) recognized by the AMF 30 is May be different from the reason value associated with one or more corresponding S-NSSAIs.

Here, a case will be described in which the second network slice information is included in the registration accept message. One or more S-NSSAIs included in the second network slice information and the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) held by the UE 10 When one or more associated S-NSSAIs match, the UE 10 may delete the matching one or more S-NSSAIs from the third network slice information (Rejected NSSAI). The UE 10 transmits a registration request (initial registration request, mobility registration update, or periodic registration update) message to the AMF 30 using one or more S-NSSAIs deleted from the third network slice information (Rejected NSSAI). (S0903)

For example, it is assumed that the UE 10 holds S-NSSAI #1 as the S-NSSAI corresponding to the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. At this time, if the UE 10 receives a registration accept message including S-NSSAI#1 as the second network slice information, the UE 10 selects the S-NSSAI that it holds as the S-NSSAI corresponding to the third network slice information (Rejected NSSAI). Delete #1. Furthermore, the UE 10 may transmit a registration request (initial registration request, mobility registration update, or periodic registration update) message using S-NSSAI#1 to the AMF 30 (S0903).

A certain case will be described in which the third network slice information and the second reason value are included in the registration accept message. One or more S-NSSAIs included in the third network slice information and the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) held by the UE 10 When the one or more associated S-NSSAIs match, the UE 10 may rewrite the reason value associated with the matched one or more S-NSSAIs to the reason value indicated by the second reason value. Here, the reason value indicated by the second reason value may be a reason value indicating failure.

For example, it is assumed that the UE 10 holds S-NSSAI #1 as the S-NSSAI corresponding to the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. At this time, if the UE 10 receives a registration accept message including S-NSSAI#1 as the S-NSSAI corresponding to the third network slice information and the second reason value (reason value indicating failure), the UE 10 Even if the reason value associated with S-NSSAI #1 held as the S-NSSAI corresponding to the third network slice information (Rejected NSSAI) is rewritten to the second reason value (reason value indicating failure) good.

In some cases, for example, if the fourth network slice information includes Configured NSSAI, the UE 10 may delete the third network slice information (Rejected NSSAI) that it holds. That is, the UE 10 may reset the held third network slice information (Rejected NSSAI) by receiving the fourth network slice information (Configured NSSAI). The UE 10 transmits a registration request (initial registration request, mobility registration update, or periodic registration update) message using one or more S-NSSAI associated with the fourth network slice information (Configured NSSAI) to the AMF 30. Good (S0903). The fourth network slice information set by the UE 10 includes the first reason value (indicating pending) for authentication and authorization specific to network slices in the third network slice information (Rejected NSSAI). One or more S-NSSAIs associated with the reason value) may be included. That is, in step S0903, the UE 10 selects the first reason value (indicating pending) for authentication and authorization specific to the network slice that was included in the reset third network slice information (Rejected NSSAI). A registration request (initial registration request, mobility registration update, or periodic registration update) message can be sent to the AMF 30 using one or more S-NSSAIs associated with the reason value.

For example, it is assumed that the UE 10 holds S-NSSAI#1 and S-NSSAI#2 as S-NSSAIs corresponding to the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. A third reason value (a reason value indicating "S-NSSAI not available in the current registration area") described in Non-Patent Document 3 is associated with S-NSSAI#2. At this time, if a registration accept message including the fourth network slice information (Configured NSSAI) is received, the UE 10 selects S-NSSAI#1, which is held as the S-NSSAI corresponding to the third network slice information (Rejected NSSAI). and S-NSSAI#2, or the third network slice information (Rejected NSSAI) itself held by the UE 10 may be deleted. For example, if S-NSSAI#1 is included in the fourth network slice information (Configured NSSAI), the UE 10 uses S-NSSAI#1 included in the fourth network slice information (Configured NSSAI). A registered registration request (initial registration request, mobility registration update, or periodic registration update) message may be sent to the AMF 30.

In addition, in the second and third procedure examples implemented after the first processing example, when the timer 1 stops or expires, the UE 10 transmits a registration request to the AMF 30, and the registration request is processed. The UE 10 obtains new network slice information (second network slice information, and/or third network slice information, second reason value, and/or fourth network slice information) with registration accept as a reply. is explained. In this way, a means for solving the problem of the UE 10 waiting indefinitely for network slice-specific authentication and authorization procedures has been described, but the present invention is not limited thereto.

Specifically, the UE 10 may receive a configuration update command including the first instruction information from the AMF 30. The UE 10 transmits a registration request message to the AMF 30 based on the first instruction information, and the AMF 30 includes the second network slice information and/or the third network slice information in the registration accept message in response to the registration request message. New network slice information may be set in the UE by including the second reason value and/or the fourth network slice information. The behavior of the UE 10 regarding transmission of a registration request and registration accept may be similar to the behavior of the UE 10 in the second and third procedure examples that are performed after the first process example described above.

Here, the first to third behavior examples of the first processing example may be behaviors executed based on rules and/or policies inside the UE 10. The UE 10 may hold a policy (UE policy) in the internal memory and/or control unit of the UE 10. For example, when the timer 1 expires, the UE 10 executes one or more procedure examples from the first procedure example to the third procedure example of the third behavior example of the first processing example, based on the policy. By executing one or more of the first to third procedure examples that are executed after the first processing example, the authentication and authorization procedures specific to network slices can be canceled. It is possible to solve the problem of waiting for deadlines.

An example of processing for stopping the activated timer 1 will be described below.

The UE 10 may be configured to stop timer 1 when receiving an EAP identity request from the core network, and may be configured to stop timer 1 when receiving EAP success or EAP failure. Good too.

A case will be described in which the UE 10 moves with a change in PLMN while the timer 1 is activated.

Here, the PLMN before change is referred to as a change source PLMN, and the PLMN after change is referred to as a change destination PLMN.

As a procedure example when the UE 10 moves with a change in PLMN while the timer 1 is activated, the following first procedure example may be implemented.

If the UE 10 changes the PLMN while the timer 1 is running, the setting may be such that the timer 1 does not need to be stopped. At this time, the timer 1 may be managed (stopped or activated) in units of third network slice information or in units of combinations of third network slice information and UE.

In some cases, the UE 10 uses S-NSSAI provided by the serving PLMN to which the third network slice information, or the third network slice information is mapped when the source PLMN is an HPLMN, in the destination PLMN. Transmission of a registration request message (initial registration request, mobility registration update, or periodic registration update) may be suppressed.

In a certain case, as a procedure example when the UE 10 moves with a change in PLMN while the timer 1 is activated, the following second procedure example may be implemented.

If the UE 10 changes the PLMN while the timer 1 is running, the setting may be such that the timer 1 does not need to be stopped. At this time, the timer 1 may be managed (stopped or activated) in units of third network slice information or in units of combinations of third network slice information and UE. This means that when the destination PLMN returns to the source PLMN due to a PLMN change, the management of registration request message sending that was applied in the source PLMN continues to be applied by continuing to run timer 1 that was started in the source PLMN. It is for the purpose of

In some cases, the UE 10 uses S-NSSAI provided by the serving PLMN to which the third network slice information, or the third network slice information is mapped when the source PLMN is an HPLMN, in the destination PLMN. A registration request message (initial registration request, mobility registration update, or periodic registration update) may be sent.

In a certain case, as a procedure example when the UE 10 moves with a change of PLMN while the timer 1 is activated, the following third procedure example, which is different from the first to second procedure examples, may be implemented.

If the UE 10 changes the PLMN while the timer 1 is running, the UE 10 may be configured to stop the timer 1. Timer 1 may be managed (stopped or activated) in units of third network slice information and PLMN, or in units of combinations of third network slice information, PLMN, and UE.

In some cases, the UE 10 uses S-NSSAI provided by the serving PLMN to which the third network slice information, or the third network slice information is mapped when the source PLMN is an HPLMN, in the destination PLMN. A registration request message (initial registration request, mobility registration update, or periodic registration update) may be sent.

A case where the system is changed from N1 mode to S1 mode (system interchange) while timer 1 is running will be explained.

As a procedure example when the UE 10 changes from the N1 mode to the S1 mode while the timer 1 is activated, the following first procedure example may be implemented.

The UE 10 may be configured so that when the N1 mode is changed to the S1 mode while the timer 1 is running, there is no need to stop the running timer 1. This means that when changing to N1 mode again after changing to S1 mode, the management of registration request message sending that was applied in N1 mode will continue to be applied by continuing to start timer 1 that was started in N1 mode at the beginning. It is for this purpose.

In some cases, as a procedure example when the UE 10 changes from N1 mode to S1 mode while timer 1 is activated, the following second procedure example, which is different from the first procedure example, may be implemented.

The UE 10 may be configured to stop the activated timer 1 when changing from the N1 mode to the S1 mode while the timer 1 is activated.

Up to now, we have described a case where the UE 10 receives the third network slice information, at least one of the first reason value, and the first timer information from the AMF 30. The case where the fifth network slice information is received will be described as follows.

Specifically, if all S-NSSAIs included in the first network slice information (Requested NSSAI) are subject to network slice-specific authentication and authorization, or if the first network slice information (Requested NSSAI) is not included, and all default S-NSSAIs set in the subscriber information are subject to network slice-specific authentication and authorization, or the first All S-NSSAI included in the network slice information (Requested NSSAI) do not match the S-NSSAI (Subscribed NSSAI) recorded in the subscriber information, and the S-NSSAI is set in the subscriber information. If all default S-NSSAIs are subject to network slice-specific authentication and authorization, the AMF 30 may transmit the fifth network slice information to the UE 10.

That is, since there is no S-NSSAI as the second network slice information (Allowed NSSAI) that can be transmitted to the UE 10, the AMF 30 transmits the fifth network slice information. Here, the AMF30 includes S-NSSAI, which is subject to network slice-specific authentication and authorization, in the third network slice information, and the related first reason value (reason value indicating pending). The third network slice information and the first reason value may be transmitted to the UE 10 or may not be transmitted to the UE 10.

At this time, the UE 10 receives the fifth network slice information from the AMF 30 described in this aspect, at least one of the third network slice information and the first reason value, as well as the first When timer information is received, the UE may perform the same behavior as when timer 1 was previously set in the UE.

(Second aspect)
The second aspect will be explained using FIG. 10.

In this aspect, after the UE 10 executes the processes of steps S0501 to S0505 in FIG. 5, the UE 10 receives the third network slice information including the S-NSSAI associated with the first reason value and specializes in Concerning the scenario where the user is waiting for authentication and authorization procedures. The UE 10 supports a network slice-specific authentication and authorization procedure. Here, waiting for the authentication and authorization procedure specific to a network slice means that the UE 10 is waiting for the first reason value (pending ( This is a state in which one or more S-NSSAIs associated with a reason value indicating "suspended" are held. Specifically, waiting for network slice-specific authentication and authorization procedures means not receiving an EAP identity request, or not receiving an EAP success, or not receiving an EAP failure, or not receiving new slice information. It may also mean that a message that triggers acquisition (configuration update command or de-registration request) has not been received, or a message that sets new slice information (DL NAS transport) has not been received.

The solution described here allows the UE 10 to: It manages the sending of a registration request (initial registration request, mobility registration update, or periodic registration update) using S-NSSAI associated with the first reason value (reason value indicating pending). be. Note that, unlike the first aspect, in the second aspect, when the above-described timer 1 stops or expires, another timer is activated to manage the transmission of the registration request. Furthermore, managing transmission may mean managing the behavior of transmitting and the behavior of inhibiting transmission, and the behavior of transmitting is sometimes expressed as re-attempt (reconnection).

The steps shown in FIG. 10 are explained in detail as follows.

Step (1) After executing the processes of steps S0501 to S0505 in FIG. Receive information (S1001).

At this time, the UE 10 may hold one or more S-NSSAIs associated with the third network slice information in association with the first reason value (reason value indicating pending). Further, the AMF 30 may also associate one or more S-NSSAI associated with the third network slice information with the first reason value (reason value indicating pending) and hold it as UE context information. The AMF 30 associates the first timer information with one or more S-NSSAIs associated with the third network slice information and/or the first reason value (a reason value indicating pending) with the UE context information. May be kept as .

Step (2) The UE 10 that has received the first timer information implements the second processing example (S1002). In the second processing example, the UE 10 may implement one or more of the first to third behavior examples. The second processing example is a behavior (first (behavior example), behavior until the timer 1 expires or stops (second behavior example), and behavior when the timer 1 expires or stops (third behavior example).

The first behavior example in this aspect may be a behavior in which the UE 10 sets a timer value indicated by the first timer information or a value previously set in the UE 10 to the timer 1 and starts the timer 1. . Note that starting the timer 1 here may mean starting the timer's count. Further, the timer value set in advance in the UE 10 may be set in the UE 10 so as to be used when the UE 10 is located in an HPLMN or an equivalent PLMN.

The UE 10 starts timer 1 in units of one or more S-NSSAIs associated with the first reason value (reason value indicating pending) in the third network slice information (Rejected NSSAI). Alternatively, it may be activated in units of at least one of S-NSSAI, SIM, UE, and PLMN, or a combination thereof. In other words, the first timer information including the timer value of timer 1 is one of the third network slice information (Rejected NSSAI) that is associated with the first reason value (reason value indicating pending). It may be set in units of the above S-NSSAIs, or it may be set in units of at least one of S-NSSAIs, SIMs, UEs, and PLMNs, or in units of combinations thereof. For example, the UE 10 starts timer 1 in units of one or more S-NSSAIs associated with the first reason value (reason value indicating pending) among the third network slice information (Rejected NSSAI). Timer 1 may be started for each SIM, Timer 1 may be started for each UE, or Timer 1 may be started for each PLMN. For example, the UE 10 uses a timer for each combination of one or more S-NSSAI and PLMN associated with the first reason value (reason value indicating pending) in the third network slice information (Rejected NSSAI). 1, or it may be set for each combination of one or more S-NSSAI and SIM associated with the first reason value (reason value indicating pending), or the first Timer 1 may be started for each UE and one or more S-NSSAIs associated with a reason value of 1 (a reason value indicating pending). For example, the UE 10 may start timer 1 for each combination of SIM and PLMN, or may start timer 1 for each combination of UE and PLMN. For example, the UE 10 selects one or more S-NSSAIs associated with the first reason value (reason value indicating pending) among the third network slice information (Rejected NSSAI), and the combination of the UE and PLMN. Timer 1 may be started, and one or more S-NSSAI and SIM associated with the first reason value (reason value indicating pending) among the third network slice information (Rejected NSSAI) Timer 1 may be started for each combination of SIM, UE, and PLMN, or may be started for each combination of SIM, UE, and PLMN. For example, the UE 10 selects one or more combinations of S-NSSAI, SIM, UE, and PLMN that are associated with the first reason value (reason value indicating pending) among the third network slice information (Rejected NSSAI). Timer 1 may be started in units.

Note that if there are two or more S-NSSAIs associated with the first reason value (reason value indicating pending), the first timer information includes the timer value of the single S-NSSAI and the first reason value. (reason value indicating pending) and the number of S-NSSAIs associated with it.

The second example of behavior in this aspect is that until the activated timer 1 stops or expires, the UE 10 selects the first reason value (pending One or more S-NSSAIs associated with one or more S-NSSAIs (reason value indicating pending), or associated with the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) The behavior may be to suppress the transmission of a registration request (initial registration request, mobility registration update, or periodic registration update) using the S-NSSAI of the serving PLMN to which one or more S-NSSAIs to be mapped are mapped.

As a third behavior example in this aspect, when the activated timer 1 stops or expires, the UE 10 sets the first reason value (a reason value indicating pending) and/or the third network slice. It may include a behavior of updating at least one of the information of one or more S-NSSAI corresponding to the information (Rejected NSSAI).

Specifically, the UE 10 may implement the following first procedure example as a third behavior example.
When the activated timer 1 stops or expires, the UE 10 receives the first reason value (reason value indicating pending) and third network slice information (Rejected NSSAI) held by the UE 10. The association with one or more S-NSSAIs associated with may be canceled. Here, disassociating the first reason value (reason value indicating pending) from one or more S-NSSAIs associated with the third network slice information (Rejected NSSAI) means that the UE maintains For one or more S-NSSAIs associated with the third network slice information (Rejected NSSAI) that is ) may mean deleting the reason value (reason value indicating failure), or may mean rewriting it with a second reason value (reason value indicating failure). At this time, the UE 10 may rewrite the message to the second reason value (a reason value indicating failure) without transmitting or receiving messages with the core network and/or the access network (locally). Note that deleting the first reason value (reason value indicating pending) may mean that no reason value is associated with the one or more S-NSSAIs.

In some cases, the UE 10 may implement the following second procedure example, which is different from the first procedure example, as a third behavior example.

When the activated timer 1 stops or expires, the UE 10 receives the first reason value (reason indicating pending) of the third network slice information (Rejected NSSAI) held by the UE 10. one or more S-NSSAIs associated with a value) may be deleted. Here, deleting one or more S-NSSAIs associated with the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) means that the UE retains the S-NSSAI. This means deleting both the first reason value (reason value indicating pending) and one or more S-NSSAIs associated with the associated third network slice information (Rejected NSSAI). It's fine.

In some cases, the UE 10 may implement the following third procedure example, which is different from the first to second procedure examples, as a third behavior example.

When the activated timer 1 stops or expires, the UE 10 selects one or more of the third network slice information (Rejected NSSAI) associated with the first reason value (reason value indicating pending). If the UE 10 holds only the S-NSSAI, the UE 10 may reset the third network slice information (Rejected NSSAI) held by the UE 10. Here, resetting the third network slice information (Rejected NSSAI) may mean deleting all the third network slice information (Rejected NSSAI) held by the UE.

In some cases, the UE 10 may implement the following first example procedure, which is performed after the second example procedure.

FIG. 11 shows the use of S-NSSAI associated with the first reason value (reason value indicating pending) in the first procedure example executed after the second processing example of this aspect. FIG.

Specifically, when the activated timer 1 stops or expires as shown in FIG. 11, the UE 10 receives the first reason value (pending A registration request (initial registration request, mobility registration update, or periodic registration update) message that does not use one or more S-NSSAIs associated with (reason value indicating pending) may be sent to the AMF 30 (S1101) . Note that among the third network slice information (Rejected NSSAI), one or more S-NSSAI associated with the first reason value (reason value indicating pending) is the third network slice information (Rejected NSSAI). As explained in the first procedure of behavior example 3, one or more S-NSSAIs whose associated reason value has been deleted or rewritten with a second reason value (a reason value indicating failure) It may be. In this case, the UE 10 may start the timer 2 and/or the timer 3. Here, the timer 2 is a mobility timer that waits for a registration accept message from the core network, which is activated after the UE 10 transmits a registration request message, as described in Section 10.2 of Non-Patent Document 3. good. The timer 3 may be a timer that manages retransmission of the registration request message, as described in Section 10.2 of Non-Patent Document 3.

The AMF 30 receives a registration request message that does not use one or more S-NSSAIs that is associated with the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI). do. Next, when setting the new second network slice information (Allowed NSSAI) to the UE, the AMF 30 sets the second network slice information in the registration accept message and sets the new third network slice information (Rejected NSSAI). When setting the UE, the third network slice information and the second reason value are set in the registration accept message, and when setting the new fourth network slice information (Configured NSSAI) in the UE, the fourth network slice information and the second reason value are set in the registration accept message. network slice information may be set, and a registration accept message including these information may be transmitted to the UE 10 (S1102).

Note that the reason why the UE 10 is associated with one or more S-NSSAI associated with the third network slice information (Rejected NSSAI) based on the first procedure example of the third behavior example of the second processing example Even if the value is deleted or rewritten to the second reason value (reason value indicating failure), the AMF 30 determines that the reason value associated with the S-NSSAI as UE Context information is the first reason value. (reason value indicating pending). In other words, the reason value associated with one or more S-NSSAIs associated with the third network slice information (Rejected NSSAI) recognized by the AMF 30 is the reason value associated with the third network slice information (Rejected NSSAI) recognized by the UE 10. ) may be different from the reason value associated with one or more S-NSSAIs associated with the S-NSSAI. The reason value recognized by the AMF 30 is associated with one or more S-NSSAIs associated with the third network slice information (Rejected NSSAI).

Here, a case will be described in which the second network slice information is included in the registration accept message. One or more S-NSSAIs included in the second network slice information and the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) held by the UE 10 When one or more associated S-NSSAIs match, the UE 10 may delete the matching one or more S-NSSAIs from the third network slice information (Rejected NSSAI). The UE 10 transmits a registration request (initial registration request, mobility registration update, or periodic registration update) message to the AMF 30 using one or more S-NSSAIs deleted from the third network slice information (Rejected NSSAI). (S1103).

For example, it is assumed that the UE 10 holds S-NSSAI #1 as the S-NSSAI associated with the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. At this time, if a registration accept message including S-NSSAI #1 is received as the second network slice information, the UE 10 selects the S-NSSAI that is retained as the S-NSSAI associated with the third network slice information (Rejected NSSAI). Delete #1. Furthermore, the UE 10 may transmit a registration request (initial registration request, mobility registration update, or periodic registration update) message using S-NSSAI#1 to the AMF 30 (S1103).

A certain case will be described in which the third network slice information and the second reason value are included in the registration accept message. One or more S-NSSAIs included in the third network slice information and the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) held by the UE 10 When the one or more associated S-NSSAIs match, the UE 10 may rewrite the reason value associated with the matched one or more S-NSSAIs to the reason value indicated by the second reason value. Here, the reason value indicated by the second reason value may be a reason value indicating failure.

For example, it is assumed that the UE 10 holds S-NSSAI #1 as the S-NSSAI included in the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. At this time, if the UE 10 receives a registration accept message including S-NSSAI #1 and the second reason value (reason value indicating failure) as the S-NSSAI associated with the third network slice information, the UE 10 Even if the reason value associated with S-NSSAI#1, which is held as S-NSSAI associated with the third network slice information (Rejected NSSAI), is rewritten to the second reason value (reason value indicating failure), good.

In some cases, for example, if the fourth network slice information includes Configured NSSAI, the UE 10 may delete the third network slice information (Rejected NSSAI) that it holds. That is, the UE 10 may reset the held third network slice information (Rejected NSSAI) by receiving the fourth network slice information (Configured NSSAI). The UE 10 transmits a registration request (initial registration request, mobility registration update, or periodic registration update) message using one or more S-NSSAI associated with the fourth network slice information (Configured NSSAI) to the AMF 30. Good (S1103). The fourth network slice information set by the UE 10 includes the first reason value (indicating pending) for authentication and authorization specific to network slices in the third network slice information (Rejected NSSAI). One or more S-NSSAIs associated with the reason value) may be included. That is, in step S1103, the UE 10 selects the first reason value (indicating pending) for authentication and authorization specific to the network slice that was included in the reset third network slice information (Rejected NSSAI). A registration request (initial registration request, mobility registration update, or periodic registration update) message can be sent to the AMF 30 using one or more S-NSSAIs associated with the reason value.

For example, it is assumed that the UE 10 holds S-NSSAI#1 and S-NSSAI#2 as S-NSSAIs associated with the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. A fourth reason value (a reason value indicating "S-NSSAI not available in the current registration area") described in Non-Patent Document 3 is associated with S-NSSAI#2. At this time, when receiving the registration accept message including the fourth network slice information (Configured NSSAI), the UE 10 selects S-NSSAI#1, which is held as the S-NSSAI associated with the third network slice information (Rejected NSSAI). and S-NSSAI#2, or the third network slice information (Rejected NSSAI) itself held by the UE 10 may be deleted. For example, if S-NSSAI#1 is included in the fourth network slice information (Configured NSSAI), the UE 10 uses S-NSSAI#1 included in the fourth network slice information (Configured NSSAI). A registered registration request (initial registration request, mobility registration update, or periodic registration update) message may be sent to the AMF 30.

In some cases, the UE 10 may implement the following second example procedure, which is performed after the second example procedure.

FIG. 12 shows the use of S-NSSAI associated with the first reason value (reason value indicating pending) in the second procedure example executed after the second processing example of this aspect. FIG. 3 is a diagram showing a procedure for reconnection.

Specifically, when the activated timer 1 stops or expires as shown in FIG. 12, the UE 10 receives the first reason value (of the third network slice information (Rejected NSSAI) A registration request (initial registration request, mobility registration update, or periodic registration update) message to the AMF 30 (S1201). Note that one or more S-NSSAIs associated with the first reason value (reason value indicating pending) in the third network slice information (Rejected NSSAI) are the same as those in the second processing example. As explained in the first procedure of the third behavior example, one or more S- It may be NSSAI. In this case, the UE 10 may start the timer 2 and/or the timer 3. Here, the timer 2 is a mobility timer that waits for a registration accept message from the core network, which is activated after the UE 10 transmits a registration request message, as described in Section 10.2 of Non-Patent Document 3. good. The timer 3 may be a timer that manages retransmission of the registration request message, as described in Section 10.2 of Non-Patent Document 3.

The AMF 30 receives a registration request message using one or more S-NSSAIs associated with the first reason value (reason value indicating pending) from the third network slice information (Rejected NSSAI). do. Next, when setting the new second network slice information (Allowed NSSAI) to the UE, the AMF 30 sets the second network slice information in the registration accept message and sets the new third network slice information (Rejected NSSAI). When setting the UE, the third network slice information and the second reason value are set in the registration accept message, and when setting the new fourth network slice information (Configured NSSAI) in the UE, the fourth network slice information and the second reason value are set in the registration accept message. network slice information may be set and a registration accept message including these information may be transmitted to the UE 10 (S1202).

Note that the reason why the UE 10 is associated with one or more S-NSSAI associated with the third network slice information (Rejected NSSAI) based on the first procedure example of the third behavior example of the second processing example Even if the value is deleted or rewritten to the second reason value (reason value indicating failure), the AMF 30 determines that the reason value associated with the S-NSSAI as UE Context information is the first reason value. (reason value indicating pending). In other words, the reason value associated with one or more S-NSSAIs associated with the third network slice information (Rejected NSSAI) recognized by the AMF 30 is the reason value associated with the third network slice information (Rejected NSSAI) recognized by the UE 10. ) may be different from the reason value associated with one or more S-NSSAIs associated with the S-NSSAI.

Here, a case will be described in which the second network slice information is included in the registration accept message. One or more S-NSSAIs included in the second network slice information and the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) held by the UE 10 When one or more associated S-NSSAIs match, the UE 10 may delete the matching one or more S-NSSAIs from the third network slice information (Rejected NSSAI). The UE 10 transmits a registration request (initial registration request, mobility registration update, or periodic registration update) message to the AMF 30 using one or more S-NSSAIs deleted from the third network slice information (Rejected NSSAI). (S1203).

For example, it is assumed that the UE 10 holds S-NSSAI #1 as the S-NSSAI associated with the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. At this time, if a registration accept message including S-NSSAI #1 is received as the second network slice information, the UE 10 selects the S-NSSAI that is retained as the S-NSSAI associated with the third network slice information (Rejected NSSAI). Delete #1. Furthermore, the UE 10 may transmit a registration request (initial registration request, mobility registration update, or periodic registration update) message using S-NSSAI#1 to the AMF 30 (S1203).

A certain case will be described in which the third network slice information and the second reason value are included in the registration accept message. One or more S-NSSAIs included in the third network slice information and the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) held by the UE 10 When the one or more associated S-NSSAIs match, the UE 10 may rewrite the reason value associated with the matched one or more S-NSSAIs to the reason value indicated by the second reason value. Here, the reason value indicated by the second reason value may be a reason value indicating failure.

For example, it is assumed that the UE 10 holds S-NSSAI #1 as the S-NSSAI associated with the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. At this time, if the UE 10 receives a registration accept message including S-NSSAI #1 and the second reason value (reason value indicating failure) as the S-NSSAI associated with the third network slice information, the UE 10 Even if the reason value associated with S-NSSAI#1, which is held as S-NSSAI associated with the third network slice information (Rejected NSSAI), is rewritten to the second reason value (reason value indicating failure), good.

In some cases, for example, if the fourth network slice information includes Configured NSSAI, the UE 10 may delete the third network slice information (Rejected NSSAI) that it holds. That is, the UE 10 may reset the held third network slice information (Rejected NSSAI) by receiving the fourth network slice information (Configured NSSAI). The UE 10 transmits a registration request (initial registration request, mobility registration update, or periodic registration update) message using one or more S-NSSAI associated with the fourth network slice information (Configured NSSAI) to the AMF 30. Good (S1203). The fourth network slice information set by the UE 10 includes the first reason value (indicating pending) for authentication and authorization specific to network slices in the third network slice information (Rejected NSSAI). One or more S-NSSAIs associated with the reason value) may be included. That is, in step S1203, the UE 10 selects the first reason value (indicating pending) for authentication and authorization specific to the network slice that was included in the reset third network slice information (Rejected NSSAI). A registration request (initial registration request, mobility registration update, or periodic registration update) message can be sent to the AMF 30 using one or more S-NSSAIs associated with the reason value.

For example, it is assumed that the UE 10 holds S-NSSAI#1 and S-NSSAI#2 as S-NSSAIs associated with the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. A fourth reason value (a reason value indicating "S-NSSAI not available in the current registration area") described in Non-Patent Document 3 is associated with S-NSSAI#2. At this time, when receiving the registration accept message including the fourth network slice information (Configured NSSAI), the UE 10 selects S-NSSAI#1, which is held as the S-NSSAI associated with the third network slice information (Rejected NSSAI). and S-NSSAI#2, or the third network slice information (Rejected NSSAI) itself held by the UE 10 may be deleted. For example, if S-NSSAI#1 is included in the fourth network slice information (Configured NSSAI), the UE 10 uses S-NSSAI#1 included in the fourth network slice information (Configured NSSAI). A registered registration request (initial registration request, mobility registration update, or periodic registration update) message may be sent to the AMF 30.

In addition, in the first and second procedure examples implemented after the second processing example, when the timer 1 stops or expires, the UE 10 transmits a registration request to the AMF 30, and the registration request is processed. The UE 10 obtains new network slice information (second network slice information, and/or third network slice information, second reason value, and/or fourth network slice information) with registration accept as a reply. , and that the UE 10 starts the timer 2 and/or the timer 3. In this way, a solution to the problem that the UE 10 waits indefinitely for network slice-specific authentication and authorization procedures has been described, but the present invention is not limited thereto.

Specifically, the UE 10 may receive a configuration update command including the first instruction information from the AMF 30. The UE 10 transmits a registration request message to the AMF 30 based on the first instruction information, and the AMF 30 includes the second network slice information and/or the third network slice in the registration accept message in response to the registration request message. New network slice information may be configured in the UE by including the information and the second reason value and/or the fourth network slice information. The behavior of the UE 10 regarding transmission of a registration request and registration accept may be similar to the behavior of the UE 10 in the first and second procedure examples that are performed after the second process example described above.

Here, the first to third behaviors of the second processing example may be behaviors executed based on rules and/or policies inside the UE 10. The UE 10 may hold a policy (UE policy) in the internal memory and/or control unit of the UE 10. For example, the UE 10 may be configured to start the timer 2 and/or the timer 3 based on the policy when the timer 1 expires and the registration request message is sent to the AMF 30.

An example of processing for stopping the activated timer 1 will be described below.

The UE 10 may be configured to stop timer 1 when receiving an EAP identity request from the core network, and may be configured to stop timer 1 when receiving EAP success or EAP failure. Good too.

A case will be described in which the UE 10 moves with a change in PLMN while the timer 1 is activated.

Here, the PLMN before change is referred to as a change source PLMN, and the PLMN after change is referred to as a change destination PLMN.

As a procedure example when the UE 10 moves with a change in PLMN while the timer 1 is activated, the following first procedure example may be implemented.

If the UE 10 changes the PLMN while the timer 1 is running, the setting may be such that the timer 1 does not need to be stopped. At this time, the timer 1 may be managed (stopped or activated) in units of third network slice information or in units of combinations of third network slice information and UE.

In some cases, the UE 10 uses S-NSSAI provided by the serving PLMN to which the third network slice information, or the third network slice information is mapped when the source PLMN is an HPLMN, in the destination PLMN. Transmission of a registration request message (initial registration request, mobility registration update, or periodic registration update) may be suppressed.

In a certain case, as a procedure example when the UE 10 moves with a change in PLMN while the timer 1 is activated, the following second procedure example may be implemented.

If the UE 10 changes the PLMN while the timer 1 is running, the setting may be such that the timer 1 does not need to be stopped. At this time, the timer 1 may be managed (stopped or activated) in units of third network slice information or in units of combinations of third network slice information and UE. This means that when the destination PLMN returns to the source PLMN due to a PLMN change, the management of registration request message sending that was applied in the source PLMN continues to be applied by continuing to run timer 1 that was started in the source PLMN. It is for the purpose of

In some cases, the UE 10 uses S-NSSAI provided by the serving PLMN to which the third network slice information, or the third network slice information is mapped when the source PLMN is an HPLMN, in the destination PLMN. A registration request message (initial registration request, mobility registration update, or periodic registration update) may be sent.

In a certain case, as a procedure example when the UE 10 moves with a change of PLMN while the timer 1 is activated, the following third procedure example, which is different from the first to second procedure examples, may be implemented.

If the UE 10 changes the PLMN while the timer 1 is running, the UE 10 may be configured to stop the timer 1. Timer 1 may be managed (stopped or activated) in units of third network slice information and PLMN, or in units of combinations of third network slice information, PLMN, and UE.

In some cases, the UE 10 uses S-NSSAI provided by the serving PLMN to which the third network slice information, or the third network slice information is mapped when the source PLMN is an HPLMN, in the destination PLMN. A registration request message (initial registration request, mobility registration update, or periodic registration update) may be sent.

A case where the system is changed from N1 mode to S1 mode (system interchange) while timer 1 is running will be explained.

As a procedure example when the UE 10 changes from the N1 mode to the S1 mode while the timer 1 is activated, the following first procedure example may be implemented.

The UE 10 may be configured so that when the N1 mode is changed to the S1 mode while the timer 1 is running, there is no need to stop the running timer 1. This means that when changing to N1 mode again after changing to S1 mode, the management of registration request message sending that was applied in N1 mode will continue to be applied by continuing to start timer 1 that was started in N1 mode at the beginning. It is for this purpose.

In some cases, as a procedure example when the UE 10 changes from N1 mode to S1 mode while timer 1 is activated, the following second procedure example, which is different from the first procedure example, may be implemented.

The UE 10 may be configured to stop the activated timer 1 when changing from the N1 mode to the S1 mode while the timer 1 is activated.

Up to now, after executing the processes of steps S0501 to S0505 in FIG. The case where the fifth network slice information is received will be explained as follows.

Specifically, if all S-NSSAIs included in the first network slice information (Requested NSSAI) are subject to network slice-specific authentication and authorization, or if the first network slice information (Requested NSSAI) is not included, and all default S-NSSAIs set in the subscriber information are subject to network slice-specific authentication and authorization, or the first All S-NSSAI included in the network slice information (Requested NSSAI) do not match the S-NSSAI (Subscribed NSSAI) recorded in the subscriber information, and the S-NSSAI is set in the subscriber information. If all default S-NSSAIs are subject to network slice-specific authentication and authorization, the AMF 30 may send the fifth network slice information to the UE 10 instead of the second network slice information. .

That is, since there is no S-NSSAI as the second network slice information (Allowed NSSAI) that can be transmitted to the UE 10, the AMF 30 transmits the fifth network slice information. Here, the AMF30 includes S-NSSAI, which is subject to network slice-specific authentication and authorization, in the third network slice information, and the related first reason value (reason value indicating pending). The third network slice information and the first reason value may be transmitted to the UE 10 or may not be transmitted to the UE 10.

At this time, if the UE 10 receives the first timer information in addition to at least one of the third network slice information and the first reason value from the AMF 30 described in this aspect, or The same behavior as when timer 1 is set in the UE may be performed.

(Third aspect)
The third aspect will be explained using FIG. 13.

In this aspect, after the UE 10 executes the processes of steps S0501 to S0505 in FIG. 5, the UE 10 receives the third network slice information including the S-NSSAI associated with the first reason value and specializes in Concerning the scenario where the user is waiting for authentication and authorization procedures. The UE 10 supports a network slice-specific authentication and authorization procedure. Here, waiting for the authentication and authorization procedure specific to a network slice means that the UE 10 is waiting for the first reason value (pending ( This is a state in which one or more S-NSSAIs associated with a reason value indicating "suspended" are held. Specifically, waiting for network slice-specific authentication and authorization procedures means not receiving an EAP identity request, or not receiving an EAP success, or not receiving an EAP failure, or not receiving new slice information. It may also mean that a message that triggers acquisition (configuration update command or de-registration request) has not been received, or a message that sets new slice information (DL NAS transport) has not been received.

The solution described here is based on the timer 11 activated by the core network, and the registration request ( It manages the sending of initial registration requests, mobility registration updates, or periodic registration updates. Note that managing transmission may mean managing the behavior of transmitting and the behavior of suppressing transmission, and the behavior of transmitting is sometimes expressed as re-attempt (reconnection).

Here, the timer 11 is a timer that is activated when the core network transmits to the UE 10 a registration accept message using S-NSSAI to which the third network slice information and the first reason value are associated. good. That is, the timer 11 may be a timer for determining whether or not the network is abnormal while performing authentication and authorization procedures specific to network slices.

The steps shown in FIG. 13 are explained in detail as follows.

Step (1) After executing the processes of steps S0501 to S0505 in FIG. 5, the AMF 30 transmits at least one information among the third network slice information and the first reason value to the UE 10 (S1301). The transmission of at least one of the third network slice information and the first reason value may be caused by the AMF 30 receiving a registration complete message from the UE 10 in response to step (1).

At this time, the UE 10 may hold one or more S-NSSAIs indicated by the third network slice information in association with the first reason value (reason value indicating pending). Further, the AMF 30 may also associate one or more S-NSSAI corresponding to the third network slice information with the first reason value (reason value indicating pending) and hold it as UE context information. The AMF 30 sets the timer value to be set in the timer 11 in association with one or more S-NSSAIs associated with the third network slice information and/or the first reason value (reason value indicating pending). May be retained as context information.

Step (2) The AMF 30 implements the third processing example (S1302). In the third processing example, the AMF 30 may implement one or more of the first behavior example, the second behavior example, and the third behavior example. The third processing example is the behavior (first (behavior example), behavior until the timer 11 expires or stops (second behavior example), and behavior when the timer 11 expires or stops (third behavior example).

The first behavior example in this aspect may be a behavior in which the AMF 30 starts the timer 11.

The AMF 30 sets the timer 11 to one or more S-NSSAIs associated with the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) and/or the UE. , and/or PLMN or a combination thereof. In other words, the first timer information including the timer value of the timer 11 is one of the third network slice information (Rejected NSSAI) that is associated with the first reason value (reason value indicating pending). The above S-NSSAI, and/or UE, and/or PLMN, or a combination thereof may be set. For example, the AMF 30 starts the timer 11 in units of one or more S-NSSAIs associated with the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI). or in units of combinations of one or more S-NSSAIs and PLMNs associated with the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI). The timer 11 may be started, and one or more S-NSSAI and UE associated with the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) The timer 11 may be started for each combination of UE and PLMN, the timer 11 may be started for each UE, the timer 11 may be started for each PLMN, or the timer 11 may be started for each combination of UE and PLMN. The timer 11 may be started, and one or more S-NSSAI and UE associated with the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) The timer 11 may be activated in units of combinations of .

In addition, if there are two or more S-NSSAIs associated with the first reason value (reason value indicating pending), the timer value set in the timer 11 is the timer value of the single S-NSSAI and the first one. It may be obtained by multiplying the number of S-NSSAIs associated with the reason value (reason value indicating pending).

As a second behavior example in this aspect, the following procedure example 1 may be implemented.

Until the activated timer 11 stops or expires, the AMF 30 receives the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) received from the UE 10. ), or one or more S-NSSAIs associated with the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI). A registration request (initial registration request, mobility registration update, or periodic registration update) using the S-NSSAI of the serving PLMN to which the NSSAI is mapped may be ignored.

The AMF 30 may implement the following procedure example 2 as a second behavior example.

Until the activated timer 11 stops or expires, the AMF 30 receives the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) from the UE 10. or one or more S-NSSAIs associated with the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI). When receiving a registration request (initial registration request, mobility registration update, or periodic registration update) using the S-NSSAI of the serving PLMN to which the A registration reject message or a registration accept message in which a reason value (Reject cause) for each S-NSSAI is set may be transmitted to the UE 10 depending on the processing status of the procedure. Reject cause may include Network Slice specific authentication and authorization on going, AAA server not responding, AAA server failure, AAA server not found, etc.

As a second behavior example in this aspect, the following procedure example 3 may be implemented.

Until the activated timer 11 stops or expires, the AMF 30 is associated with the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI). One or more S-NSSAIs or one or more S-NSSAIs associated with the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) are mapped. When the AMF 30 receives a Namf_Communication_N1N2MessageTransfer message for the S-NSSAI of the serving PLMN from the SMF 40, the AMF 30 indicates that the S-NNSAI is currently executing a network slice-specific authentication and authorization procedure. The Namf_Communication_N1N2MessageTransfer response message may be sent to the SMF 40 by setting information indicating this. Information indicating that the relevant S-NNSAI is executing a network slice-specific authentication and authorization procedure (Network Slice-Specific Authentication and Authorization procedure) is notified that the Namf_Communication_N1N2MessageTransfer message cannot be processed temporarily. Information (Temporally not available) may also be included. The SMF 40 receives information indicating that the S-NNSAI is executing a network slice-specific authentication and authorization procedure. Next, the SMF 40 may start a locally configured timer and resend the Namf_Communication_N1N2MessageTransfer message to the AMF 40 after a certain period of time.

As a third behavior example in this aspect, the AMF 30 displays a first reason value (pending ( The third network slice information (Rejected NSSAI) may be disassociated from one or more S-NSSAIs associated with the third network slice information (Rejected NSSAI). Here, canceling the association between the first reason value (reason value indicating pending) and one or more S-NSSAIs associated with the third network slice information (Rejected NSSAI) means that the AMF 30 maintains For one or more S-NSSAIs associated with the third network slice information (Rejected NSSAI) that is ) may mean deleting the reason value (reason value indicating failure), or may mean rewriting it with a second reason value (reason value indicating failure).

Step (3) After implementing the third processing example, in order to solve the problem that the UE 10 waits indefinitely for authentication and authorization procedures specific to network slices, the AMF 30 issues a configuration update command or de-registration The behavior (S1303/S1304/S1305) of transmitting a request message or a DL NAS transport message to the UE 10 may be implemented. These messages may be for setting new network slice information in the UE 10. The new network slice information may be the second network slice information (Allowed NSSAI), the third network slice information (Rejected NSSAI), and/or the fourth network slice information (Configured NSSAI).

Specifically, the AMF 30 may implement the following first procedure example shown in FIG. 13A as step (3) performed after the third processing example.

When the activated timer 11 stops or expires, the AMF 30 places the first instruction information, the third network slice information, and/or the first reason value in the de-registration request, and sends the UE 10 may be sent to (S1303). In the de-registration request message, re-registration required or another information element may be set, and the AMF may prompt the UE 10 to start the re-registration process by sending this message.

In some cases, the AMF 30 performs the following second procedure example, which is different from the first procedure example shown in FIG. 13(B), as step (3) performed after the third processing example. It's okay.

When the activated timer 11 stops or expires, the AMF 30 provides first instruction information, and/or second network slice information, and/or third network slice information, and/or the first reason. The value may be placed in the configuration update command and transmitted to the UE 10 (S1304). Re-registration required or another information element is set in the configuration update command message, and the AMF 30 may prompt the UE 10 to start the re-registration process by sending this message.

In some cases, the AMF 30 performs the following third procedure example, which is different from the first to second procedure examples shown in FIG. 13(C), as step (3) performed after the third processing example. may be implemented.

When the activated timer 11 stops or expires, the AMF 30 outputs second network slice information, and/or third network slice information, and/or first reason value, and/or fourth network slice information. The slice information may be included in a DL NAS transport message and transmitted to the UE 10 (S1305). A re-registration required or another information element is set in the DL NAS transport message, and the AMF 30 may prompt the UE 10 to start the re-registration process by transmitting this message.

Here, the UE 10 that has received each message described in the first procedure example, second procedure example, or third procedure example in this aspect described above implements the fourth processing example. In the fourth processing example, the UE 10 may implement the first behavior example.

Specifically, the UE 10 may implement the following first procedure example as a first behavior example.

When the UE 10 receives the second network slice information, the UE 10 selects one or more S-NSSAI included in the second network slice information and one or more of the third network slice information (Rejected NSSAI) held by the UE 10. If one or more S-NSSAIs associated with the first reason value (reason value indicating pending) match, the UE 10 transfers the matching one or more S-NSSAIs to the third network slice information. (Rejected NSSAI).

In some cases, the UE 10 may implement the following second example procedure as a first example behavior.

When the UE 10 receives the third network slice information and the second reason value, the UE 10 receives one or more S-NSSAIs included in the third network slice information and the third network slice information held by the UE 10 ( If one or more S-NSSAIs associated with the first reason value (reason value indicating pending) of Rejected NSSAIs match, the UE 10 The associated reason value may be rewritten to the reason value indicated by the second reason value. Here, the reason value indicated by the second reason value may be a reason value indicating failure.

In some cases, the UE 10 may implement the following third procedure example as a first behavior example.

When the UE 10 receives the fourth network slice information including the Configured NSSAI, the UE 10 may delete the third network slice information (Rejected NSSAI) that it holds. That is, the UE 10 may reset the held third network slice information (Rejected NSSAI) by receiving the fourth network slice information (Configured NSSAI). The UE 10 transmits a registration request (initial registration request, mobility registration update, or periodic registration update) message using one or more S-NSSAI associated with the fourth network slice information (Configured NSSAI) to the AMF 30. Good too. The fourth network slice information set by the UE 10 includes the first reason value (indicating pending) for authentication and authorization specific to network slices in the third network slice information (Rejected NSSAI). One or more S-NSSAIs associated with the reason value) may be included. In other words, the UE 10 receives the first reason value (reason value indicating pending) regarding authentication and authorization specific to the network slice that was included in the reset third network slice information (Rejected NSSAI). A registration request (initial registration request, mobility registration update, or periodic registration update) message can be sent to the AMF 30 using one or more S-NSSAIs associated with the AMF 30 .

In a certain case, after implementing the fourth processing example, the UE 10 may implement the following first procedure example as a second behavior example. Furthermore, the first procedure example in the second behavior example may be implemented in addition to the first procedure example, second procedure example, or third procedure example in the first behavior example.

FIG. 14 shows the reconnection procedure without using S-NSSAI associated with the first reason value (reason value indicating pending) in the first procedure example of the second behavior example of this aspect. FIG.

Specifically, after implementing the fourth processing example in this aspect as shown in FIG. 14, the UE 10 selects the first reason value (pending) of the third network slice information (Rejected A registration request (initial registration request, mobility registration update, or periodic registration update) message that does not use one or more S-NSSAIs may be sent to the AMF 30 (S1401).

Here, one or more S-NSSAIs that were associated with the first reason value (reason value indicating pending) among the third network slice information (Rejected NSSAI) are, for example, It may be the S-NSSAI in which the reason value described in the first behavior example of the fourth processing example is rewritten to the second reason value (reason value indicating failure).

The AMF 30 receives a registration request message that does not use one or more S-NSSAIs that is associated with the first reason value (reason value indicating pending) among the third network slice information (Rejected NSSAI). do. Next, when setting the new second network slice information (Allowed NSSAI) to the UE, the AMF 30 sets the second network slice information in the registration accept message and sets the new third network slice information (Rejected NSSAI). When setting the UE, the third network slice information and the second reason value are set in the registration accept message, and when setting the new fourth network slice information (Configured NSSAI) in the UE, the fourth network slice information and the second reason value are set in the registration accept message. network slice information may be set and a registration accept message including these information may be transmitted to the UE 10 (S1402).

Here, a case will be described in which the second network slice information is included in the registration accept message. One or more S-NSSAIs included in the second network slice information and the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) held by the UE 10 When one or more associated S-NSSAIs match, the UE 10 may delete the matching one or more S-NSSAIs from the third network slice information (Rejected NSSAI). The UE 10 transmits a registration request (initial registration request, mobility registration update, or periodic registration update) message to the AMF 30 using one or more S-NSSAIs deleted from the third network slice information (Rejected NSSAI). (S1403).

For example, it is assumed that the UE 10 holds S-NSSAI #1 as the S-NSSAI associated with the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. At this time, if a registration accept message including S-NSSAI #1 is received as the second network slice information, the UE 10 selects the S-NSSAI that is retained as the S-NSSAI associated with the third network slice information (Rejected NSSAI). Delete #1. Furthermore, the UE 10 may transmit a registration request (initial registration request, mobility registration update, or periodic registration update) message using S-NSSAI#1 to the AMF 30 (S1403).

A certain case will be described in which the third network slice information and the second reason value are included in the registration accept message. One or more S-NSSAIs included in the third network slice information and the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) held by the UE 10 When the one or more associated S-NSSAIs match, the UE 10 may rewrite the reason value associated with the matched one or more S-NSSAIs to the reason value indicated by the second reason value. Here, the reason value indicated by the second reason value may be a reason value indicating failure.

For example, it is assumed that the UE 10 holds S-NSSAI #1 as the S-NSSAI associated with the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. At this time, if a registration accept message including S-NSSAI#1 and a second reason value (a reason value indicating failure) is received as the third network slice information, the UE 10 receives the third network slice information. The reason value associated with S-NSSAI#1 held as the S-NSSAI associated with (Rejected NSSAI) may be rewritten to a second reason value (reason value indicating failure).

In some cases, for example, if the fourth network slice information includes Configured NSSAI, the UE 10 may delete the third network slice information (Rejected NSSAI) that it holds. That is, the UE 10 may reset the held third network slice information (Rejected NSSAI) by receiving the fourth network slice information (Configured NSSAI). The UE 10 transmits a registration request (initial registration request, mobility registration update, or periodic registration update) message using one or more S-NSSAI associated with the fourth network slice information (Configured NSSAI) to the AMF 30. Good (S1403). The fourth network slice information set by the UE 10 includes the first reason value (indicating pending) for authentication and authorization specific to network slices in the third network slice information (Rejected NSSAI). One or more S-NSSAIs associated with the reason value) may be included. That is, in step S1403, the UE 10 selects the first reason value (indicating pending) for authentication and authorization specific to the network slice that was included in the reset third network slice information (Rejected NSSAI). A registration request (initial registration request, mobility registration update, or periodic registration update) message can be sent to the AMF 30 using one or more S-NSSAIs associated with the reason value.

For example, it is assumed that the UE 10 holds S-NSSAI#1 and S-NSSAI#2 as S-NSSAIs associated with the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. A fourth reason value (a reason value indicating "S-NSSAI not available in the current registration area") described in Non-Patent Document 3 is associated with S-NSSAI#2. At this time, when receiving the registration accept message including the fourth network slice information (Configured NSSAI), the UE 10 selects S-NSSAI#1, which is held as the S-NSSAI associated with the third network slice information (Rejected NSSAI). and S-NSSAI#2, or the third network slice information (Rejected NSSAI) itself held by the UE 10 may be deleted. For example, if S-NSSAI#1 is included in the fourth network slice information (Configured NSSAI), the UE 10 uses S-NSSAI#1 included in the fourth network slice information (Configured NSSAI). A registered registration request (initial registration request, mobility registration update, or periodic registration update) message may be sent to the AMF 30.

In some cases, the UE 10 may implement the following second procedure example as a second behavior example after implementing the fourth processing example.

FIG. 15 shows the reconnection procedure using the S-NSSAI associated with the first reason value (reason value indicating pending) in the second procedure example of the second behavior example of this aspect. FIG.

Specifically, after implementing the fourth processing example in this aspect as shown in FIG. 15, the UE 10 selects the first reason value (pending) from the third network slice information (Rejected NSSAI). A registration request (initial registration request, mobility registration update, or periodic registration update) message may be sent to the AMF 30 using one or more S-NSSAIs associated with the reason value shown (S1501).

The AMF 30 sends a registration request message using one or more S-NSSAIs associated with the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI). Receive. Next, when setting the new second network slice information (Allowed NSSAI) to the UE, the AMF 30 sets the second network slice information in the registration accept message and sets the new third network slice information (Rejected NSSAI). When setting the UE, the third network slice information and the second reason value are set in the registration accept message, and when setting the new fourth network slice information (Configured NSSAI) in the UE, the fourth network slice information and the second reason value are set in the registration accept message. network slice information may be set, and a registration accept message including these information may be transmitted to the UE 10 (S1502).

Note that, based on the first procedure example, the UE 10 deletes the reason value associated with one or more S-NSSAIs associated with the third network slice information (Rejected NSSAI), or deletes the reason value associated with the second reason value (failure (reason value indicating failure), the AMF 30 determines that the reason value associated with the S-NSSAI as UE Context information is the first reason value (reason value indicating pending). It is good to recognize that. That is, the reason value recognized by the AMF 30 may be different from the reason value associated with one or more S-NSSAIs associated with the third network slice information (Rejected NSSAI) recognized by the UE 10. The reason value recognized by the AMF 30 is associated with one or more S-NSSAIs associated with the third network slice information (Rejected NSSAI) to be recognized.

Here, a case will be described in which the second network slice information is included in the registration accept message. One or more S-NSSAIs included in the second network slice information and the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) held by the UE 10 When one or more associated S-NSSAIs match, the UE 10 may delete the matching one or more S-NSSAIs from the third network slice information (Rejected NSSAI). The UE 10 transmits a registration request (initial registration request, mobility registration update, or periodic registration update) message to the AMF 30 using one or more S-NSSAIs deleted from the third network slice information (Rejected NSSAI). (S1503)

For example, it is assumed that the UE 10 holds S-NSSAI #1 as the S-NSSAI associated with the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. At this time, if a registration accept message including S-NSSAI #1 is received as the second network slice information, the UE 10 selects the S-NSSAI that is retained as the S-NSSAI associated with the third network slice information (Rejected NSSAI). Delete #1. Furthermore, the UE 10 may transmit a registration request (initial registration request, mobility registration update, or periodic registration update) message using S-NSSAI#1 to the AMF 30 (S1503).

A certain case will be described in which the third network slice information and the second reason value are included in the registration accept message. One or more S-NSSAIs included in the third network slice information and the first reason value (reason value indicating pending) of the third network slice information (Rejected NSSAI) held by the UE 10 When the one or more associated S-NSSAIs match, the UE 10 may rewrite the reason value associated with the matched one or more S-NSSAIs to the reason value indicated by the second reason value. Here, the reason value indicated by the second reason value may be a reason value indicating failure.

For example, assume that the UE 10 holds S-NSSAI #1 as the third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. At this time, if a registration accept message including S-NSSAI#1 and a second reason value (a reason value indicating failure) is received as the third network slice information, the UE 10 receives the third network slice information. The reason value associated with S-NSSAI#1 held as the S-NSSAI associated with (Rejected NSSAI) may be rewritten to a second reason value (reason value indicating failure).

In some cases, for example, if the fourth network slice information includes Configured NSSAI, the UE 10 may delete the third network slice information (Rejected NSSAI) that it holds. That is, the UE 10 may reset the held third network slice information (Rejected NSSAI) by receiving the fourth network slice information (Configured NSSAI). The UE 10 transmits a registration request (initial registration request, mobility registration update, or periodic registration update) message using one or more S-NSSAI associated with the fourth network slice information (Configured NSSAI) to the AMF 30. Good (S1503). The fourth network slice information set by the UE 10 includes the first reason value (indicating pending) for authentication and authorization specific to network slices in the third network slice information (Rejected NSSAI). One or more S-NSSAIs associated with the reason value) may be included. That is, in step S1503, the UE 10 selects the first reason value (indicating pending) for authentication and authorization specific to the network slice that was included in the reset third network slice information (Rejected NSSAI). A registration request (initial registration request, mobility registration update, or periodic registration update) message can be sent to the AMF 30 using one or more S-NSSAIs associated with the reason value.

For example, assume that the UE 10 holds S-NSSAI#1 and S-NSSAI#2 as third network slice information (Rejected NSSAI). A first reason value (a reason value indicating pending) is associated with S-NSSAI#1. A fourth reason value (a reason value indicating "S-NSSAI not available in the current registration area") described in Non-Patent Document 3 is associated with S-NSSAI#2. At this time, when receiving the registration accept message including the fourth network slice information (Configured NSSAI), the UE 10 selects S-NSSAI#1, which is held as the S-NSSAI associated with the third network slice information (Rejected NSSAI). and S-NSSAI#2, or the third network slice information (Rejected NSSAI) itself held by the UE 10 may be deleted. For example, if S-NSSAI#1 is included in the fourth network slice information (Configured NSSAI), the UE 10 uses S-NSSAI#1 included in the fourth network slice information (Configured NSSAI). A registered registration request (initial registration request, mobility registration update, or periodic registration update) message may be sent to the AMF 30.

Next, an example of processing for stopping the activated timer 11 will be described as follows.

The AMF 30 may be configured to stop the timer 11 when transmitting an EAP identity request to the UE 10, or may be configured to stop the timer 11 when transmitting EAP success or EAP failure to the UE 10. It's okay.

So far, we have explained the case where the UE 10 receives at least one of the third network slice information and the first reason value from the AMF 30 after executing the processes of steps S0501 to S0505 in FIG. A case in which the network node receives the fifth network slice information will be described below.

Specifically, if all S-NSSAIs included in the first network slice information (Requested NSSAI) are subject to network slice-specific authentication and authorization, or if the first network slice information (Requested NSSAI) is not included, and all default S-NSSAIs set in the subscriber information are subject to network slice-specific authentication and authorization, or the first All S-NSSAI included in the network slice information (Requested NSSAI) do not match the S-NSSAI (Subscribed NSSAI) recorded in the subscriber information, and the S-NSSAI is set in the subscriber information. If all default S-NSSAIs are subject to network slice-specific authentication and authorization, the AMF 30 may transmit the fifth network slice information to the UE 10.

At this time, since there is no S-NSSAI as the second network slice information (Allowed NSSAI) that can be transmitted to the UE 10, the AMF 30 transmits the fifth network slice information. Here, the AMF30 includes S-NSSAI, which is subject to network slice-specific authentication and authorization, in the third network slice information, and the related first reason value (reason value indicating pending). The third network slice information and the first reason value may be transmitted to the UE 10 or may not be transmitted to the UE 10.

At this time, the UE 10 may perform the same behavior as when receiving at least one of the third network slice information and the first reason value from the AMF 30 described in this aspect.

(Fourth aspect)
The fourth aspect will be explained using FIG. 16.

In this aspect, after the UE 10 executes the processes of steps S0501 to S0505 in FIG. 5, the UE 10 receives the third network slice information including the S-NSSAI associated with the first reason value and specializes in regarding the scenario where the AMF is moved to another registration area with a change in the serving AMF while waiting for the authentication and authorization procedures that have been completed. The UE 10 supports a network slice-specific authentication and authorization procedure. Here, waiting for the authentication and authorization procedure specific to a network slice means that the UE 10 is waiting for the first reason value (pending ( This is a state in which one or more S-NSSAIs associated with a reason value indicating "suspended" are held. Specifically, waiting for network slice-specific authentication and authorization procedures means not receiving an EAP identity request, or not receiving an EAP success, or not receiving an EAP failure, or not receiving new slice information. It may also mean that a message that triggers acquisition (configuration update command or de-registration request) has not been received, or a message that sets new slice information (DL NAS transport) has not been received. Here, the AMF before the change may be expressed as the old AMF, and the AMF after the change may be expressed as the new AMF.

The solution described here is to send and receive UE context information related to authentication and authorization procedures specific to network slices between the old AMF and the new AMF, so that when the serving AMF changes, However, the UE 10 sends a registration request (initial registration request, mobility registration update, or periodic registration update) using the S-NSSAI that was associated with the first reason value (reason value indicating pending). It is to manage the Note that managing transmission may mean managing the behavior of transmitting and the behavior of suppressing transmission, and the behavior of transmitting is sometimes expressed as re-attempt (reconnection).

The steps shown in FIG. 16 are explained in detail as follows.

Step (1) After executing steps S0501 to S0505 in FIG. 5, the UE 10 receives the third network slice information, the first reason value, the second reason value, the third reason value, and the fourth reason value from the AMF 30. At least one of the reason values is received (S1602).

At this time, when transmitting the third network slice information (Rejected NSSAI) to the UE 10, the AMF 30 may configure the associated reason value as follows.

Specifically, the AMF 30 sets at least the first reason value, the second reason value, the third reason value, and the fourth reason value to the S-NSSAI included in the third network slice information. One information element may be configured by combining one of them. That is, the reason value combined with the S-NSSAI included in the third network slice information may be one information element.

Furthermore, the AMF 30 assigns at least one of the first reason value, the second reason value, the third reason value, and the fourth reason value to the S-NSSAI included in the third network slice information. Two or more information elements may be configured in combination. For example, each information element may be combined as a first reason value and a second reason value, a first reason value and a third reason value, or a first reason value and a fourth reason value. good. That is, the reason value combined with the S-NSSAI included in the third network slice information may be two or more information elements.

Here, for example, the UE 10 receives third network slice information including the S-NSSAI associated with a reason value that is a combination of the first reason value and the fourth reason value. The UE 10 sets one or more S-NSSAIs associated with the third network slice information to a first reason value (a reason value indicating pending) and a fourth reason value (S-NSSAI not available in the current (reason value indicating the registration area). The AMF 30 also assigns one or more S-NSSAIs associated with the third network slice information to a first reason value (reason value indicating pending) and a fourth reason value (S-NSSAI not available in The reason value indicating the current registration area) may be stored as UE context information in association with the UE context information.

Here, the UE 10 implements the fifth processing example. A fifth processing example in this aspect is a registration request (initial registration request, mobility registration update, or periodic registration update) based on the reason value associated with the S-NSSAI included in the third network slice information. The behavior may be to manage the transmission of .

For example, the reason value associated with S-NSSAI included in the third network slice information is a combination of the reason value indicated by the first reason value and the reason value indicated by the fourth reason value (referred to as the reason value). ), the UE 10 maps one or more S-NSSAIs associated with the reason value or one or more S-NSSAIs associated with the reason value until the reason value is resolved. The transmission of a registration request (initial registration request, mobility registration update, or periodic registration update) using the S-NSSAI of the serving PLMN may be managed.

The UE 10 may implement the following first procedure example. To explain using a more specific example, assume that the third network slice information includes S-NSSAI#1. S-NSSAI#1 is associated with a first reason value (reason value indicating pending) and a fourth reason value (reason value indicating S-NSSAI not available in the current registration area). Suppose there is. Here, it is assumed that the authentication and authorization procedures specific to network slices are successful. Note that the success of the network slice-specific authentication and authorization procedure may mean that the UE 10 receives EAP success. At this time, the first reason is selected from among the reason value indicated by the first reason value and the reason value indicated by the fourth reason value associated with S-NSSAI#1 included in the third network slice information held by the UE 10. The reason value indicated by the value has been resolved, but the reason value indicated by the fourth reason value has not been resolved. Therefore, a registration request (initial registration request, , mobility registration update, or periodic registration update) may be suppressed.

The UE 10 may implement the following second procedure example. The second procedure example may be a case where the UE 10 moves to another registration area with a change in serving AMF.

To explain using a more specific example, assume that the third network slice information includes S-NSSAI#1. A first reason value (reason value indicating pending) and a fourth reason value (reason value indicating S-NSSAI not available in the current registration area) are associated with S-NSSAI#1. shall be. Here, when the UE 10 moves to another registration area, the reason value of the fourth reason value has been resolved, but the reason value indicated by the first reason value has not been resolved. Therefore, a registration request (initial registration request, , mobility registration update, or periodic registration update) may be suppressed.

An example of the preliminary operation of the AMF 30 for realizing the second procedure example of the fifth processing example will be described below.

Here, regarding the registration area movement of the UE 10 described in the second procedure example, the registration area before movement is referred to as RA1, and the registration area after movement is referred to as RA2. It is assumed that the core network is configured such that the AMF 30 (referred to as old AMF 30) that sends and receives messages via RA1 and the AMF 30 (referred to as new AMF 30) that sends and receives messages via RA2 are different AMFs.

The new AMF 30, which has received the registration request (mobility registration update) message sent when the UE 10 moves from RA1 to RA2, acquires UE context information related to network slice-specific authentication and authorization from the old AMF 30 (S1601).

Specifically, the new AMF 30 activates the Namf_Communication_UEContextTransfer function or service described in Non-Patent Document 1, and requests the old AMF 30 for the execution status of authentication and authorization procedures specific to network slices. You may. The old AMF 30 that has been requested to know the execution status of the network slice-specific authentication and authorization procedure may respond with the execution status of the network slice-specific authentication and authorization procedure regarding the UE 10. When the new AMF 30 acquires the execution state of the authentication and authorization procedure specialized for the network slice regarding the UE 10, it may execute the authentication and authorization procedure specialized for the network slice regarding the UE 10. Executing an authentication and authorization procedure specific to a network slice may be a process performed by the AMF 30 to determine whether to execute an authentication and authorization procedure specific to a network slice as described in FIG. In the process of executing the Network Slice-Specific Authentication and Authorization procedure using EAP (Extensible Authentication Protocol) described in Section 4.2.9.2 of Non-Patent Document 2, which is described in There may be.

Specifically, the new AMF 30 may transmit an EAP identity request to the UE 10 based on the UE context information related to network slice-specific authentication and authorization acquired by the old AMF 30.

In other words, the AMF 30 may be able to manage the pending state in addition to success and failure state management as network slice-specific authentication and authorization state management.

The new AMF 30 transmits the third network slice information and at least one of the first reason value, the second reason value, the third reason value, and the fourth reason value to the UE 10 (S1602). The UE 10 then implements the fifth processing example.

In the specific example of the first procedure example of the fifth processing example, when the UE 10 moves to another registration area, the reason value of the fourth reason value is canceled. Therefore, the UE 10 requests a registration request (initial A registration request, mobility registration update, or periodic registration update) may be sent to the AMF 30 (S1603).

In other words, the reason value indicated by the first reason value may be a reason value that does not depend on the registration area, and once the authentication and authorization procedures specific to the network slice are successful, even if the registration area changes. , a state in which network slice-specific authentication and authorization procedures are successful may be maintained. Note that the UE 10 may hold the state in which the authentication and authorization procedures specific to the network slice were successful in association with the relevant S-NSSAI, and specifically, hold the state in association with the reason value indicating success. It's okay to do so.

In a specific example of the second procedure example of the fifth processing example, when the UE 10 moves to another registration area, the reason value of the fourth reason value is canceled. However, since the first reason value has not been resolved, the UE 10 selects the S-NSSAI#1 associated with the reason value or the serving PLMN to which the S-NSSAI#1 associated with the reason value is mapped. Transmission of a registration request (initial registration request, mobility registration update, or periodic registration update) using S-NSSAI may be suppressed.

In other words, the reason value indicated by the first reason value may be a reason value that does not depend on the registration area. The current state may be maintained. Note that the UE 10 may hold the pending state in association with the S-NSSAI, and specifically may hold the pending state in association with a reason value indicating pending.

After that, assume that the authentication and authorization procedures specific to network slices are successful in the destination registration area. Note that the success of the network slice-specific authentication and authorization procedure may mean that the UE 10 receives EAP success. In this case, since the reason value of the first reason value is canceled, the UE 10 can map S-NSSAI#1 associated with the reason value or S-NSSAI#1 associated with the reason value. A registration request (initial registration request, mobility registration update, or periodic registration update) using the S-NSSAI of the serving PLMN may be sent to the AMF 30 (S1603).

In this specification, user equipment (UE) (or mobile station, mobile terminal, mobile device, wireless device, etc.) is a wireless device. An entity connected to a network via an interface.

The UE in this specification is not limited to a dedicated communication device, and may be any of the following devices having a communication function as a UE described in this specification.

The terms "User Equipment (UE)" (as used in 3GPP), "mobile station", "mobile terminal", "mobile device", and "wireless terminal" are generally synonymous with each other. It is intended to be a standalone mobile station, such as a terminal, mobile phone, smartphone, tablet, cellular IoT terminal, IoT device, etc.

It will be understood that the terms "UE" and "wireless terminal" also include devices that remain stationary for long periods of time.

In addition, UE includes, for example, production equipment/manufacturing equipment and/or energy-related machinery (for example, boilers, engines, turbines, solar panels, wind power generators, hydroelectric power generators, thermal power generators, nuclear power generators, storage batteries, nuclear power systems) , nuclear power related equipment, heavy electrical equipment, pumps including vacuum pumps, compressors, fans, blowers, hydraulic equipment, pneumatic equipment, metal processing machines, manipulators, robots, robot application systems, tools, molds, rolls, conveyance equipment , lifting equipment, cargo handling equipment, textile machinery, sewing machinery, printing presses, printing-related machinery, paper processing machinery, chemical machinery, mining machinery, mining-related machinery, construction machinery, construction-related machinery, agricultural machinery and/or instruments, forestry fishing machinery and/or equipment, safety and/or environmental protection equipment, tractors, bearings, precision bearings, chains, gears, power transmission devices, lubrication devices, valves, pipe fittings, and and/or any of the equipment or machine application systems mentioned above).

UE also includes, for example, transportation equipment (for example, vehicles, automobiles, motorcycles, bicycles, trains, buses, carts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones, balloons, etc.). It may be.

Further, the UE may be, for example, an information communication device (for example, a computer and related devices, a communication device and related devices, electronic components, etc.).

In addition, UE includes, for example, refrigerators, refrigerator-applied products and equipment, commercial and service equipment, vending machines, automatic service machines, office machines and equipment, consumer electrical and electronic equipment (for example, audio equipment, speakers , radios, video equipment, televisions, microwave ovens, rice cookers, coffee makers, dishwashers, washing machines, dryers, electric fans, ventilation fans and related products, vacuum cleaners, etc.).

Further, the UE may be, for example, an electronic application system or an electronic application device (for example, an X-ray device, a particle accelerator, a radioactive material application device, a sonic application device, an electromagnetic application device, a power application device, etc.).

In addition, UE includes, for example, light bulbs, lighting, weighing machines, analytical instruments, testing machines, and measuring machines (for example, smoke alarms, interpersonal alarm sensors, motion sensors, wireless tags, etc.), watches, and physical and chemical machines. , an optical machine, a medical device and/or a medical system, a weapon, a tool, a hand tool, or the like.

A UE may also be, for example, a personal digital assistant or device with wireless communication capabilities (for example, an electronic device to which a wireless card or module is attached or configured to be inserted (e.g., a personal computer, an electronic measuring instrument, etc.)). )) may be used.

Further, the UE may be, for example, a device or a part thereof that provides the following applications, services, and solutions in the "Internet of Things (IoT)" using wired and wireless communication technology.

IoT devices (or things) include appropriate electronics, software, sensors, network connections, etc. that enable the devices to collect and exchange data with each other and with other communicating devices.

An IoT device may also be an automated device that follows software instructions stored in internal memory.

IoT devices may also operate without the need for human supervision or interaction.
IoT devices may also be devices that are installed for long periods of time and/or remain inactive for long periods of time.

IoT devices can also be implemented as part of stationary equipment. IoT devices can be embedded in non-stationary equipment (such as vehicles) or attached to animals or people to be monitored/tracked.

It will be appreciated that IoT technology can be implemented on any communication device that can be connected to a communication network that sends and receives data, whether controlled by human input or software instructions stored in memory.

It will be appreciated that IoT devices are also referred to as Machine Type Communication (MTC) devices, Machine to Machine (M2M) communication devices, or NB-IoT (Narrow Band-IoT) UE. .

It will also be appreciated that the UE may support one or more IoT or MTC applications.

Some examples of MTC applications are listed in the table below (Source: 3GPP TS22.368 V13.2.0 (2017-01-13) Annex B, the contents of which are incorporated herein by reference). This list is not exhaustive and is intended to represent exemplary MTC applications.

Applications, services, and solutions include, for example, MVNO (Mobile Virtual Network Operator) services/systems, disaster prevention wireless services/systems, private branch wireless telephone (PBX (Private Branch eXchange)) services/ systems, PHS/digital cordless telephone services/systems, POS (Point of Sale) systems, advertising transmission services/systems, multicast (MBMS (Multimedia Broadcast and Multicast Service)) services/systems, V2X (Vehicle to Everything: vehicle-to-vehicle communication and vehicle-to-vehicle/pedestrian-to-vehicle communication) services/systems, in-train mobile wireless services/systems, location information-related services/systems, disaster/emergency wireless communication services/systems, IoT (Internet of Things) services/systems, Community services/systems, video distribution services/systems, Femto cell application services/systems, VoLTE (Voice over LTE) services/systems, wireless TAG services/systems, billing services/systems, radio on-demand services/systems, roaming services/systems , user behavior monitoring service/system, communication carrier/communication network selection service/system, function restriction service/system, PoC (Proof of Concept) service/system, personal information management service/system for terminals, display/video service for terminals/ It may be a system, a non-communication service/system for terminals, an ad hoc NW/DTN (Delay Tolerant Networking) service/system, etc.

Note that the UE categories described above are merely application examples of the technical idea and each aspect described in this specification. It goes without saying that the invention is not limited to these examples, and that those skilled in the art can make various changes.

Note that the present disclosure is not limited to the above embodiments, and can be modified as appropriate without departing from the spirit. Further, the present disclosure may be implemented by appropriately combining each aspect.

Although the present invention has been described above with reference to each aspect, the present invention is not limited to the above. The configuration and details of the present invention can be modified in various ways that can be understood by those skilled in the art within the scope of the invention.

Although the present invention has been described above with reference to the embodiments, the present invention is not limited to the above. The configuration and details of the present invention can be modified in various ways that can be understood by those skilled in the art within the scope of the invention.

This application claims priority based on Japanese Patent Application No. 2019-146563 filed on August 8, 2019, and the entire disclosure thereof is incorporated herein.

10 U.E.
11 Communication section 12 Control section 20 NG-(R)AN
30 AMF
31 Communication unit 32 Control unit 40 SMF
50 UPF
60 UDM
70 AAA

Claims (13)

receiving a registration request message including at least one Single Network Slice Selection Assistance Information (S-NSSAI) from the wireless terminal;
For each S-NSSAI that is subject to Network Slice-Specific Authentication and Authorization (NSSAA), start a timer for determining whether it is abnormal in the NSSAA,
If one of the timers expires, it is recognized that the NSSAA for the first S-NSSAI corresponding to the one timer has been completed as a failure, and a non-access stratum (NAS ) send a message,
The NAS message includes a Rejected NSSAI including the first S-NSSAI and a cause value, the cause value indicating that the first S-NSSAI is unavailable due to the failure of the NSSAA; An S-NSSAI is included in the at least one S-NSSAI,
A method of communication by core network nodes. sending a registration request message including at least one Single Network Slice Selection Assistance Information (S-NSSAI) to the core network node;
One of the timers for determining whether or not something is abnormal in NSSAA, which is activated for each S-NSSAI that is subject to Network Slice-Specific Authentication and Authorization (NSSAA), has expired. receiving a non-access stratum (NAS) message from the core network node after the NSSAA for the first S-NSSAI corresponding to the one timer is completed as unsuccessful;
The NAS message includes a Rejected NSSAI including the first S-NSSAI and a cause value, the cause value indicating that the first S-NSSAI is unavailable due to the failure of the NSSAA; An S-NSSAI is included in the at least one S-NSSAI,
A communication method using a wireless terminal. Receiving means for receiving a registration request message including at least one Single Network Slice Selection Assistance Information (S-NSSAI) from a wireless terminal;
For each S-NSSAI that is subject to Network Slice-Specific Authentication and Authorization (NSSAA), start a timer for determining whether it is abnormal in the NSSAA,
If one of the timers expires, it is recognized that the NSSAA for the first S-NSSAI corresponding to the one timer has been completed as a failure, and a non-access stratum (NAS ) a sending means for sending a message;
The NAS message includes a Rejected NSSAI including the first S-NSSAI and a cause value, the cause value indicating that the first S-NSSAI is unavailable due to the failure of the NSSAA; An S-NSSAI is included in the at least one S-NSSAI,
A core network node characterized by: The transmitting means is configured to transmit a registration accept message including the certain S-NSSAI associated with a pending status to the wireless terminal,
Here, the pending status indicates that the NSSAA for the certain S-NSSAI is performed;
The core network node according to claim 3, characterized in that: comprising an execution means for executing the NSSAA for the certain S-NSSAI after transmitting the registration accept message;
The core network node according to claim 4, characterized in that: If the at least one S-NSSAI included in the Requested NSSAI is still subject to the NSSAA, the registration accept message includes an empty Allowed NSSAI;
The core network node according to claim 4 or 5, characterized in that: the NAS message including the first S-NSSAI and the Rejected NSSAI including the cause value is a registration accept message;
the NSSAA for the first S-NSSAI by the other core network node is determined to be a failure based on the first S-NSSAI included in the Requested NSSAI that the wireless terminal sends to another core network node; After completion, the registration accept message is sent;
The core network node according to claim 3, characterized in that: Transmitting means for transmitting a registration request message including at least one Single Network Slice Selection Assistance Information (S-NSSAI) to the core network node;
One of the timers for determining whether or not something is abnormal in NSSAA, which is activated for each S-NSSAI that is subject to Network Slice-Specific Authentication and Authorization (NSSAA), has expired. receiving means for receiving a non-access stratum (NAS) message from the core network node after the NSSAA for a first S-NSSAI corresponding to the one timer is completed as a failure based on the ,
The NAS message includes a Rejected NSSAI including the first S-NSSAI and a cause value, the cause value indicating that the first S-NSSAI is unavailable due to the failure of the NSSAA; An S-NSSAI is included in the at least one S-NSSAI,
A wireless terminal characterized by: comprising a storage means for storing the status of the NSSAA for the certain S-NSSAI in the UE context of the wireless terminal;
Here, the status of the NSSAA for the certain S-NSSAI is one of "success", "failure", and "pending",
The wireless terminal according to claim 8, characterized in that: comprising a storage means for storing the first S-NSSAI and a Rejected NSSAI including the cause value;
not attempting to use the S-NSSAI included in the stored Rejected NSSAI until the wireless terminal is powered off or the UICC including the USIM is removed;
The wireless terminal according to claim 8 or 9, characterized in that: The timer is fired after the Registration accept message is sent.
A communication method by a core network node according to claim 1. sending a control message regarding completion of said NSSAA;
Stop the timer
A communication method by a core network node according to claim 1. The timer is fired after the Registration accept message is sent.
A communication method using a wireless terminal according to claim 2.

Images