CN113647148A

CN113647148A - Supporting non-public networks with integrated public networks

Info

Publication number: CN113647148A
Application number: CN201980094192.8A
Authority: CN
Inventors: 梁爽; 李振东
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2019-03-15
Filing date: 2019-03-15
Publication date: 2021-11-12
Also published as: WO2020186387A1

Abstract

To methods, systems, and apparatus for digital wireless communications, and more particularly to methods, systems, and apparatus for techniques related to supporting non-public networks integrated with public networks. In one exemplary aspect, a method of wireless communication includes: sending a first request to a second node requesting information to assist in selecting a network for a terminal, the terminal being associated with a first network and a first access group, the first network being a non-public network, the first access group being associated with a first network node, wherein the first request includes a first access group identifier identifying the first access group associated with the terminal. The method also includes receiving a first response from the second node, the first response including information that assists in selecting a network for a terminal, the terminal associated with a first network and a first access group, the first access group associated with the first network node.

Description

Supporting non-public networks with integrated public networks

Technical Field

This patent document relates generally to wireless communications.

Background

Mobile communication technology is advancing the world towards an increasingly connected and networked society. The rapid growth of mobile communications and advances in technology have resulted in greater demands for capacity and connectivity. Other aspects such as energy consumption, device cost, spectral efficiency, and latency are also important to meet the needs of various communication scenarios. Various techniques are being discussed, including new methods for providing higher quality of service.

Disclosure of Invention

Methods, systems, and apparatus related to digital wireless communications are disclosed herein, and more particularly, techniques related to supporting non-public networks integrated with public networks are disclosed.

In one exemplary aspect, a method of wireless communication includes: sending a first request to a second node requesting information to assist in selecting a network for a terminal, the terminal being associated with a first network and a first access group, the first network being a non-public network, the first access group being associated with a first network node, wherein the first request includes a first access group identifier identifying the first access group associated with the terminal. The method also includes receiving a first response from the second node, the first response including information that assists in selecting a network for a terminal, the terminal associated with a first network and a first access group, the first access group associated with the first network node.

In another exemplary aspect, a wireless communication device comprising a processor is disclosed. The processor is configured to implement the methods described herein.

In yet another exemplary aspect, the various techniques described herein may be implemented as processor executable code and stored on a computer readable program medium.

The details of one or more implementations are set forth in the accompanying drawings, the drawings, and the description below. Other features will be apparent from the description and drawings, and from the claims.

Drawings

FIG. 1 illustrates an example system architecture for supporting a non-public network integrated with a public network.

Fig. 2 illustrates an example non-public network integrated with a public network.

Fig. 3 illustrates an example signaling procedure for generating allowed NSSAIs during a registration procedure.

Fig. 4 shows an example signaling procedure for updating the allow list without changing the AMF.

Fig. 5 shows an example signaling procedure for updating the allow list in case of a change of AMF.

Fig. 6 shows a block diagram of a method of supporting a non-public network integrated with a public network.

Fig. 7 illustrates an example of a wireless communication system to which techniques in accordance with one or more embodiments of the disclosed technology may be applied.

FIG. 8 is a block diagram illustration of a portion of a hardware platform.

Detailed Description

The development of new generation wireless communication (5G new air interface (NR) communication) is part of the continuous development process of mobile broadband evolution to meet the increasing network demands. NR will provide greater throughput to allow more users to be connected simultaneously. Other aspects such as energy consumption, device cost, spectral efficiency, and latency are also important to meet the needs of various communication scenarios.

This patent document describes techniques that may be implemented to support non-public networks integrated with public networks. The public network may comprise a publicly used network. Non-public networks may include networks that are intended for non-public use and may be accessed by some specific authorized user. In the case of independent non-public networks, the user may not be able to access both the public and non-public networks simultaneously. In the case of a public-public network (public-public network) integrated with a public network, the public and non-public networks may share access networks and some Network Functions (NFs) in the core network. In this case, when a terminal (or "UE") accesses a network, the network may perform access control based on a subscription of the UE. The network may prevent some unauthorized UEs from attempting to access a particular non-public network in areas where the UE is not allowed to use the non-public network.

To support access control, a Control Access Group (CAG) may be implemented in a non-public network (NPN) integrated with a public network to prevent a UE from automatically selecting and registering from locations/cells that do not provide access to the NPN or from locations/cells that do not allow the UE to access the NPN. The CAG may be conceptually similar to a Closed Subscriber Group (CSG) in EPS (evolved packet system). However, there may be no need to distinguish between different networks via CSG. In 5GS, slices can be used to distinguish networks with different characteristics. Therefore, for a scenario of a non-public network integrated with a public network, how to use a combination of CAG and slices is a future continuous study (FFS).

