Method and apparatus for managing handover between access modes of operation of user equipment

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a terminal in a wireless communication system is provided. When operating in an SNPN access mode of operation, information about an independent non-public network (SNPN) may be stored in at least one list of one or more prohibited SNPNs. The SNPN access mode of operation may be deactivated. At least one list of one or more prohibited SNPNs may be maintained.

Description

Technical Field

[0001] The present disclosure relates generally to telecommunication networks and, more particularly, to a method and user equipment (UE) for managing switching between access operation modes of a UE. Background Art

[0002] Fifth-generation (5G) mobile communication technology defines a wide frequency band, making high transmission rates and new services possible, and can be implemented not only in "sub-6 GHz" frequency bands such as 3.5 gigahertz (GHz), but also in "above 6 GHz" frequency bands, including 28 GHz and 39 GHz, known as millimeter waves. Furthermore, sixth-generation (6G) mobile communication technology (referred to as a "beyond 5G system") can be implemented in terahertz (THz) frequency bands (e.g., 95 GHz to 3 THz bands) to achieve transmission rates fifty times faster than 5G mobile communication technology and ultra-low latency one-tenth that of 5G mobile communication technology.

[0003] At the start of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC) and massive machine-type communications (mMTC), there has been ongoing standardization on beamforming and massive multiple-input multiple-output (MIMO) for mitigating radio wave path loss in millimeter waves and increasing radio wave transmission range, dynamic operation of parameter sets (e.g., operating multiple subcarrier spacings) and time slot formats to support efficient utilization of millimeter wave resources, initial access technology to support multi-beam transmission and broadband, definition and operation of bandwidth parts (BWPs), new channel coding methods such as low-density parity-check (LDPC) codes for large-scale data transmission and polar codes for highly reliable transmission of control information, L2 preprocessing, and network slicing to provide dedicated networks tailored for specific services.

[0004] Currently, there are ongoing discussions on improvements and performance enhancements to initial 5G mobile communication technologies in view of the services to be supported by 5G mobile communication technologies, and there has been standardization of physical layers on technologies such as Vehicle-to-Everything (V2X) for assisting driving decisions of autonomous vehicles based on information on the position and status of vehicles transmitted by the vehicles and for enhancing user convenience, Unlicensed New Radio (NR-U) for system operation designed to comply with various regulatory requirements within unlicensed frequency bands, NR UE energy saving, Non-Terrestrial Network (NTN) as UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is not possible, and positioning.

[0005] In addition, in the air interface architecture / protocol area, standardization is already underway on technologies such as the Industrial Internet of Things (IIoT), which supports new services through interconnection and integration with other industries; Integrated Access and Backhaul (IAB), which provides nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner; mobility enhancements including conditional handover and dual-active protocol stack (DAPS) handover; and two-step random access (two-step random access channel (RACH) for NR) to simplify the random access process. In terms of system architecture / services, standardization is also underway on a 5G baseline architecture (e.g., a service-based architecture or service-based interface) for incorporating network function virtualization (NFV) and software-defined networking (SDN) technologies; and mobile edge computing (MEC) for receiving services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, the already exponentially growing number of connected devices will be connected to communication networks, and it is expected that enhanced functionality and performance of 5G mobile communication systems and the integrated operation of connected devices will become necessary. To this end, new research is being planned on extended reality (XR) for effectively supporting augmented reality (AR), virtual reality (VR), mixed reality (MR), etc., 5G performance improvements and complexity reduction through the use of artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communications.

[0007] Furthermore, such development of 5G mobile communication systems will serve as the foundation for the development of not only new waveforms for providing terahertz band coverage for 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas, metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS), but also full-duplex technologies for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technologies for leveraging satellites and AI to achieve system optimization and internalize end-to-end AI support functions from the design stage, and next-generation distributed computing technologies for implementing services at a complexity level that exceeds the operational capabilities of UEs by utilizing ultra-high-performance communication and computing resources. Summary of the Invention

[0008] Technical issues

[0009] Currently, there is a need to enhance switching between access operation modes of terminals in wireless communication systems.

[0010] Solution to the problem

[0011] In an embodiment, a method performed by a terminal in a wireless communication system is provided. When operating in an SNPN access mode of operation, information about a standalone non-public network (SNPN) may be stored in at least one list of one or more prohibited SNPNs. The SNPN access mode of operation may be deactivated. At least one list of one or more prohibited SNPNs may be maintained.

[0012] In an embodiment, a method performed by a terminal in a wireless communication system is provided. Information about a public land mobile network (PLMN) may be stored in at least one list of one or more prohibited PLMNs. An SNPN access mode of operation may be activated. At least one list of one or more prohibited PLMNs may be maintained.

[0013] In an embodiment, a terminal in a wireless communication system is provided. The terminal includes a transceiver and a controller coupled to the transceiver. The controller can be configured to store information about a SNPN in at least one list of one or more prohibited SNPNs, deactivate an SNPN access operating mode, and maintain at least one list of one or more prohibited SNPNs.

[0014] In an embodiment, a terminal in a wireless communication system is provided. The terminal includes a transceiver and a controller coupled to the transceiver. The controller can be configured to store information about a PLMN in at least one list of one or more prohibited PLMNs, activate an SNPN access mode of operation, and maintain at least one list of the one or more prohibited PLMNs.

[0015] In an embodiment, the present disclosure discloses a method for managing switching between access operation modes of a user equipment (UE). The method includes detecting a switch from an SNPN access operation mode to a not in SNPN access operation mode. In addition, the method includes maintaining a plurality of prohibited lists of SNPN access operation modes in the UE, and executing a timer started during the SNPN access operation mode. Thereafter, the method includes managing the switch between the SNPN access operation mode and the not in SNPN access operation mode by removing the plurality of prohibited lists of the SNPN access operation mode when the timer in one of the SNPN access operation mode and the not in SNPN access operation mode expires.

[0016] In an embodiment, the present disclosure discloses a method for managing switching between access operation modes of a user equipment (UE). The method includes detecting a switch from not in SNPN access operation mode to SNPN access operation mode. In addition, the method includes maintaining a plurality of prohibited lists of not in SNPN access operation mode in the UE, and executing a timer started during not in SNPN access operation mode. Thereafter, the method includes managing switching between SNPN access operation mode and not in SNPN access operation mode by removing the plurality of prohibited lists of not in SNPN access operation mode when the timer in one of the SNPN access operation mode and not in SNPN access operation mode expires.

[0017] In an embodiment, the present disclosure discloses a user equipment (UE) for managing switching between access operation modes. The UE includes a processor and a memory. The processor is configured to detect switching from not in SNPN access operation mode to SNPN access operation mode. In addition, the processor is configured to maintain multiple prohibited lists of not in SNPN access operation mode in the UE, and the execution of timers started during not in SNPN access operation mode. Thereafter, the processor is configured to manage switching between SNPN access operation mode and not in SNPN access operation mode by removing multiple prohibited lists of not in SNPN access operation mode when the timers in one of the SNPN access operation mode and not in SNPN access operation mode expire.

[0018] In an embodiment, the present disclosure discloses a user equipment (UE) for managing switching between access operation modes. The UE includes a processor and a memory. The processor is configured to detect switching from not in SNPN access operation mode to SNPN access operation mode. In addition, the processor is configured to maintain multiple prohibited lists of not in SNPN access operation mode in the UE, and the execution of a timer started during not in SNPN access operation mode. Thereafter, the processor is configured to manage switching between SNPN access operation mode and not in SNPN access operation mode by removing multiple prohibited lists of not in SNPN access operation mode when the timer in one of the SNPN access operation mode and not in SNPN access operation mode expires.

[0019] The foregoing summary is illustrative only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent through the following description in conjunction with the accompanying drawings, in which:

[0021] Figure 1 is a diagram illustrating management of switching between access operation modes of a user equipment (UE) according to an embodiment;

[0022] Figure 2 is a diagram illustrating a UE for managing switching between access operation modes according to an embodiment;

[0023] Figure 3A is a flow chart illustrating a method for managing a switch from an SNPN access mode of operation to one not in SNPN access mode of operation according to an embodiment;

[0024] Figure 3B is a flow chart illustrating a method for managing a switch from not in SNPN access mode of operation to SNPN access mode of operation according to an embodiment;

[0025] Figure 4 is a flow chart illustrating a method for managing a switch from an SNPN access mode of operation to one not in SNPN access mode of operation according to an embodiment;

[0026] Figure 5 is a flow chart illustrating a method for managing a switch from not in SNPN access mode of operation to SNPN access mode of operation according to an embodiment;

