Handling of selected n3iwf or tngf not compatible with allowed nssai in non-3gpp mobile communication

Abstract

Techniques related to handling of a selected non-3rd Generation Partnership Project (non-3GPP) Interworking Function (N3IWF) or Trusted Non-3GPP Gateway Function (TNGF) that is incompatible with allowed network slice selection assistance information (NSSAI) in non-3GPP mobile communications are described. A device (e.g., a user equipment (UE)) receives, from a network, a rejection message indicating that a selected N3IWF or TNGF is incompatible with allowed NSSAI. The UE then performs a corresponding operation in response to receiving the rejection message.

Description

[0001] Cross-referencing

[0002] This disclosure claims priority to Indian Patent Application No. 202421027389, filed on April 2, 2024, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to mobile communications, and more specifically, to the handling of incompatibility between a selected non-3GPP Interworking Function (N3IWF) or a Trusted Non-3GPP Gateway Function (TNGF) and permitted network slice selection assistance information (NSSAI) in non-3GPP mobile communications. Background Technology

[0004] In current 3rd Generation Partnership Project (3GPP) specifications for wireless communications (e.g., mobile communications), if the Access & Mobility Management Function (AMF) receives a Mobility and Periodic Registration Update Request from a User Equipment (UE) via a non-3GPP access and detects that the N3IWF used by the UE is incompatible with the allowed NSSAI, and the UE has indicated its support for slice-based N3IWF selection in the REGISTRATION REQUEST message, then the AMF can send a REGISTRATION REJECT message with 5th Generation Mobility Management (5GMM) reason #81 "Selected N3IWF is not compatible with the allowed NSSAI," and can provide information on a suitable N3IWF in the REGISTRATION REJECT message to indicate the suitable N3IWF compatible with the requested NSSAI. Furthermore, if the AMF receives the Mobility and Periodic Registration Update Request via the non-3GPP access network and detects that the TNGF used by the UE is incompatible with the allowed NSSAI, and the UE has indicated its support for slice-based TNGF selection in the REGISTRATION REQUEST message, the AMF can send a REGISTRATIONREJECT message with 5GMM reason #82 "Selected TNGF is not compatible with the allowed NSSAI," and can provide information for a suitable Trusted Non-3GPP Access Network (TNAN) located in the TNAN information element (IE) of the REGISTRATION REJECT message, indicating a suitable TNGF compatible with the requested NSSAI.

[0005] However, at the time of this invention, when the UE receives reason #81 or #82, if the reason is received from an incorrect cell (e.g., a 3GPP cell or a standalone non-public network (SNPN) cell), the UE's behavior is not yet defined. Therefore, a solution is needed to handle incompatibility between the selected N3IWF or TNGF and the permitted NSSAI in non-3GPP mobile communications. Summary of the Invention

[0006] The following summary is for illustrative purposes only and is not intended to be limiting in any way. That is, the following summary aims to introduce the concepts, key points, benefits, and advantages of the novel and non-obvious techniques described herein. Selected embodiments will be further described in the detailed embodiments below. Therefore, the following summary is not intended to identify the essential features of the claimed subject matter, nor is it intended to define the scope of the claimed subject matter.

[0007] One objective of this disclosure is to provide solutions or methods for resolving the problems described herein. More specifically, the various solutions proposed in this disclosure are believed to provide solutions for processing incompatible with the selected N3IWF or TNGF and permitted NSSAI in non-3GPP mobile communications. It is believed that implementations of one or more of the solutions proposed herein can solve or otherwise mitigate the aforementioned problems.

[0008] In one aspect, a method may involve a UE receiving from a network a rejection message indicating that a selected N3IWF or TNGF is incompatible with an allowed NSSAI. The method may also involve the UE performing an operation in response to receiving the rejection message.

[0009] In another aspect, a device may include a transceiver configured to perform wireless communication and a processor coupled to the transceiver. The processor may receive from a network a rejection message indicating that a selected N3IWF or TNGF is incompatible with an allowed NSSAI. The processor may also perform operations in response to receiving the rejection message.

[0010] It is worth noting that while the descriptions provided herein may be set against the backdrop of certain wireless access technologies, networks, and network topologies, such as 5th Generation (5G) / New Radio (NR) / Beyond Fifth Generation (B5G) mobile communications, the proposed concepts, schemes, and any variations / derivatives thereof can be implemented, be implemented, and be implemented in other types of wireless access technologies, networks, and network topologies, such as, but not limited to, 4th Generation (4G) / Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet of Things (IoT), Narrow Band Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), Vehicle-to-Everything (V2X), and non-terrestrial network (NTN) communications. Therefore, the scope of this disclosure is not limited to the examples described herein. Attached Figure Description