Embodiments of the present disclosure relate to accessing particular non-public networks (including appropriate access networks, core networks, etc.), and in many cases, to accessing non-public networks integrated with public networks.

FIG. 1 illustrates an example system architecture 100 for supporting a non-public network integrated with a public network. In many cases, a 5G system may include the following network functions. One such network function may comprise a 5G access node (or "5G-AN"), which may also comprise a NG-RAN or a RN (radio network). The 5G-AN may be connected to AN access and mobility management function (AMF) via AN N2 interface. As described below, the AMF and 5G-AN may exchange configuration information (e.g., Tracking Area Identification (TAI) list, Public Land Mobile Network (PLMN), supported single network slice selection assistance information (S-NSSAI), etc.) over the N2 interface. The NG-RAN may select the AMF based on one or more PLMN and AMF supported S-NSSAIs and the requested NSSAI from the UE.

The access and mobility management functions (AMF) may include various functions, such as: UE mobility management, reachability management, connection management, etc. The AMF may terminate Radio Access Network (RAN) Control Plane (CP) interface (or "N2" interface) and non-access stratum (NAS) (or "N1" interface), NAS ciphering, and integrity protection. The AMF may also distribute Session Management (SM) NAS to the appropriate Session Management Function (SMF) via the N1 interface. To support reliability, the concept of AMF set may be used.

The Session Management Function (SMF) may include any one of UE IP (internet protocol) address assignment and management, selection and control of UP (user plane) functions, Protocol Data Unit (PDU) connection management, and the like.

The User Plane Function (UPF) may be an anchor point for intra-RAT (radio access technology)/inter-RAT mobility and an external PDU session point interconnected to the data network. The UPF may also route and forward packets based on the indication from the SMF. The UPF may also buffer downlink data when the UE is in idle mode.

A Unified Data Management (UDM) may store subscription profiles for multiple UEs.

A Policy Control Function (PCF) may manage network behavior based on subscriptions and indications from the AMF. The PCF may also provide policy rules to CP functions (e.g., AMF and SMF) to enforce them.

To support such access control, a CAG may be introduced to the NPN integrated with the public network to prevent the UE from automatically selecting and registering to a location/cell that does not provide access to the NPN or from automatically selecting and registering from a location/cell that does not allow the UE to access the NPN. The CAG may be identified by a CAG identifier that is unique within the scope of the PLMN ID, and the CAG cell broadcasts the CAG identifier in the PLMN. The UE may be configured to be included in an allowed CAG list for network selection. The UE may initiate access to the network if the broadcasted CAG ID is included in the allowed CAG list. Otherwise, the UE may reselect a suitable CAG cell or common cell. CAG is a similar concept as CSG in EPS. CSG in EPS can be used for access control in MME (mobility management entity). In case of access control approval, i.e., allowing a CSG cell to be accessed by the UE, the CSG may not be used for GW (gateway) selection or other CN (core network) function selection. In some 5GS, the current definition of CAG may not be extended for NF selection.

In 5GS, a network slice may include a logical network that provides specific network capabilities and network characteristics. A network slice may be defined within a PLMN and may include an access network (NR for 3GPP (third generation partnership project), or N3IWF for non-3 GPP (non-3 GPP interworking function)), a core network control plane, and user plane network functions. The network may provide one or more network slice instances to a single UE via the 5G-AN at the same time regardless of the access type (i.e., 3GPP access and/or N3GPP access) with which the UE is registered. The selection of a set of network slice instances for the UE may be triggered by the AMF of the first contact during the registration procedure, typically by interacting with NSSF (network slice selection function). The S-NSSAI may identify a network slice. The NSSF and AMF may generate an allowed NSSAI (which includes one or more S-NSSAIs for the UE) and send the allowed NSSAI to the UE. The UE may store an allowed CSG list. If the S-NSSAI associated with a particular slice is included in the allowed NSSAIs, the UE may initiate a PDU session setup for that slice. Based on local policy, subscription changes, and/or UE mobility, operational reasons (e.g., network slice instances are no longer available, or load level information of network slice instances provided by NWDAF (network data analysis function)), the network may change the network slice set to which the UE is registered and provide the UE with new allowed NSSAI. Network slices may be introduced to distinguish non-public networks.

To reuse current CAG and network slices in non-public networks integrated with public networks, the presented embodiments may combine CAG and network slices to differentiate non-public networks.

