JP7380005B2 - Wireless terminals, core network nodes, and methods thereof - Google Patents

Description

TECHNICAL FIELD This disclosure relates to cellular networks, and more particularly to private (or local) cellular networks.

The 3rd Generation Partnership Project (3GPP) is promoting the standardization of private (or local) cellular networks (see, for example, non-patent documents 1-6). In 3GPP terminology (terminology), private (or local) cellular networks are: It is called a non-public network (NPN). NPN is a 5G system (5GS) deployed for non-public use. NPN is also called private 5G network or local 5G network.

NPNs are deployed as stand-alone Non-Public Networks (SNPNs) or as public network integrated NPNs. Public network integrated NPNs are deployed with support for Public Land Mobile Networks (PLMNs). In contrast, SNPNs are operated by NPN operators and do not rely on network functions provided by Public Land Mobile Networks (PLMNs).

The SNPN is identified by a combination of PLMN identifier/identity (PLMN ID) and network identifier (NID). That is, SNPN identity is a combination of PLMN ID and NID. PLMN IDs used for SNPNs do not need to be unique. PLNM IDs reserved for private networks can be used for SNPN. For example, the PLMN ID that specifies the SNPN consists of a Mobile Country Code (MCC) indicating "999" and a Mobile Network Code (MNC) defined by 3GPP. MCC 999 is assigned by the International Telecommunication Union (ITU) for internal use within a private network.

NIDs support two assignment models: locally managed NIDs and universally managed NIDs. Universally managed NIDs are assumed to be globally unique. In contrast, locally managed NIDs are assumed to be self-managed by SNPNs. That is, locally managed NIDs are individually selected by SNPNs at deployment time. Therefore, locally managed NIDs need not be unique. Locally managed NIDs use a different numbering space than universally managed NIDs. The NID is assumed to consist of an assignment model indication and a NID value (see Non-Patent Document 6). Assignment model indication indicates universally managed NID or locally managed NID.

Next Generation Radio Access Network (NG-RAN) nodes that provide access to SNPNs broadcast system information indicating one or more PLMN IDs and a List of NIDs per PLMN ID. SNPN-enabled User Equipment (UE) supports receiving multiple combinations of PLMN ID and NID. Additionally, NG-RAN nodes may optionally broadcast a human-readable network name per NID. The human-readable network name for each NID is used only for manual SNPN selection described below.

The SNPN-enabled UE (or mobile equipment (ME)) is configured with a "list of subscriber data". The "list of subscriber data" contains zero or more entries. Each entry in the "list of subscriber data" includes a subscriber identifier, credentials, and SNPN identity. The Subscriber identifier is in the form of a 5G Subscription Permanent Identifier (SUPI).

SNPN-enabled UE supports SNPN access mode. SNPN-enabled When a UE is set to operate in SNPN access mode, it selects and registers only with SNPN over the air interface (i.e., 5G Uu interface). In other words, the UE operating in SNPN access mode performs the SNPN selection process instead of the PLMN selection process. There are two modes for the SNPN selection process: automatic SNPN selection mode and manual SNPN selection mode. A UE operating in SNPN access mode reads one or more PLMN IDs and a list of NIDs for each PLMN ID from broadcast system information and takes these into account in network selection (i.e., SNPN selection).

In automatic SNPN selection mode, the UE selects an SNPN that is available and allowed, and is identified by the SNPN identity contained in the "list of subscriber data" entry in the UE (ME). do. Here, the allowable SNPN means an SNPN that is not included in the "permanently forbidden SNPNs" list and also not included in the "temporarily forbidden SNPNs" list. That is, in the automatic SNPN selection process, the UE does not select SNPNs identified by SNPN identities stored in the "permanently forbidden SNPNs" list or the "temporarily forbidden SNPNs" list. The UE attempts registrations to the selected SNPN. Specifically, the UE sends a Non-Access Stratum (NAS) message (i.e., REGISTRATION REQUEST message) to the 5GC via the NG-RAN to request registration with the selected SNPN.

The SNPN-enabled UE manages a "temporarily forbidden SNPNs" list and a "permanently forbidden SNPNs" list. Among these, the "temporarily forbidden SNPNs" list is managed as follows (in particular, Section 5.30.2.5 of Non-Patent Document 2, Section 4.9 of Non-Patent Document 3, Section 5.5.1.2.5 of Non-Patent Document 4). , 5.5.1.3.5, and 5.6.1.5, and Non-Patent Document 5).

Access and Mobility The Management Function (AMF) sends the relevant UE with an appropriate cause code or value to temporarily prevent the UE from automatically selecting and registering with the same SNPN. Reject the UE. Specifically, when rejecting the REGISTRATION REQUEST (or SERVICE REQUEST) message from the UE to the SNPN identified by the PLMN ID and locally managed NID, the AMF shall A REGISTRATION REJECT (or SERVICE REJECT) message indicating “for this SNPN” is sent to the UE. AMF is one of the network functions of 5G Core Network (5GC). AMF includes, for example, termination of the RAN Control Plane (CP) interface (i.e., N2 interface), registration management, connection management, and mobility management. Some or all AMF functionalities may be supported in a single instance or entity of AMF.

If the received REGISTRATION REJECT (or SERVICE REJECT) message indicates 5GMM cause #74 (Temporarily not authorized for this SNPN), the UE adds the SNPN identity to the "temporarily forbidden SNPNs" list and starts a timer. The timer is assumed to be not shorter than 60 minutes. Furthermore, the UE enters the 5GMM-DEREGISTERED.PLMN-SEARCH state and performs SNPN selection.

The UE (MS) removes a SNPN from the “temporarily forbidden SNPNs” list if any of the following conditions are true:
- There is a successful Location Registration (LR) following manual SNPN selection by the user;
- A specific timer of not shorter than 60 minutes expires;
- the UE (MS) is switched off; or - the entry regarding the SNPN identity of the SNPN in the "list of subscriber data" is updated.

3GPP TR 23.734 V16.2.0 (2019-06) “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancement of 5G System (5GS) for vertical and Local Area Network (LAN) services(Release 16)”, June 2019 3GPP TS 23.501 V16.1.0 (2019-06) “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 16)”, June 2019 3GPP TS 23.122 V16.2.0 (2019-06) “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode (Release 16)”, June 2019 3GPP TS 24.501 V16.1.0 (2019-06) “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 16)”, June 2019 Ericsson, Qualcomm Incorporated, “Lists of temporarily and permanently forbidden SNPNs” , C1-194768, 3GPP TSG-CT WG1 Meeting #119, Wroclaw, Poland, 26-30 August 2019 Nokia, Nokia Shanghai Bell, “Network Identifier for SNPN”, C4-193815, 3GPP TSG-CT WG4 Meeting #93, Wroclaw, Poland, 26-30 August 2019

As mentioned above, according to previous agreements for SNPNs, a UE in automatic SNPN selection mode cannot be activated by the user switching from automatic SNPN selection mode to manual SNPN selection mode, powering off the UE (MS), or “ If the entries in the "list of subscriber data" are not updated, the registration procedure for SNPNs included in the "temporarily forbidden SNPNs" list cannot be performed until a timer of at least 60 minutes has expired.