[0011] The accompanying drawings are included to provide a further understanding of this disclosure and are incorporated in and constitute a part of this disclosure. The drawings illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the disclosure. It will be understood that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to actual dimensions in order to clearly illustrate the concepts of the disclosure.

[0012] Figure 1 This is a schematic diagram of an example network environment in which various solutions and schemes according to this disclosure can be implemented.

[0013] Figure 2 This is a block diagram of an example communication system according to one embodiment of the present disclosure.

[0014] Figure 3 This is a flowchart of a second example program according to one embodiment of the present disclosure. Detailed Implementation

[0015] This document discloses detailed embodiments and implementations of the claimed subject matter. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter, which can be embodied in various forms. This disclosure can be embodied in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided to make the description of this disclosure exhaustive and complete, and to fully convey the scope of this disclosure to those skilled in the art. In the following description, details of well-known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations.

[0016] Overview

[0017] The embodiments of this disclosure relate to various techniques, methods, schemes, and / or solutions related to processing incompatible N3IWF or TNGF selected in non-3GPP mobile communications with permitted NSSAI. According to this disclosure, multiple possible solutions can be implemented individually or in combination. That is, although these possible solutions are described individually below, two or more of these possible solutions can be implemented in one or another combination.

[0018] Figure 1 An example network environment 100 is shown, in which various solutions and schemes according to this disclosure can be implemented. Figures 2 to 3 Examples of implementing various proposed schemes in a network environment 100 according to this disclosure are shown. The following description of the various proposed schemes is available in [reference needed]. Figures 1 to 3 It was carried out.

[0019] See Figure 1 Network environment 100 may involve UE 110 (e.g., a mobile device or smartphone) wirelessly communicating with wireless network 120 as part of a communication network. Wireless network 120 may be a public land mobile network (PLMN) including 5G / NR and 4G / LTE domains. UE 110 may initially communicate wirelessly with wireless network 120 via base station or network node 125 (e.g., eNB, gNB, or transmit-receive point (TRP)). In network environment 100, UE 110 and wireless network 120 may implement various schemes related to processing incompatible with permitted NSSAI in non-3GPP mobile communications, as described below, according to the embodiments of this disclosure.

[0020] It is worth noting that although the various proposed schemes may be described individually or separately below, in actual implementations, some or all of the proposed schemes may be used in combination or implemented in other ways. Of course, each proposed scheme may also be used individually or separately or implemented in other ways. In addition, as used herein, "lower layer" may refer to layers in the 5GMM protocol stack below the radio resource control (RRC) layer, such as the packet data convergence protocol (PDCP) layer, radio control link (RLC) layer, medium access control (MAC) layer, physical (PHY) layer, etc.

[0021] Under the current 3GPP specification, upon receiving 5GMM reason #81 (Selected N3IWF is not compatible with the allowed NSSAI), UE 110 will abort the initial registration procedure, set the 5th Generation System (5GS) update status to 5U2 NOTUPDATED, and enter the state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION or 5GMM-DEREGISTERED.PLMN-SEARCH. Furthermore, UE 110 will reset the registration attempt counter. If the REGISTRATIONREJECT message includes the N3IWF identifier IE and UE 110 supports slice-based N3IWF selection, UE 110 can use the provided N3IWF identifier IE in the N3IWF selection as specified in 3GPP Technical Specification (TS) 24.502 before immediately making subsequent initial registration attempts to the network; otherwise, UE 110 will ignore the N3IWF identifier IE. Furthermore, upon receiving 5GMM reason #82 (Selected TNGF is not compatible with the allowed NSSAI), UE 110 will abort the initial registration procedure, set the 5GS update status to 5U2 NOT UPDATED, and enter the state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION or 5GMM-DEREGISTERED.PLMN-SEARCH. Additionally, UE 110 will reset the registration attempt counter. If the REGISTRATION REJECT message includes TNAN information IE and UE110 supports slice-based TNGF selection, then UE110 can use the provided TNAN information IE in the TNAN selection as specified in 3GPP TS 24.502 before immediately making subsequent registration attempts to the network; otherwise, UE110 will ignore the TNAN information IE.

[0022] According to the scheme proposed in this disclosure, when UE 110 receives 5GMM reason #81 under a first condition or 5GMM reason #82 under a second condition, UE 110 may perform one or more of a plurality of operations accordingly.

