WO2020186387A1 - Prise en charge d'un réseau non public intégré à un réseau public - Google Patents

Prise en charge d'un réseau non public intégré à un réseau public Download PDF

Info

Publication number
WO2020186387A1
WO2020186387A1 PCT/CN2019/078273 CN2019078273W WO2020186387A1 WO 2020186387 A1 WO2020186387 A1 WO 2020186387A1 CN 2019078273 W CN2019078273 W CN 2019078273W WO 2020186387 A1 WO2020186387 A1 WO 2020186387A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
network
terminal
access group
information
Prior art date
Application number
PCT/CN2019/078273
Other languages
English (en)
Inventor
Shuang Liang
Zhendong Li
Original Assignee
Zte Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zte Corporation filed Critical Zte Corporation
Priority to PCT/CN2019/078273 priority Critical patent/WO2020186387A1/fr
Priority to CN201980094192.8A priority patent/CN113647148A/zh
Publication of WO2020186387A1 publication Critical patent/WO2020186387A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/186—Processing of subscriber group data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data

Definitions

  • This patent document is directed generally to wireless communications.
  • This document discloses methods, systems, and devices related to digital wireless communication, and more specifically, to techniques related to supporting a public network integrated non-public network.
  • a method for wireless communication includes transmitting a first request to a second node requesting information that assists in selecting a network for a terminal that is associated with a first network that is non-public network and a first access group 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 that includes the information that assists in selecting the network for the terminal associated with the first network and the first access group associated with the first network node.
  • a wireless communications apparatus comprising a processor.
  • the processor is configured to implement a method described herein.
  • the various techniques described herein may be embodied as processor-executable code and stored on a computer-readable program medium.
  • FIG. 1 illustrates an example system architecture for supporting a public network integrated non-public network.
  • FIG. 2 illustrates an example public network integrated non-public network.
  • FIG. 3 illustrates an example signaling process for generating an allowed NSSAI during the registration procedure.
  • FIG. 4 illustrates an example signaling processes to update an allowed list without changing the AMF.
  • FIG. 5 illustrates an example signaling process for updating an allowed list with an AMF change.
  • FIG. 6 illustrates a block diagram of a method to support a public network integrated non-public network.
  • FIG. 7 shows an example of a wireless communication system where techniques in accordance with one or more embodiments of the present technology can be applied.
  • FIG. 8 is a block diagram representation of a portion of a hardware platform.
  • NR New Radio
  • a public network may include a network for public use.
  • Non-public networks may include networks that are intended for non-public use and may be accessed by some specific authorized users.
  • a user may be unable to access the public network and non-public network concurrently.
  • the public and the non-public network may share an access network and some network functions (NFs) in the core network.
  • NFs network functions
  • the network may preform access control based on subscription of the UE. The network may prevent some unauthorized UEs from trying to access the specific non-public network in areas which the UE is not allowed to use the non-public network.
  • a control access group may be implemented in Public network integrated non-public networks (NPNs) to prevent a UE from automatically selecting and registering from a location/cell which does not provide access to the NPN, or from a location/cell which the UE is not allowed to access the NPN.
  • CAG may be similar in concept to a Closed Subscriber Group (CSG) in EPS. However, there may be no requirement for distinguishing a different network via CSG.
  • CSG Closed Subscriber Group
  • a slice may be used for differentiating networks with different features. Accordingly, for the scenario of public network integrated non-public network, how to use the combination of CAG and a slice is for further study (FFS) .
  • the embodiments of the present disclosure relate to accessing a specific non-public network (including a proper access network, a core network, etc. ) and in many cases, a public network integrated non-public network.
  • FIG. 1 illustrates an example system architecture 100 for supporting a public network integrated non-public network.
  • a 5G system may include the following network functions.
  • One such network function may include a 5G-access node (or “5G-AN” ) , which may also include a NG-RAN or a RN.
  • the 5G-AN may connect to an Access and Mobility Management function (AMF) via a N2 interface.
  • AMF Access and Mobility Management function
  • the AMF and 5G-AN may exchange the configuration information (e.g. a tracking area identity (TAI) list, a public land mobile network (PLMN) , a Supported single network slice selection assistance information (S-NSSAI) , etc. ) on the N2 interface.
  • the NG-RAN may select an AMF based on one or more PLMNs and supported S-NSSAIs of the AMF and requested NSSAIs from the UE.
  • TAI tracking area identity
  • PLMN public land mobile network
  • An Access and Mobility Management function may include various functionalities, such as: UE mobility management, reachability management, connection management, etc.
  • the AMF may terminate the radio access network (RAN) control plane (CP) interface (or the “N2” interface) and a non-access stratum (NAS) (or “N1” interface) , NAS ciphering and integrity protection.
  • the AMF may also distribute a session management (SM) NAS to a proper Session Management function (SMF) via the N1 interface.
  • SM session management
  • SMF Session Management function
  • a Session Management function may include any of UE IP address allocation & management, selection and control of UP function, protocol data unit (PDU) connection management, etc.
  • a user plane function may be the anchor point for Intra/Inter-RAT mobility and an external PDU session point of interconnecting to the Data Network.
  • the UPF may also route and forward data packets based on an indication from the SMF.
  • the UPF may also buffer the downlink data when the UE is in idle mode.
  • a Unified Data Management may store a subscription profile for multiple UEs.
  • a Policy Control Function may govern network behavior based on the subscription and indication from the AMF.
  • the PCF may also provide policy rules to CP functions (e.g., AMF and SMF) to enforce them.
  • a CAG may be introduced to Public network integrated NPNs to prevent a UE from automatically selecting and registering to a location/cell that does not provide access to the NPN or from a location/cell which the UE is not allowed to access the NPN.
  • a CAG may be identified by a CAG Identifier that is unique within the scope of a PLMN ID, and a CAG cell broadcasts a CAG Identifier in a PLMN.
  • the UE may be configured to be included in an allowed CAG list for network selection. If the broadcasted CAG ID is included in the allowed CAG list, the UE may initiate access to the network. Otherwise, the UE may re-select a proper CAG cell or a public cell.
  • a CAG is a similar concept to CSG in EPS.
  • a CSG in EPS may be used for access control in MME.
  • the access control approval i.e. CSG cell is permitted to accessed by a UE, the CSG may not be used for GW selection or other CN function selection.
  • the present definition of a CAG may not be extended for NF selection in some 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, or N3IWF for non-3GPP) , a Core Network Control Plane, and User Plane Network Functions.
  • the network may serve a single UE with one or more Network Slice instances simultaneously via a 5G-AN regardless of the access type (s) over which the UE is registered (i.e. 3GPP Access and/or N3GPP Access) .
  • the selection of a set of Network Slice instances for a UE may be triggered by the first contacted AMF in a Registration procedure normally by interacting with a NSSF.
  • a S-NSSAI may identify a Network Slice.
  • the NSSF and the 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 the Allowed CSG list. If a S-NSSAI associated with a specific slice is included in the Allowed NSSAI, the UE can initiate a PDU session establishment for such slice.
  • the network based on local policies, subscription changes and/or UE mobility, operational reasons (e.g. a Network Slice instance is no longer available or load level information for a network slice instance provided by the NWDAF) may change the set of Network Slice (s) to which the UE is registered and provide the UE with a new Allowed NSSAI.
  • a network slice may be introduced to distinguish the non-public networks.
  • the present embodiments may combine the CAG and network slice to distinguish a non-public network.
  • a Network Function may handle service logic and expose services to other authorized NF nodes.
  • a NF Service may be grouped into one or more NF Service Sets. Within a NF Service Set, the capability of each NF service instance may be the same. Accordingly, any NF Service or NF Service Instance within a Service Instance set may be able to process UE transactions, as the NF service/NF service instance may have access to UE context.
  • a NF Service instance within a given NF Service Instance Set may be expected to have access to the same data sets in a data storage entity (e.g. a UDSF) .
  • a data storage entity e.g. a UDSF
  • a Network Repository Function may support service discovery.
  • the NRF may maintain a NF service profile of available NF service instances and their supported services.
  • the NRF may receive a NF service Discovery Request from NF service instance and provide the information of the discovered NF instances (be discovered) to the NF service instance.
  • the Service Framework functionalities 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 could support various models of distribution and connectivity with the network function services.
  • the NF/Service Sets may be deployed in one or more Units. Each Unit may share a common platform function, and each Unit may include one or multiple NF/Service sets and a Service Framework. If the NF/Service in a Unit communicates with the NF/Service in another Unit, the request/response messages may be exchanged via the Service Frameworks.
  • the embodiments disclosed in the present application may include utilizing a routing ID in the communication between the NF/Services via different Service Framework.
  • FIG. 2 illustrates an example public network integrated non-public network.
  • a non-public network 1 may be identified by CAG1 and Slice1 (identified by S-NSSAI1) .
  • Non-public network 2 may be identified by CAG2 and Slice2 (identified by S-NSSAI2)
  • non-public network 3 may be identified by CAG1 and Slice3 (identified byS-NSSAI3) .
  • a UE may subscribe to one or more CAGs (i.e. A CAG list may be included in the subscription) , and the UE may be allowed to access more than one slice.
  • CAGs i.e. A CAG list may be included in the subscription
  • An access node (5G-AN1) broadcasts CAG1 and can block users that don’t subscribe to CAG1 to access the network.
  • 5G-AN2 broadcasts CAG2, and can block the users which don’t subscribe for CAG2 to access the network.
  • 5G-AN3 broadcasts CAG3 and can block the users which don’t subscribe for CAG3 to access the network.
  • the AMF may request the NSSF to generate an allowed NSSAI for the UE, where this request includes a CAG ID.
  • the allowed NSSAI may ensure that a UE cannot access a slice that mismatches the CAG identified in the CAG ID.
  • the UE may subscribe to both CAG2 and CAG3.
  • the allowed NSSAI generated by the NSSF includes a S-NSSAI (e.g., S-NSSAI2) associated with CAG2.
  • the NSSF may generate an updated allowed NSSAI that includes a S-NSSAI (e.g., S-NSSAI3) associated with CAG3.
  • the NSSF may store the mapping between the CAG and S-NSSAI, and the mapping may be configured by an operator management system.
  • FIG. 3 illustrates an example signaling process for generating an allowed NSSAI during the registration procedure.
  • one of a UE 310 and a NR 320 may transmit a registration request to an AMF 330.
  • the registration request may include an AN message, wherein the AN message may include AN parameters.
  • the registration request may include a registration type that may include any one of a
  • Subscription Concealed Identifier SUCI
  • 5G-GUTI 5G Globally Unique Temporary Identity
  • PEI permanent equipment identifier
  • TAI last visited Tracking Area Identifier
  • the registration request may include at least one of: security parameters, a requested NSSAI, a mapping of a requested NSSAI, a default configured NSSAI indication, a UE Radio Capability Update, a UE MM Core Network Capability, a protocol data unit (PDU) Session status, a List Of PDU Sessions To Be Activated, a follow-on request, a mobile initiated connection only (MICO) mode preference, a requested discontinuous reception (DRX) parameters, a Local Area Data Network (LADN) at a Network Name (DNN) or Indicator Of Requesting LADN Information, and a UE Policy Container (the list of PSIs, indication of UE support for ANDSP and the operating system identifier) .
  • security parameters e.g., security parameters, a requested NSSAI, a mapping of a requested NSSAI, a default configured NSSAI indication, a UE Radio Capability Update, a UE MM Core Network Capability, a protocol data unit (PDU) Session
  • an access node may select an AMF 330 based on (R)AT and a requested NSSAI if a 5G-S-TMSI or a GUAMI is not included or the 5G-S-TMSI or GUAMI does not indicate a valid AMF. If the (R) AN cannot select an appropriate AMF, the (R)AN may forward the Registration Request to an AMF which has been configured to perform AMF selection.
  • the registration request may be transmitted from a (R) AN to the AMF via a N2 message over an N2 interface.
  • the N2 message may include any of: N2 parameters, the registration request, and a UE policy container.
  • N2 parameters may include any of a Selected PLMN ID, a CAG ID, Location Information and a Cell Identity related to the cell in which the UE is camping, a UE Context Request that indicates that a UE context including security information needs to be setup at the NG-RAN.
  • the AMF 330 and UDM 350 may communicate to retrieve Access and Mobility Subscription data from the UDM 350. If the AMF 330 does not have subscription data for the UE 310, the AMF 330 may transmit a request (302A) to the UDM 350 for the Access and Mobility Subscription data.
  • the request (302A) may include SMF Selection Subscription data and UE context in SMF data using a Nudm_SDM_Get message.
  • the UDM 350 may retrieve the requested information from a UDR using a Nudr_DM_Query message.
  • the UDM 350 may transmit the requested information in a response (302B) to the AMF 330. After a response (302B) is received, the AMF 330 may subscribe to be notified using Nudm_SDM_Subscribe when the data requested is modified. The UDM 350 may subscribe to UDR by Nudr_DM_Subscribe. The subscription may include the slice information and the CAG information.
  • the AMF 330 may check whether the CAG provided by the NG-RAN is included in the subscribed CAG list. If not, the AMF 330 may reject the registration. For example, the CAG provided by the NG-RAN may be included in the subscribed CAG list.
  • the AMF 330 may transmit a request for allowed network slice selection assistance information (303A) to a NSSF 340.
  • the request (303A) may include a Nnssf_NSSelection_Get message, where the message may include any one of: a Requested NSSAI, a Mapping Of Requested NSSAI, a Subscribed S-NSSAI (s) with the default S-NSSAI indication, a TAI, an Allowed NSSAI for the other access type (if any) , a Mapping of Allowed NSSAI, a PLMN ID of the SUPI, and a CAG ID.
  • the CAG ID may be provided by the NG-RAN in the registration request (301) .
  • the NSSF 340 may transmit a response (303B) that includes the allowed network slice selection assistance information to the AMF 330.
  • the response (303B) may include a Nnssf_NSSelection_Get message, where the response may include at least one of: a AMF Set or list of AMF addresses, an Allowed NSSAI for the first access type, a Mapping Of Allowed NSSAI, an Allowed NSSAI for the second access type, a Mapping of Allowed NSSAI, a NSI ID(s) , a NRF (s) , a List of rejected S-NSSAI (s) , a list of rejected cause value (s) , a Configured NSSAI for the Serving PLMN, and a Mapping Of Configured NSSAI.
  • the NSSF 340 may generate the Allowed NSSAI for the first access type (i.e. NG-RAN) that is based on the CAG ID.
  • the AMF 330 may transmit a registration accept message to the UE 310.
  • the Registration Accept message may include at least one of a 5G-GUTI, a Registration Area, Mobility restrictions, a PDU Session status, an Allowed NSSAI, a Mapping Of Allowed NSSAI, a Configured NSSAI for the Serving PLMN, a Mapping Of Configured NSSAI, a rejected S-NSSAI, a Periodic Registration Update timer, a LADN Information and accepted MICO mode, a IMS Voice over PS session supported Indication, an Emergency Service Support indicator, an Accepted DRX parameter, a Network support of Interworking without N26, an Access Stratum Connection Establishment NSSAI Inclusion Mode, a Network Slicing Subscription Change Indication, and an Operator-defined access category definition.
  • the Allowed NSSAI for the Access Type for the UE may be included in a N2 message carrying the Registration Accept message over the N2 interface.
  • FIG. 4 illustrates an example signaling processes to update an allowed list without changing the AMF.
  • the allowed NSSAI may be updated based on at least one of the current CAG ID changing (step 401A) and the subscribed CAG/NSSAI change (step 401B) .
  • Step 401A the current CAG cell in which the UE 410 is associated with (or “camps” ) may change.
  • a RAN node e.g., new NR 420
  • the new NR 420 may transmit a message notifying the AMF 430 of the new CAG ID.
  • the new NR 420 may transmit a NAS service request message to the AMF 430 that includes N2 interface parameters.
  • the N2 interface parameters may include at least one of a selected PLMN ID, a CAG ID, Location Information, and a Cell Identity related to the cell in which the UE is camping on.
  • the target NR may transmit a N2 Path Switch Request message to the AMF. If the target cell and/or CAG ID is modified, the target NR may transfer the current cell ID and CAG ID to the AMF.
  • a handover procedure e.g., a Xn interface handover procedure
  • the old NR may transmit a target CAD ID to the AMF via a Handover Required message.
  • the subscribed CAG (s) and/or the NSSAI may change.
  • the AMF 430 and UDM 450 communicate, and the UDM 450 may transmit updated subscription information to the AMF 430.
  • the AMF 430 may determine whether it is necessary to update UE configuration information based on receiving a subscriber data update notification from the UDM 450 that includes information indicating a change to the network slice and/or the CAG configuration.
  • the AMF 430 may de-register the UE 410 by sending a deregistration message to the UE 410 if the CAG configuration is updated and the current CAG ID associated with the UE is not subscribed. In this embodiment, steps 402-403 may be skipped.
  • the AMF 430 may transmit a message to the NSSF 440 requesting an allowed NSSAI based on the updated subscribed NSSAI and the current CAG.
  • the AMF 430 may request the allowed NSSAI based on the CAG information and/or slice configuration information being updated.
  • the NSSF 440 may generate and transmit the new allowed NSSAI to the AMF 430 based on the input provided by the AMF 430 in the request message (402A) .
  • Steps 402A-B may be skipped.
  • the AMF 430 may transmit a UE configuration update command (step 403A) to the UE 410 that does not include an allowed NSSAI. Based on this configuration update command, the UE 410 may receive the new allowed NSSAI during a re-registration procedure similar to that as described in FIG. 2.
  • the AMF 430 may transmit a UE configuration update command to the UE 410 that includes information indicating updated configuration information, such as updated network slicing subscription information or the new allowed NSSAI received by the NSSF 440.
  • FIG. 5 illustrates an example signaling process for updating an allowed list with an AMF change.
  • the allowed NSSAI may be updated based on at least one of the current CAG ID changing (step 501A) and/or the subscribed CAG/NSSAI changing (step 501B) .
  • one of the new RAN node 520 and the old/initial AMF 530 may transmit a new or updated CAG ID associated with the terminal to the new AMF 532.
  • the new NR 520 may transmit the current CAG ID to the new AMF 532 via an initial UE message, or the initial AMF 530 transmits the current CAG ID to the new AMF 532 via a N1MessageNotify message.
  • the initial UE message may include N2 parameters, including the CAG ID.
  • the Communication N1MessageNotify message may include a re-routed NAS message that includes the current CAG ID received from the NR during the registration to the initial AMF.
  • the old NR may transfer a target CAG ID to the old AMF 530 via Handover Required message, and the old AMF 530 may forward the target CAG ID to the new AMF 532 via a CreateUEContext Request message.
  • the new AMF 532 may receive Access and Mobility Subscription data, SMF Selection Subscription data, and UE context in SMF data using a Nudm_SDM_Get message if the new AMF 532 does not include subscription data for the UE.
  • the UDM 550 receive the Access and Mobility Subscription data from a UDR via a Nudr_DM_Query message.
  • the new AMF 532 may subscribe to be notified using Nudm_SDM_Subscribe when the data requested is updated/modified.
  • the UDM 550 may subscribe to UDR by Nudr_DM_Subscribe to be notified if the requested data is updated/modified.
  • the subscription may include an update to the slice information and/or the CAG information.
  • the new AMF 532 may determine whether the CAG provided by a NG-RAN is included in a 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 procedure and transmit a proper cause.
  • step 502A-502B assuming that the CAG provided by a NG-RAN included in a subscribed CAG list, the AMF 532 and NSSF 540 may communicate to receive an updated allowed NSSAI from the NSSF.
  • the message from the new AMF 532 to NSSF 540 may include a request for an updated allowed NSSAI via a Nnssf_NSSelection_Get message.
  • This message may include at least one of a Requested NSSAI, a Mapping of Requested NSSAI, a subscribed S-NSSAI (s) with the default S-NSSAI indication, a TAI, an Allowed NSSAI for the other access type (if any) , a Mapping of Allowed NSSAI, a PLMN ID of the SUPI, and a CAG ID.
  • the CAG ID may be provided by the NG-RAN.
  • the response from the NSSF 540 to the new AMF 532 may include the updated allowed NSSAI via a Nnssf_NSSelection_Get message.
  • This message may include at least one of a AMF Set or list of AMF addresses, an allowed NSSAI for the first access type, a Mapping Of Allowed NSSAI, an allowed NSSAI for the second access type, a mapping of allowed NSSAI, a NSI ID (s) , a NRF (s) , a list of rejected S-NSSAI (s) or cause value (s) , a configured NSSAI for the Serving PLMN, and a mapping of configured NSSAI.
  • the NSSF may generate the allowed NSSAI (i.e. NG-RAN) based on the CAG ID.
  • the new AMF 532 may notify the UE 510 of an allowed NSSAI or that there is no new allowed NSSAI. If the new AMF 532 includes a previously-received (or “old” ) Allowed NSSAI (e.g. receiving the allowed NSSAI from the old AMF) , the new AMF 532 may compare the old Allowed NSSAI and 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.
  • a previously-received (or “old” ) Allowed NSSAI e.g. receiving the allowed NSSAI from the old AMF
  • the new AMF 532 may compare the old Allowed NSSAI and the newly-received/updated Allowed NSSAI received by the NSSF in 502B. If the old allowed NSSA
  • FIG. 6 illustrates a block diagram of a method to support a public network integrated non-public network.
  • a node may transmit a first request to a second node requesting information that assists in selecting a network for a terminal that is associated with a first network that is non-public and a first access group 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 include a NS selection request, as illustrated in Step 303A of FIG. 4, Step 502A of FIG. 5, or Step 602A of FIG. 5, for example.
  • An example of the node may include the AMF as described in the present disclosure.
  • An example of the second node may include the NSSF as described in the present disclosure.
  • An example of a network that is non-public may include a non-public network or public network integrated non-public network, as described in the present disclosure.
  • the method includes the node receiving a first response from the second node that includes the information that assists in selecting the logical network for the terminal associated with the first logical network and the first access group associated with the first network node (block 604) .
  • the first response may include the NS Selection Response message, as illustrated in Step 303B of FIG. 4, Step 502B of FIG. 5, or Step 602B of FIG. 5, for example.
  • the information that assists in selecting a logical network for a terminal may include the allowed NSSAI as described in the present disclosure.
  • An example of the first logical network configured to perform network functions may include a network slice (e.g., Slice1) , as described in the present disclosure.
  • the first access group associated with a first network node may include a CAG (e.g., CAG1) as described in the present disclosure.
  • the first access group identifier identifying the first access group associated with the terminal may include a CAG ID associated with the terminal, as described in the present disclosure.
  • the second node is configured to store a mapping between the first access group and the information that assists in selecting the logical network.
  • the method includes receiving, by the node, a registration request from one of the first network node and the terminal, the first network node adding the first access group identifier identifying the first access group associated with the terminal to the registration request.
  • the method includes transmitting, by the node, the first access group identifier to the second node in the first request.
  • the method includes transmitting, by the node, 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.
  • the method includes receiving, by the node, 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 that the terminal is allowed to access.
  • the method includes transmitting, by the node, the at least one access group identifier identifying at least one access group that the terminal is allowed to access to the second node.
  • the third node is configured to retrieve the mobility subscription information from a fourth node that includes a repository of data and subscribe to the fourth node.
  • the information that assists in selecting the network for the terminal is represented as allowed network slice selected assistance information (NSSAI) .
  • NSSAI network slice selected assistance information
  • the method includes transmitting, by the node, a registration acceptance message to the terminal including the information that assists in selecting the network for the terminal.
  • the method includes receiving, by the node, 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 identifying the second access group associated with the terminal.
  • the method includes transmitting, by the node, the second access group identifier to the second node in the first request.
  • the method includes receiving, by the node, at least one of a path switch request message and an initial UE message from the second network node, wherein the path switch request message and the initial UE message includes at least one of a new target cell identifier and the second access group identifier.
  • the method includes receiving, by the node, a subscriber data update notification from the third node that includes a subscriber data update indicating a change to at least one of the first network and the access group configuration; determining, by the node, whether to transmit a third request to the second node requesting a second set of information that assists in selecting a network for the terminal based on the change to at least one of the first network and the access group configuration; and transmitting, by the node, the third request to the second node requesting the second set of information that assists in selecting the network for the terminal associated with at least one of a second network that is non-public and the second access group of the second network node, wherein the third request includes the second access group identifier identifying the second access group associated with the terminal.
  • the method includes transmitting, by the node, a deregistration message to the terminal to deregister the terminal based on determining that the configuration of the first access group is updated and the first access group identifier is not associated with the terminal.
  • the method includes receiving, by the node, a third response from the second node that includes the second set of information that assists in selecting the network for the terminal associated with at least one of the second network and the second access group.
  • the method includes transmitting, by the node, a second registration acceptance message to the terminal including the second set of information that assists in selecting a logical network for the terminal.
  • the method includes transmitting, by the node, 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.
  • a second network node is configured to transmit a notification message to a fifth node configured to manage terminal access and mobility, the notification message including a second access group identifier identifying a second access group associated with the terminal.
  • the notification message to the fifth node includes a re-routed non-access stratum (NAS) message and the second access group identifier.
  • NAS non-access stratum
  • the fifth node is configured to transmit a mobility subscription data request message requesting mobility subscription data of the terminal from a third node configured to manage and store mobility subscription information.
  • the fifth node is configured to transmit a fourth request to the second node requesting a third set of information that assists in selecting a network for the terminal based on the second access group identifier.
  • the fifth node is configured to receive a fourth response that includes the third set of information that assists in selecting the logical network from the second node.
  • the fifth node is configured to compare the third set of information that assists in selecting the logical network and the information that assists in selecting the logical network, and wherein the fifth node is configured to transmit the third set of information that assists in selecting the logical network to the terminal if the information that assists in selecting the logical network is different than the third set of information that assists in selecting the logical network.
  • FIG. 7 shows an example of a wireless communication system where techniques in accordance with one or more embodiments of the present technology can be applied.
  • a wireless communication system 700 can include one or more base stations (BSs) 705a, 705b, one or more wireless devices 710a, 710b, 710c, 710d, and a core network 725.
  • a base station 705a, 705b can provide wireless service to wireless devices 710a, 710b, 710c and 710d in one or more wireless sectors.
  • a base station 705a, 705b includes directional antennas to produce two or more directional beams to provide wireless coverage in different sectors.
  • the core network 725 can communicate with one or more base stations 705a, 705b.
  • the core network 725 provides connectivity with other wireless communication systems and wired communication systems.
  • the core network may include one or more service subscription databases to store information related to the subscribed wireless devices 710a, 710b, 710c, and 710d.
  • a first base station 705a can provide wireless service based on a first radio access technology
  • a second base station 705b can provide wireless service based on a second radio access technology.
  • the base stations 705a and 705b may be co-located or may be separately installed in the field according to the deployment scenario.
  • the wireless devices 710a, 710b, 710c, and 710d can support multiple different radio access technologies.
  • a wireless communication system can include multiple networks using different wireless technologies.
  • a dual-mode or multi-mode wireless device includes two or more wireless technologies that could be used to connect to different wireless networks.
  • FIG. 8 is a block diagram representation of a portion of a hardware platform.
  • a hardware platform 805 such as a network device or a base station or a wireless device (or UE) can include processor electronics 810 such as a microprocessor that implements one or more of the techniques presented in this document.
  • the hardware platform 805 can include transceiver electronics 815 to send and/or receive wired or wireless signals over one or more communication interfaces such as antenna 820 or a wireline interface.
  • the hardware platform 805 can implement other communication interfaces with defined protocols for transmitting and receiving data.
  • the hardware platform 805 can include one or more memories (not explicitly shown) configured to store information such as data and/or instructions.
  • the processor electronics 810 can include at least a portion of the transceiver electronics 815. In some embodiments, at least some of the disclosed techniques, modules or functions are implemented using the hardware platform 805.
  • the disclosed and other embodiments, modules and the functional operations described in this document can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this document and their structural equivalents, or in combinations of one or more of them.
  • the disclosed and other embodiments can 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 composition of matter effecting a machine-readable propagated signal, or a combination of one or more them.
  • data processing apparatus encompasses 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, 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 in this document 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.
  • 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 performing instructions and one or more memory devices for storing instructions and data.
  • 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.
  • mass storage devices for storing data, e.g., magnetic, magneto optical disks, or optical disks.
  • a computer need not have such devices.
  • 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, e.g., internal hard disks or removable disks; magneto optical disks; and CD ROM and DVD-ROM disks.
  • semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
  • magnetic disks e.g., internal hard disks or removable disks
  • magneto optical disks e.g., CD ROM and DVD-ROM disks.
  • the processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne des procédés, des systèmes et des dispositifs concernant les communications sans fil numériques et, plus précisément, des techniques associées à la prise en charge d'un réseau non public intégré à un réseau public. Dans un aspect donné à titre d'exemple, un procédé de communication sans fil consiste à transmettre une première demande à un second nœud demandant des informations qui aident à sélectionner un réseau pour un terminal qui est associé à un premier réseau qui est non public et un premier groupe d'accès associé à un premier nœud de réseau, la première demande comprenant un premier identifiant de groupe d'accès identifiant le premier groupe d'accès associé au terminal. Le procédé consiste également à recevoir une première réponse en provenance du second nœud qui comprend les informations qui aident à sélectionner le réseau pour le terminal associé au premier réseau et le premier groupe d'accès associé au premier nœud de réseau.