A network function (or "NF") may process the service logic and expose the service to other authorized NF nodes. NF services may be grouped into one or more NF service sets. Within the NF service set, the capabilities of each NF service instance may be the same. Thus, any NF service or NF service instance within the set of service instances may be able to process the UE transaction because the NF service/NF service instance may access the UE context. NF service instances within a given set of NF service instances may be expected to access the same set of data in a data storage entity, e.g., a UDSF (unstructured data storage function).

A network storage function (NRF) may support service discovery. The NRF may maintain NF service configurations for available NF service instances and their supported services. The NRF may receive a NF service discovery request from a NF service instance and provide information of the discovered (discovered) NF instance to the NF service instance.

Service framework functions may include service registration/discovery, communication between service instances, and security functions. The service framework may be included in an operator network using various mechanisms and may support various distribution models and connectivity with network function services.

The NF/service sets may be deployed in one or more units (units). Each unit may share common platform functionality and each unit may include one or more NF/service sets and a service framework. Request/response messages may be exchanged via the service framework if a NF/service in a cell communicates with a NF/service in another cell.

However, in many cases, it may not be clear how to route request/response messages in different units via the service framework. Embodiments disclosed herein may include utilizing route IDs in communications between NFs/services via different service frameworks.

Fig. 2 illustrates an example non-public network integrated with a public network. Non-public network 1 may be identified by CAG1 and slice 1 (identified by S-NSSAI 1). Non-public network 2 may be identified by CAG2 and slice 2 (identified by S-NSSAI2), while non-public network 3 may be identified by CAG3 and slice 3 (identified by S-NSSAI 3).

The UE may subscribe to one or more CAGs (i.e., a list of CAGs may be included in the subscription) and may allow the UE to access multiple slices.

The access node (5G-AN1) broadcasts CAG1 and can block users not subscribed to CAG1 from accessing the network. Similarly, 5G-AN2 broadcasts CAG2 and users not subscribed to CAG2 may be blocked from accessing the network. 5G-AN3 broadcasts CAG3 and users that are not subscribed to CAG3 may be blocked from accessing the network.

When the UE registers, the AMF may request the NSSF to generate an allowed NSSAI for the UE, where the request includes a CAG ID. Given confidentiality in non-public networks, the allowed NSSAI may ensure that the UE cannot access slices that do not match the CAG identified in the CAG ID. As an example, a UE may subscribe to both CAG2 and CAG 3. In this example, when the UE accesses CAG2, the allowed NSSAIs generated by the NSSF include the S-NSSAI associated with CAG2 (e.g., S-NSSAI 2). Further describing the example, if the UE moves to access CAG3, the NSSF may generate an updated allowed NSSAI including an S-NSSAI associated with CAG3 (e.g., S-NSSAI 3).

The NSSF may store a mapping between CAG and S-NSSAI, and the mapping may be configured by an operator management system.

Fig. 3 illustrates an example signaling procedure for generating allowed NSSAIs during a registration procedure. At step 301, one of the UE 310 and NR 320 may send a registration request to the AMF 330. The registration request may include AN message, which may include AN parameter. The registration request may include a registration type, which may include any one of: a user hidden Identifier (SUCI), a 5G globally unique temporary Identifier (5G-GUTI), a permanent device Identifier (PEI), and a last accessed Tracking Area Identifier (TAI), if available. The registration request may include at least one of: security parameters, requested NSSAI, mapping of requested NSSAI, default configured NSSAI indication, UE Radio Capability Update (Radio Capability Update), UE MM core network Capability, Protocol Data Unit (PDU) session status, list of PDU sessions to activate, follow-up request, mobile originated connection only (MICO) mode preference, requested Discontinuous Reception (DRX) parameter, Local Area Data Network (LADN) with network name (DNN) or indicator requesting LADN information, and UE policy container (PSI list, indication that UE supports andsdsp (access network discovery and selection policy), and operating system identifier).

In some embodiments, if 5G-S-TMSI or GUAMI is not included, or is not indicated, the access node (or "NR") may select the AMF 330 based on the (R) AT and the requested NSSAI. If the (R) AN is unable to select AN appropriate AMF, the (R) AN may forward the registration request to the AMF that has been configured to perform AMF selection.

The registration request may be sent from the (R) AN to the AMF via AN N2 message on AN N2 interface. The N2 message may include any of the following: n2 parameter, registration request, and UE policy container. The N2 parameter may include any of the following: a selected PLMN ID, CAG ID, location information, cell identity, UE context request related to a cell in which the UE is camped, the UE context request indicating that a UE context including security information needs to be established at the NG-RAN.