SNPN identity may be a non-unique combination of PLMN ID and locally managed NID. Therefore, a situation may arise where different SNPNs operated by different SNPN operators are identified by the same SNPN identity. As an example, consider a case where SNPN #1 and SNPN #2 operated by different SNPN operators are identified by the same SNPN identity. In this case, even if the UE reads the SNPN identity from the system information broadcast by the NG-RAN, it cannot know which SNPN (i.e., SNPN #1 or SNPN #2) the SNPN identity is associated with. I can't.

Thus, for example, if a UE configured with a "list of subscriber data" that includes an entry corresponding to SNPN #2 but not an entry corresponding to SNPN #1 is sent from an NG-RAN providing access to SNPN #1, It may receive the broadcast system information and perform automatic SNPN selection, thereby sending a REGISTRATION REQUEST (or SERVICE REQUEST) message to SNPN #1. In this case, the AMF associated with SNPN #1 may send a REGISTRATION REJECT (or SERVICE REJECT) message to the UE indicating 5GMM cause #74 (Temporarily not authorized for this SNPN). In response to receiving this REGISTRATION REJECT (or SERVICE REJECT) message, the UE adds the SNPN identity to the "temporarily forbidden SNPNs" list and starts a specific timer of 60 minutes or more. Then, even if the UE moves and enters the coverage of the NG-RAN providing access to SNPN #2, the user's switching from automatic SNPN selection mode to manual SNPN selection mode, the power supply of the UE (MS) If it is turned off or the "list of subscriber data" entry is not updated, the UE cannot start the registration procedure to SNPN #2 until the timer expires.

However, if the UE moves and is expected to come within the coverage of the NG-RAN providing access to SNPN #2, the UE should preferably be able to remove that SNPN identity from the "temporarily forbidden SNPNs" list. Maybe. This allows the UE to promptly start the registration procedure to SNPN #2.

One of the objectives that embodiments disclosed herein seek to achieve is to enable wireless terminals to remove entries from the list of temporarily forbidden private (or local) cellular networks (e.g., SNPNs). An object of the present invention is to provide an apparatus, method, and program that contribute to enabling a wireless terminal (e.g., UE) to perform actions in response to the establishment of new conditions related to the movement of the (e.g., UE). It should be noted that this objective is only one of the objectives that the embodiments disclosed herein seek to achieve. Other objects or objects and novel features will become apparent from the description of this specification or the accompanying drawings.

In a first aspect, the wireless terminal manages a list of temporarily prohibited private cellular networks, selects a private cellular network based on one or more selection criteria, and accesses the selected network. configured to attempt to register. The one or more selection conditions include the condition that the selected private cellular network is not included in the list. The wireless terminal sends a rejection message to a network to which the wireless terminal is associated with the first private cellular network to temporarily prevent the wireless terminal from selecting and registering with the first private cellular network. Storing the first private cellular network in the list if the wireless terminal receives a registration request message or a service request message from the core network after sending it to the core network. Further, the wireless terminal is configured to determine whether the wireless characteristics of the wireless access network providing access to the first private cellular network are the same as the wireless characteristics of the wireless access network that previously provided access to the first private cellular network when the registration request or service request message was rejected. If the characteristics are different, the first private cellular network is removed from the list.

In a second aspect, a method performed by a wireless terminal includes managing a list of temporarily prohibited private cellular networks and selecting a private cellular network based on one or more selection criteria; and attempting to register with the selected network. The one or more selection conditions include the condition that the selected private cellular network is not included in the list. Furthermore, said managing:
(a) the wireless terminal transmits a rejection message to a registration request associated with the first private cellular network to temporarily prevent the wireless terminal from selecting and registering with the first private cellular network; (b) storing the first private cellular network in the list if the wireless terminal receives a message or service request message from the core network after transmitting it to the core network; and (b) storing the first private cellular network in the list. - the first private removing a cellular network from said list;
including.

In a third aspect, the core network node receives a registration request message or a service request message associated with a first private cellular network from a wireless terminal, and if subscriber information for the wireless terminal does not exist. , configured to send a rejection message to the wireless terminal to temporarily prevent the wireless terminal from selecting and registering with a first private cellular network. The rejection message includes an information element indicating a first condition for implementing or lifting the temporary restriction of selection and registration of the first private cellular network.

In a fourth aspect, a method performed by a core network node includes: (a) receiving a registration request message or a service request message associated with a first private cellular network from a wireless terminal; sending a rejection message to the wireless terminal to temporarily prevent the wireless terminal from selecting and registering with a first private cellular network if subscriber information for the terminal does not exist; including. The rejection message includes an information element indicating a first condition for implementing or lifting the temporary restriction of selection and registration of the first private cellular network.

In a fifth aspect, the program includes a group of instructions (software code) for causing the computer to perform the method according to the second or fourth aspect described above when the program is read into the computer.

According to the above-mentioned aspects, the deletion of an entry from the list of temporarily prohibited private (or local) cellular networks (e.g., SNPNs) is determined by the fulfillment of new conditions related to the movement of a wireless terminal (e.g., UE). It is possible to provide an apparatus, method, and program that contribute to enabling a wireless terminal (e.g., UE) to perform operations according to the following.

FIG. 1 is a diagram illustrating a configuration example of a cellular network according to an embodiment. It is a flowchart which shows an example of operation of UE concerning an embodiment. It is a flowchart which shows an example of operation of UE concerning an embodiment. It is a flowchart which shows an example of operation of UE concerning an embodiment. FIG. 3 is a sequence diagram showing an example of operations of the UE and AMF according to the embodiment. It is a flowchart which shows an example of operation of UE concerning an embodiment. It is a flowchart which shows an example of operation of UE concerning an embodiment. FIG. 3 is a sequence diagram showing an example of operations of the UE and AMF according to the embodiment. It is a flowchart which shows an example of operation of UE concerning an embodiment. It is a flowchart which shows an example of operation of UE concerning an embodiment. It is a flowchart which shows an example of operation of UE concerning an embodiment. FIG. 2 is a block diagram illustrating a configuration example of a UE according to an embodiment. FIG. 2 is a block diagram showing a configuration example of an AMF according to an embodiment.

Below, specific embodiments will be described in detail with reference to the drawings. In each drawing, the same or corresponding elements are denoted by the same reference numerals, and for clarity of explanation, redundant explanation will be omitted as necessary.

A plurality of embodiments described below can be implemented independently or in appropriate combinations. These multiple embodiments have novel features that are different from each other. Therefore, these multiple embodiments contribute to solving mutually different objectives or problems, and contribute to producing mutually different effects.

A plurality of embodiments shown below will be described with a 3GPP fifth generation mobile communication system (5G system (5GS)) as the main target. However, these embodiments may be applied to other cellular communication systems that support private (or local) cellular networks similar to 3GPP's non-public network (NPN).

<First embodiment>
FIG. 1 shows an example of the configuration of a cellular network according to this embodiment. The wireless terminal (UE) 1 is an SNPN-enabled UE, and a list of subscriber data 11 is set. List of subscriber data 11 includes zero or more entries. Each entry in the list of subscriber data 11 includes a subscriber identifier, credentials, and SNPN identity. The Subscriber identifier may be in the form of a 5G Subscription Permanent Identifier (SUPI).