[0027] Figure 6 is a diagram illustrating a general computing system for managing switching between access operating modes of a UE according to an embodiment;

[0028] Figure 7 is a diagram showing the structure of a UE or terminal according to an embodiment;

[0029] Figure 8 is a diagram showing a structure of a base station (BS) according to an embodiment; and

[0030] Figure 9 is a diagram showing a structure of a network entity according to an embodiment.

[0031] It should be understood by those skilled in the art that any block diagrams herein represent conceptual views of illustrative systems embodying the principles of the present subject matter. Similarly, it should be understood that any flow charts, flowcharts, state transition diagrams, pseudo-code, etc. represent various processes that can be substantially represented in a computer-readable medium and executed by a computer or processor, whether or not such a computer or processor is explicitly shown. DETAILED DESCRIPTION

[0032] In this document, the term "exemplary" is used herein to mean serving as an example, instance, or illustration. Any embodiment or implementation described herein as exemplary is not necessarily to be construed as preferred or advantageous over other embodiments.

[0033] While the present disclosure may take various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the accompanying drawings and will be described in detail below. However, it should be understood that there is no intention to limit the present disclosure to the particular forms disclosed, but on the contrary, the present disclosure is intended to cover all modifications, equivalents, and alternatives falling within the scope of the present disclosure.

[0034] The terms "comprise," "comprising," or any other variations thereof are intended to cover a non-exclusive inclusion, such that an arrangement, apparatus, or method that comprises a list of components or steps includes not only those components or steps, but may also include other components or steps not expressly listed or inherent to such arrangement, apparatus, or method. In other words, one or more elements in a system or apparatus followed by "comprising..." does not, without more constraints, exclude the presence of other or additional elements in the system or apparatus.

[0035] A private network, or non-public network (NPN), is intended for non-public or private use. These networks are implemented, for example, in hospitals, industrial facilities, enterprises, and stadiums. Third Generation Partnership Project (3GPP) specifications support various NPN configurations. While there are many possible NPN configurations, 3GPP defines two main categories of NPNs: SNPNs and public network integrated NPNs (PNI-NPNs). SNPNs are NPNs operated by an NPN operator and do not rely on the network functionality provided by a public mobile network (PLMN). PNI-NPNs are non-public networks deployed with the support of a public mobile network (PLMN).

[0036] The 3GPP specification defines two access operation modes for UE. The UE can operate in SNPN access operation mode or outside of SNPN access operation mode. A UE capable of operating in SNPN access operation mode resides on the SNPN and receives various services provided by the NPN operator via the SNPN. When the UE is not SNPN enabled, the UE is considered to be not operating in SNPN access operation mode (also known as not in SNPN access operation mode). In such a case, the UE performs PLMN selection and receives services provided by the PLMN operator. When the UE is SNPN enabled, the UE can operate in SNPN access operation mode.

[0037] Currently, 3GPP specifications define UE behavior for both SNPN access and non-SNPN access modes. 3GPP specifications require the UE to maintain a specific access mode for configuring features and receiving services from the network. Specifications exist for managing forbidden lists (both temporary and permanent rejection causes) and associated timers when the UE interacts with the network. For example, TS 24.501 specifies that entries in the subscriber data list manage available SNPNs present in a temporarily forbidden SNPN list or a permanently forbidden SNPN list. 3GPP specifications also specify a forbidden PLMN list or a forbidden PLMN list for General Packet Radio Service (GPRS) services for entries in the PLMN subscription or subscriber data lists. In SNPN access mode, the UE can select only an SNPN, not a PLMN for any service. When the UE receives a registration reject, service reject, or network-initiated deregistration request, an SNPN is added to any forbidden list. If an SNPN is present in any forbidden list, the UE in SNPN access mode cannot select an SNPN for normal service. When an SNPN is added to any forbidden list, the UE is required to start a timer (e.g., T3245). When the timer expires, the forbidden list is cleared.

[0038] When the UE switches from SNPN access mode of operation to not in SNPN access mode of operation, there is no clear procedure in the 3GPP specifications regarding the UE behavior with respect to handling the prohibited list and timers of SNPN access mode of operation. Similarly, when the UE switches from not in SNPN access mode of operation to SNPN access mode of operation, there is no clear procedure in the 3GPP specifications regarding the UE behavior with respect to handling the prohibited list and timers of not in SNPN access mode of operation.

[0039] The information disclosed in this background section of this disclosure is only for enhancement of understanding of the general background of the invention and should not be regarded as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0040] A private network or non-public network is intended for non-public or private use. SNPN refers to an NPN that is operated by an NPN operator and does not rely on network functionality provided by a public land mobile network (PLMN). The UE can operate in or outside of the SNPN access mode of operation. Currently, according to 3GPP specifications, UE behavior is defined for SNPN access mode of operation and for not in SNPN access mode of operation. There are specifications for managing prohibited lists (both temporary and permanent rejection reasons) and related timers. However, when the UE switches between access modes of operation, there are no clear procedures in the 3GPP specifications regarding the UE behavior regarding handling prohibited lists and timers for SNPN access mode of operation.

[0041] The present disclosure provides a method and a UE for managing switching between access operation modes of a UE. The present disclosure provides a solution for maintaining a prohibited list of SNPNs or PLMNs when the UE switches between an SNPN access operation mode and a mode not in the SNPN access operation mode. In addition, the present disclosure provides a solution for maintaining the execution of a timer started during an SNPN access operation mode or a PLMN access operation mode, and the deletion of the corresponding prohibited list when the timer expires, regardless of the access operation mode. Thus, the switching between the access operation modes of the UE is managed. When the UE switches back to the corresponding access operation mode, the present disclosure enables the UE to select an SNPN or PLMN that is present in the prohibited list.

[0042] The present subject matter relates generally to the field of wireless communications, and more particularly to switching of operating access modes by user equipment.

[0043] A Standalone Non-Public Network (SNPN) is operated by an NPN operator and does not rely on network functionality provided by a PLMN or a Public Network Integrated NPN (PNI-NPN), which is a non-public network deployed with the support of a PLMN. Currently, 3GPP specifications define two operating modes for UEs (User Equipment). They can operate in SNPN access mode or not in SNPN access mode (for example, when the UE performs PLMN selection, which is referred to as, but not limited to, PLMN mode). Not in SNPN access mode is referred to as non-SNPN access mode or non-SNPN access mode. A UE capable of operating in SNPN access mode camps on an SNPN and receives various services provided to the UE by the NPN operator via the SNPN. If a UE is not SNPN-enabled, it is always considered to be operating not in SNPN access mode, i.e., in non-SNPN access mode or non-SNPN access mode. If a UE is SNPN-enabled, it can operate in SNPN access mode. The details of activation and deactivation of the SNPN access mode of operation at an SNPN-enabled UE are based on the UE implementation.

[0044] According to the 3GPP specifications, UE behavior is defined for a standalone SNPN access mode of operation and / or a non-SNPN access mode of operation. The 3GPP specifications require that the UE maintain a specific access mode of operation for its functionality and services from the network. However, the UE behavior is unclear with respect to certain events when the UE switches between available access modes of operation. According to 3GPP, there are specifications for managing prohibited lists (both temporary and permanent rejection causes) and their associated timers when the UE interacts with the network. For example, TS24.501 specifies that the available SNPNs present in the list of temporarily prohibited SNPNs or the list of permanently prohibited SNPNs are managed for entries in the list of PLMN subscriptions or subscriber data. When the UE is shut down or restarted, the 3GPP specifications also specify lists and entries for temporarily prohibited SNPNs, or a list of permanently prohibited SNPNs, or a prohibited PLMN list, or a prohibited PLMN list for GPRS services for entries in the list of PLMN subscriptions or subscriber data. However, if the UE decides to perform an access operation mode switch between its two available operation access modes, switching from SNPN access operation mode to non-SNPN access operation mode or vice versa, the above lists applicable to a specific mode or common to both modes will not be managed when the UE switches to the other mode.

[0045] Embodiments disclose processing UE behaviors according to 3GPP technical specifications so that they are reasonable and acceptable relative to 3GPP standards. The UE can manage entries in a list of temporarily banned SNPNs, a list of permanently banned SNPNs, a banned PLMN list, or a banned PLMN list for GPRS services for entries in a list of PLMN subscriptions or subscriber data. Furthermore, UE behaviors are specified with respect to timers associated with these respective lists (e.g., but not limited to, T3245).