In steps 302A and 302B, AMF 330 and UDM 350 may communicate to retrieve Access and Mobility Subscription (Access and Mobility Subscription) data from UDM 350. If the AMF 330 does not have subscription data for the UE 310, the AMF 330 may send a request for access and mobility subscription data to the UDM 350 (302A). The request (302A) may include SMF selection subscription data and UE context in SMF data using a numm _ SDM _ Get message. Upon receiving the request (302A), the UDM 350 may retrieve the requested information from the UDR (unified data store) using the nurr DM Query message.

The UDM 350 may send the requested information to the AMF 330 in a response (302B). After receiving the response (302B), the AMF 330 may Subscribe to notifications using the numm _ SDM _ Subscribe when the requested data is modified. UDM 350 may Subscribe to UDR through Nudr _ DM _ Subscribe. The subscription may contain slice information and CAG information.

The AMF 330 may check whether CAG provided by the NG-RAN is included in the subscribed CAG list. If not, the AMF 330 may deny registration. For example, CAG provided by NG-RAN may be included in the list of subscribed CAGs.

In steps 303A and 303B, AMF 330 may send a request for allowed network slice selection assistance information (303A) to NSSF 340. The request (303A) may comprise an nssf _ NSSelection _ Get message, wherein the message may comprise any of the following: requested NSSAI, mapping of requested NSSAI, subscribed S-NSSAI with default S-NSSAI indication, TAI, allowed NSSAI for other access types (if any), mapping of allowed NSSAI, PLMN ID of SUPI (user permanent identifier), and CAG ID. As described above, the CAG ID may be provided by the NG-RAN in the registration request (301).

In response to the request for allowed network slice selection assistance information (303A), the NSSF340 may send a response to the AMF 330 including the allowed network slice selection assistance information (303B). The response (303B) may comprise an nssf _ NSSelection _ Get message, wherein the response may comprise at least one of: an AMF set or AMF address list, allowed NSSAI for a first access type, mapping of allowed NSSAI, allowed NSSAI for a second access type, mapping of allowed NSSAI, NSI ID (network slice instance identifier), NRF, rejected S-NSSAI list, list of reason values for rejection, configured NSSAI for a serving PLMN, and mapping of configured NSSAI. NSSF340 may generate an allowed NSSAI for the first access type (i.e., NG-RAN) based on the CAG ID.

In step 304, the AMF 330 may send a registration accept message to the UE 310. The registration acceptance message may include at least one of: 5G-GUTI, registration area, mobility restrictions, PDU session state, allowed NSSAI, mapping of allowed NSSAI, configured NSSAI for serving PLMN, mapping of configured NSSAI, rejected S-NSSAI, periodic registration update timer, LADN information and accepted MICO mode, IMS Voice over PS session supported Indication (IMS Voice over PS session supported Indication), emergency services support indicator, accepted DRX parameters, network support for network interworking without N26, access layer connection establishment NSSAI containing mode, network slice subscription change Indication, and operator defined access category definition. The allowed NSSAI for the access type of the UE may be included in the N2 message carrying the registration accept message over the N2 interface.

Fig. 4 shows an example signaling procedure for updating the allow list without changing the AMF. As shown in fig. 4, the allowed NSSAI may be updated based on at least one of a current CAG ID change (step 401A) and a subscribed CAG/NSSAI change (step 401B).

In step 401A, the current CAG cell with which UE 410 is associated (or "camped") may change. In this case, the RAN node (e.g., new NR 420) may send a message informing AMF 430 of the new CAG ID. During the service request procedure, the new NR 420 may transmit a NAS service request message including the N2 interface parameters to the AMF 430. The N2 interface parameters may include at least one of: a selected PLMN ID, CAG ID, location information, and cell identification associated with a cell in which the UE is camped.

During a handover procedure (e.g., an Xn interface handover procedure), the target NR may send an N2 path switch request message to the AMF. If the target cell and/or the CAG ID is modified, the target NR may send the current cell ID and the CAG ID to the AMF.

During the N2 Handover procedure, the old NR may send the target CAG ID to the AMF via a Handover Required (Handover Required) message.

In step 401B, the subscribed CAG and/or NSSAI may change. In this case, the AMF 430 and the UDM450 communicate, and the UDM450 may send updated subscription information to the AMF 430. In some embodiments, the AMF 430 may determine whether it is necessary to update the UE configuration information based on receiving a subscription data update notification from the UDM450, the subscription data update notification including information indicating a change to the network slice and/or the CAG configuration.