NG-RAN nodes 21 and 22 provide access to one or more SNPNs. NG-RAN nodes 21 and 22 may be 5G gNBs. In the example of FIG. 1, the NG-RAN node 21 provides access to multiple SNPNs including SNPN #1 and SNPN #2. That is, the NG-RAN node 21 is shared by a plurality of SNPNs including SNPNs #1 and #2. In other words, the NG-RAN node 21 belongs to multiple SNPNs including SNPNs #1 and #2. In the example of FIG. 1, SNPNs #1 and #2 are associated with different 5G Core Networks (5GCs) 31 and 32, respectively, and the NG-RAN node 21 is connected to the 5GCs 31 and 32. However, in some implementations different SNPNs (or SNPN identities) may be associated with the same 5GC.

On the other hand, the NG-RAN node 22 provides access to multiple SNPNs including SNPN #3 and SNPN #4. SNPNs #3 and #4 are associated with different 5G Core Networks (5GCs) 33 and 34, respectively, and the NG-RAN node 22 is connected to the 5GCs 33 and 34. In some implementations, SNPNs #3 and #4 (or their SNPN identities) may be associated with the same 5GC. At least some of the multiple SNPNs to which the NG-RAN node 22 belongs may be included in the multiple SNPNs to which the NG-RAN node 21 belongs.

The NG-RAN node 21 broadcasts system information indicating SNPN identities of a plurality of SNPNs including SNPNs #1 and #2. As already explained, SNPN identity is a combination of PLMN ID and NID. Therefore, the NG-RAN node 21 broadcasts one or more PLMN IDs and a list of NIDs per PLMN ID for identifying multiple SNPNs including SNPNs #1 and #2. Similarly, the NG-RAN node 22 broadcasts one or more PLMN IDs and a list of NIDs per PLMN ID to identify multiple SNPNs including SNPNs #3 and #4. . The system information of each of the NG-RAN nodes 21 and 22 further includes additional parameters (e.g., cell-ID, and one or more Tracking Area Codes (TACs)) per PLMN or per SNPN.

UE1 supports SNPN access mode. When UE1 is set to operate in SNPN access mode, UE1 only selects and registers with SNPN over the air interface (i.e., 5G Uu interface). There are automatic SNPN selection mode and manual SNPN selection mode for the SNPN selection process. For example, when UE 1 operating in SNPN access mode is located within the coverage of NG-RAN node 21, UE 1 receives system information of NG-RAN node 21, and receives one or more PLMN IDs and read the list of NIDs from the system information and consider these in the SNPN selection.

The SNPN-enabled UE 1 manages a temporarily forbidden SNPNs list 12. The SNPN-enabled UE1 may further manage a permanently forbidden SNPNs list (not shown). As already explained, temporarily forbidden SNPNs 12 (and permanently forbidden SNPNs) are used for SNPN selection in automatic SNPN selection mode.

Specifically, in the automatic SNPN selection mode, the UE 1 selects an SNPN that is available, allowed, and specified by the SNPN identity included in the entry of the list of subscriber data 11. Here, the allowable SNPN means an SNPN that is not included in the temporarily forbidden SNPNs list 12 and (if UE1 manages it) also not included in the permanently forbidden SNPNs list. That is, in the automatic SNPN selection process, the UE 1 does not select SNPNs identified by the SNPN identities stored in the temporarily forbidden SNPNs list 12 or the permanently forbidden SNPNs list. UE1 attempts registrations to the selected SNPN. Specifically, UE1 sends a Non-Access Stratum (NAS) message (i.e., REGISTRATION REQUEST message) to AMF in 5GC via the NG-RAN node to request registration to the selected SNPN. .

FIG. 2 is a flowchart illustrating an example of the operation of the UE 1 in the automatic selection mode. In step 201, UE1 manages the temporarily forbidden SNPNs list 12. This management includes adding an entry (SNPN identity) to the list 12 and deleting an entry (SNPN identity) from the list 12. In step 202, the UE 1 selects an SNPN based on one or more selection conditions in automatic SNPN selection mode and attempts to register with the selected SNPN. The one or more selection conditions include at least the condition that the selected SNPN is not included in the temporarily forbidden SNPNs list 12.

A specific example of management of the temporarily forbidden SNPNs list 12 by the UE 1 will be described below with reference to FIGS. 3 and 4. FIG. 3 shows an example of a procedure for adding an entry to the temporarily forbidden SNPNs list 12. In step 301, UE1 sends a REGISTRATION REQUEST message or a SERVICE REQUEST message associated with the first SNPN to the AMF. The REGISTRATION REQUEST message is sent from the UE to the AMF during the registration procedure for initial registration to 5GS services, for 5GS services registration update due to the mobility of UE1, or for periodic 5GS services registration update. be done. On the other hand, the SERVICE REQUEST message is sent from the UE to the AMF in the service request procedure. The service request procedure involves changing the UE's 5GS mobility management (5GMM) mode from 5GMM-IDLE to 5GMM-CONNECTED mode or establishing user-plane resources for PDU sessions. used to request.

In step 302, UE1 receives a REGISTRATION REJECT (or SERVICE REJECT) message from the AMF to temporarily prevent UE1 from selecting and registering the first SNPN. Specifically, the REGISTRATION REJECT (or SERVICE REJECT) message indicates 5GMM cause #74 “Temporarily not authorized for this SNPN”. For example, AMF sends a REGISTRATION indicating 5GMM cause #74 to reject UE1 when the first SNPN is identified by PLMN ID and locally managed NID and there is no subscription for UE1. Send a REJECT (or SERVICE REJECT) message.

In step 303, in response to receiving the REGISTRATION REJECT (or SERVICE REJECT) message indicating 5GMM cause #74, the UE 1 stores the first SNPN (i.e., its SNPN identity) in the Temporarily forbidden SNPNs list 12. . Furthermore, the UE 1 may start a specific timer that is used in the decision to remove the first SNPN from the list 12. The timer may be not shorter than 60 minutes. Furthermore, the UE may enter the 5GMM-DEREGISTERED.PLMN-SEARCH state and perform SNPN selection.

Note that, as already explained, the SNPN identity may be a combination of a non-unique PLMN ID and a locally managed NID. Therefore, a situation may arise where different SNPNs operated by different SNPN operators are identified by the same SNPN identity. As an example, SNPN #1 and SNPN #3 shown in FIG. 1 are identified by the same SNPN identity, and list of subscriber data 11 set in UE 1 includes an entry corresponding to SNPN #3. Consider a case that does not contain an entry corresponding to 1. In this case, UE1 cannot distinguish the SNPN identity of SNPN #1 read from the system information of NG-RAN node 21 from that of SNPN #3. Therefore, the UE 1 may receive the system information of the NG-RAN node 21, perform automatic SNPN selection, and thereby send a REGISTRATION REQUEST (or SERVICE REQUEST) message to SNPN #1.

In this case, the AMF associated with SNPN #1 determines that there is no subscription for SNPN #1 for UE1 and sends a REGISTRATION REJECT (or SERVICE REJECT) message indicating 5GMM cause #74. It may be sent to UE1. In response to receiving this REGISTRATION REJECT (or SERVICE REJECT) message, UE 1 adds the SNPN identity to the temporarily forbidden SNPNs list 12 and starts a specific timer of 60 minutes or more. Then, even if UE1 moves and enters the coverage of NG-RAN node 22 providing access to SNPN #3, the user can switch from automatic to manual SNPN selection mode, power on UE1 (MS) If it is off or the entry in the list of subscriber data 11 is not updated, the UE 1 cannot start the registration procedure to SNPN #3 until the timer expires.