[0023] For example, UE 110 may receive 5GMM reason #81 under any of the following possible first conditions: (a) UE 110 is not using N3IWF; (b) the 5GMM reason #81 is received via 3GPP access; (c) the 5GMM reason #81 is received via wired access; (d) UE 110 does not indicate its support for slice-based N3IWF selection in the REGISTRATION REQUEST message sent by UE 110 to network 120; or (e) the 5GMM reason #81 is received from SNPN. Similarly, UE110 may receive 5GMM reason #82 under any of the following possible second conditions: (a) UE110 does not use TNGF; (b) the 5GMM reason #82 is received via 3GPP access; (c) the 5GMM reason #82 is received via wired access; (d) UE110 does not indicate its support for slice-based TNGF selection in the REGISTRATION REQUEST message sent by UE110 to network 120; or (e) the 5GMM reason #82 is received from SNPN.

[0024] Furthermore, the operations that UE 110 may perform in response to receiving the 5GMM cause #81 under the first condition or the 5GMM cause #82 under the second condition may include one or more of the following operations.

[0025] For example, UE 110 can stop timer T3510 (if it is running). Alternatively, if the registration request is neither an initial registration request for emergency services nor an initial registration request for a Protocol Data Unit (PDU) session for which the request type is set to "existing emergency PDU session", UE 1110 can set the registration attempt counter to 5. Alternatively, UE 1110 can increment the registration attempt counter. Alternatively, UE 1110 can start timer T3511. Alternatively, if the registration attempt counter is less than 5, UE 1110 can change its state to 5GMM-(DE-REGISTTERED or REGISTERED.ATTEMPTING-REGISTRATION). Alternatively, if the registration attempt counter is equal to 5, UE 1110 can delete the tracking area identifier (TAI) list and the last accessed registration TAI, start timer T3502, change the 5GS update state to 5U2NOT UPDATED, delete the 5th Generation Globally Unique Temporary UE Identity (5G-GUTI), ngKSI, and equivalent PLMN list (if any) or equivalent SNPN list (if any), and, based on the registration or deregistration state, change the UE's status to 5GMM-(DE-REGISTTERED or REGISTERED.ATTEMPTING-REGISTRATION). The state of UE 110 changes to 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION and / or 5GMM-DEREGISTERED.PLMN-SEARCH and / or 5GMM-REGISTERED.PLMN-SEARCH and / or 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE. Alternatively, UE 1110 may perform PLMN selection, SNPN selection, or SNPN selection for network access services. Alternatively, if the value of timer T3502 indicated by network 120 is zero, UE 1110 may perform one or more actions defined for the expiration of timer T3502.Alternatively, if the procedure is performed via 3GPP access and UE 110 is operating in single-registration mode, UE 1110 may, as specified in 3GPP TS 24.301, handle the EPS Mobility Management (EMM) parameters EPS update status, EMM status, 4th Generation GUTI (4G-GUTI), TAI list, last accessed registered TAI, equivalent PLMN list, and eKSI in the exceptional case where the Evolved Packet System (EPS) attach procedure fails and the attach attempt counter equals 5. Alternatively, UE 1110 may attempt to select Evolved Universal Terrestrial Radio Access Network (E-UTRAN) radio access technology and continue with the appropriate EMM-specific procedures. Furthermore, UE 110 may disable its N1 mode capabilities.

[0026] In light of the foregoing, as an example implementation, if the registration attempt counter is less than 5, and the initial registration request is not for emergency services, timer T3511 can be started, and the state of UE 110 can be changed to 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION. When timer T3511 expires, the registration process for the initial registration can be restarted if still necessary. Alternatively, if the registration attempt counter is equal to 5, UE 110 can delete the TAI list and the last accessed registration TAI. If the value of the timer indicated by network 120 is not zero, timer T3502 is started, and the 5GS update state can be set to 5U2 NOT UPDATED. If UE 110 is not currently registering or has not already registered to the same PLMN via both 3GPP access and non-3GPP access, UE 110 can additionally delete the 5G-GUTI, ngKSI, and equivalent PLMN list (if any) or equivalent SNPN list (if any). The state of UE110 can be changed to 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION, or optionally to 5GMM-DEREGISTERED.PLMN-SEARCH, in order to perform PLMN selection, SNPN selection, or SNPN selection for network access service according to 3GPP TS 23.122. When the value of T3502 indicated by network 120 is zero, UE 110 can perform the action defined for the expiration of that timer T3502. When the procedure is performed via 3GPP access and UE 110 is operating in single registration mode: (a) UE 110 may, as specified in 3GPP TS 24.301, handle the EMM parameters EPS update status, EMM status, 4G-GUTI, TAI list, last accessed registered TAI, equivalent PLMN list, and eKSI in case of an exception when the EPS attach procedure fails and the attach attempt counter equals 5; and (b) UE 110 may attempt to select the E-UTRAN radio access technology and continue with the appropriate EMM-specific procedures. Furthermore, UE 110 may disable this N1 mode capability.