In some embodiments, if the CAG configuration is updated and the current CAG ID associated with the UE is not subscribed, the AMF 430 may deregister the UE 410 by sending a deregistration message to the UE 410. In this embodiment, steps 402 and 403 may be skipped.

In step 402A, AMF 430 may send a message to NSSF 440 requesting an allowed NSSAI based on the updated subscribed NSSAI and the current CAG. The AMF 430 may request allowed NSSAI based on CAG information and/or updated slice configuration information. In step 402B, NSSF 440 may generate and send a new allowed NSSAI to AMF 430 based on the input provided by AMF 430 in the request message (402A).

In some embodiments, if the AMF 430 cannot determine a new allowed NSSAI after updating the subscribed S-NSSAI, steps 402A and 402B may be skipped. In this embodiment, the AMF 430 may send a UE configuration update command (step 403A) to the UE 410 that does not include the allowed NSSAI. Based on the configuration update command, the UE 410 may receive a new allowed NSSAI during the re-registration procedure, similar to that described in connection with fig. 3.

In step 403A, the AMF 430 may send a UE configuration update command to the UE 410, the command including information indicating updated configuration information, such as updated network slice subscription information or a new allowed NSSAI received by the NSSF 440.

Fig. 5 shows an example signaling procedure for updating the allow list in case of a change of AMF. The allowed NSSAI may be updated based on at least one of a current CAG ID change (step 501A) and/or a subscribed CAG/NSSAI change (step 501B).

In step 501A, one of the new RAN node 520 and the old/initial AMF 530 may send a new or updated CAG ID associated with the terminal to the new AMF 532. In some embodiments, during the AMF redirection procedure, the new NR 520 may send the current CAG ID to the new AMF 532 via an initial UE message, or the initial AMF 530 sends the current CAG ID to the new AMF 532 via an N1MessageNotify message. The initial UE message may include an N2 parameter that includes a CAG ID. The communication N1MessageNotify message may comprise a rerouted NAS message comprising the current CAG ID received from the NR during registration with the initial AMF.

During the N2 handover procedure, the old NR may transfer the target CAG ID to the old AMF 530 via a handover required message, and the old AMF 530 may forward the target CAG ID to the new AMF 532 via a createcontext Request message.

In step 501B, if the new AMF 532 does not include subscription data for the UE, the new AMF 532 may receive access and mobility subscription data, SMF selection subscription data, and UE context in the SMF data using a numm _ SDM _ Get message. In some embodiments, UDM 550 receives access and mobility subscription data from UDR via a nurr DM Query message.

After the new AMF 532 receives the successful response, the new AMF 532 may Subscribe to notifications using the Nudm _ SDM _ Subscripte when the requested data is updated/modified. Similarly, UDM 550 may Subscribe to UDR through Nudr _ DM _ Subscribe to be notified if requested data is updated/modified. The subscription may include updates to the slice information and/or CAG information.

In some embodiments, the new AMF 532 may determine whether the CAG provided by the NG-RAN is included in the subscribed CAG list. If the new AMF 532 does not determine that the provided CAG is not included in the subscribed CAG list, the new AMF 532 may terminate the process and send the appropriate cause.

In steps 502A to 502B, the AMF 532 and the NSSF540 may communicate to receive an updated allowed NSSAI from the NSSF, assuming that the CAG provided by the NG-RAN is included in the subscribed CAG list. In step 502A, the message from the new AMF 532 to the NSSF540 may include a request for an updated allowed NSSAI via an NSSF _ NSSelection _ Get message. The message may include at least one of: requested NSSAI, mapping of requested NSSAI, subscribed S-NSSAI with default S-NSSAI indication, TAI, allowed NSSAI for other access types (if any), mapping of allowed NSSAI, PLMN ID of SUPI, and CAG ID. As described above, the CAG ID may be provided by the NG-RAN.

In step 502B, the response from the NSSF540 to the new AMF 532 may include the updated allowed NSSAI via the NSSF _ NSSelection _ Get message. The message may include at least one of: an AMF set or AMF address list, allowed NSSAIs for a first access type, a mapping of allowed NSSAIs, allowed NSSAIs for a second access type, a mapping of allowed NSSAIs, an NSI ID, NRF, a list of rejected S-NSSAIs or cause values, a configured NSSAI for a serving PLMN, and a mapping of configured NSSAIs. The NSSF may generate an allowed NSSAI (i.e., NG-RAN) based on the CAG ID.