PCT/CN2019/078273 2019-03-15 2019-03-15 Prise en charge d'un réseau non public intégré à un réseau public WO2020186387A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2019/078273 WO2020186387A1 (fr) 2019-03-15 2019-03-15 Prise en charge d'un réseau non public intégré à un réseau public
CN201980094192.8A CN113647148A (zh) 2019-03-15 2019-03-15 支持集成有公共网络的非公共网络

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/078273 WO2020186387A1 (fr) 2019-03-15 2019-03-15 Prise en charge d'un réseau non public intégré à un réseau public

Publications (1)

Publication Number Publication Date
WO2020186387A1 true WO2020186387A1 (fr) 2020-09-24

Family

ID=72519442

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/078273 WO2020186387A1 (fr) 2019-03-15 2019-03-15 Prise en charge d'un réseau non public intégré à un réseau public

Country Status (2)

Country Link
CN (1) CN113647148A (fr)
WO (1) WO2020186387A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114389943A (zh) * 2020-10-22 2022-04-22 中移(成都)信息通信科技有限公司 一种网络配置方法、装置、设备及计算机存储介质
WO2022083438A1 (fr) * 2020-10-21 2022-04-28 华为技术有限公司 Procédé d'enregistrement de réseau
WO2022069481A3 (fr) * 2020-10-01 2022-05-12 Nokia Technologies Oy Procédé, appareil et produit-programme informatique pour une configuration de sélection de tranche de réseau et de bande de fréquence
US11445335B2 (en) * 2018-08-17 2022-09-13 Huawei Technologies Co., Ltd. Systems and methods for enabling private communication within a user equipment group
WO2023077391A1 (fr) * 2021-11-05 2023-05-11 Zte Corporation Procédé d'accès et décision de politique de mobilité
WO2023153842A1 (fr) * 2022-02-09 2023-08-17 삼성전자 주식회사 Procédé et appareil de gestion de configuration de terminal à l'aide d'un message nas dans un système de communication sans fil
WO2023241502A1 (fr) * 2022-06-16 2023-12-21 中国移动通信有限公司研究院 Procédé de contrôle d'accès, procédé de facturation, appareil, dispositif de communication et support de stockage
WO2024114288A1 (fr) * 2022-12-01 2024-06-06 华为技术有限公司 Procédé d'accès au réseau et appareil de communication

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114760209B (zh) * 2022-03-29 2022-11-18 广州爱浦路网络技术有限公司 数据处理方法、系统、装置及存储介质
CN116170859B (zh) * 2023-02-27 2023-10-31 广州爱浦路网络技术有限公司 无线接入方法、装置、计算机设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013029672A1 (fr) * 2011-08-31 2013-03-07 Telefonaktiebolaget L M Ericsson (Publ) Informations de recherche de réseau d'accès contrôlé via une politique andsf
CN103327453A (zh) * 2012-03-22 2013-09-25 北京三星通信技术研究有限公司 一种选择pcef和pcrf的方法
WO2016123247A1 (fr) * 2015-01-29 2016-08-04 Blackberry Limited Communication dans un spectre sans licence
WO2018229694A1 (fr) * 2017-06-16 2018-12-20 Telefonaktiebolaget Lm Ericsson (Publ) Sélection de cellule, resélection de cellule, et résidence sur une cellule

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107580360A (zh) * 2016-07-04 2018-01-12 中国移动通信有限公司研究院 一种网络切片选择的方法、设备及网络架构
EP3557913B1 (fr) * 2017-05-09 2022-10-19 Huawei Technologies Co., Ltd. Procédé et appareil de mise à jour de politique de sélection de tronçon de réseau

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013029672A1 (fr) * 2011-08-31 2013-03-07 Telefonaktiebolaget L M Ericsson (Publ) Informations de recherche de réseau d'accès contrôlé via une politique andsf
CN103327453A (zh) * 2012-03-22 2013-09-25 北京三星通信技术研究有限公司 一种选择pcef和pcrf的方法
WO2016123247A1 (fr) * 2015-01-29 2016-08-04 Blackberry Limited Communication dans un spectre sans licence
WO2018229694A1 (fr) * 2017-06-16 2018-12-20 Telefonaktiebolaget Lm Ericsson (Publ) Sélection de cellule, resélection de cellule, et résidence sur une cellule

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11445335B2 (en) * 2018-08-17 2022-09-13 Huawei Technologies Co., Ltd. Systems and methods for enabling private communication within a user equipment group
WO2022069481A3 (fr) * 2020-10-01 2022-05-12 Nokia Technologies Oy Procédé, appareil et produit-programme informatique pour une configuration de sélection de tranche de réseau et de bande de fréquence
WO2022083438A1 (fr) * 2020-10-21 2022-04-28 华为技术有限公司 Procédé d'enregistrement de réseau
CN114389943A (zh) * 2020-10-22 2022-04-22 中移(成都)信息通信科技有限公司 一种网络配置方法、装置、设备及计算机存储介质
CN114389943B (zh) * 2020-10-22 2023-08-15 中移(成都)信息通信科技有限公司 一种网络配置方法、装置、设备及计算机存储介质
WO2023077391A1 (fr) * 2021-11-05 2023-05-11 Zte Corporation Procédé d'accès et décision de politique de mobilité
WO2023153842A1 (fr) * 2022-02-09 2023-08-17 삼성전자 주식회사 Procédé et appareil de gestion de configuration de terminal à l'aide d'un message nas dans un système de communication sans fil
WO2023241502A1 (fr) * 2022-06-16 2023-12-21 中国移动通信有限公司研究院 Procédé de contrôle d'accès, procédé de facturation, appareil, dispositif de communication et support de stockage
WO2024114288A1 (fr) * 2022-12-01 2024-06-06 华为技术有限公司 Procédé d'accès au réseau et appareil de communication