[0027] Example Implementation

[0028] Figure 2An example communication system 200 according to one embodiment of the present disclosure is shown, which has at least example device 210 and example device 220. Each of device 210 and device 220 can perform various functions to implement the schemes, techniques, procedures and methods described herein related to the processing of N3IWF or TNGF selected in non-3GPP mobile communications that is incompatible with permitted NSSAI, including various schemes described with respect to the various designs, concepts, schemes, systems and methods proposed above, including network environment 100, and procedures described below.

[0029] Each of devices 210 and 220 can be part of an electronic device, which can be a network device or UE (e.g., UE 110), such as a portable or mobile device, wearable device, in-vehicle device or vehicle, wireless communication device, or computing device. For example, each of devices 210 and 220 can be implemented in a smartphone, smartwatch, personal digital assistant, electronic control unit (ECU) in a vehicle, digital camera, or computing device such as a tablet, laptop, or notebook computer. Each of devices 210 and 220 can also be part of a machine-type device, which can be an IoT device, such as a non-mobile or fixed device, home appliance, roadside unit (RSU), wired communication device, or computing device. For example, each of devices 210 and 220 can be implemented in a smart thermostat, smart refrigerator, smart door lock, wireless speaker, or home control center. When implemented in or as a network device, device 210 and / or device 220 can be implemented in an eNodeB in an LTE, LTE-Advanced, or LTE-Advanced Pro network, or in a gNB or TRP in a 5G, NR, or IoT network.

[0030] In some embodiments, each of devices 210 and 220 can be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more complex instruction-set computing (CISC) processors, or one or more reduced instruction-set computing (RISC) processors. In all the above embodiments, each of devices 210 and 220 can be implemented in or as a network device or UE. Each of devices 210 and 220 can respectively include at least some... Figure 2 The components shown include, for example, processors 212 and 222. Each of devices 210 and 220 may also include one or more other components (e.g., internal power supply, display device, and / or user interface device) unrelated to the scheme presented in this disclosure; therefore, for simplicity, such components of devices 210 and 220 are not described in detail. Figure 2 It is shown in the text and is not described in the following text.

[0031] In one aspect, each of processors 212 and 222 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC or RISC processors. That is, although the singular term "a processor" is used herein to refer to processors 212 and 222, each of processors 212 and 222 may include multiple processors in some embodiments and a single processor in other embodiments, according to this disclosure. In another aspect, each of processors 212 and 222 may be implemented as hardware (and optionally firmware) having electronic components, including, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more transformers, which are configured and arranged to achieve a particular purpose according to this disclosure. In other words, in at least some embodiments, each of processors 212 and 222 is a dedicated machine that is specifically designed, arranged, and configured to perform specific tasks, including tasks related to processing in non-3GPP mobile communications that are incompatible with the N3IWF or TNGF selected in non-3GPP mobile communications, according to various embodiments of this disclosure.

[0032] In some embodiments, device 210 may further include a transceiver 216 coupled to processor 212. Transceiver 216 may be capable of wirelessly transmitting and receiving data. In some embodiments, transceiver 216 may be capable of wireless communication with different types of wireless networks using different radio access technologies (RATs). In some embodiments, transceiver 216 may be equipped with multiple antenna ports (not shown), such as four antenna ports. That is, transceiver 216 may be equipped with multiple transmit antennas and multiple receive antennas for multiple-input multiple-output (MIMO) wireless communication. In some embodiments, device 220 may further include a transceiver 226 coupled to processor 222. Transceiver 226 may include a transceiver capable of wirelessly transmitting and receiving data. In some embodiments, transceiver 226 may be capable of wireless communication with different types of UE / wireless networks using different RATs. In some embodiments, transceiver 226 may be equipped with multiple antenna ports (not shown), such as four antenna ports. That is, transceiver 226 can be equipped with multiple transmit antennas and multiple receive antennas for MIMO wireless communication.