To deal with such a problem, for example, the UE 1 may perform the procedure shown in FIG. 4. In step 401, the UE1 obtains the radio characteristics of the radio access network (i.e., NG-RAN) providing access to the first SNPN. For example, the UE 1 acquires the radio characteristics of the NG-RAN node 22 that broadcasts the SNPN identity that identifies the first RAN. The SNPN identity of the first SNPN is, for example, an SNPN identity common to different SNPN #1 and SNPN #3.

In step 402, UE1 determines whether the obtained radio characteristics are different from those previously when the REGISTRATION REQUEST (or SERVICE REQUEST) message to the first SNPN was rejected. If the obtained radio characteristics are different from those previously when the REGISTRATION REQUEST (or SERVICE REQUEST) message was rejected, the UE1 removes the SNPN identity of the first SNPN from the temporarily forbidden SNPNs list 12.

In some implementations, the NG-RAN radio characteristic used in the procedure of Figure 4 is a tracking area (e.g., tracking area) identifier (e.g., Tracking Area Code (TAC) or Tracking Area Identity (TAI)). May include. Additionally or alternatively, the NG-RAN radio characteristics may include a cell identifier (e.g., Cell-ID). Additionally or alternatively, the NG-RAN radio characteristic may be a frequency band (or frequency range, or spectrum). This may be a frequency band (or frequency range, or spectrum) used for the transmission of downlink signals (e.g., Physical Broadcast Channel (PBCH)) of the NG-RAN node. Additionally or alternatively, the NG-RAN radio characteristic may be a Timing Advance (TA) value. As is well known, timing advances are used to control uplink signal transmission timing. For example, the NG-RAN node estimates an initial TA value from a Physical Random Access Channel (PRACH) received from the UE in a random access procedure, and sends a Timing Advance Command to the UE in a Random Access Response (RAR). Timing Advance Command indicates an index corresponding to the TA value estimated by the NG-RAN node.

It can be said that the radio characteristics of NG-RAN used in the procedure of FIG. 4 are parameters related to the movement of UE1. Therefore, instead of or in addition to the expiration of a specific timer, the UE 1 selects an SNPN (SNPN identity) can be removed.

For example, consider the case described above, in which the UE 1 attempts to register with the SNPN #1 identified by the PLMN ID and the locally managed NID within the coverage of the NG-RAN node 21, but is rejected by the AMF. Following the steps in Figure 4, UE 1 moves into the coverage of NG-RAN node 22 that provides access to SNPN #3 (identified by a PLMN ID common to SNPN #1 and a locally managed NID). If this can be expected, the UE 1 can remove the SNPN identity of the first SNPN (for example, the SNPN identity common to different SNPN #1 and SNPN #3) from the temporarily forbidden SNPNs list 12. Therefore, UE1 can immediately start the registration procedure with SNPN #3 without depending on the expiration of a specific timer.

In the above description, an example was shown in which the UE 1 removes the SNPN identity of the first SNPN from the temporarily forbidden SNPNs list 12 based on differences or changes in the radio characteristics of the NG-RAN. Additionally or alternatively, other parameters related to the movement of the UE 1 may be considered for determining whether to remove the SNPN identity from the temporarily forbidden SNPNs list 12. In some implementations, UE1 may determine whether to remove the SNPN identity of the SNPN from the temporarily forbidden SNPNs list 12 based on internal information of UE1. For example, the geographical location information held by UE1 (e.g., data indicated by the Global Positioning System) indicates the location when the REGISTRATION REQUEST (or SERVICE REQUEST) message to the first SNPN is rejected. , the UE 1 may remove the SNPN identity of the first SNPN from the temporarily forbidden SNPNs list 12, regardless of the radio characteristics of the NG-RAN. With such an operation, the UE 1 can also select the temporarily forbidden SNPNs list 12 in consideration of other parameters related to the movement of the UE 1 (i.e., location information of the UE 1) instead of or in addition to the expiration of a specific timer. SNPN (SNPN identity) can be removed.

<Second embodiment>
This embodiment is directed to UE and AMF operations regarding temporary prohibition of SNPN selection and registration. The configuration example of the cellular network according to this embodiment may be similar to the example shown in FIG. 1.

FIG. 5 shows an example of the operation of the UE 1 and the AMF 500 according to this embodiment. In step 501, UE1 starts a registration request procedure (or service request procedure) to the SNPN and sends a REGISTRATION REQUEST (or SERVICE REQUEST) message. The message reaches the AMF 500 via the NG-RAN node.

In step 502, the AMF 500 sends a REGISTRATION REJECT (or SERVICE REJECT) message to the UE1 to temporarily prevent the UE1 from selecting and registering the SNPN. Specifically, the REGISTRATION REJECT (or SERVICE REJECT) message indicates 5GMM cause #74 “Temporarily not authorized for this SNPN”. For example, when the SNPN is identified by the PLMN ID and the locally managed NID, and there is no subscription information for the UE1, the AMF 500 sends a REGISTRATION REJECT (5GMM cause #74) to reject the UE1. or SERVICE REJECT) message.

Further, in step 502, the AMF 500 includes in the REGISTRATION REJECT (or SERVICE REJECT) message an information element indicating conditions for implementing or canceling the temporary restriction on selection and registration of the SNPN. UE1 receives a REGISTRATION REJECT (or SERVICE REJECT) message that includes 5GMM CAUSE #74 and further includes the information element that indicates the implementation (or cancellation) condition. In response to receiving the message, UE1 adds the SNPN to the temporarily forbidden SNPNs list 12. Further, the UE 1 determines whether or not to remove the SNPN from the temporarily forbidden SNPNs list 12 based on the received implementation condition or release condition.

FIG. 6 shows an example of the operation of the UE 1 to delete an entry from the temporarily forbidden SNPNs list 12. In step 601, the UE 1 determines whether the implementation (or cancellation) conditions specified by the AMF 500 are satisfied. In step 602, the UE 1 removes the SNPN from the temporarily forbidden SNPNs list 12 when the implementation condition is no longer satisfied or when the cancellation condition is satisfied.

In some implementations, the implementation (or deactivation) conditions specified by the AMF 500 may include conditions regarding changes in the radio characteristics of the NG-RAN. In this case, the UE 1 determines whether or not to remove the SNPN from the temporarily forbidden SNPNs list 12 based on the radio characteristics of the NG-RAN. The radio characteristics of NG-RAN are, for example, a location registration area (e.g., tracking area) identifier, a cell identifier (e.g., Cell-ID), a frequency band (or frequency range, or spectrum), or a timing advance value, or Any combination of these may be used. Specifically, the implementation (or release) conditions specified by the AMF 500 may indicate that selection and registration of the SNPN is temporarily prohibited until the UE 1 enters a new tracking area (or cell). . The UE 1 may remove the SNPN from the temporarily forbidden SNPNs list 12 if the acquired radio characteristics are different from those previously when the REGISTRATION REQUEST (or SERVICE REQUEST) message was rejected.

Additionally or alternatively, the implementation (or release) conditions specified by AMF 500 may include conditions regarding changing from automatic SNPN selection mode to manual SNPN selection mode. Specifically, the enforcement (or release) conditions specified by the AMF 500 may indicate that selection and registration of the SNPN is temporarily prohibited until the UE 1 enters manual SNPN selection mode. The UE 1 may remove the SNPN from the temporarily forbidden SNPNs list 12 in response to the change from automatic selection mode to manual selection mode.