Also Published As

Publication number Publication date
CN113647148A (zh) 2021-11-12

Similar Documents

Publication Publication Date Title
WO2020186387A1 (fr) Prise en charge d'un réseau non public intégré à un réseau public
CN110291837B (zh) 网络注册和网络切片选择系统和方法
JP7075066B2 (ja) ネットワークスライス選択ポリシを用いたｕｅの構成および更新
US20210352465A1 (en) Method for performing service parameter provisioning to ue and network in 5g system
US20240007878A1 (en) Minimization of service interruption
EP4138438A1 (fr) Procédé et appareil de communication, et puce
US20220116816A1 (en) Method of authorization for network slicing
US11503533B2 (en) Method of registration with access and mobility management function re-allocation
KR20170083073A (ko) 통신 네트워크들에서 그룹 통신 메시지들을 전달하는 그룹 통신 기능
US20230362766A1 (en) Access network node, user equipment, network function node and control method
JP2019518395A (ja) ローカル・ネットワーク・コネクション方法、装置、及びシステム
US20220303935A1 (en) Amf re-allocation solution with network slice isolation
KR101010816B1 (ko) 이동성 관리를 촉진시키는 장치 및 방법
US20220225459A1 (en) Communication network component and method for handling a service request
JP2023535961A (ja) 通信端末、コアネットワークノード、及び方法
WO2021233980A1 (fr) Manipulation d'un id de cellule fourni par un ue dans de grandes tailles de cellules
WO2023193128A1 (fr) Procédé de sélection de réseau sur la base d'informations de tranche
WO2023279387A1 (fr) Procédé, dispositif et produit programme informatique pour communication sans fil
US20240171963A1 (en) Method, device and computer program product for wireless communication
CN117528462B (zh) 一种多网络组网实现的工业物联网的数据传输方法
WO2024040436A1 (fr) Schémas de communication sans fil de prise en charge de découpage en tranches de réseau
WO2022217571A1 (fr) Procédé et appareil d'authentification pour tranche de réseau, et dispositif et support de stockage
KR20220163439A (ko) 네트워크 요청 등록 절차 개시
CN114466346A (zh) 获取边缘服务的方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19920289

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19920289

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 19920289

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 20.05.22)

122 Ep: pct application non-entry in european phase

Ref document number: 19920289

Country of ref document: EP

Kind code of ref document: A1