[0033] In some embodiments, device 210 may further include a memory 214 coupled to processor 212, accessible by processor 212, and storing data therein. In some embodiments, device 220 may further include a memory 224 coupled to processor 222, accessible by processor 222, and storing data therein. Each of memory 214 and memory 224 may include a random-access memory (RAM), such as dynamic random-access memory (DRAM), static random-access memory (SRAM), thyristor RAM (T-RAM), and / or zero-capacitor RAM (Z-RAM). Alternatively, each of memories 214 and 224 may include a read-only memory (ROM), such as a mask ROM, a programmable ROM (PROM), an erasable programmable ROM (EPROM), and / or an electrically erasable programmable ROM (EEPROM). Alternatively, each of memories 214 and 224 may include a non-volatile random-access memory (NVRAM), such as flash memory, solid-state memory, ferroelectric RAM (FeRAM), magnetoresistive RAM (MRAM), and / or phase-change memory.

[0034] Each of devices 210 and 220 can be a communication entity capable of communicating with each other using various proposed schemes according to this disclosure. For illustrative purposes and without limitation, the following description provides the capabilities of device 210 as a UE (e.g., UE 110) and device 220 as a network node (e.g., network node 125) of a network (e.g., a wireless network 120 as a 5G / NR mobile network) in the context of example program 300.

[0035] Example Program

[0036] Figure 3 An example program 300 according to one embodiment of the present disclosure is shown. Program 300 may represent one aspect of implementing the various proposed designs, concepts, schemes, systems, and methods described above. More specifically, program 300 may represent one aspect of proposed concepts and schemes related to processing incompatible with permitted NSSAI in non-3GPP mobile communications using the selected N3IWF or TNGF. Program 300 may include one or more operations, actions, or functions as shown in one or more of program blocks 310, 320, and 330. Although shown as discrete program blocks, the individual program blocks of program 300 may be divided into additional program blocks, combined into fewer program blocks, or removed according to the desired implementation. Furthermore, the program blocks / subprogram blocks of program 300 may be arranged in... Figure 3 The execution may be performed in the order shown, or alternatively, in a different order. Furthermore, one or more program blocks / subroutines of program 300 may be executed repeatedly or iteratively. Program 300 may be implemented by devices 210 and 220, and any variations thereof. For illustrative purposes only and without limitation, program 300 is described below in the context of device 210 as a UE (e.g., UE 110) and device 220 as a communication entity such as a network node or base station (e.g., network node 125) of a network (e.g., wireless network 120). Program 300 may begin with program block 310.

[0037] In block 310, procedure 300 may involve the processor 212 of device 210, acting as a UE, sending a request message to a network (e.g., via network 120, acting as network node 220) through transceiver 216. This request may include, for example, a REGISTRATION REQUEST message. Procedure 300 may continue from block 310 to block 320.

[0038] In block 320, program 300 may involve processor 212 receiving, via transceiver 216, a rejection message from the network indicating that the selected N3IWF or TNGF is incompatible with an allowed NSSAI. For example, the rejection message may include, for instance, a REGISTRATION REJECT message. Program 300 may continue from block 320 to block 330.

[0039] In program block 330, program 300 may involve processor 212 performing an operation in response to receiving the rejection message via transceiver 216.

[0040] In some implementations, upon receiving the rejection message, procedure 300 may involve processor 212 receiving a REGISTRATION REJECT message with a 5GMM reason #81 indicating that the selected N3IWF is incompatible with the allowed NSSAI. Furthermore, upon receiving the rejection message, procedure 300 may also involve processor 212 receiving the 5GMM reason #81 if: (a) the UE is not using the N3IWF; or (b) the rejection message is received via 3GPP access; or (c) the rejection message is received via wired access; or (d) the UE did not indicate its support for slice-based N3IWF selection in a REGISTRATION REQUEST message sent by the UE to the network; or (e) the rejection message is received from SNPN.

[0041] In some implementations, upon receiving the rejection message, procedure 300 may involve processor 212 receiving a REGISTRATION REJECT message with 5GMM reason #82, which indicates that the selected TNGF is incompatible with the allowed NSSAI. Furthermore, upon receiving the rejection message, procedure 300 may also involve processor 212 receiving the 5GMM reason #82 if: (a) the UE is not using the N3IWF; or (b) the rejection message is received via 3GPP access; or (c) the rejection message is received via wired access; or (d) the UE did not indicate its support for slice-based TNGF selection in a REGISTRATION REQUEST message sent by the UE to the network; or (e) the rejection message is received from SNPN.