Additionally or alternatively, if the implementation (or cancellation) conditions specified by the AMF 500 include conditions regarding changing from automatic SNPN selection mode to manual SNPN selection mode, UE 1 may change the mode from automatic SNPN selection mode to manual SNPN selection mode. It may be changed to SNPN selection mode. For example, as shown in FIG. 7, the UE 1 may determine whether the implementation (or cancellation) conditions specified by the AMF 500 include conditions regarding changing from automatic SNPN selection mode to manual SNPN selection mode. (Step 701). Then, if the implementation (or cancellation) conditions include conditions regarding changing from automatic SNPN selection mode to manual SNPN selection mode, UE1 may enter manual SNPN selection mode (step 702).

Additionally or alternatively, the enforcement (or release) conditions specified by AMF 500 may include conditions regarding the expiration of a particular timer. Specifically, the REGISTRATION REJECT (or SERVICE REJECT) message sent from the AMF 500 may include a timer value. A specific timer controlled by this timer value is used by the UE 1 to determine whether to remove the first SNPN from the list 12 or not. For example, the AMF 500 can prevent frequent reception of REGISTRATION REQUEST (or SERVICE REQUEST) messages from the UE 1 by specifying a long timer value (large numerical value).

If the enforcement (or release) conditions specified by the AMF 500 do not include conditions regarding the expiration of a specific timer, the UE 1 operates not to start the specific timer when storing the SNPN in the temporarily forbidden SNPNs list 12. Good too.

According to the operations of the UE 1 and the AMF 500 of this embodiment, the AMF 500 can explicitly instruct the UE 1 about the conditions for implementing or canceling the temporary prohibition of SNPN selection and registration.

<Third embodiment>
This embodiment is directed to UE and AMF operations regarding temporary prohibition of SNPN selection and registration. The configuration example of the cellular network according to this embodiment may be similar to the example shown in FIG. 1.

FIG. 8 shows an example of the operation of the UE 1 and the AMF 800 according to this embodiment. In step 801, UE1 starts a registration request procedure (or service request procedure) to the SNPN and sends a REGISTRATION REQUEST (or SERVICE REQUEST) message. The message reaches AMF 800 via the NG-RAN node.

In step 802, the AMF 800 sends a REGISTRATION REJECT (or SERVICE REJECT) message to the UE1 to temporarily prevent the UE1 from selecting and registering the SNPN. Specifically, the REGISTRATION REJECT (or SERVICE REJECT) message indicates 5GMM cause #74 “Temporarily not authorized for this SNPN”. For example, when the SNPN is identified by the PLMN ID and the locally managed NID, and there is no subscription information for the UE1, the AMF 800 sends a REGISTRATION REJECT (5GMM cause #74) to reject the UE1. or SERVICE REJECT) message. The REGISTRATION REJECT (or SERVICE REJECT) message may include a timer value. A specific timer controlled by this timer value is used by the UE 1 to determine whether to remove the first SNPN from the list 12 or not. For example, the AMF 500 can prevent frequent reception of REGISTRATION REQUEST (or SERVICE REQUEST) messages from the UE 1 by specifying a long timer value (large numerical value).

Furthermore, in step 802, the AMF 800 includes human-readable information in the REGISTRATION REJECT (or SERVICE REJECT) message to be displayed to the user. UE1 receives a REGISTRATION REJECT (or SERVICE REJECT) message that includes 5GMM CAUSE #74 and further includes human-readable information. In response to receiving the message, UE1 adds the SNPN to the temporarily forbidden SNPNs list 12. Furthermore, UE1 enters manual SNPN selection mode if the REGISTRATION REJECT (or SERVICE REJECT) message includes human-readable information.

FIG. 9 shows an example of the operation of the UE 1 according to this embodiment. In step 901, UE1 receives a REGISTRATION REJECT (or SERVICE REJECT) message from the AMF to temporarily prevent UE1 from selecting and registering a first SNPN. The REGISTRATION REJECT (or SERVICE REJECT) message may indicate 5GMM cause #74. In step 902, UE1 adds the first SNPN to the temporarily forbidden SNPNs list 12. In step 903, if the REGISTRATION REJECT (or SERVICE REJECT) message includes human-readable information, the UE1 enters manual SNPN selection mode.

After entering manual SNPN selection mode, UE1 may provide the human readable information received from AMF 800 to the user. Specifically, UE1 may display human readable information on a display screen installed in UE1. Human readable information can be used for manual SNPN selection (NID selection) by the user.

According to the operations of the UE 1 and the AMF 800 of this embodiment, the AMF 800 can forcibly change the UE 1 to manual SNPN selection mode when temporarily prohibiting the UE 1 from selecting and registering an SNPN. In addition, the AMF 800 can provide the UE 1 with human-readable information that can be used for manual SNPN selection (NID selection) by the user. Manual SNPN selection by the user in consideration of human-readable information can contribute to avoiding unfavorable (automatic) SNPN selection due to collision of SNPN identities identified by locally managed NIDs.

<Fourth embodiment>
This embodiment is directed to UE operations regarding temporary prohibition of SNPN selection and registration. The configuration example of the cellular network according to this embodiment may be similar to the example shown in FIG. 1.

FIG. 10 shows an example of the operation of the UE 1 according to this embodiment. Steps 1001-1003 are similar to steps 301-303 in FIG. That is, the AMF rejects the registration request or service request for the first SNPN from the UE 1, and the UE 1 adds the first SNPN to the temporarily forbidden SNPNs list 12. In step 1004, if UE1 is in automatic SNPN selection mode and has previously been allowed to register with the first SNPN and has received a human-readable network name associated with the first SNPN; UE1 enters manual SNPN selection mode.

As previously discussed, NG-RAN nodes may optionally broadcast a human-readable network name per NID. Human-readable network names for each NID are used only for manual SNPN selection. The UE 1 receives system information broadcast from the NG-RAN nodes prior to a registration request or service request to the first SNPN, and determines the SNPN identity (PLMN ID and NID) corresponding to the first SNPN from the system information. Read out. If the system information further includes a human-readable network name associated with the NID of the first SNPN, UE1 retains this.

According to the operation of the UE 1 in this embodiment, the UE 1 can enter the manual SNPN selection mode when there is a possibility that a collision of the SNPN identity identified by the locally managed NID has occurred. Manual SNPN selection by the user considering the human-readable network name can contribute to avoiding unfavorable (automatic) SNPN selection due to collision of SNPN identities identified by locally managed NIDs.

<Fifth embodiment>
This embodiment is directed to SNPN selection by the UE. The configuration example of the cellular network according to this embodiment may be similar to the example shown in FIG. 1.

FIG. 11 shows an example of the operation of the UE 1 according to this embodiment. In step 1101, UE1 is in automatic SNPN selection mode and selects an SNPN. In step 1102, the UE1 enters manual SNPN selection mode if it receives the SNPN identity (or NID) of the selected SNPN from multiple cells simultaneously.

According to the operation of the UE 1 in this embodiment, the UE 1 can enter the manual SNPN selection mode when there is a possibility that a collision of the SNPN identity identified by the locally managed NID has occurred. Manual SNPN selection by the user can contribute to avoiding unfavorable (automatic) SNPN selection due to collision of SNPN identities identified by locally managed NIDs.