In step 503, the new AMF 532 may inform the UE 510 of the allowed NSSAI or the absence of a new allowed NSSAI. If the new AMF 532 includes a previously received (or "old") allowed NSSAI (e.g., received allowed NSSAI from the old AMF), the new AMF 532 may compare the old allowed NSSAI with the newly received/updated allowed NSSAI received by the NSSF in 502B. If the old allowed NSSAI does not match the updated allowed NSSI, the AMF 532 may notify the UE 510 of the updated allowed NSSAI via a registration accept message to the UE.

Fig. 6 shows a block diagram of a method of supporting a non-public network integrated with a public network. The node may send a first request to a second node requesting information to assist in selecting a network for a terminal associated with a first network and a first access group, the first network being a non-public network, the first access group being associated with a first network node, wherein the first request includes a first access group identifier identifying the first access group associated with the terminal (block 602). The first request may comprise an NS selection request, for example, as shown in step 303A of fig. 3, step 402A of fig. 4, or step 502A of fig. 5. Examples of nodes may include AMFs as described in this disclosure. An example of the second node may include an NSSF as described in this disclosure. Examples of non-public networks may include non-public networks as described in this disclosure or non-public networks integrated with public networks.

The method includes the node receiving a first response from a second node, the first response including information that assists in selecting a logical network for a terminal, the terminal being associated with a first logical network and a first access group, the first access group being associated with a first network node (block 604). The first Response may comprise an NS Selection Response (NS Selection Response) message, e.g., as shown in step 303B of fig. 3, step 402B of fig. 4, or step 502B of fig. 5. The information that assists in selecting a logical network for the terminal may include allowed NSSAIs as described in this disclosure. An example of a first logical network configured to perform network functions may include a network slice (e.g., slice 1) as described in this disclosure. The first access group associated with the first network node may include a CAG (e.g., CAG1) as described in this disclosure. As described herein, the first access group identifier that identifies the first access group associated with the terminal may include a CAG ID associated with the terminal.

In some embodiments, the second node is configured to store a mapping between the first access group and information assisting in selecting the logical network.

In some embodiments, the method includes the node receiving a registration request from one of a first network node and a terminal, the first network node adding a first access group identifier to the registration request that identifies a first access group associated with the terminal.

In some embodiments, the method includes the node sending a first access group identifier to the second node in a first request.

In some embodiments, the method includes the node sending a second request to a third node for managing and storing mobility subscription information, wherein the second request requests mobility subscription information from the third node.

In some embodiments, the method includes the node receiving a second response from the third node including mobility subscription information, wherein the mobility subscription information includes at least one access group identifier identifying at least one access group to which the terminal is allowed access.

In some embodiments, the method comprises the node sending to the second node at least one access group identifier identifying at least one access group to which the terminal is allowed access.

In some embodiments, the third node is configured to retrieve mobility subscription information from a fourth node comprising the data repository, and subscribe to the fourth node.

In some embodiments, the information assisting in selecting a network for the terminal is represented as allowed Network Slice Selection Assistance Information (NSSAI).

In some embodiments, the method includes the node sending a registration accept message to the terminal, the registration accept message including information to assist in selecting a network for the terminal.

In some embodiments, the method includes the node receiving an update message from the second network node indicating that the terminal is associated with the second access group, wherein the update message includes a second access group identifier identifying the second access group associated with the terminal.

In some embodiments, the method includes the node sending the second access group identifier to the second node in the first request.

In some embodiments, the method includes the node receiving at least one of a path switch request message and an initial UE message from a second network node, wherein the path switch request message and the initial UE message include at least one of a new target cell identifier and a second access group identifier.

In some embodiments, the method includes the node receiving a subscription data update notification from a third node, the subscription data update notification including a subscription data update indicating a change to at least one of the first network and the access group configuration; the node determining, based on the change to at least one of the first network and access group configuration, whether to send a third request to the second node requesting a second set of information, the second set of information assisting in selecting a network for the terminal; and the node sends a third request to the second node requesting a second set of information assisting in selecting a network for the terminal associated with at least one of the non-public second network and a second access group of the second network node, wherein the third request includes a second access group identifier identifying the second access group associated with the terminal.

In some embodiments, the method comprises: based on determining that the configuration of the first access group is updated and that the first access group identifier is not associated with the terminal, the node sends a deregistration message to the terminal to deregister the terminal.

In some embodiments, the method includes the node receiving a third response from the second node, the third response including a second set of information that assists in selecting a network for the terminal, the terminal being associated with at least one of the second network and the second access group.

In some embodiments, the method includes the node sending a second registration accept message to the terminal, the second registration accept message including a second set of information that assists in selecting a logical network for the terminal.