[0042] In some implementations, when performing this operation, program 300 may involve processor 212 starting timer T3510 while timer T3510 is running.

[0043] In some implementations, when performing this operation, program 300 may involve processor 212 setting the registration attempt counter to 5 in response to a registration request that is neither an initial registration request for an emergency service nor an initial registration request for a PDU session for which the request type is set to "existing emergency PDU session".

[0044] In some implementations, when performing this operation, program 300 may involve processor 212 incrementing the registration attempt counter.

[0045] In some implementations, when performing this operation, program 300 may involve processor 212 starting timer T3511 or changing the state to 5GMM-DE-REGISTERED or 5GMM-REGISTERED.ATTEMPTING-REGISTRATION in response to the registration attempt counter being less than 5.

[0046] In some implementations, when performing this operation, program 300 may involve processor 212 performing one or more of the following operations in response to the registration attempt counter being equal to 5: (1) deleting the TAI list and the last accessed registered TAI; (2) starting timer T3502; (3) setting the 5GS update status to 5U2 NOT. UPDATED; (4) Delete the 5G-GUTI, ngKSI and equivalent PLMN list, or equivalent SNPN list; (5) Set the UE's status to 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION or 5GMM-DEREGISTERED.PLMN-SEARCH or 5GMM-REGISTERED.PLMN-SEARCH or 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE, depending on the registration or deregistration status; (6) Perform PLMN selection, SNPN selection or SNPN selection for network access service; (7) In response to the timer T3502 indicated by the network having a value of zero, perform one or more actions defined for the expiration of the timer T3502; (8) In response to the registration procedure being performed via 3GPP access and the UE operating in single registration mode, such as 3GPP TS As specified in 24.301, when the EPS attachment procedure fails and the attachment attempt counter is equal to 5, process the EMM parameters EPS update status, EMM status, 4G-GUTI, TAI list, last accessed registered TAI, equivalent PLMN list and eKSI; (9) attempt to select E-UTRAN radio access technology and continue the EMM-specific procedure; and (10) disable the N1 mode capability of the UE.

[0047] Additional Notes

[0048] The topics described herein sometimes illustrate different components contained within or connected to different other components. It should be understood that such illustrated architectures are merely examples, and many other architectures can actually be implemented to achieve the same functionality. Conceptually, any arrangement of components to achieve the same functionality is effectively “associated” to achieve the desired function. Therefore, any two components combined in this document to achieve a specific function can be considered “associated” with each other to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two components so associated can also be considered “operably connected” or “operably coupled” to each other to achieve the desired function, and any two components that can be so associated can also be considered “operably coupled” to each other to achieve the desired function. Specific examples of being operablely coupled include, but are not limited to, physically matable and / or physically interactive components and / or wirelessly interactive and / or logically interactive and / or logically interactive components.

[0049] Furthermore, regarding the use of virtually any plural and / or singular terms in this document, those skilled in the art can appropriately convert from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be explicitly described herein.

[0050] Furthermore, those skilled in the art will understand that, generally, the terms used herein, particularly those used in the appended claims (e.g., the body of the appended claims), are intended to be “open-ended” terms; for example, the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” and the term “including” should be interpreted as “including but not limited to,” etc. Those skilled in the art will also further understand that if there is an intent to express a specific quantity recited in the introduced claim, such intent will be explicitly stated in the claim, and if no such statement is made, such intent will not exist. For example, as an aid to understanding, the appended claims may contain the use of the introductory phrases “at least one” and “one or more” to introduce the recitation of the claim. However, the use of such phrases should not be construed as implying that introducing a claim with the indefinite article "a" would limit any particular claim containing such an introduced claim to an embodiment containing only one such claim, even when the same claim includes the introductory phrase "one or more" or "at least one" and an indefinite article such as "a," for example, "a" should be interpreted as meaning "at least one" or "one or more"; the same applies to the use of definite articles used to introduce a claim. Furthermore, even when a specific number of introduced claims is explicitly stated, those skilled in the art will recognize that such a statement should be interpreted as meaning at least the number stated, for example, simply stating "two" without any other modifiers means at least two, or two or more, claims. Moreover, in cases where conventional expressions such as "at least one of A, B, and C" are used, such structures are generally intended to have the meaning of the conventional expression understood by those skilled in the art; for example, "a system having at least one of A, B, and C" would include, but is not limited to, systems having a single A, a single B, a single C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. In cases where conventional expressions such as "at least one of A, B, or C" are used, such structures are generally intended to have a meaning that is understood by a person skilled in the art. For example, "a system having at least one of A, B, or C" will include, but is not limited to, systems having a single A, a single B, a single C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc. Those skilled in the art will further understand that virtually any extractive word and / or phrase presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to include the possibility of including one of these terms, any one of these terms, or both of these terms. For example, the phrase "A or B" will be understood to include the possibility of including "A" or "B" or "A and B".