Next, configuration examples of the UE and AMF according to the plurality of embodiments described above will be described below. FIG. 12 is a block diagram showing an example of the configuration of UE1. Radio Frequency (RF) transceiver 1201 performs analog RF signal processing to communicate with NG-RAN nodes. RF transceiver 1201 may include multiple transceivers. Analog RF signal processing performed by RF transceiver 1201 includes frequency upconversion, frequency downconversion, and amplification. RF transceiver 1201 is coupled with antenna array 1202 and baseband processor 1203. RF transceiver 1201 receives modulation symbol data (or OFDM symbol data) from baseband processor 1203, generates a transmit RF signal, and provides the transmit RF signal to antenna array 1202. Further, RF transceiver 1201 generates a baseband reception signal based on the reception RF signal received by antenna array 1202 and supplies this to baseband processor 1203. RF transceiver 1201 may include analog beamformer circuitry for beamforming. The analog beamformer circuit includes, for example, multiple phase shifters and multiple power amplifiers.

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

For example, digital baseband signal processing by the baseband processor 1203 includes a Service Data Adaptation Protocol (SDAP) layer, a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer signal processing may also be included. Further, the control plane processing by the baseband processor 1203 may include processing of a Non-Access Stratum (NAS) protocol, a Radio Resource Control (RRC) protocol, and a MAC Control Elements (CEs).

Baseband processor 1203 may perform multiple input multiple output (MIMO) encoding and precoding for beamforming.

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

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

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

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

Memory 1206 may store one or more software modules (computer programs) 1207 that include instructions and data for performing processing by UE 1 as described in the embodiments above. In some implementations, the baseband processor 1203 or the application processor 1204 is configured to read and execute the software module 1207 from the memory 1206 to perform the processing of the UE1 illustrated in the above embodiments. may be done.

Memory 1206 may be used to store data for SNPN selection described in the embodiments above (e.g., list of subscriber data 11, temporarily forbidden SNPNs list 12, and permanently forbidden SNPNs list). .

Note that the control plane processing and operations performed by the UE 1 described in the above embodiments are performed by other elements other than the RF transceiver 1201 and the antenna array 1202, that is, at least one of the baseband processor 1203 and the application processor 1204 and the software module 1207. This can be realized by a memory 1206 that stores .

FIG. 13 shows a configuration example of an AMF (e.g., AMF500). Referring to FIG. 13, AMF includes a network interface 1301, a processor 1302, and a memory 1303. Network interface 1301 is used, for example, to communicate with NG-RAN nodes as well as with other control plane functions or nodes within the 5GC. Other control plane functions or nodes within 5GC include, for example, Unified Data Management (UDM), Network Exposure Function (NEF), and Session Management Function (SMF). Network interface 1301 may include, for example, a network interface card (NIC) compliant with the IEEE 802.3 series.

Processor 1302 may be, for example, a microprocessor, Micro Processing Unit (MPU), or Central Processing Unit (CPU). Processor 1302 may include multiple processors.

Memory 1303 is composed of volatile memory and nonvolatile memory. Memory 1303 may include multiple physically independent memory devices. Volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM) or a combination thereof. Non-volatile memory is masked Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or a hard disk drive, or any combination thereof. Memory 1303 may include storage located remotely from processor 1302. In this case, processor 1302 may access memory 1303 via network interface 1301 or an I/O interface (not shown).

Memory 1303 may store one or more software modules (computer programs) 1304 containing instructions and data for performing processing by the AMF described in the embodiments above. In some implementations, processor 1302 may be configured to read and execute the software module 1304 from memory 1303 to perform the AMF processing described in the embodiments above.

A wireless terminal (User Equipment (UE)) in this specification is an entity connected to a network via a wireless interface. The wireless terminal (UE) in this specification is not limited to a dedicated communication device, but may be any of the following devices that have the communication function of the wireless terminal (UE) described in this specification. It's okay.

``User Equipment (UE)'' (as used in 3GPP), ``mobile station'', ``mobile terminal'', ``mobile device'', and ``wireless The terms "wireless device" are generally intended to be synonymous with each other. UE is a standalone mobile station such as a terminal, mobile phone, smartphone, tablet, cellular IoT terminal, IoT device, etc. The terms "UE" and "wireless terminal" also encompass devices that are stationary for long periods of time.

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

UE is, for example, a transportation device (for example, a vehicle, a car, a motorcycle, a bicycle, a train, a bus, a cart, a rickshaw, a ship and other watercraft, an airplane, a rocket, an artificial satellite, a drone, a balloon, etc.). There may be.

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

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

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

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

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

The UE may be, for example, a device or a part thereof that provides the following applications, services, and solutions in the Internet of Things (IoT) using wired and wireless communication technologies. IoT devices (or things) include appropriate electronics, software, sensors, network connections, etc. that enable the devices to collect and exchange data with each other and with other communicating devices. An IoT device may be an automated appliance that follows stored software instructions in internal memory. IoT devices may operate without the need for human supervision or interaction. An IoT device may be a device that is installed for an extended period of time and/or may remain in an inactive state for an extended period of time. IoT devices can be implemented as part of stationary equipment. IoT devices can be embedded in non-stationary equipment (such as vehicles) or attached to animals or people to be monitored/tracked. IoT technology can be implemented on any communication device that can be connected to a communication network that sends and receives data without control by human input or software instructions stored in memory. IoT devices are also called Machine Type Communication (MTC) devices, Machine to Machine (M2M) communication devices, or Narrow Band-IoT (NB-IoT) UEs.

A UE may support one or more IoT or MTC applications.

Some examples of MTC applications are enumerated in the list provided in 3GPP TS22.368 V13.2.0 (2017-01-13) Annex B, the contents of which are incorporated herein by reference. This list is not exhaustive and is intended to represent exemplary MTC applications. In this list, the Service Areas of MTC applications are Security, Tracking & Tracing, Payment, Health, Remote Maintenance/Control, Includes metering and consumer devices.

Examples of MTC applications related to security are Surveillance systems, Backup for landline, Control of physical access (e.g. to buildings), and Vehicle /Includes Car/driver security.

Examples of MTC applications for track and trace are Fleet Management, Order Management, Telematics Insurance: Pay as you drive (PAYD), Asset Tracking, and Navigation. (Navigation), Traffic information, Road tolling, and Road traffic optimization/steering.

Examples of MTC applications related to payments include points of sales (POS), vending machines, and gaming machines.

Examples of health-related MTC applications are Monitoring vital signs, Supporting the aged or handicapped, Web Access Telemedicine points, and Remote diagnostics. including.

Examples of MTC applications for remote maintenance/control are Sensors, Lighting, Pumps, Valves, Elevator control, Vending machine control, and Vehicles. Including vehicle diagnostics.

Examples of MTC applications related to metering are Power, Gas
Includes Water, Heating, Grid control, and Industrial metering.

Examples of MTC applications for consumer devices include digital photo frames, digital cameras, and electronic books (ebooks).

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

The categories of UEs described above are merely examples of applications of the technical ideas and embodiments described herein. The UE herein is not limited to these examples, and those skilled in the art can make various changes thereto.

The embodiments described above are merely examples regarding the application of the technical idea obtained by the inventor of the present invention. It goes without saying that the technical idea is not limited to the above-described embodiments, and can be modified in various ways.

For example, some or all of the above embodiments may be described as in the following additional notes, but are not limited to the following.