[0046] The UE is capable of operating in both SNPN access mode and non-SNPN mode. The UE selects to operate in a specific access mode, performs access mode-specific selection, and maintains a specific prohibited list and timer. The UE and the Access and Mobility Management Function (AMF) perform SNPN / PLMN selection and registration. Due to certain triggers, the UE can switch access modes. When the UE switches access modes, it is unclear whether the prohibited list and timer for the previous access mode are maintained. The UE and the AMF perform PLMN / SNPN selection and registration.

[0047] In one aspect of the present disclosure, clear entries are provided in the corresponding prohibited lists and timers. The UE may be able to operate in the SNPN access operation mode and switch the mode from the SNPN access operation mode to the non-SNPN access operation mode. In this document, for all entries in the list of subscriber data, the UE may delete all entries in the list of temporarily prohibited SNPNs or the list of permanently prohibited SNPNs. If there is any running timer associated with the list of temporarily prohibited SNPNs or the list of permanently prohibited SNPNs, whether specific to the SNPN access operation mode or common to both operation modes (for example, but not limited to T3245, etc.), the timer may be stopped. Any implementation-specific timer associated with the SNPN access operation mode may also be stopped. If there are any non-zero retry counters, whether specific to the SNPN access mode or common to both operation modes, they may be reset to 0.

[0048] The UE supports SNPN access mode of operation and non-SNPN mode of operation. The UE elects to operate in SNPN access mode of operation, performs SNPN selection, and maintains SNPN-specific prohibited lists and timers. The UE and the AMF perform SNPN selection and registration. Due to some triggers, the UE switches from SNPN access mode of operation to non-SNPN access mode of operation. When the UE is out of SNPN access mode of operation, the UE shall clear the prohibited list specific to the SNPN access mode of operation and clear the retry counter, and stop the timer specific to the SNPN or common to both modes, if running (e.g., T3245). The UE and the AMF perform PLMN selection and registration.

[0049] In another embodiment, the UE may be able to operate in the SNPN access operation mode and switch the mode from the non-SNPN access operation mode to the SNPN access operation mode. In this article, for PLMN subscription, the UE can delete all entries in the prohibited PLMN list or the prohibited PLMN for GPRS service list. If there is any running timer associated with the prohibited PLMN list or the list of prohibited PLMNs for GPRS service, whether specific to the non-SNPN access operation mode or common to the two operation modes (such as but not limited to T3245, etc.), the timer can be stopped. Any implementation-specific timer associated with the SNPN access operation mode can also be stopped. If there are any non-zero retry counters, whether specific to the SNPN access operation mode or common to the two operation modes, they can be reset to 0.

[0050] The UE supports SNPN access operation mode and non-SNPN access operation mode. The UE chooses to operate in non-SNPN access operation mode, performs PLMN selection, and maintains PLMN-specific prohibited lists and timers. The UE and the AMF perform PLMN selection and registration. Due to some triggers, the UE switches from non-SNPN access operation mode to SNPN access operation mode. When the UE is now in SNPN access operation mode, the UE may clear the prohibited list specific to the non-SNPN access operation mode, clear all retry counters and stop all timers (if running) specific to the non-SNPN access operation mode or common to both modes (e.g., T3245). The UE and the AMF may perform SNPN selection and registration.

[0051] In another aspect of the present disclosure, entries may be maintained in corresponding prohibited lists and timers. The UE may be able to operate in an SNPN access operating mode and switch the mode from the SNPN access operating mode to a non-SNPN access operating mode. In this document, for all entries in the list of subscriber data, the UE may store and maintain all entries in a list of temporarily prohibited SNPNs or a list of permanently prohibited SNPNs. If there is any running timer associated with a list of temporarily prohibited SNPNs or a list of permanently prohibited SNPNs, whether specific to the SNPN access operating mode or common to both operating modes (e.g., T3245, etc.), the timer may be maintained (i.e., continue to run). Any implementation-specific timer associated with the SNPN access operating mode may also be maintained. If there are any non-zero retry counters, whether specific to the SNPN access operating mode or common to both operating modes, they may be maintained.

[0052] The UE supports SNPN access operation mode and non-SNPN access operation mode. The UE chooses to operate in SNPN access operation mode, performs SNPN selection, and maintains SNPN-specific prohibited lists and timers. The UE and AMF perform SNPN selection and registration. Due to some triggers, the UE switches from SNPN access operation mode to non-SNPN access operation mode. When the UE is outside the SNPN access operation mode, the UE shall maintain a prohibited list specific to the SNPN access operation mode, as well as retry counters and timers specific to SNPN or common to both modes, if running (e.g., T3245). The UE and AMF perform PLMN selection and registration. The maintained and running timers expire. The UE may use the following exemplary logic to reset the retry counters and delete the prohibited list:

[0053] If (Run Timer specific to non-SNPN access mode)

[0054] Remove all entries from the list of "temporarily banned SNPNs" and the list of "permanently banned SNPNs"