[0051] As will be understood from the foregoing, various embodiments of this disclosure have been described herein for illustrative purposes, and various modifications may be made without departing from the scope and spirit of this disclosure. Therefore, the various embodiments disclosed herein are not intended to be limiting, and the true scope and spirit are indicated by the following claims.

Claims

1. A method comprising: The processor of the user equipment receives a rejection message from the network, which indicates that the selected non-3rd generation partner program interoperability function or trusted non-3rd generation partner program gateway function is incompatible with the permitted network slice selection auxiliary information. as well as The processor performs the operation in response to receiving the rejection message.

2. The method of claim 1, wherein receiving the rejection message includes receiving a registration rejection message with a fifth-generation mobility management reason #81, the fifth-generation mobility management reason #81 indicating that the selected non-third-generation partner program interoperability is incompatible with the permitted network slice selection assistance information.

3. The method of claim 2, wherein receiving the rejection message further includes receiving the fifth-generation mobility management reason #81 in the following circumstances: The user equipment is not using the non-3rd generation partner program interoperability function; or Received the rejection message through the third-generation partner program; or The rejection message was received via wired access; or The user equipment did not indicate support for slice-based non-3rd generation partner program interoperability selection in the registration request message sent by the user equipment to the network; or The rejection message was received from an independent, non-public network.

4. The method of claim 1, wherein receiving the rejection message includes receiving a registration rejection message with a fifth-generation mobility management reason #82, the fifth-generation mobility management reason #82 indicating that the selected trusted non-third-generation partner program gateway function is incompatible with the permitted network slice selection assistance information.

5. The method of claim 4, wherein receiving the rejection message further includes receiving the fifth-generation mobility management reason #82 in the following circumstances: The user equipment is not using the Trusted Non-Generation 3 Partner Program gateway function; or Received the rejection message through the third-generation partner program; or The rejection message was received via wired access; or The user equipment did not indicate support for slice-based trusted non-3rd generation partner program gateway functionality selection in the registration request message sent by the user equipment to the network; or The rejection message was received from an independent, non-public network.

6. The method of claim 1, wherein the operation comprises starting timer T3510 while timer T3510 is running.

7. The method of claim 1, wherein the execution of the operation includes setting the registration attempt counter to 5 in response to a registration request that is neither an initial registration request for an emergency service nor an initial registration request for initiating a Protocol Data Unit session for one or more emergency services and whose request type is set to "existing emergency Protocol Data Unit session".

8. The method of claim 1, wherein the execution of the operation includes incrementing the registration attempt counter.

9. The method of claim 1, wherein the execution of the operation includes, in response to a registration attempt counter being less than 5, starting timer T3511 or changing the state to 5GMM-DE-REGISTERED or 5GMM-REGISTERED.ATTEMPTING-REGISTRATION.

10. The method of claim 1, wherein performing the operation includes, in response to the registration attempt counter being equal to 5, performing one or more of the following: Remove the tracking area identifier list and the last accessed registered tracking area identifier; Start timer T3502; Set the fifth-generation system update status to 5U2 NOT UPDATED; Remove the fifth-generation globally unique temporary user equipment identifier, ngKSI, and the equivalent list of public terrestrial mobile networks or the equivalent list of independent non-public networks; Based on whether the user equipment is registered or unregistered, set the status of the user equipment to 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION or 5GMM-DEREGISTERED.PLMN-SEARCH or 5GMM-REGISTERED.PLMN-SEARCH or 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE. Perform the selection of a public land mobile network, an independent non-public network, or an independent non-public network for network access services; In response to the network indicating that the value of timer T3502 is zero, perform one or more actions defined for the expiration of timer T3502; In response to the registration process being performed via 3GPP access and the user equipment operating in single registration mode, if the ESB attach procedure fails and the attach attempt counter equals 5, the ESB mobility management parameters, including ESB update status, ESB mobility management status, 4G globally unique temporary user equipment identifier, tracking area identifier list, last visited registered tracking area identifier, equivalent public land mobile network list, and eKSI, shall be processed in accordance with the method specified in 3GPP Technical Specification 24.