(Additional note 1)
A wireless terminal,
a first means for managing a list of temporarily prohibited private cellular networks;
second means for selecting a private cellular network based on one or more selection criteria and attempting to register with the selected network;
Equipped with
the one or more selection conditions comprising the condition that the selected private cellular network is not included in the list;
The first means is:
a registration request message or service associated with the first private cellular network; storing the first private cellular network in the list if the wireless terminal receives a request message from the core network after sending the request message to the core network;
the radio characteristics of the radio access network providing access to the first private cellular network are different from the radio characteristics of the previous radio access network at the time the registration request or service request message was rejected; removing a first private cellular network from said list;
A wireless terminal configured as follows.

(Additional note 2)
The wireless characteristics include a location registration area identifier;
The wireless terminal described in Appendix 1.

(Additional note 3)
The location registration area is a tracking area,
The identifier of the location registration area includes a Tracking Area Code (TAC).
The wireless terminal described in Appendix 2.

(Additional note 4)
the radio characteristics include a cell identifier;
The wireless terminal according to any one of Supplementary Notes 1 to 3.

(Appendix 5)
The wireless characteristics include frequency bands;
The wireless terminal according to any one of Supplementary Notes 1 to 4.

(Appendix 6)
the radio characteristics include a timing advance value;
The wireless terminal according to any one of Supplementary Notes 1 to 5.

(Appendix 7)
The rejection message includes an information element indicating a first condition for implementing or lifting a temporary restriction on selection and registration of the first private cellular network;
The first means is configured to determine whether to remove the first private cellular network from the list based on the first condition.
The wireless terminal according to any one of Supplementary Notes 1 to 6.

(Appendix 8)
The first means determines whether to remove the first private cellular network from the list based on the wireless characteristics when the first condition includes a condition regarding a change in the wireless characteristics. It is configured as follows.
The wireless terminal described in Appendix 7.

(Appendix 9)
The first means is configured not to start the timer when storing the first private cellular network in the list if the first condition does not include a condition regarding expiration of the timer. ,
The wireless terminal according to appendix 7 or 8.

(Appendix 10)
The second means is configured to select a private cellular network based on the one or more selection conditions when the wireless terminal is in an automatic selection mode;
said second means are configured to attempt to register with a private cellular network selected by a user when said wireless terminal is in manual selection mode;
The wireless terminal further comprises means for changing the wireless terminal from the automatic selection mode to the manual selection mode when the first condition includes a condition regarding changing from the automatic selection mode to the manual selection mode.
The wireless terminal according to any one of Supplementary Notes 7 to 9.

(Appendix 11)
The second means is configured to select a private cellular network based on the one or more selection conditions when the wireless terminal is in an automatic selection mode;
said second means are configured to attempt to register with a private cellular network selected by a user when said wireless terminal is in manual selection mode;
The wireless terminal changes the wireless terminal from the automatic selection mode to the manual selection mode when the wireless terminal is in the automatic selection mode and the rejection message includes human-readable information for display to a user. further equipped with means;
The wireless terminal according to any one of Supplementary Notes 1 to 6.

(Appendix 12)
The second means is configured to select a private cellular network based on the one or more selection conditions when the wireless terminal is in an automatic selection mode;
said second means are configured to attempt to register with a private cellular network selected by a user when said wireless terminal is in manual selection mode;
the wireless terminal is in the automatic selection mode, receives the rejection message, has previously been allowed to register with the first private cellular network, and further comprising means for changing the wireless terminal from the automatic selection mode to the manual selection mode when receiving a human-readable network name associated with a network;
The wireless terminal according to any one of Supplementary Notes 1 to 6.

(Appendix 13)
The second means is configured to select a private cellular network based on the one or more selection conditions when the wireless terminal is in an automatic selection mode;
said second means are configured to attempt to register with a private cellular network selected by a user when said wireless terminal is in manual selection mode;
means for changing the wireless terminal from the automatic selection mode to the manual selection mode when the wireless terminal is in the automatic selection mode and receives the same private cellular network identifier from multiple cells simultaneously; further comprising,
The wireless terminal according to any one of Supplementary Notes 1 to 6.

(Appendix 14)
A method performed by a wireless terminal, the method comprising:
managing a list of temporarily prohibited private cellular networks; and selecting a private cellular network based on one or more selection criteria and attempting to register with the selected network;
Equipped with
the one or more selection conditions comprising the condition that the selected private cellular network is not included in the list;
The said managing is
a registration request message or service associated with the first private cellular network; storing the first private cellular network in the list if the wireless terminal receives from the core network after sending a request message to the core network; and accessing the first private cellular network. the first private cellular network from the list if the radio characteristics of the radio access network providing the first private cellular network differ from the radio characteristics of the previous radio access network at the time the registration request or service request message was rejected; to remove,
A method of providing.

(Appendix 15)
The wireless characteristics include a location registration area identifier;
The method described in Appendix 14.

(Appendix 16)
The location registration area is a tracking area,
The identifier of the location registration area includes a Tracking Area Code (TAC).
The method described in Appendix 15.

(Appendix 17)
the radio characteristics include a cell identifier;
The method according to any one of Supplementary Notes 14 to 16.

(Appendix 18)
The wireless characteristics include frequency bands;
The method according to any one of Supplementary Notes 14 to 17.

(Appendix 19)
the radio characteristics include a timing advance value;
The method according to any one of Supplementary Notes 14 to 18.

(Additional note 20)
The rejection message includes an information element indicating a first condition for implementing or lifting a temporary restriction on selection and registration of the first private cellular network;
The managing comprises determining whether to remove the first private cellular network from the list based on the first condition.
The method according to any one of Supplementary Notes 14 to 19.

(Additional note 21)
The managing includes determining whether to remove the first private cellular network from the list based on the wireless characteristics when the first condition includes a condition regarding a change in the wireless characteristics. Equipped with
The method described in Appendix 20.

(Additional note 22)
The managing comprises not starting the timer when storing the first private cellular network in the list if the first condition does not include a condition for expiration of a timer.
The method described in Appendix 20 or 21.

(Additional note 23)
A program for causing a computer to perform a method performed by a wireless terminal,
The method includes:
managing a list of temporarily prohibited private cellular networks; and selecting a private cellular network based on one or more selection criteria and attempting to register with the selected network;
Equipped with
the one or more selection conditions comprising the condition that the selected private cellular network is not included in the list;
The said managing is
a registration request message or service associated with the first private cellular network; storing the first private cellular network in the list if the wireless terminal receives from the core network after sending a request message to the core network; and accessing the first private cellular network. the first private cellular network from the list if the radio characteristics of the radio access network providing the first private cellular network differ from the radio characteristics of the previous radio access network at the time the registration request or service request message was rejected; to remove,
A program with.

(Additional note 24)
A core network node,
first means for receiving a registration request message or a service request message associated with a first private cellular network from a wireless terminal;
sending a rejection message to the wireless terminal to temporarily prevent the wireless terminal from selecting and registering with a first private cellular network if subscriber information for the wireless terminal does not exist; a second means;
Equipped with
The rejection message includes an information element indicating a first condition for implementing or lifting the temporary restriction of selection and registration of the first private cellular network.
Core network node.

(Additional note 25)
the rejection message causes the wireless terminal to store the first private cellular network in a list of temporarily prohibited private cellular networks;
the rejection message causes the wireless terminal to determine whether to remove the first private cellular network from the list based on the first condition;
Core network node according to appendix 24.

(Additional note 26)
The first condition includes a condition regarding a change in radio characteristics of a radio access network providing access to the first private cellular network;
the rejection message causes the wireless terminal to determine whether to remove the first private cellular network from the list based on the wireless characteristics;
Core network node according to appendix 25.