[0055] if (runtimer is common to both access modes) {

[0056] Remove all entries from the list of "temporarily banned SNPNs" and the list of "permanently banned SNPNs"

[0057] Delete all entries from the list of "Prohibited PLMN List" or "Prohibited PLMN for GPRS Service"

[0058] In another embodiment, the UE may be able to operate in the SNPN access operation mode and switch the mode from the non-SNPN access operation mode to the SNPN access operation mode. In this article, the UE can store and maintain all entries in the prohibited PLMN list or the prohibited PLMN for the GPRS service list. If there is any running timer related to the prohibited PLMN list or the list of prohibited PLMN for the GPRS service list, whether it is specific to the non-SNPN access operation mode or common to the two operation modes (such as but not limited to T3245, etc.), the timer can be maintained (i.e., continue to run). Any implementation-specific timer related to the SNPN access operation mode can also be maintained. If there is any non-zero retry counter, whether it is specific to the SNPN access operation mode or common to the two operation modes, they can be maintained.

[0059] The UE supports SNPN access operation mode and non-SNPN access operation mode. The UE chooses to operate in non-SNPN access operation mode, performs PLMN selection, and maintains PLMN-specific prohibited lists and timers. The UE and the AMF perform PLMN selection and registration. Due to some triggers, the UE switches from non-SNPN access operation mode to SNPN access operation mode. When the UE is now in SNPN access operation mode, the UE may maintain a prohibited list specific to the non-SNPN access operation mode, as well as retry counters and all timers specific to non-SNPN or common to both modes, if running (e.g., T3245). The UE and the AMF perform SNPN selection and registration. The maintained and running timers expire. The UE may use the following exemplary logic to reset the retry counters and delete the prohibited list:

[0060] if (running timer specific to SNPN access mode)

[0061] Delete all entries from the list of "Prohibited PLMN List" or "Prohibited PLMN for GPRS Service"

[0062] if (runtimer is common to both access modes) {

[0063] Remove all entries from the list of "temporarily banned SNPNs" and the list of "permanently banned SNPNs"

[0064] Delete all entries from the "Prohibited PLMN List" or "Prohibited PLMN for GPRS Services" list}

[0065] In addition, the UE may be able to operate in an SNPN access operation mode and switch the mode from the SNPN access operation mode to the non-SNPN access operation mode, and vice versa. In this document, for entries in the list of PLMN subscriptions or subscriber data, the list of temporarily prohibited SNPNs or the prohibited PLMN list or the list of permanently prohibited SNPNs or the prohibited PLMN for GPRS services list, it may be necessary to maintain corresponding timers (such as, but not limited to, T3245, etc.). For these lists, the following logic (explained using the timer T3245 example) may be used to maintain those timers.

[0066] For example, when the UE switches between its two available operating access modes, T3245 continues to run. If the UE operating access mode is switched while timer T3245 is running, the UE may behave as follows. That is, when the UE switches back to the previous access operating mode and the selected SNPN subscription remains the same, let t1 be the remaining time of T3245 that times out at the time of the access operating mode switch, and let t be the time elapsed between the access operating mode switch and the return to the same access operating mode. If t1 is greater than t, the timer should be restarted with the value t1-t. If t1 is less than or equal to t, the UE may follow the behavior defined in the above paragraphs when timer T3245 expires. If the UE cannot determine t, the UE shall restart the timer with the value t1.

[0067] In yet another embodiment, when a change (or handover) of the access operation mode is performed, the implementation-related timers and T3245 may continue to run, and they may also follow the above logic. In addition, when the timer expires, there may be multiple possibilities for the UE behavior.

[0068] In an embodiment, when a timer specific to the SNPN access mode expires, the UE may delete the permanently prohibited SNPN list and the temporarily prohibited SNPN list and set the entries of the list of selected subscriber data or the selected PLMN subscription to be valid for 3GPP access and non-3GPP access. When the list is deleted, the UE performs cell selection according to 3GPP TS 38.304. This deletion / erasure is performed regardless of the UE's current operating access mode.

[0069] In an embodiment, when a timer specific to the non-SNPN access mode expires, the UE may delete the prohibited PLMN list and the prohibited PLMN for GPRS services list and set the USIM to be valid for 5GS services for 3GPP access and non-3GPP access. When the list is deleted, the UE performs cell selection according to 3GPP TS 38.304

[28] or 3GPP TS 36.304 [25C]. This deletion / erasure may be performed regardless of the UE's current operating access mode.

[0070] In an embodiment, when a timer common to both modes (running only a single instance for both SNPN and PLMN, such as T3245) expires, the UE may delete the permanently prohibited SNPN list and the temporarily prohibited SNPN list, the prohibited PLMN list and the prohibited PLMN for GPRS service list, and set the entries of the USIM or the selected subscriber data list or the selected PLMN subscription to be valid for 3GPP access and non-3GPP access based on the current UE operating access mode. This deletion / erasure may be performed regardless of the UE's current operating access mode.

[0071] Figure 1 1 is a diagram illustrating an exemplary environment for managing switching between access modes of operation of a UE according to an embodiment. Exemplary environment 100 includes a UE 102 and multiple networks, including a SNPN 104a and PLMNs 106a, 106b, and 106c. Embodiments relate to managing switching between access modes of operation of a UE 102. UE 102 can be any device configured to communicate in an SNPN access mode in a wireless network. Examples of UE 102 include, but are not limited to, mobile phones, smartphones, laptop computers, wearable devices, and the like.

[0072] SNPN refers to an NPN that is operated by an NPN operator and does not rely on network functions provided by a PLMN. The UE 102 can operate in or outside the SNPN access mode of operation. When the UE 102 operates outside the SNPN access mode of operation, such a mode is referred to as "not in the SNPN access mode of operation." Figure 1 As shown, a UE 102 capable of operating in an SNPN access mode of operation 104 camps on an SNPN 104a and receives various services provided by an NPN operator via the SNPN 104a. When the UE 102 is not operating in the SNPN access mode of operation 104, the UE 102 may switch to a not in SNPN access mode of operation 106. In this case, the UE 102 may perform PLMN selection and receive services provided by the PLMN operator via the PLMNs 106a, 106b, 106c. Figure 1 The numbers of SNPNs and PLMNs shown in FIG are shown for exemplary purposes only.

[0073] Herein, UE 102 is configured to manage switching between access modes of operation. UE 102 may detect a switch from SNPN access mode of operation 104 to not in SNPN access mode of operation 106. When SNPN access mode of operation 104 is deactivated, UE 102 switches from SNPN access mode of operation 104 to not in SNPN access mode of operation 106. For example, UE 102 may move out of SNPN 104a to PLMN 106a. UE 102 may have multiple prohibited lists for SNPN access mode of operation 104.

[0074] The multiple forbidden lists for SNPN access mode of operation 104 may include a permanently forbidden SNPN list, a temporarily forbidden SNPN list managed independently by access type, a permanently forbidden SNPN list for network onboarding services, and a temporarily forbidden SNPN list for network onboarding services. When UE 102 receives a registration reject, service reject, or network-initiated deregistration request with a cause value of #74 (temporarily not authorized for this SNPN) or #75 (permanently not authorized for this SNPN), the SNPN may be added to the forbidden list. When a SNPN is on one of the multiple forbidden lists, UE 102 cannot select the SNPN for normal service while operating in SNPN access mode of operation 104. When a SNPN is added to one of the multiple lists, UE 102 is required to start a timer (e.g., T3245). When the timer expires, the multiple forbidden lists are cleared. Referring to the above example, when operating in SNPN access mode of operation 104, UE 102 may have SNPN 104b (not shown) on multiple forbidden lists. However, according to current 3GPP specifications, there is no trigger for removing multiple prohibited lists when UE 102 switches from SNPN access mode of operation 104 to not in SNPN access mode of operation 106. Referring to the above example, the multiple prohibited lists including SNPN 104b may not be removed. In this case, when UE 102 switches back to SNPN access mode of operation 104, UE 102 may not be able to select SNPN 104b.

[0075] Herein, the UE 102 is configured to maintain multiple prohibited lists for the SNPN access mode of operation 104 in the UE 102, as well as the execution of timers started during the SNPN access mode of operation 104. Herein, the UE 102 can continue the execution of the timers started during the SNPN access mode of operation 104 and store the multiple prohibited lists for the SNPN access mode of operation 104. The UE 102 can then remove the multiple prohibited lists for the SNPN access mode of operation 104 upon expiration of the timers in the SNPN access mode of operation 104 or in the not in SNPN access mode of operation 106. In this manner, the UE 102 is able to select the SNPN 104b when operating in the SNPN access mode of operation 104.

[0076] In one embodiment, UE 102 may detect a switch from not in SNPN access mode of operation 106 to SNPN access mode of operation 104. When SNPN access mode of operation 104 is activated, UE 102 switches from not in SNPN access mode of operation 106 to SNPN access mode of operation 104. For example, UE 102 may move out of PLMN 106a to SNPN 104a. UE 102 may have multiple barred lists for not in SNPN access mode of operation 106.

[0077] The multiple forbidden lists for Not in SNPN Access Mode 106 may include lists of forbidden PLMNs managed independently by access type, lists of forbidden PLMNs for GPRS services, and lists of forbidden PLMNs for non-3GPP access to 5GCN. A PLMN may be added to the forbidden list when UE 102 receives a Registration Reject, Service Reject, or network-initiated Deregistration request with cause value #74 (temporarily unauthorized for this PLMN) or #75 (permanently unauthorized for this PLMN). When a PLMN is on the multiple forbidden lists, UE 102 cannot select a PLMN when operating in Not in SNPN Access Mode 106. Referring to the above example, when operating in Not in SNPN Access Mode 106, UE 102 may have PLMN 106c on the multiple forbidden lists. According to current 3GPP specifications, the multiple forbidden lists including PLMN 106c may not be removed when the UE switches to SNPN Access Mode 104. In this case, when the UE 102 switches back to the not in SNPN access mode of operation 106, the UE 102 may be unable to select the PLMN 106c.

[0078] Herein, the UE 102 is configured to maintain multiple prohibited lists of the not in SNPN access mode of operation 106 in the UE 102, as well as execution of timers started during the not in SNPN access mode of operation 106. The UE 102 can then remove the multiple prohibited lists of the not in SNPN access mode of operation 106 upon expiration of the timers in the SNPN access mode of operation 104 or in the not in SNPN access mode of operation 106. In this manner, the UE 102 is able to select the PLMN 106c when operating in the not in SNPN access mode of operation 106.

[0079] Figure 2 200 is a diagram illustrating a UE 102 for managing switching between access operating modes according to an embodiment. Diagram 200 shows that UE 102 may include a central processing unit (CPU) (also referred to as a processor 206), an input / output (I / O) interface 202, and memory 204. Memory 204 may be communicatively coupled to processor 206. Memory 204 stores instructions executable by processor 206. Processor 206 may include at least one data processor for executing program components for carrying out user- or system-generated requests. Memory 204 may be communicatively coupled to processor 206. Memory 204 stores instructions executable by processor 206 that, when executed, may cause processor 206 to manage switching between access operating modes. In an embodiment, memory 204 may include one or more modules 210 and data 208. One or more modules 210 may be configured to use data 208 to perform the steps of the present disclosure to manage switching between access operating modes. Each of the one or more modules 210 may be a hardware unit that may be external to memory 204 and coupled to UE 102. As used herein, the term "module" refers to an application-specific integrated circuit (ASIC), an electronic circuit, a field-programmable gate array (FPGA), a programmable system-on-chip (PSoC), a combinational logic circuit, and / or other suitable components that provide the described functionality. When configured with the described functionality defined herein, one or more modules 210 result in novel hardware. Furthermore, I / O interface 202 is coupled to processor 206, and input signals and / or output signals are communicated through processor 206.

[0080] In one implementation, the modules 210 may include, for example, a detection module 220, an execution module 222, a management module 224, and other modules 226. The modules 210 may be represented as a single module or a combination of different modules. The data 208 may include, for example, detection data 212, execution data 214, management data 216, and other data 218.

[0081] In an embodiment, the detection module 220 may be configured to detect a switch of the UE 102 from the SNPN access mode of operation 104 to the not-in-SNPN access mode of operation 106. The UE 102 may be capable of operating in the SNPN access mode of operation to access SNPN services. In this case, the UE 102 may be capable of operating in two modes: the SNPN access mode of operation 104 and the not-in-SNPN access mode of operation 106. Initially, the UE 102 may operate in the SNPN access mode of operation 104. The UE 102 may select an SNPN and complete registration with the SNPN by communicating with an AMF server. When the UE 102 is in a mobile state, the UE 102 may move out of the SNPN and the SNPN access mode of operation 104 may be deactivated. The detection module 220 may detect a switch of the UE 102 from the SNPN access mode of operation 104 to the not-in-SNPN access mode of operation 106. In an example, the UE 102 may be located in a hospital that provides SNPN services. The UE 102 may move out of the hospital. In this case, the SNPN access mode of operation 104 may be deactivated.

[0082] refer to Figure 3A As shown in block 1, the UE 102 may be capable of operating in two modes, namely, the SNPN access mode of operation 104 and the not in SNPN access mode of operation 106. As shown in block 2, the UE 102 may communicate with the AMF server 302 to perform SNPN selection and registration. As shown in block 3, the detection module 220 may detect the switching of the UE 102 from the SNPN access mode of operation 104 to the not in SNPN access mode of operation 106.

[0083] In an embodiment, the detection module 220 may be configured to detect a switch of the UE 102 from the not in SNPN access mode of operation 106 to the SNPN access mode of operation 104. The UE 102 switches from the not in SNPN access mode of operation 106 to the SNPN access mode of operation 104 when the SNPN access mode of operation 104 is activated.

[0084] refer to Figure 3B As shown in block 1, the UE 102 may be capable of operating in two modes, namely, the SNPN access mode of operation 104 and the not in SNPN access mode of operation 106. As shown in block 2, the UE 102 may communicate with the AMF server 302 to perform PLMN selection and registration. As shown in block 3, the detection module 220 may detect that the UE 102 switches from the not in SNPN access mode of operation 106 to the SNPN access mode of operation 106. Return to Reference Figure 2 , data related to the detection of switching between access operating modes may be stored in memory 204 as detection data 212 .

[0085] In an embodiment, the execution module 222 may be configured to receive the detection data 212 from the detection module 220. In addition, the execution module 222 may be configured to maintain a plurality of prohibited lists for the SNPN access operation mode 104. The plurality of prohibited lists for the SNPN access operation mode 104 may include a permanently prohibited SNPN list, a temporarily prohibited SNPN list independently managed by access type, a permanently prohibited SNPN list for a network loading service, and a temporarily prohibited SNPN list for a network loading service. The execution module 222 may store the prohibited list for the SNPN access operation mode 104 in the memory 204 of the UE 102.

[0086] In addition, the execution module 222 can be configured to maintain the execution of the timer started during the SNPN access operation mode 104 in the UE 102. The timer can include T3245. The execution module 222 can be configured to continue to execute the timer or run the timer at the time of the handover. For example, the plurality of prohibited lists can include SNPN '2'. In addition, the value of the timer can be 60 minutes. Considering that the timer was executed for 40 minutes before the handover, the execution module 222 continues to execute the timer for the next 20 minutes. Return to Reference Figure 3A At block 5, the execution module 222 may maintain a plurality of barred lists for the SNPN access mode of operation 104 and timers specific to the SNPN access mode of operation 104. The UE 102 may then perform PLMN selection and registration while maintaining the plurality of barred lists for the SNPN access mode of operation 104 and timers specific to the SNPN access mode of operation 104.

[0087] Return Reference Figure 2 In an embodiment, the execution module 222 may be configured to maintain multiple forbidden lists for the Not in SNPN access mode of operation 106 when the UE 102 switches from the Not in SNPN access mode of operation 106 to the SNPN access mode of operation 104. The multiple forbidden lists for the Not in SNPN access mode of operation 106 may include a list of forbidden PLMNs managed independently by access type, a list of forbidden PLMNs for GPRS services, and a list of forbidden PLMNs for non-3GPP access to 5GCN. The execution module 222 may store the forbidden lists for the Not in SNPN access mode of operation 106 in the memory 204 of the UE 102. In addition, the execution module 212 may be configured to maintain execution of a timer started during the Not in SNPN access mode of operation 106 in the UE 102. The timer may include T3245. The execution module 222 may be configured to continue executing the timer or running the timer during the switch.

[0088] Return Reference Figure 3B At block 5, the execution module 212 may maintain a plurality of barred lists of the not in SNPN access mode of operation 106 and a timer specific to the not in SNPN access mode of operation 106. The UE 102 may then perform SNPN selection and registration while maintaining the plurality of barred lists of the not in SNPN access mode of operation 106 and the timer specific to the not in SNPN access mode of operation 106.

[0089] Return Reference Figure 2 , the execution status of the plurality of prohibited lists and timers may be stored in the memory 204 as execution data 214 .

[0090] In an embodiment, the management module 224 may be configured to manage switching between the SNPN access mode of operation 104 and the not in SNPN access mode of operation 106. The management module 224 may be configured to remove multiple prohibited lists for the SNPN access mode of operation 104 upon expiration of a timer for the not in SNPN access mode of operation 106 and the SNPN access mode of operation 104. The management module 224 may reset any retry counters specific to the SNPN access mode of operation 104 and remove multiple prohibited lists for the SNPN access mode of operation 104, such as Figure 3A As shown in box 8 in .

[0091] In an embodiment, the management module 224 may be configured to remove the plurality of prohibited lists for the not in SNPN access mode of operation 106 upon expiration of the timer for the not in SNPN access mode of operation 106 and the not in SNPN access mode of operation 104. The management module 224 may reset any retry counters specific to the not in SNPN access mode of operation 106 and remove the plurality of prohibited lists for the not in SNPN access mode of operation 106, as Figure 3B As shown in box 8 in .

[0092] Other data 218 may store data generated by one or more modules 210 for performing various functions of UE 102, including temporary data and temporary files. One or more modules 210 may also include other modules 226 to perform various other functions of UE 102. Other data 218 may be stored in memory 204. One or more modules 210 may be represented as a single module or a combination of different modules.

[0093] Figure 4 1 is a flow chart illustrating a method for managing a handover of a UE 102 from a SNPN access mode of operation 104 to a not in SNPN access mode of operation 106 according to an embodiment. Figure 4As shown, method 400 may include one or more steps. Method 400 may be described in the general context of computer-executable instructions. Generally, computer-executable instructions may include routines, programs, objects, components, data structures, procedures, modules, and functions that perform specific functions or implement specific abstract data types.

[0094] The order in which method 400 is described is not intended to be construed as limiting, and any number of the described method blocks can be combined in any order to implement the method. Furthermore, individual blocks can be deleted from the method without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or a combination thereof.

[0095] At step 402, a switch from the SNPN access mode of operation 104 to the not in SNPN access mode of operation 106 is detected. The UE 102 switches from the SNPN access mode of operation 104 to the not in SNPN access mode of operation 106 when the SNPN access mode of operation 104 is deactivated.

[0096] In step 404, a plurality of prohibited lists of the SNPN access operation mode 104 and execution of timers started during the SNPN access operation mode 104 are maintained in the UE 102. The plurality of prohibited lists of the SNPN access operation mode 104 may include a permanently prohibited SNPN list, a temporarily prohibited SNPN list independently managed by access type, a permanently prohibited SNPN list for network loading service, and a temporarily prohibited SNPN list for network loading service.

[0097] In step 406, switching is performed between the SNPN access operation mode 104 and the not in SNPN access operation mode 106 by removing multiple prohibited lists of the SNPN access operation mode 104 when a timer in one of the modes SNPN access operation mode 104 and not in SNPN access operation mode 106 expires.

[0098] Figure 5 1 is a flow chart illustrating a method for managing a switch of a UE 102 from a not in SNPN access mode of operation 106 to a SNPN access mode of operation 104 according to an embodiment. Figure 5 As shown, method 500 may include one or more steps. Method 500 may be described in the general context of computer-executable instructions. Generally, computer-executable instructions may include routines, programs, objects, components, data structures, procedures, modules, and functions that perform specific functions or implement specific abstract data types.

[0099] The order in which method 500 is described is not intended to be construed as limiting, and any number of the described method blocks can be combined in any order to implement the method. Furthermore, individual blocks can be deleted from the method without departing from the scope of the subject matter described herein. Furthermore, the method can be implemented in any suitable hardware, software, firmware, or a combination thereof.

[0100] At step 502, a switch from not in SNPN access mode of operation 106 to SNPN access mode of operation 104 is detected. UE 102 switches from not in SNPN access mode of operation 106 to SNPN access mode of operation 104 when SNPN access mode of operation 104 is activated.

[0101] At step 504, a plurality of forbidden lists of not in SNPN access operation mode 106 and execution of a timer started during not in SNPN access operation mode 106 are maintained in UE 102. The plurality of forbidden lists of not in SNPN access operation mode 106 may include a list of forbidden PLMNs managed independently by access type, a list of forbidden PLMNs for GPRS service, and a list of forbidden PLMNs for non-3GPP access to 5GCN.

[0102] In step 506, switching between the SNPN access operation mode 104 and the not in SNPN access operation mode 106 is managed by removing multiple prohibited lists of the not in SNPN access operation mode 106 when a timer in one of the modes SNPN access operation mode 104 and not in SNPN access operation mode 106 expires.

[0103] Figure 4 and Figure 5 The operations shown illustrate specific events that occur in a particular order. In alternative embodiments, certain operations may be performed, modified, or removed in a different order. In addition, steps may be added to the above logic and still conform to the described embodiments. In addition, the operations described herein may occur sequentially, or certain operations may be processed in parallel. In addition, the operations may be performed by a single processing unit or by a distributed processing unit.

[0104] Figure 66 is a diagram illustrating an exemplary computer system for implementing embodiments consistent with the present disclosure. In embodiments, computer system 600 may be UE 102. Thus, computer system 600 may be used to manage switching between access modes of operation for UE 102. Computer system 600 may communicate with AMF 624 via communication network 618. Computer system 600 may include a CPU (also referred to as processor 604). Processor 604 may include at least one data processor. Processor 604 may include specialized processing units, such as an integrated system (bus) controller, a memory management control unit, a floating point unit, a graphics processing unit, a digital signal processing unit, and the like.

[0105] The processor 604 may be configured to communicate with one or more I / O devices via the I / O interface 602. The I / O interface 602 may employ communication protocols / methods such as, but not limited to, audio, analog, digital, mono, RCA, stereo, Institute of Electrical and Electronics Engineers (IEEE)-1394, serial bus, Universal Serial Bus (USB), infrared, PS / 2, BNC, coaxial, component, composite, Digital Visual Interface (DVI), High-Definition Multimedia Interface (HDMI), radio frequency (RF) antenna, S-video, VGA, IEEE 802.n / b / g / n / x, Bluetooth, cellular (e.g., Code Division Multiple Access (CDMA), High-Speed ​​Packet Access (HSPA+), Global System for Mobile Communications (GSM), Long Term Evolution (LTE), WiMax, etc.), and the like.

[0106] Computer system 600 can communicate with one or more I / O devices using I / O interface 602. For example, input device 620 can be an antenna, keyboard, mouse, joystick, (infrared) remote control, camera, card reader, fax machine, dongle, biometric reader, microphone, touch screen, touchpad, trackball, stylus, scanner, storage device, transceiver, video device / source, etc. Output device 622 can be a printer, fax machine, video display (e.g., cathode ray tube (CRT), liquid crystal display (LCD), light emitting diode (LED), plasma, plasma display panel (PDP), organic light emitting diode display (OLED)), audio speaker, etc.

[0107] The processor 604 can be configured to communicate with a communication network 618 via a network interface 606. The network interface 606 can communicate with the communication network 618. The network interface 606 can use connection protocols including, but not limited to, direct connection, Ethernet (e.g., twisted pair 10 / 100 / 1000 Base T), Transmission Control Protocol / Internet Protocol (TCP / IP), Token Ring, IEEE 802.11 a / b / g / n / x, etc. The communication network 618 can include, but not limited to, direct interconnection, a local area network (LAN), a wide area network (WAN), a wireless network (e.g., using Wireless Application Protocol (WAP)), the Internet, etc. The network interface 606 can use connection protocols including, but not limited to, direct connection, Ethernet (e.g., twisted pair 10 / 100 / 1000 Base T), Transmission Control Protocol / Internet Protocol (TCP / IP), Token Ring, IEEE 802.11 a / b / g / n / x, etc.

[0108] The communication network 618 includes, but is not limited to, direct interconnections, e-commerce networks, peer-to-peer (P2P) networks, local area networks (LANs), wide area networks (WANs), wireless networks (e.g., using the Wireless Application Protocol), the Internet, Wi-Fi, and the like. The first network and the second network can be dedicated networks or shared networks, representing a connection between different types of networks that communicate with each other using various protocols (e.g., Hypertext Transfer Protocol (HTTP), Transmission Control Protocol / Internet Protocol (TCP / IP), WAP, and the like). Furthermore, the first network and the second network can include various network devices, including routers, bridges, servers, computing devices, storage devices, and the like.

[0109] In some embodiments, the processor 604 may be arranged to communicate with a memory 610 (e.g., random access memory (RAM), read-only memory (ROM), etc.) via a storage interface 608. The storage interface 608 may be connected to the memory 610 using a connection protocol such as Serial Advanced Technology Attachment (SATA), Integrated Drive Electronics (IDE), IEEE-1394, Universal Serial Bus (USB), Fibre Channel, Small Computer System Interface (SCSI), etc., including but not limited to a memory drive, a removable disk drive, etc. The memory drive may also include a drum, a magnetic disk drive, a magneto-optical drive, an optical drive, a redundant array of independent disks (RAID), a solid-state memory device, a solid-state drive, etc.

[0110] Memory 610 can store a collection of program or database components, including but not limited to a user interface 612, an operating system 614, a web browser 616, etc. In some embodiments, computer system 600 can store user / application data, such as data, variables, records, etc., as described herein. Such a database can be implemented as a fault-tolerant, relational, scalable, secure database, such as Oracle® or Sybase®.

[0111] Operating system 614 may facilitate resource management and operation of computer system 600. Examples of operating systems include, but are not limited to, APPLE MACINTOSH R OS X, UNIX R , UNIX-like system distributions (for example, BERKELEY SOFTWARE DISTRIBUTION TM (BSD), FREEBSD TM , NETBSD TM 、OPENBSD TM etc.), LINUX DISTRIBUTIONS TM (For example, RED HAT TM UBUNTU TM 、KUBUNTU TM etc.), IBM TM OS / 2, MICROSOFT TM WINDOWS TM (XP TM VISTA TM / 7 / 8, 10, etc.), APPLE R iOS TM 、GOOGLE R Android TM , BLACKBERRY R OS, etc.

[0112] In some embodiments, computer system 600 may implement a program component stored in a web browser 616. Web browser 616 may be a hypertext viewing application, such as MICROSOFT R INTERNET EXPLORER TM 、GOOGLE R CHROME TM0 、MOZILLA R FIREFOX TM 、APPLE R SAFARI TMSecure web browsing can be provided using secure hypertext transfer protocol (HTTPS), secure socket layer (SSL), transport layer security (TLS), etc. The web browser 616 can utilize AJAX TM 、DHTML TM 、ADOBE R FLASH TM 、JAVASCRIPT TM , JAVA TM , application programming interface (API) and other facilities. In some embodiments, the computer system 600 can implement a program component stored in a mail server. The mail server can be an Internet mail server, such as Microsoft Exchange. The mail server can utilize a mail server such as ASP. TM ACTIVEX TM , ANSI TM C++ / C#、MICROSOFT R ,NET TM 、CGI SCRIPTS TM , JAVA TM 、JAVASCRIPT TM PERL TM PHP TM 、PYTHON TM 、WEBOBJECTS TM The mail server can use Internet Message Access Protocol (IMAP), Messaging Application Programming Interface (MAPI), MICROSOFT R Communication protocols such as Exchange, Post Office Protocol (POP), Simple Mail Transfer Protocol (SMTP), etc. In some embodiments, the computer system 600 may implement a program component stored in a mail client. The mail client may be an email viewing application such as APPLE R MAIL TM MICROSOFT R ENTOURAGE TM MICROSOFT R OUTLOOK TM 、MOZILLA R Thunderbird TM wait.

[0113] In addition, embodiments consistent with the present disclosure may be implemented using one or more computer-readable storage media. A computer-readable storage medium refers to any type of physical memory that can store information or data readable by a processor. Thus, a computer-readable storage medium can store instructions for execution by one or more processors, including instructions for causing a processor to perform steps or stages consistent with the embodiments described herein. The term "computer-readable medium" should be understood to include tangible items and exclude carrier waves and transient signals, i.e., to be non-transitory. Examples include RAM, ROM, volatile memory, non-volatile memory, hard drives, compact disk read-only memory (CD ROM), digital video disks (DVD), flash drives, disks, and any other known physical storage media.

[0114] The present disclosure provides a method and a UE for managing switching between access operation modes of a UE. The present disclosure provides a solution for maintaining a prohibited list of SNPNs or PLMNs when the UE switches between an SNPN access operation mode and a mode not in the SNPN access operation mode. In addition, the present disclosure provides a solution for maintaining the execution of a timer started during an SNPN access operation mode or a PLMN access operation mode, and the deletion of the corresponding prohibited list when the timer expires, regardless of the access operation mode. Thus, the switching between access operation modes of the UE is managed. When the UE switches back to the corresponding access operation mode, the present disclosure enables the UE to select an SNPN or PLMN that is present in the prohibited list.

[0115] Figure 7 is a diagram showing the structure of a UE according to an embodiment.

[0116] like Figure 7 As shown, the UE may include a transceiver 710, a memory 720, and a processor 730. The transceiver 710, the memory 720, and the processor 730 of the UE may operate according to the communication method of the UE described above. However, the components of the UE are not limited thereto. For example, the UE may include more or fewer components than the above components. In addition, the processor 730, the transceiver 710, and the memory 720 may be implemented as a single chip. In addition, the processor 730 may include at least one processor. In addition, Figure 7 The UE corresponds to Figures 1 to 3B UE 102.

[0117] The transceiver 710 is collectively referred to as a UE receiver and a UE transmitter, and can transmit and receive signals to and from a base station or a network entity. The signals transmitted to and received from the base station or network entity may include control information and data. The transceiver 710 may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for amplifying the low noise and down-converting the frequency of the received signal. However, this is merely an example of the transceiver 710, and the components of the transceiver 710 are not limited to the RF transmitter and the RF receiver.

[0118] The transceiver 710 may receive a signal through a wireless channel and output a signal to the processor 730 , and transmit a signal output from the processor 730 through a wireless channel.

[0119] The memory 720 may store programs and data required for the operation of the UE. In addition, the memory 720 may store control information or data included in signals obtained by the UE. The memory 720 may be a storage medium such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

[0120] The processor 730 may control a series of processes so that the UE operates as described above. For example, the transceiver 710 may receive a data signal including a control signal transmitted by a base station or a network entity, and the processor 730 may determine a result of receiving the control signal and the data signal transmitted by the base station or the network entity.

[0121] Figure 8 is a diagram showing the structure of a base station according to an embodiment of the present disclosure.

[0122] like Figure 8 As shown, the base station may include a transceiver 810, a memory 820, and a processor 830. The transceiver 810, the memory 820, and the processor 830 of the base station may operate according to the communication method of the above-mentioned base station. However, the components of the base station are not limited thereto. For example, the base station may include more or fewer components than the above-mentioned components. In addition, the processor 830, the transceiver 810, and the memory 820 may be implemented as a single chip. In addition, the processor 830 may include at least one processor. In addition, Figure 8 The base station corresponds to Figure 1 BS.

[0123] The transceiver 810 is collectively referred to as a base station receiver and a base station transmitter, and can transmit and receive signals to and from a terminal (UE) or a network entity. Signals transmitted to and received from a terminal or a network entity may include control information and data. The transceiver 810 may include an RF transmitter for up-converting and amplifying the frequency of transmitted signals, and an RF receiver for amplifying low-noise signals and down-converting the frequency of received signals. However, this is merely an example of the transceiver 810, and the components of the transceiver 810 are not limited to an RF transmitter and an RF receiver.

[0124] The transceiver 810 may receive a signal through a wireless channel and output a signal to the processor 830 , and transmit a signal output from the processor 830 through a wireless channel.

[0125] The memory 820 may store programs and data required for the operation of the base station. In addition, the memory 820 may store control information or data included in the signal obtained by the base station. The memory 820 may be a storage medium such as ROM, RAM, hard disk, CD-ROM and DVD, or a combination of storage media.

[0126] The processor 830 may control a series of processes so that the base station operates as described above. For example, the transceiver 810 may receive a data signal including a control signal transmitted by a terminal, and the processor 830 may determine a result of receiving the control signal and the data signal transmitted by the terminal.

[0127] Figure 9 is a diagram showing a structure of a network entity according to an embodiment.

[0128] like Figure 9 As shown, the network entity may include a transceiver 910, a memory 920, and a processor 930. The transceiver 910, the memory 920, and the processor 930 of the network entity may operate according to the communication method of the above-mentioned network entity. However, the components of the terminal are not limited thereto. For example, the network entity may include more or fewer components than the above-mentioned components. In addition, the processor 930, the transceiver 910, and the memory 920 may be implemented as a single chip. In addition, the processor 930 may include at least one processor. In addition, Figure 9 The network entities shown in may correspond to network entities (e.g., Figure 3A and 3B AMF entity 302 or Figure 6 AMF entity 624 in.

[0129] The transceiver 910 is generally referred to as a network entity receiver and a network entity transmitter, and can transmit and receive signals to and from a base station or a UE. The signals transmitted to or received from the base station or UE may include control information and data. In this regard, the transceiver 910 may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for amplifying the low noise and down-converting the frequency of the received signal. However, this is merely an example of the transceiver 910, and the components of the transceiver 910 are not limited to the RF transmitter and the RF receiver.

[0130] In addition, the transceiver 910 may receive a signal through a wireless channel and output a signal to the processor 930 , and transmit a signal output from the processor 930 through a wireless channel.

[0131] The memory 920 may store programs and data required for the operation of the network entity. In addition, the memory 920 may store control information or data included in signals obtained by the network entity. The memory 920 may be a storage medium such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

[0132] The processor 930 may control a series of processes so that the network entity operates as described above. For example, the transceiver 910 may receive a data signal including a control signal, and the processor 930 may determine a result of receiving the data signal.

[0133] The methods according to the embodiments described in the claims or detailed description of the present disclosure may be implemented in hardware, software, or a combination of hardware and software.

[0134] When the electrical structure and method are implemented using software, a computer-readable recording medium may be provided, having one or more programs (software modules) recorded thereon. The one or more programs recorded on the computer-readable recording medium are configured to be executable by one or more processors in an electronic device. The one or more programs include instructions for executing the methods according to the embodiments described in the claims or detailed description of this disclosure.

[0135] The program (e.g., software module or software) may be stored in RAM, non-volatile memory including flash memory, ROM, electrically erasable programmable read-only memory (EEPROM), magnetic disk storage, CD-ROM, DVD, another type of optical storage device, or magnetic tape cassette. Alternatively, the program may be stored in a memory system that includes a combination of some or all of the above memory devices. Furthermore, multiple memory devices may be included.

[0136] The program may also be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a LAN, a wireless LAN (WLAN), or a storage area network (SAN), or a combination thereof. The storage device may be connected to an apparatus according to an embodiment of the present disclosure via an external port. Another storage device on the communication network may also be connected to an apparatus performing an embodiment of the present disclosure.

[0137] In the above embodiments, the elements included in the present disclosure are expressed in singular or plural form depending on the embodiment. However, for ease of explanation, the singular or plural form is appropriately selected, and the present disclosure is not limited thereto. Therefore, an element expressed in plural form may also be configured as a single element, and an element expressed in singular form may also be configured as a plurality of elements.

[0138] Although the figures illustrate different examples of user devices, various changes may be made to the figures. For example, the user devices may include any number of each component in any suitable arrangement. Generally, the figures do not limit the scope of the present disclosure to any particular configuration. Furthermore, although the figures illustrate operating environments in which various user device features disclosed in this patent document may be used, these features may be used in any other suitable system.

[0139] At least some of the example embodiments described herein may be constructed, in part or in whole, using dedicated, specialized hardware. Terms such as "component," "module," or "unit" as used herein may include, but are not limited to, hardware devices that perform certain tasks or provide related functionality, such as circuits, FPGAs, or ASICs in discrete or integrated component form. In some embodiments, the described elements may be configured to reside on a tangible, persistent, addressable storage medium and may be configured to execute on one or more processors. In some embodiments, these functional elements may include, for example, components (such as software components, object-oriented software components, class components, and task components), processes, functions, properties, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. Although the example embodiments have been described with reference to the components, modules, and units discussed herein, such functional elements may be combined into fewer elements or separated into additional elements. Various combinations of optional features have been described herein, and it should be understood that the described features may be combined in any suitable combination. Specifically, features of any example embodiment may be appropriately combined with features of any other embodiment, except where such combinations are mutually exclusive. Throughout the specification, the term “comprising” or “comprise” means including specified components but does not exclude the existence of other components.

[0140] Attention is paid to all papers and documents related to this application that were filed concurrently with or before this specification and are open to public inspection with this specification, and the contents of all such papers and documents are incorporated herein by reference.

[0141] All features disclosed in this specification (including any accompanying claims, abstract and drawings) and / or all steps of any method or process so disclosed may be combined in any combination, except combinations where at least some of such features and / or steps are mutually exclusive.

[0142] Unless expressly stated otherwise, each feature disclosed in this specification (including any accompanying claims, abstract, and drawings) may be replaced by alternative features serving the same, equivalent, or similar purpose. Thus, unless expressly stated otherwise, each feature disclosed is one example only of a generic series of equivalent or similar features.

[0143] The invention is not limited to the details of the foregoing embodiments. The invention extends to any novel feature or any novel combination of features disclosed in this specification (including any accompanying claims, abstract and drawings), or to any novel step or any novel combination of steps in any method or process so disclosed.

[0144] Any of the above variant embodiments may be used independently or in combination with at least one other variant embodiment. The above flowcharts illustrate example methods that can be implemented according to the principles of the present disclosure, and various changes may be made to the methods shown in the flowcharts herein. For example, although shown as a series of steps, the various steps in each figure may overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, a step may be omitted or replaced by another step.

[0145] This specification has described methods and apparatus for selecting a selective security mode for applying selective security and flow management for selective security to a user equipment (UE) under mobility. Furthermore, this specification has described methods and apparatus for flow management for selective security during handover. The steps shown are described to explain the illustrated embodiments, and it is expected that ongoing technological development will change the manner in which specific functions are performed. These embodiments are presented herein for purposes of illustration, not limitation. Furthermore, for ease of description, the boundaries of functional building blocks have been arbitrarily defined herein. Alternative boundaries may be defined so long as the specified functions and their relationships are appropriately performed. Based on the teachings contained herein, alternatives (including equivalents, extensions, variations, and deviations of those described herein) will be apparent to those skilled in the relevant art. Such alternatives fall within the scope and spirit of the disclosed embodiments.

[0146] Although the present disclosure has been described using exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. The present disclosure is intended to encompass such changes and modifications as fall within the scope of the appended claims. Nothing in this application should be construed as implying that any particular element, step, or function is essential to the scope of the claims. The scope of a patented subject matter is defined by the claims.

[0147] Unless expressly stated otherwise, the terms "embodiment," "embodiments," "embodiments," "the embodiment," "the embodiments," "one or more embodiments," "some embodiments," and "one embodiment" mean "one or more (but not all) embodiments of the invention."

[0148] Unless expressly stated otherwise, the terms "includes," "comprising," "having" and variations thereof mean "including but not limited to."

[0149] The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly stated otherwise. Unless expressly stated otherwise, the terms "a," "an," and "the" mean "one or more."

[0150] The description of an embodiment with several components in communication with each other does not imply that all such components are required. Rather, various optional components are described to illustrate the wide variety of possible embodiments of the present invention.

[0151] When a single device or article is described herein, it will be apparent that more than one device / article (whether or not they cooperate) may be used in place of a single device / article. Similarly, where more than one device or article (whether or not they cooperate) is described herein, it will be apparent that a single device / article may be used in place of the more than one device or article, or a different number of devices / articles may be used in place of the number of devices or procedures shown. The functions and / or features of a device may alternatively be embodied by one or more other devices that are not explicitly described as having such functions / features. Thus, other embodiments of the present invention need not include the device itself.

[0152] The language used in this specification is primarily selected for readability and instructional purposes and may not be selected to describe or limit the subject matter of the present invention. Accordingly, it is intended that the scope of the present invention be limited not by this detailed description, but by any claims issued based on the application herein. Accordingly, the disclosure of the embodiments of the present invention is intended to illustrate, not to limit, the scope of the invention, which is set forth in the appended claims.

[0153] While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for purposes of illustration and not limitation, with the true scope being indicated by the following claims.

[0154] Reference Number:

[0155] Reference Number describe 100 Example Environment 101 UE 102 network 200 Detailed drawing 201 I / O Interface 202 Memory 203 processor 204 data 205 Module 206 Session data 207 Measurement to determine data 208 Temperature data 209 Transferring Data 210 Other data 211 Session detection module 212 Determine the module 213 Temperature detection module 214 Transmission Module 215 Other modules 600 Computer system 602 I / O Interface 604 processor 606 Network interface 608 Storage interface 610 Memory 612 user interface 614 operating system 616 Web browser 618 Communication Network 620 Input devices 622 output device 624 AMF

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: When operating in a stand-alone non-public network (SNPN) access operating mode, storing information about the SNPNs in a plurality of lists of prohibited SNPNs; Disable SNPN access operation mode; as well as The plurality of lists of prohibited SNPNs are maintained.

2. The method according to claim 1, further comprising: Upon expiration of the timer, deleting the plurality of lists of prohibited SNPNs, and Among them, the timer includes T3245.

3. The method according to claim 1, in, said plurality of lists of prohibited SNPNs comprising a list of permanently prohibited SNPNs and a list of temporarily prohibited SNPNs, wherein storing information about the SNPN comprises selecting the SNPN when operating in an SNPN access operating mode, Wherein, information about SNPN is included in the service rejection message, and The method further comprises: Setting the selected entry or the selected public land mobile network (PLMN) subscription to be valid for a 3rd Generation Partnership Project (3GPP) access and a non-3GPP access; and Perform cell selection.

4. A method performed by a terminal in a wireless communication system, the method comprising: storing information about public land mobile networks (PLMNs) in a plurality of lists of prohibited PLMNs; Activate the Standalone Non-Public Network (SNPN) access operation mode; as well as The plurality of lists of prohibited PLMNs are maintained.

5. The method according to claim 4, further comprising: upon expiration of the timer, deleting the plurality of lists of prohibited PLMNs, and Among them, the timer includes T3245.

6. The method according to claim 4, wherein: The plurality of lists of forbidden PLMNs include a list of forbidden PLMNs and a list of forbidden PLMNs for General Packet Radio Service (GPRS).

7. The method according to claim 4, in, Storing information about PLMNs includes selecting a PLMN when not in SNPN access mode of operation, wherein information about the PLMN is included in the registration reject message, and The method further comprises: Setting the terminal's Universal Subscriber Identity Module (USIM) to be valid for Fifth Generation System (5GS) services for Third Generation Partnership Project (3GPP) access and non-3GPP access; and Perform cell selection.

8. A terminal in a wireless communication system, the terminal comprising: transceiver; and a controller coupled to the transceiver and configured to: storing information about stand-alone non-public networks (SNPNs) in a plurality of lists of prohibited SNPNs; Disable SNPN access operation mode; as well as The plurality of lists of prohibited SNPNs are maintained.

9. The terminal according to claim 8, in, The controller is further configured to delete the plurality of lists of prohibited SNPNs upon expiration of the timer, and Among them, the timer includes T3245.

10. The terminal according to claim 8, wherein: The multiple lists of prohibited SNPNs include a list of permanently prohibited SNPNs and a list of temporarily prohibited SNPNs.

11. The terminal according to claim 8, in, The controller is further configured to select the SNPN when in the SNPN access mode of operation, Wherein, information about SNPN is included in the service rejection message, and The controller is further configured as follows: Setting the selected entry or the selected public land mobile network (PLMN) subscription to be valid for a 3rd Generation Partnership Project (3GPP) access and a non-3GPP access; and Perform cell selection.

12. A terminal in a wireless communication system, the terminal comprising: transceiver; and a controller coupled to the transceiver and configured to: storing information about public land mobile networks (PLMNs) in a plurality of lists of prohibited PLMNs; Activate the Standalone Non-Public Network (SNPN) access operation mode; as well as The plurality of lists of prohibited PLMNs are maintained.

13. The terminal according to claim 12, in, The controller is further configured to delete the plurality of lists of prohibited PLMNs upon expiration of the timer, and Among them, the timer includes T3245. The terminal according to claim 12 , wherein: The plurality of lists of forbidden PLMNs include a list of forbidden PLMNs and a list of forbidden PLMNs for General Packet Radio Service (GPRS).

15. The terminal according to claim 12, in, The controller is further configured to select a PLMN when not in the SNPN access mode of operation, wherein information about the PLMN is included in the registration reject message, and The controller is further configured as follows: Setting the terminal's Universal Subscriber Identity Module (USIM) to be valid for Fifth Generation System (5GS) services for Third Generation Partnership Project (3GPP) access and non-3GPP access; and Perform cell selection.

Images