In some embodiments, the method includes the node sending a notification message to a fifth node configured to manage terminal access and mobility, wherein the notification message includes a second access group identifier identifying a second access group associated with the terminal.

In some embodiments, the second network node is configured to send a notification message to a fifth node, the fifth node configured to manage terminal access and mobility, the notification message comprising a second access group identifier identifying a second access group associated with the terminal.

In some embodiments, the notification message to the fifth node comprises a rerouted non-access stratum (NAS) message and the second access group identifier.

In some embodiments, the fifth node is configured to send a mobility subscription data request message to request mobility subscription data of the terminal from the third node configured to manage and store mobility subscription information.

In some embodiments, the fifth node is configured to send a fourth request to the second node based on the second access group identifier to request a third set of information to assist in selecting a network for the terminal.

In some embodiments, the fifth node is configured to receive a fourth response from the second node, the fourth response comprising a third set of information that assists in selecting the logical network.

In some embodiments, the fifth node is configured to compare the third set of information assisting in the selection of the logical network with the information assisting in the selection of the logical network, and wherein the fifth node is configured to send the third set of information assisting in the selection of the logical network to the terminal if the information assisting in the selection of the logical network is different from the third set of information assisting in the selection of the logical network.

Fig. 7 illustrates an example of a wireless communication system in which techniques in accordance with one or more embodiments of the disclosed technology may be applied. The wireless communication system 700 may include: one or more Base Stations (BSs) 705a, 705 b; one or

more wireless devices

710a, 710b, 710c, 710 d; and a core network 725. Base stations 705a, 705b may provide wireless service to

wireless devices

710a, 710b, 710c, and 710d in one or more wireless sectors. In some embodiments, the base stations 705a, 705b include directional antennas to generate two or more directional beams to provide wireless coverage in different sectors.

The core network 725 may communicate with one or more base stations 705a, 705 b. The core network 725 provides connectivity to other wireless and wireline communication systems. The core network may include one or more service subscription databases to store information related to subscribed

wireless devices

710a, 710b, 710c, and 710 d. The first base station 705a may provide wireless service based on a first radio access technology, while the second base station 705b may provide wireless service based on a second radio access technology. Depending on the deployment scenario, the base stations 705a and 705b may be co-located or may be separately installed in the field.

Wireless devices

710a, 710b, 710c, and 710d may support a plurality of different radio access technologies.

In some embodiments, a wireless communication system may include multiple networks using different wireless technologies. A dual-mode or multi-mode wireless device includes two or more wireless technologies that may be used to connect to different wireless networks.

FIG. 8 is a block diagram illustration of a portion of a hardware platform. Hardware platform 805, such as a network device or base station or wireless device (or UE), may include processor electronics 810, such as a microprocessor implementing one or more of the techniques presented herein. Hardware platform 805 may include transceiver electronics 815 to transmit and/or receive wired or wireless signals over one or more communication interfaces, such as an antenna 820 or a wired interface. Hardware platform 805 may implement other communication interfaces using defined protocols for sending and receiving data. Hardware platform 805 may include one or more memories (not explicitly shown) configured to store information such as data and/or instructions. In some implementations, processor electronics 810 may include at least a portion of transceiver electronics 815. In some embodiments, at least some of the disclosed techniques, modules, or functions are implemented using a hardware platform 805.

From the foregoing, it will be appreciated that specific embodiments of the disclosed technology have been described herein for purposes of illustration, but that various modifications may be made without deviating from the scope of the invention. Accordingly, the techniques of this disclosure are not limited, except as by the appended claims.

The and other embodiments, modules, and functional operations disclosed herein may be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed herein and their structural equivalents, or in combinations of one or more of them. The disclosed and other embodiments may be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a combination of matter effecting a machine-readable propagated signal, or a combination of one or more of them. The term "data processing apparatus" includes all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.