301. Try selecting the radio access technology for the Evolved Universal Terrestrial Radio Access Network and continue with the Evolved Packet System Mobility Management specific procedures; and Disable the N1 mode capability of this user device.

11. An apparatus that can be implemented in a user equipment, comprising: A transceiver configured for wireless communication; as well as A processor, coupled to the transceiver and configured to perform operations including: The transceiver receives a rejection message from the network indicating that the selected non-3G Partner Program (NDP) interoperability function or trusted NDP gateway function is incompatible with permitted network slice selection assistance information; and The transceiver performs the operation in response to receiving the rejection message.

12. The apparatus of claim 11, wherein receiving the rejection message includes receiving a registration rejection message with a fifth-generation mobility management reason #81, the fifth-generation mobility management reason #81 indicating that the selected non-third-generation partner program interoperability is incompatible with the permitted network slice selection assistance information.

13. The apparatus of claim 12, wherein receiving the rejection message further includes receiving the fifth-generation mobility management reason #81 in the following circumstances: The user equipment is not using the non-3rd generation partner program interoperability function; or Received the rejection message through the third-generation partner program; or The rejection message was received via wired access; or The user equipment did not indicate support for slice-based non-3rd generation partner program interoperability selection in the registration request message sent by the user equipment to the network; or The rejection message was received from an independent, non-public network.

14. The apparatus of claim 11, wherein receiving the rejection message includes receiving a registration rejection message with a fifth-generation mobility management reason #82, the fifth-generation mobility management reason #82 indicating that the selected trusted non-third-generation partner program gateway function is incompatible with the permitted network slice selection assistance information.

15. The apparatus of claim 14, wherein receiving the rejection message further includes receiving the fifth-generation mobility management reason #82 in the following cases: The user equipment is not using the Trusted Non-Generation 3 Partner Program gateway function; or Received the rejection message through the third-generation partner program; or The rejection message was received via wired access; or The user equipment did not indicate support for slice-based trusted non-3rd generation partner program gateway functionality selection in the registration request message sent by the user equipment to the network; or The rejection message was received from an independent, non-public network.

16. The apparatus of claim 11, wherein the operation comprises starting timer T3510 while timer T3510 is running.

17. The apparatus of claim 11, wherein the execution of the operation includes setting the registration attempt counter to 5 in response to a registration request that is neither an initial registration request for an emergency service nor an initial registration request for initiating a Protocol Data Unit session for one or more emergency services and whose request type is set to "existing emergency Protocol Data Unit session".

18. The apparatus of claim 11, wherein the execution of the operation includes incrementing the registration attempt counter.

19. The apparatus of claim 11, wherein the execution of the operation includes, in response to a registration attempt counter being less than 5, starting timer T3511 or changing the state to 5GMM-DE-REGISTERED or 5GMM-REGISTERED.ATTEMPTING-REGISTRATION.

20. The apparatus of claim 11, wherein the execution of the operation includes, in response to the registration attempt counter being equal to 5, performing one or more of the following: Remove the tracking area identifier list and the last accessed registered tracking area identifier; Start timer T3502; Set the fifth-generation system update status to 5U2 NOT UPDATED; Remove the fifth-generation globally unique temporary user equipment identifier, ngKSI, and the equivalent list of public terrestrial mobile networks or the equivalent list of independent non-public networks; Based on whether the user equipment is registered or unregistered, set the status of the user equipment to 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION or 5GMM-DEREGISTERED.PLMN-SEARCH or 5GMM-REGISTERED.PLMN-SEARCH or 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE. Perform the selection of a public land mobile network, an independent non-public network, or an independent non-public network for network access services; In response to the network indicating that the value of timer T3502 is zero, perform one or more actions defined for the expiration of timer T3502; In response to the registration process being performed via 3GPP access and the user equipment operating in single registration mode, if the ESB attach procedure fails and the attach attempt counter equals 5, the ESB mobility management parameters, including ESB update status, ESB mobility management status, 4G globally unique temporary user equipment identifier, tracking area identifier list, last visited registered tracking area identifier, equivalent public land mobile network list, and eKSI, shall be processed in accordance with the method specified in 3GPP Technical Specification 24.

301. Try selecting the radio access technology for the Evolved Universal Terrestrial Radio Access Network and continue with the Evolved Packet System Mobility Management specific procedures; and Disable the N1 mode capability of this user device.

Images