(Additional note 27)
The rejection message causes the wireless terminal not to start the timer when storing the first private cellular network in the list if the first condition does not include a condition for expiration of a timer. ,
The core network node according to appendix 25 or 26.

(Additional note 28)
The first condition includes a condition regarding changing from automatic selection mode to manual selection mode,
the rejection message causes the wireless terminal to change from the automatic selection mode to the manual selection mode;
The automatic selection mode is an operating mode in which the wireless terminal automatically attempts to register with a selected private cellular network;
The manual selection mode is an operating mode that attempts to register with a private cellular network selected by the user;
Core network node according to appendix 24.

(Additional note 29)
A method performed by a core network node, the method comprising:
receiving a registration request message or a service request message associated with a first private cellular network from a wireless terminal; and if subscriber information for the wireless terminal does not exist, the wireless terminal - sending a rejection message to the wireless terminal to temporarily prevent it from selecting and registering with a cellular network;
Equipped with
The rejection message includes an information element indicating a first condition for implementing or lifting the temporary restriction of selection and registration of the first private cellular network.
Method.

(Additional note 30)
A program for causing a computer to perform a method performed by a core network node, the program comprising:
The method includes:
receiving a registration request message or a service request message associated with a first private cellular network from a wireless terminal; and if subscriber information for the wireless terminal does not exist, the wireless terminal - sending a rejection message to the wireless terminal to temporarily prevent it from selecting and registering with a cellular network;
Equipped with
The rejection message includes an information element indicating a first condition for implementing or lifting the temporary restriction of selection and registration of the first private cellular network.
program.

(Appendix A)
A wireless terminal,
a first means for managing a list of temporarily prohibited private cellular networks;
a second means for attempting to register with the selected private cellular network;
Equipped with
The second means is configured to select a private cellular network based on one or more selection conditions when the wireless terminal is in an automatic selection mode;
the one or more selection conditions comprising the condition that the selected private cellular network is not included in the list;
said second means are configured to attempt to register with a private cellular network selected by a user when said wireless terminal is in manual selection mode;
The first means associates a rejection message with the first private cellular network by the wireless terminal to temporarily prevent the wireless terminal from selecting and registering with the first private cellular network. configured to store the first private cellular network in the list if the wireless terminal receives a registered registration request message or a service request message from the core network after transmitting the registered registration request message or service request message to the core network;
The wireless terminal changes the wireless terminal from the automatic selection mode to the manual selection mode when the wireless terminal is in the automatic selection mode and the rejection message includes human-readable information for display to a user. further equipped with means;
wireless terminal.

(Appendix B)
A wireless terminal,
a first means for managing a list of temporarily prohibited private cellular networks;
a second means for attempting to register with the selected private cellular network;
Equipped with
The second means is configured to select a private cellular network based on one or more selection conditions when the wireless terminal is in an automatic selection mode;
the one or more selection conditions comprising the condition that the selected private cellular network is not included in the list;
said second means are configured to attempt to register with a private cellular network selected by a user when said wireless terminal is in manual selection mode;
The first means associates a rejection message with the first private cellular network by the wireless terminal to temporarily prevent the wireless terminal from selecting and registering with the first private cellular network. configured to store the first private cellular network in the list if the wireless terminal receives a registered registration request message or a service request message from the core network after transmitting the registered registration request message or service request message to the core network;
the wireless terminal is in the automatic selection mode, receives the rejection message, has previously been allowed to register with the first private cellular network, and further comprising means for changing the wireless terminal from the automatic selection mode to the manual selection mode when receiving a human-readable network name associated with a network;
wireless terminal.

(Appendix C)
A wireless terminal,
a first means for attempting to register with the selected private cellular network;
the first means is configured to attempt registration with a private cellular network selected by the wireless terminal based on one or more selection conditions when the wireless terminal is in an automatic selection mode;
the first means are configured to attempt to register with a private cellular network selected by a user when the wireless terminal is in manual selection mode;
means for changing the wireless terminal from the automatic selection mode to the manual selection mode when the wireless terminal is in the automatic selection mode and receives the same private cellular network identifier from multiple cells simultaneously; further comprising,
wireless terminal.

1 U.E.
11 list of subscriber data
12 temporarily forbidden SNPNs list 21, 22 NG-RAN node
31-34 5GC
500, 800 AMF
1203 Baseband processor 1204 Application processor 1206 Memory 1207 Modules
1302 Processor 1303 Memory 1304 Modules

Claims (10)

A wireless terminal,
a first means for managing a list of temporarily prohibited private cellular networks;
second means for selecting a private cellular network based on one or more selection criteria and attempting to register with the selected network;
Equipped with
the one or more selection conditions comprising the condition that the selected private cellular network is not included in the list;
The first means is:
a registration request message or service associated with the first private cellular network; storing the first private cellular network in the list if the wireless terminal receives a request message from the core network after sending the request message to the core network;
when the radio characteristics of the radio access network providing access to the first private cellular network are different from the radio characteristics of the radio access network at the time the registration request or service request message was rejected; 1 private cellular network from said list;
A wireless terminal configured as follows. The wireless characteristics include a location registration area identifier;
The wireless terminal according to claim 1. The location registration area is a tracking area,
The identifier of the location registration area includes a Tracking Area Code (TAC).
The wireless terminal according to claim 2. the radio characteristics include a cell identifier;
The wireless terminal according to any one of claims 1 to 3. The wireless characteristics include frequency bands;
The wireless terminal according to any one of claims 1 to 4. the radio characteristics include a timing advance value;
The wireless terminal according to any one of claims 1 to 5. The rejection message includes an information element indicating a first condition for implementing or lifting a temporary restriction on selection and registration of the first private cellular network;
The first means is configured to determine whether to remove the first private cellular network from the list based on the first condition.
The wireless terminal according to any one of claims 1 to 6. The first means determines whether to remove the first private cellular network from the list based on the wireless characteristics when the first condition includes a condition regarding a change in the wireless characteristics. It is configured as follows.
The wireless terminal according to claim 7. A method performed by a wireless terminal, the method comprising:
managing a list of temporarily prohibited private cellular networks; and selecting a private cellular network based on one or more selection criteria and attempting to register with the selected network;
Equipped with
the one or more selection conditions comprising the condition that the selected private cellular network is not included in the list;
The said managing is
a registration request message or service associated with the first private cellular network; storing the first private cellular network in the list if the wireless terminal receives from the core network after sending a request message to the core network; and accessing the first private cellular network. removing the first private cellular network from the list if the radio characteristics of the radio access network providing the service differ from the radio characteristics of the radio access network at the time the registration request or service request message was rejected; thing,
A method of providing. A core network node,
first means for receiving a registration request message or a service request message associated with a first private cellular network from a wireless terminal;
sending a rejection message to the wireless terminal to temporarily prevent the wireless terminal from selecting and registering with a first private cellular network if subscriber information for the wireless terminal does not exist; a second means;
Equipped with
The rejection message includes an information element indicating a first condition for implementing or lifting a temporary restriction on selection and registration of the first private cellular network;
the rejection message causes the wireless terminal to store the first private cellular network in a list of temporarily prohibited private cellular networks;
The first condition includes a condition regarding a change in radio characteristics of a radio access network providing access to the first private cellular network;
The rejection message causes the wireless terminal to determine whether to remove the first private cellular network from the list based on a condition regarding the change in radio characteristics.
Core network node.

Images