A computer program (also known as a program, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described herein can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

While this patent document contains many specifics, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this patent document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Moreover, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.

Only a few embodiments and examples have been described and other implementations, enhancements and variations can be made based on what is described and illustrated in this patent document.

Claims

1. A method of wireless communication, comprising:

a node sends a first request to a second node requesting information to assist in selecting a network for a terminal, the terminal being associated with a first network and a first access group, the first network being a non-public network, the first access group being associated with a first network node, wherein the first request includes a first access group identifier identifying the first access group associated with the terminal; and

the node receives a first response from a second node, the first response including the information assisting in selecting a network for a terminal associated with the first network and the first access group associated with the first network node.

2. The method of claim 1, wherein the second node is configured to store a mapping between the first access group and the information that assists in selecting a network.

3. The method of claim 1, further comprising:

the node receives a registration request from one of the first network node and the terminal, the first network node adding the first access group identifier identifying a first access group associated with the terminal to the registration request.

4. The method of claim 3, further comprising:

the node sends the first access group identifier to the second node in the first request.

5. The method of claim 1, further comprising:

the node sends a second request to a third node for managing and storing mobility subscription information, wherein the second request requests the mobility subscription information from the third node.

6. The method of claim 5, further comprising:

the node receives a second response from the third node including the mobility subscription information, wherein the mobility subscription information includes at least one access group identifier identifying at least one access group to which the terminal is allowed access.

7. The method of claim 6, further comprising:

the node sends the at least one access group identifier identifying at least one access group to which the terminal is allowed access to the second node.

8. The method of claim 5, wherein the third node is configured to retrieve the mobility subscription information from a fourth node comprising a data repository and subscribe to the fourth node.

9. The method of claim 1, wherein the information assisting in selecting a network for a terminal is denoted as allowed Network Slice Selection Assistance Information (NSSAI).

10. The method of claim 1, further comprising:

and the node sends a registration acceptance message to the terminal, wherein the registration acceptance message comprises the information for assisting in selecting the network for the terminal.

11. The method of claim 1, further comprising:

the node receives an update message from a second network node indicating that the terminal is associated with a second access group, wherein the update message includes a second access group identifier that identifies the second access group associated with the terminal.

12. The method of claim 11, further comprising:

the node sends the second access group identifier to the second node in the first request.

13. The method of claim 11, further comprising:

the node receives at least one of a path switch request message or an initial User Equipment (UE) message from the second network node, wherein the path switch request message and the initial UE message include at least one of a new target cell identifier and the second access group identifier.

14. The method of claim 1, further comprising:

the node receiving a subscription data update notification from a third node, the subscription data update notification including a subscription data update indicating a change to at least one of the first network and access group configuration;

the node determining, based on the change to at least one of the first network and access group configuration, whether to send a third request to the second node requesting a second set of information that assists in selecting a network for the terminal; and the number of the first and second groups,

the node sends a third request to the second node requesting a second set of information that assists in selecting a network for the terminal associated with at least one of a second network that is a non-public network and a second access group of the second network node, wherein the third request includes a second access group identifier that identifies the second access group associated with the terminal.

15. The method of claim 14, further comprising:

based on determining that the configuration of the first access group is updated and that the first access group identifier is not associated with the terminal, the node sends a deregistration message to the terminal to deregister the terminal.

16. The method of claim 14, further comprising:

the node receives a third response from the second node, the third response including the second set of information that assists in selecting a network for a terminal associated with at least one of the second network and the second access group.

17. The method of claim 16, further comprising:

the node sends a second registration accept message to the terminal, the second registration accept message including the second set of information that assists in selecting a logical network for the terminal.

18. The method of claim 1, further comprising:

the node sends a notification message to a fifth node configured to manage terminal access and mobility, wherein the notification message includes a second access group identifier identifying a second access group associated with the terminal.

19. The method of claim 1, wherein the second network node is configured to send a notification message to a fifth node configured to manage terminal access and mobility, the notification message comprising a second access group identifier identifying a second access group associated with the terminal.

20. The method according to any of claims 18 and 19, wherein the notification message to the fifth node comprises a rerouted non-access stratum (NAS) message and the second access group identifier.

21. A method according to any of claims 18 and 19, wherein the fifth node is configured to send a mobility subscription data request message to request mobility subscription data of the terminal from a third node configured to manage and store mobility subscription information.

22. The method according to any of claims 18 and 19, wherein the fifth node is configured to send a fourth request to the second node based on the second access group identifier to request a third set of information to assist in selecting a network for the terminal.

23. The method of claim 22, wherein the fifth node is configured to receive a fourth response from the second node, the fourth response comprising the third set of information that assists in selecting a logical network.

24. The method of claim 23, wherein the fifth node is configured to compare the third set of information assisting in selecting a logical network with information assisting in selecting a logical network, and wherein the fifth node is configured to transmit the third set of information assisting in selecting a logical network to the terminal if the information assisting in selecting a logical network is different from the third set of information assisting in selecting a logical network.

25. A wireless communication device, comprising: a processor configured to perform the method of any one of claims 1 to 24.

26. A non-transitory computer-readable medium having code stored thereon, which, when executed by a processor, causes the processor to implement the method of any one of claims 1 to 24.