WO2020074542A1 - Nssai configurées pour d'autres plmn - Google Patents

Nssai configurées pour d'autres plmn Download PDF

Info

Publication number
WO2020074542A1
WO2020074542A1 PCT/EP2019/077268 EP2019077268W WO2020074542A1 WO 2020074542 A1 WO2020074542 A1 WO 2020074542A1 EP 2019077268 W EP2019077268 W EP 2019077268W WO 2020074542 A1 WO2020074542 A1 WO 2020074542A1
Authority
WO
WIPO (PCT)
Prior art keywords
amf
network
nssai
processing circuitry
plmn
Prior art date
Application number
PCT/EP2019/077268
Other languages
English (en)
Inventor
Peter Hedman
Kaj Johansson
Qian Chen
Sune Gustafsson
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2020074542A1 publication Critical patent/WO2020074542A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection

Definitions

  • the present disclosure relates to means for providing Public Land Mobile Networks (PLMNs) configured Network Slice Selection Assistance Information (NSSAI).
  • PLMNs Public Land Mobile Networks
  • NSSAI Network Slice Selection Assistance Information
  • a Network Slice is introduced as a logical network that provides specific network capabilities and network characteristics.
  • An instance of a network slice i.e., a network slice instance
  • NF Network Function
  • a NF is a 3GPP adopted or 3GPP defined processing function in a network, which has defined functional behavior and 3GPP defined interfaces.
  • a NF can be implemented either as a network element on dedicated hardware, a software instance running on a dedicated hardware, or as a virtualized functional instantiated on an appropriate platform, e.g., on a cloud infrastructure.
  • a Network Slice is identified by Single Network Slice Selection Assistance Information (S-NSSAI), which is comprised of a slice/service type (SST) that refers to the expected network slice behavior in terms of features and services and a slice differentiator (SD) that is optional information that complements the SST(s) to differentiate amongst multiple network slices of the same SST.
  • SST slice/service type
  • SD slice differentiator
  • a network can provide UE with slice info which can include allowed NSSAI and configured NSSAI. However, it’s only limited to the current PLMN that UE is registered on. See below text from Third Generation Partnership Project (3GPP) Technical Specification (TS) 23.501 V15.3.0:
  • An S-NSSAI identifies a Network Slice.
  • An S-NSSAI is comprised of:
  • SST Slice/Service type
  • a Slice Differentiator which is optional information that complements the Slice/Service type(s) to differentiate amongst multiple Network Slices of the same Slice/Service type.
  • An S-NSSAI can have standard values (i.e. such S-NSSAI is only comprised of an SST with a standardised SST value, see clause 5.15.2.2, and no SD) or non-standard values (i.e. such S-NSSAI is comprised of either both an SST and an SD or only an SST without a standardised SST value and no SD).
  • An S-NSSAI with a non-standard value identifies a single Network Slice within the PLMN with which it is associated.
  • An S-NSSAI with a non-standard value shall not be used by the UE in access stratum procedures in any PLMN other than the one to which the S-NSSAI is associated.
  • Subscribed S-NSSAIs (see clause 5.15.3) contain only HPLMN S-NSSAI values.
  • the S-NSSAIs in the Configured NSSAI, the Allowed NSSAI (see clause 5.15.4.1), the Requested NSSAI (see clause 5.15.5.2.1), the Rejected S-NSSAIs contain only values from the Serving PLMN.
  • the Serving PLMN can be the HPLMN or a VPLMN.
  • the UE stores (S-) NSSAI s as follows:
  • the Configured NSSAI and/or if present, the associated mapping shall both be stored in the UE until a new Configured NSSAI for this PLMN and/or the associated mapping are provisioned in the UE, or until the network slicing subscription changes, as described in clause 5.15.4.2:
  • the UE When provisioned with a new Configured NSSAI for a PLMN and/or the new associated mapping of this Configured NSSAI to HPLMN S-NSSAIs, or when requested to remove the configuration due to network slicing subscription change, the UE shall:
  • the UE keeps storing a received Configured NSSAI for a PLMN and associated mapping to HPLMN S-NSSAIs even when registering in another PLMN.
  • the number of Configured NSSAIs and associated mapping to be kept stored in the UE for PLMNs other than the HPLMN is up to UE implementation.
  • a UE shall at least be capable of storing a Configured NSSAI for the serving PLMN including any necessary mapping of the Configured NSSAI for the Serving PLMN to HPLMN S-NSSAIs and the Default Configured NSSAI.
  • the Allowed NSSAI for a PLMN and Access Type and any associated mapping of this Allowed NSSAI to HPLMN S-NSSAIs shall be stored in the UE.
  • the UE should store this Allowed NSSAI and any associated mapping of this Allowed NSSAI to HPLMN S-NSSAIs also when the UE is turned off, or until the network slicing subscription changes, as described in clause 5.15.4.2:
  • the UE When a new Allowed NSSAI for a PLMN and any associated mapping of the Allowed NSSAI to HPLMN S-NSSAIs are received over an Access Type, the UE shall:
  • an S-NSSAI rejected for the entire PLMN shall be stored in the UE while RM- REGISTERED in this PLMN regardless of the Access Type or until it is deleted.
  • an S-NSSAI rejected for the current Registration Area shall be stored in the UE while RM-REGISTERED until the UE moves out of the current Registration Area or until the S-NSSAI is deleted.
  • the UE When a UE registers over an Access Type with a PLMN, if the UE for this PLMN has a Configured NSSAI for this PLMN and the Access Type has an Allowed NSSAI, the UE shall provide to the network in AS layer and NAS layer a Requested NSSAI containing the S-NSSAI(s) corresponding to the slice(s) to which the UE wishes to register, in addition to the 5G-S-TMSI if one was assigned to the UE.
  • the Requested NSSAI shall be one of:
  • the Configured-NSSAI or a subset thereof as described below, e.g. if the UE has no Allowed NSSAI for the Access Type for the serving PLMN; or
  • Allowed-NSSAI for the Access Type over which the Requested NSSAI is sent, or a subset thereof, plus one or more S-NSSAIs from the Configured-NSSAI not yet in the Allowed NSSAI for the Access Type as described below.
  • the subset of S-NSSAIs in the Configured-NSSAI provided in the Requested NSSAI consists of one or more S-NSSAI(s) in the Configured NSSAI applicable to this PLMN, if one is present, and for which no corresponding S-NSSAI is already present in the Allowed NSSAI for the access type for this PLMN.
  • the UE shall not include in the Requested NSSAI any S-NSSAI that is currently rejected by the network (i.e. rejected in the current registration area or rejected in the PLMN).
  • the S-NSSAIs provided in the Requested NSSAI correspond to the S-NSSAI(s) in the Default Configured NSSAI.
  • the UE When a UE registers over an Access Type with a PLMN, the UE shall also indicate in the Registration Request message when the Requested NSSAI is based on the Default Configured NSSAI.
  • the UE shall include the Requested NSSAI in the RRC Connection Establishment and in the establishment of the connection to the N3IWF (as applicable) and in the NAS Registration procedure messages. However, the UE shall not indicate any NSSAI in RRC Connection Establishment or Initial NAS message unless it has either a Configured NSSAI for the corresponding PLMN, an Allowed NSSAI for the corresponding PLMN and Access Type, or the Default Configured NSSAI.
  • the (R)AN shall route the NAS signalling between this UE and an AMF selected using the Requested NSSAI obtained during RRC Connection Establishment or connection to N3IWF respectively. If the (R)AN is unable to select an AMF based on the Requested NSSAI, it routes the NAS signalling to an AMF from a set of default AMFs. In the NAS signalling the UE provides the mapping of each S- NSSAI of the Requested NSSAI to a corresponding FIPLMN S-NSSAI.
  • the Configured NSSAI will be stored by UE per PLMN and access type. For a UE moves to a PLMN for the first time, it’s normally lack of the“Configured NSSAI” from this particular PLMN, thus the formulation of the Requested NSSAI when first time Registering to this PLMN is not accurate which may impact the slice selectin in the PLMN and creates latency
  • the network can be deployed in different ways. It can support multiple PLMNs (as part of the shared network) where the network by itself supports several PLMNs in the same NF (e.g. AMF) and owns all the info valid for all the PLMNs). The network even can consider UE is registered at different PLMNs at the same time if the network allocates a registration area which includes TAIs from different PLMNs
  • UE handling of the Configuration NSSAI shall be improved to handle the possibilities with multiple PLMNs included.
  • Certain embodiments may provide one or more of the following technical advantage(s).
  • Figure 1 is a call-flow diagram illustrating a general registration process according to one embodiment of the present disclosure
  • Figure 2 is a call-flow diagram illustrating a registration procedure with AMF re-allocation according to one embodiment of the present disclosure
  • Figure 3 is a schematic illustration of a wireless network in which embodiments described herein can be
  • Figure 4 is a schematic illustration of a 5G network architecture, wherein interaction between any two NFs is represented by a point-to-point reference point/interface;
  • Figure 5 is a schematic illustration of a 5G network architecture using service-based interfaces between the NFs in the control plane;
  • FIG. 6 is a schematic illustration of one embodiment of a UE in accordance with various aspects described herein;
  • Figure 7 is a schematic block diagram illustrating a virtualization environment in which some embodiments described herein can be implemented.
  • a Network Slice is defined within a PLMN and shall include:
  • the N3IWF functions to the non-3GPP Access Network described in clause 4.27.2 of 3GPP TS 23.501 V15.3.0.
  • the 5G System deployed in a PLMN shall always support the procedures, information, and configurations specified for network slicing in the present document, 3GPP TS 23.502 and 3GPP TS 23.503.
  • a Network Slice is defined per PLMN, but an operator can make the same Network Slice to be applicable for multiple PLMN IDs and in such case the Registration Area can include TAIs from more than one PLMN ID.
  • Network slicing support for roaming is described in clause 5.15.6 of 3GPP TS 23.501 V15.3.0.
  • Network slices may differ for supported features and network functions optimizations, in which case such Network Slices may have e.g. different S-NSSAIs with different Slice/Service Types (see clause 5.15.2.1 of 3GPP TS 23.501 V15.3.0).
  • the operator can deploy multiple Network Slice instances delivering exactly the same features but for different groups of UEs, e.g. as they deliver a different committed service and/or because they are dedicated to a customer, in which case such Network Slices may have e.g. different S-NSSAIs with the same Slice/Service Type but different Slice Differentiators (see clause 5.15.2.1 of 3GPP TS 23.501 V15.3.0).
  • An S-NSSAI identifies a Network Slice.
  • An S-NSSAI is comprised of:
  • SST Slice/Service type
  • a Slice Differentiator which is optional information that complements the Slice/Service type(s) to differentiate amongst multiple Network Slices of the same Slice/Service type.
  • An S-NSSAI can have standard values (i.e. such S-NSSAI is only comprised of an SST with a standardised SST value, see clause 5.15.2.2, and no SD) or non-standard values (i.e. such S-NSSAI is comprised of either both an SST and an SD or only an SST without a standardised SST value and no SD).
  • An S-NSSAI with a non-standard value identifies a single Network Slice within the PLMN with which it is associated.
  • An S-NSSAI with a non-standard value shall not be used by the UE in access stratum procedures in any PLMN other than the one to which the S-NSSAI is associated.
  • the S-NSSAIs in the NSSP of the URSP rules (see 3GPP TS 23.503 clause 6.6.2) and in the Subscribed S- NSSAIs (see clause 5.15.3 of 3GPP TS 23.501 V15.3.0) contain only HPLMN S-NSSAI values.
  • the S-NSSAIs in the Configured NSSAI, the Allowed NSSAI (see clause 5.15.4.1), the Requested NSSAI (see clause 5.15.5.2.1), the Rejected S-NSSAIs contain values from the Serving PLMN.
  • the Serving PLMN can be the HPLMN or a VPLMN.
  • the S-NSSAIs in the configured NSSAI from network to UE may also include NSSAI information for multiple PLMNs.
  • the AMF may have the configured NSSAI of other PLMNs either based on the location configuration (e.g. typically when you have the multiple PLMNs support in the AMF) in the AMF or may be retrieved from NSSF and O&M system (e.g. typically when there is separate core network but with close cooperation between 2 PLMNs).
  • the Network Slice configuration information contains one or more Configured NSSAI(s).
  • a Configured NSSAI may either be configured by a Serving PLMN and apply to the Serving PLMN, or may be a Default Configured NSSAI configured by the HPLMN and that applies to any PLMNs for which no specific Configured NSSAI has been provided to the UE. There is at most one Configured NSSAI per PLMN. For networks which make use of multiple PLMN IDs, the Configured NSSAI may include a list of PLMN IDs that the Configured NSSAI relates to.
  • the value(s) used in the Default Configured NSSAI are expected to be commonly decided by all roaming partners, e.g. by the use of values standardized by 3GPP or other bodies.
  • the Default Configured NSSAI if it is configured in the UE, is used by the UE in a Serving PLMN only if the UE has no Configured NSSAI for the Serving PLMN.
  • Figure 1 is a call-flow diagram illustrating a general registration process according to one embodiment of the present disclosure. The details of this process are described below.
  • UE to (R)AN AN message (AN parameters, Registration Request (Registration type, SUCI or 5G-GUTI or PEI, last visited TAI (if available), Security parameters, Requested NSSAI, [Mapping Of Requested NSSAI], Default Configured NSSAI Indication, UE Radio Capability Update, UE MM Core Network Capability, PDU Session status, List Of PDU Sessions To Be Activated, follow-on request, MICO mode preference, Requested DRX parameters, [LADN DNN(s) or Indicator Of Requesting LADN Information]) and UE Policy Container (the list of PSIs, indication of UE support for ANDSP)).
  • AN message AN parameters, Registration Request (Registration type, SUCI or 5G-GUTI or PEI, last visited TAI (if available), Security parameters, Requested NSSAI, [Mapping Of Requested NSSAI], Default Configured NSSAI Indication, UE Radio Capability Update, UE MM Core Network Capability, PDU
  • the AN parameters include e.g. SUCI or the 5G-GUTI, the Selected PLMN ID and Requested NSSAI, the AN parameters also include Establishment cause.
  • the Establishment cause provides the reason for requesting the establishment of an RRC connection.
  • the Registration type indicates if the UE wants to perform an Initial Registration (i.e. the UE is in RM- DEREGISTERED state), a Mobility Registration Update (i.e. the UE is in RM-REGISTERED state and initiates a Registration procedure due to mobility or due to the UE needs to update its capabilities or protocol parameters, or to request a change of the set of network slices it is allowed to use), a Periodic Registration Update (i.e. the UE is in RM- REGISTERED state and initiates a Registration procedure due to the Periodic Registration Update timer expiry, see clause 4.2.2.2.1 of 3GPP TS 23.502 V15.3.0) or an Emergency Registration (i.e. the UE is in limited service state).
  • an Initial Registration i.e. the UE is in RM- DEREGISTERED state
  • a Mobility Registration Update i.e. the UE is in RM-REGISTERED state and initiates a Registration procedure due to mobility or due to the UE needs to update its capabilities or
  • the UE When the UE is performing an Initial Registration the UE shall indicate its UE identity in the Registration Request message as follows, listed in decreasing order of preference:
  • This can also be a 5G-GUTIs assigned via another access type.
  • the UE shall include its SUCI in the Registration Request as defined in 3GPP TS 33.501.
  • the UE When the UE is performing an Initial Registration (i.e., the UE is in RM-DEREGISTERED state) with a native 5G-GUTI then the UE shall indicate the related GUAMI information in the AN parameters. When the UE is performing an Initial Registration with its SUCI, the UE shall not indicate any GUAMI information in the AN parameters.
  • the UE performs a Mobility Registration and shall not include any GUAMI information in the AN parameters.
  • the SUCI shall be included if the UE does not have a valid 5G-GUTI available; the PEI shall be included when the UE has no SUPI and no valid 5G-GUTI. In other cases, the 5G-GUTI is included and it indicates the last serving AMF.
  • the UE may provide the UE's usage setting based on its configuration as defined in 3GPP TS 23.501 clause 5.16.3.7.
  • the UE includes the Mapping of Requested NSSAI (if available), which is the mapping of each S-NSSAI of the Requested NSSAI to the HPLMN S-NSSAIs, to ensure that the network is able to verify whether the S-NSSAI(s) in the Requested NSSAI are permitted based on the Subscribed S-NSSAIs.
  • the UE includes the Default Configured NSSAI Indication if the UE is using a Default Configured NSSAI, as defined in TS 23.501 [2],
  • the UE includes in the List Of PDU Sessions To Be Activated the PDU Sessions for which there are pending uplink data.
  • the UE shall indicate PDU Sessions only associated with the access the Registration Request is related to.
  • the UE may include PDU Sessions in the List Of PDU Sessions To Be Activated even if there are no pending uplink data for those PDU Sessions.
  • a PDU Session corresponding to a LADN is not included in the List Of PDU Sessions To Be Activated when the UE is outside the area of availability of the LADN.
  • the UE MM Core Network Capability is provided by the UE and handled by AMF as defined in 3GPP TS 23.501 clause 5.4.4a
  • the UE includes in the UE MM Core Network Capability an indication if it supports Request Type flag "handover" for PDN connectivity request during the attach procedure as defined in clause 5.17.2.3.1 of 3GPP TS 23.501.
  • the UE may provide either the LADN DNN(s) or an Indication Of Requesting LADN Information as described in 3GPP TS 23.501 clause 5.6.5. If available, the last visited TAI shall be included in order to help the AMF produce Registration Area for the UE.
  • the Security parameters are used for Authentication and integrity protection, see 3GPP TS 33.501.
  • the Requested NSSAI indicates the Network Slice Selection Assistance Information (as defined in clause 5.15 of 3GPP TS 23.501 [2]).
  • the PDU Session status indicates the previously established PDU Sessions in the UE.
  • the PDU Session status indicates the established PDU Session of the current PLMN in the UE.
  • the Follow-on request is included when the UE has pending uplink signaling and the UE doesn't include List of PDU Sessions To Be Activated, or the Registration type indicates the UE wants to perform an Emergency Registration.
  • UE provides the UE Requested DRX parameters, as defined in clause 5.4.5 of 3GPP TS 23.501.
  • the UE provides UE Radio Capability Update indication as described in 3GPP TS 23.501.
  • the UE access selection and PDU session selection identifies the list of UE access selection and PDU session selection policy information stored in the UE, defined in clause 6.6 of 3GPP TS 23.503. They are used by the PCF to determine if the UE has to be updated with new PSIs or if some of the stored ones are no longer applicable and have to be removed.
  • the (R)AN based on (R)AT and Requested NSSAI, if available, selects an AMF.
  • the (R)AN selects an AMF as described in 3GPP TS 23.501 , clause 6.3.5. If UE is in CM-CONNECTED state, the (R)AN can forward the Registration Request message to the AMF based on the N2 connection of the UE. If the (R)AN cannot select an appropriate AMF, it forwards the Registration Request to an AMF which has been configured, in (R)AN, to perform AMF selection.
  • the N2 parameters include the Selected PLMN ID, Location Information and Cell Identity related to the cell in which the UE is camping, UE Context Request which indicates that a UE context including security information needs to be setup at the NG-RAN.
  • the N2 parameters also include the Establishment cause. Mapping Of Requested NSSAI is provided only if available. If the Registration type indicated by the UE is Periodic Registration Update, then steps 4 to 20 may be omitted.
  • new AMF NudsfJJnstructured Data Management_Query().
  • new AMF and old AMF are in the same AMF Set and UDSF is deployed, the new AMF retrieves the stored UE's SUPI and UE context directly from the UDSF using Nudsf_UnstructuredDataManagement_Query service operation or they can share stored UE context via implementation specific means if UDSF is not deployed. This includes also event subscription information by each NF consumer for the given UE. In this case, the new AMF uses integrity protected complete Registration request NAS message to perform and verify integrity protection.
  • the old AMF uses either 5G-GUTI and the integrity protected complete Registration request NAS message, or the SUPI and an indication that the UE is validated from the new AMF, to verify integrity protection if the context transfer service operation invocation corresponds to the UE requested.
  • the old AMF also transfers the event subscriptions information by each NF consumer, for the UE, to the new AMF.
  • the new AMF sets the indication that the UE is validated according to step 9a, in case the new AMF has performed successful UE authentication after previous integrity check failure in the old AMF.
  • the NF consumers do not need to subscribe for the events once again with the new AMF after the UE is successfully registered with the new AMF. If the new AMF has already received UE contexts from the old AMF during handover procedure, then steps 4, 5, and 10 shall be skipped.
  • UDSF Context in AMF (as per Table 5.2.2.2.2-1 of 3GPP TS 23.502 V15.3.0) or UDSF to new AMF: NudsfJJnstructured Data Management_Query().
  • the old AMF may start an implementation specific (guard) timer for the UE context.
  • the UDSF responds to the new AMF for the NudsfJJnstructured Data Management_Query invocation with the related contexts including established PDU Sessions
  • the old AMF includes SMF information DNN, S- NSSAI(s) and PDU Session ID, active NGAP UE-TNLA bindings to N3IWF
  • the old AMF includes information about the NGAP UE-TNLA bindings. If the Old AMF was queried in step 4, Old AMF responds to the new AMF for the
  • Namf_Communication_UEContextTransfer invocation by including the UE's SUPI and UE Context.
  • old AMF holds information about established PDU Session(s)
  • the old AMF includes SMF information, DNN(s), S-NSSAI(s) and PDU Session ID(s).
  • old AMF holds information about active NGAP UE-TNLA bindings to N3IWF
  • the old AMF includes information about the NGAP UE-TNLA bindings.
  • old AMF fails the integrity check of the Registration Request NAS message, the old AMF shall indicate the integrity check failure.
  • old AMF holds information about AM Policy Association
  • the old AMF includes the information about the AM Policy Association including the policy control request trigger and PCF ID. In the roaming case, V-PCF ID and H-PCF ID are included.
  • UE to new AMF Identity Response ().
  • the UE responds with an Identity Response message including the SUCI.
  • the UE derives the SUCI by using the provisioned public key of the HPLMN, as specified in 3GPP TS 33.501.
  • the AMF may decide to initiate UE authentication by invoking an AUSF. In that case, the AMF selects an AUSF based on SUPI or SUCI, as described in 3GPP TS 23.501 , clause 6.3.4. If the AMF is configured to support Emergency Registration for unauthenticated SUPIs and the UE indicated Registration type Emergency Registration, the AMF skips the authentication or the AMF accepts that the authentication may fail and continues the Registration procedure.
  • the AMF requests it from the AUSF; if Tracing Requirements about the UE are available at the AMF, the AMF provides Tracing Requirements in its request to AUSF.
  • the AUSF shall execute authentication of the UE. The authentication is performed as described in 3GPP TS 33.501.
  • the AUSF selects a UDM as described in 3GPP TS 23.501 , clause 6.3.8 and gets the authentication data from UDM.
  • the AUSF provides relevant security related information to the AMF. In case the AMF provided a SUCI to AUSF, the AUSF shall return the SUPI to AMF only after the authentication is successful.
  • the new AMF invokes step 4 above again and indicates that the UE is validated (i.e. through the reason parameter as specified in clause 5.2.2.2.2 of 3GPP TS 23.502 V15.3.0).
  • the AMF decides if the Registration Request needs to be rerouted as described in clause 4.2.2.2.3 of 3GPP TS 23.502 V15.3.0, where the initial AMF refers to the AMF.
  • the AMF initiates NGAP procedure to provide the 5G-AN with security context as specified in 3GPP
  • the AMF provides the 5G-AN with Tracing Requirements in the NGAP procedure.
  • the 5G-AN stores the security context and acknowledges to the AMF.
  • the 5G-AN uses the security context to protect the messages exchanged with the UE as described in 3GPP TS 33.501.
  • the new AMF invokes the Namf_Communication_RegistrationCompleteNotify service operation with a reject indication reason code towards the old AMF.
  • the old AMF continues as if the UE context transfer service operation was never received.
  • the new AMF determines which PDU Session cannot be supported in the new Registration Area.
  • the new AMF invokes the Namf_Communication_RegistrationCompleteNotify service operation including the rejected PDU Session ID and a reject cause (e.g. the S-NSSAI becomes no longer available) towards the old AMF.
  • the new AMF modifies the PDU Session Status correspondingly.
  • the old AMF informs the corresponding SMF(s) to locally release the UE's SM context by invoking the Nsmf_PDUSession_ReleaseSMContext service operation. See clause 5.2.2.2.3 of 3GPP TS 23.502 V15.3.0 for details of Namf_Communication_RegistrationCompleteNotify service operation.
  • step 2 If new AMF received in the UE context transfer in step 2 the information about the AM Policy Association including the PCF ID(s) and decides, based on local policies, not to use the PCF(s) identified by the PCF ID(s) for the AM Policy Association, then it will inform the old AMF that the AM Policy Association in the UE context is not used any longer and then the PCF selection is performed in step 15. The old AMF terminates the AM Policy Association to the (V-)PCF identified by the PCF ID in step 20.
  • the PEI shall be transferred encrypted unless the UE performs Emergency Registration and cannot be authenticated. For an Emergency Registration, the UE may have included the PEI in the Registration Request. If so, the PEI retrieval is skipped.
  • the new AMF initiates ME identity check by invoking the N5g- eir_EquipmentldentityCheck_Get service operation (see clause 5.2.4.2.2 of 3GPP TS 23.502 V15.3.0).
  • the PEI check is performed as described in clause 4.7 of 3GPP TS 23.502 V15.3.0.
  • For an Emergency Registration if the PEI is blocked, operator policies determine whether the Emergency Registration procedure continues or is stopped.
  • step 14 the new AMF, based on the SUPI, selects a UDM, then UDM may select a UDR instance. See 3GPP TS 23.501 , clause 6.3.9. The AMF selects a UDM as described in 3GPP TS 23.501 , clause 6.3.8.
  • the new AMF registers with the UDM using Nudm_UECM_Registration and subscribes to be notified when the UDM deregisters this AMF.
  • the UDM stores the AMF identity associated to the Access Type and does not remove the AMF identity associated to the other Access Type.
  • the UDM may store information provided at registration in UDR, by Nudr_DM_Update.
  • the AMF provides the "Homogenous Support of IMS Voice over PS Sessions” indication (see
  • the AMF retrieves the Access and Mobility Subscription data, SMF Selection Subscription data and UE context in SMF data using Nudm_SDM_Get. This requires that UDM may retrieve this information from UDR by Nudr_DM_Query. After a successful response is received, the AMF subscribes to be notified using Nudm_SDM_Get. This requires that UDM may retrieve this information from UDR by Nudr_DM_Query. After a successful response is received, the AMF subscribes to be notified using Nudm_SDM_Get. This requires that UDM may retrieve this information from UDR by Nudr_DM_Query. After a successful response is received, the AMF subscribes to be notified using Nudm_SDM_Get. This requires that UDM may retrieve this information from UDR by Nudr_DM_Query. After a successful response is received, the AMF subscribes to be notified using Nudm_SDM_Get. This requires that UDM may retrieve this information from UDR by Nudr_DM_Query. After a successful
  • UDM may subscribe to UDR by Nudr_DM_Subscribe.
  • the GPSI is provided to the AMF in the Access and Mobility Subscription data from the UDM if the GPSI is available in the UE subscription data.
  • the UDM may provide indication that the subscription data for network slicing is updated for the UE. If the UE is subscribed to MPS in the serving PLMN, "MPS priority" is included in the Access and Mobility Subscription data provided to the AMF.
  • the new AMF provides the Access Type it serves for the UE to the UDM and the Access Type is set to "3GPP access".
  • the UDM stores the associated Access Type together with the serving AMF in UDR by
  • the new AMF creates an UE context for the UE after getting the Access and Mobility Subscription data from the UDM.
  • the AMF shall not register with the UDM.
  • the AMF shall not check for access restrictions, regional restrictions or subscription restrictions.
  • the AMF shall ignore any unsuccessful registration response from UDM and continue with the Registration procedure.
  • the UDM When the UDM stores the associated Access Type (e.g. 3GPP) together with the serving AMF as indicated in step 14a, it will cause the UDM to initiate a Nudm_UECM_DeregistrationNotification (see clause 5.2.3.2.2 of 3GPP TS 23.502 V15.3.0) to the old AMF corresponding to the same (e.g. 3GPP) access, if one exists. If the timer started in step 5 is not running, the old AMF may remove the UE context. Otherwise, the AMF may remove UE context when the timer expires.
  • the UDM stores the associated Access Type (e.g. 3GPP) together with the serving AMF as indicated in step 14a, it will cause the UDM to initiate a Nudm_UECM_DeregistrationNotification (see clause 5.2.3.2.2 of 3GPP TS 23.502 V15.3.0) to the old AMF corresponding to the same (e.g. 3GPP) access, if one exists. If the timer started in step
  • the old AMF invokes the Nsmf_PDUSession_ReleaseSMContext (SUPI, PDU Session ID) service operation towards all the associated SMF(s) of the UE to notify that the UE is deregistered from old AMF.
  • the SMF(s) shall release the PDU Session on getting this notification.
  • the old AMF shall perform AN Release (see clause 4.2.6) with a cause value that indicates that the UE has already locally released the NG-RAN's RRC Connection.
  • the AMF acts as follows. If the new AMF decided to contact the (V-)PCF identified by PCF ID included in UE context from the old AMF in step 5, the AMF contacts the (V- )PCF identified by the (V-)PCF ID. If the AMF decides to perform PCF discovery and selection and the AMF selects a (V)-PCF and may select an H-PCF (for roaming scenario) as described in 3GPP TS 23.501, clause 6.3.7.1 and according to the V-NRF to H-NRF interaction described in clause 4.3.2.2.3.3 of 3GPP TS 23.502 V15.3.0.
  • H-PCF for roaming scenario
  • the AMF notifies the Mobility Restrictions (e.g. UE location) to the PCF for adjustment, or if the PCF updates the Mobility Restrictions itself due to some conditions (e.g. application in use, time and date), the PCF shall provide the updated Mobility Restrictions to the AMF. If the subscription information includes Tracing Requirements, the AMF provides the PCF with Tracing Requirements. [0063] 17. [Conditional] AMF to SMF: Nsmf_PDUSession_UpdateSMContext (). For an Emergency Registered
  • this step is applied when the Registration Type is Mobility Registration Update.
  • the AMF invokes the Nsmf_PDUSession_UpdateSMContext (see clause 5.2.8.2.6 of 3GPP TS 23.502 V15.3.0) in the following scenario(s):
  • the AMF sends Nsmf_PDUSession_UpdateSMContext Request to SMF(s) associated with the PDU Session(s) in order to activate User Plane connections of these PDU Session(s).
  • Steps from step 5 onwards described in clause 4.2.3.2 are executed to complete the User Plane connection activation without sending MM NAS Service Accept from the AMF to (R)AN described in step 12 of clause 4.2.3.2 of 3GPP TS 23.502 V15.3.0.
  • the new serving AMF When the serving AMF has changed, the new serving AMF notifies the SMF for each PDU Session that it has taken over the responsibility of the signalling path towards the UE: the new serving AMF invokes the
  • Nsmf_PDUSession_UpdateSMContext service operation using SMF information received from the old AMF at step 5. It also indicates whether the PDU Session is to be re-activated. In the case of PLMN change from V-PLMN to H-PLMN, the new serving AMF only invokes the Nsmf_PDUSession_UpdateSMContext service operation for Home Routed PDU session(s). If the UE moves into a V-PLMN, the AMF in the V-PLMN cannot insert or change the V-SMF(s) even for Home Routed PDU session(s).
  • Steps from step 5 onwards described in clause 4.2.3.2 are executed.
  • the procedure is performed without N11 and N2 interactions to update the N3 user plane between (R)AN and 5GC.
  • the AMF invokes the Nsmf_PDUSession_ReleaseSMContext service operation towards the SMF in the following scenario: If any PDU Session status indicates that it is released at the UE, the AMF invokes the
  • the new AMF shall wait until step 18 is finished with all the SMFs associated with the UE. Otherwise, steps 19 to 22 can continue in parallel to this step.
  • New AMF to N3IWF N2 AMF Mobility Request (). If the AMF has changed and the old AMF has indicated an existing NGAP UE association towards a N3IWF, the new AMF creates an NGAP UE association towards the N3IWF to which the UE is connected. This automatically releases the existing NGAP UE association between the old AMF and the N3IWF
  • the old AMF previously initiated a Policy Association to the PCF, and the old AMF did not transfer the PCF ID(s) to the new AMF (e.g. new AMF is in different PLMN)
  • the old AMF performs an AMF-initiated Policy Association Termination procedure, as defined in clause 4.16.3.2 of 3GPP TS 23.502 V15.3.0, to delete the association with the PCF.
  • the old AMF transfers the PCF ID(s) in the UE context but the new AMF informed in step 10 that the AM Policy Association information in the UE context will not be used then the old AMF performs an AMF-initiated Policy Association Termination procedure, as defined in clause 4.16.3.2 of 3GPP TS 23.502 V15.3.0, to delete the association with the PCF.
  • New AMF to UE Registration Accept (5G-GUTI, Registration Area, Mobility restrictions, PDU Session status, Allowed NSSAI, [Mapping Of Allowed NSSAI], [Configured NSSAI for the Serving PLMN and optionally other PLMNs], [Mapping Of Configured NSSAI], Periodic Registration Update timer, LADN Information and accepted MICO mode, IMS Voice over PS session supported Indication, Emergency Service Support indicator, Accepted DRX parameters, Network support of Interworking without N26, Network Slicing Subscription Change Indication).
  • the Allowed NSSAI for the Access Type for the UE is included in the N2 message carrying the Registration Accept message.
  • the AMF sends a Registration Accept message to the UE indicating that the Registration Request has been accepted.
  • 5G-GUTI is included if the AMF allocates a new 5G-GUTI. If the UE is already in RM-REGISTERED state via another access in the same PLMN, the UE shall use the 5G-GUTI received in the Registration Accept for both registrations. If no 5G-GUTI is included in the Registration Accept, then the UE uses the 5G-GUTI assigned for the existing registration also for the new registration. If the AMF allocates a new Registration area, it shall send the Registration area to the UE via Registration Accept message. If there is no Registration area included in the Registration Accept message, the UE shall consider the old Registration Area as valid.
  • Mobility Restrictions is included in case mobility restrictions applies for the UE and Registration Type is not Emergency Registration.
  • the AMF indicates the established PDU Sessions to the UE in the PDU Session status.
  • the UE removes locally any internal resources related to PDU Sessions that are not marked as established in the received PDU Session status. If the AMF invokes the Nsmf_PDUSession_UpdateSMContext procedure for UP activation of PDU Session(s) in step 18 and receives rejection from the SMF, then the AMF indicates to the UE the PDU Session ID and the cause why the User Plane resources were not activated.
  • the UE When the UE is connected to the two AMFs belonging to different PLMN via 3GPP access and non-3GPP access then the UE removes locally any internal resources related to the PDU Session of the current PLMN that are not marked as established in received PDU Session status. If the PDU Session status information was in the Registration Request, the AMF shall indicate the PDU Session status to the UE.
  • the Mapping Of Allowed NSSAI is the mapping of each S-NSSAI of the Allowed NSSAI to the HPLMN S-NSSAIs.
  • the Mapping Of Configured NSSAI is the mapping of each S-NSSAI of the Configured NSSAI for the Serving PLMN or other PLMNs to the HPLMN S-NSSAIs.
  • the AMF shall include in the Registration Accept message the LADN Information for the list of LADNs, described in 3GPP TS 23.501 clause 5.6.5, that are available within the Registration area determined by the AMF for the UE. If the UE included MICO mode in the request, then AMF responds whether MICO mode should be used.
  • the AMF sets the IMS Voice over PS session supported Indication as described in clause 5.16.3.2 of 3GPP TS 23.501.
  • the AMF may need to perform the UE Capability Match Request procedure in clause 4.2.8a of 3GPP TS 23.502 V15.3.0 to check the compatibility of the UE and NG-RAN radio capabilities related to IMS Voice over PS. If the AMF hasn't received Voice Support Match Indicator from the NG-RAN on time then, based on implementation, AMF may set IMS Voice over PS session supported Indication and update it at a later stage.
  • the AMF sets the IMS Voice over PS session supported Indication as described in clause 5.16.3.2a of 3GPP TS 23.501.
  • the Emergency Service Support indicator informs the UE that emergency services are supported, i.e. the UE is allowed to request PDU Session for emergency services. If the AMF received "MPS priority" from the UDM as part of Access and Mobility Subscription data, based on operator policy, "MPS priority" is included in the Registration Accept message to the UE to inform the UE whether configuration of Access Identity 1 is valid within the selected PLMN, as specified in 3GPP TS 24.501.
  • the Accepted DRX parameters are defined in clause 5.4.5 of 3GPP TS 23.501.
  • the AMF sets the Interworking without N26 parameter as described in clause 5.17.2.3.1 of 3GPP TS 23.501.
  • RRC Inactive Assistance Information might be provided to NG-RAN (see 3GPP TS 23.501 clause 5.3.3.2.5) in this step.
  • the UDM intends to indicate the UE that subscription has changed, the Network Slicing Subscription Change Indication is included. If the AMF includes Network Slicing Subscription Change Indication, then the UE shall locally erase all the network slicing configuration for all PLMNs and, if applicable, update the configuration for the current PLMN based on any received information.
  • UE to new AMF Registration Complete ().
  • the UE sends a Registration Complete message to the AMF when it has successfully updated itself after receiving any of the [Configured NSSAI for the Serving PLMN], [Mapping Of Configured NSSAI] and a Network Slicing Subscription Change Indication in step 21.
  • the UE sends a Registration Complete message to the AMF to acknowledge if a new 5G-GUTI was assigned.
  • the AMF releases the signaling connection with UE, according to clause 4.2.6 of 3GPP TS 23.502 V15.3.0.
  • the AMF should not release the signaling connection after the completion of the Registration procedure. If the AMF is aware that some signaling is pending in the AMF or between the UE and the 5GC, the AMF should not release the signaling connection immediately after the completion of the Registration procedure.
  • the AMF provides the UE acknowledgement to UDM using Nudm_SDM_lnfo.
  • Nudm_SDM_lnfo For more details regarding the handling of Steering of Roaming information refer to 3GPP TS 23.122.
  • the AMF also uses the Nudm_SDM_lnfo service operation to provide an acknowledgment to UDM that the UE received the Network Slicing Subscription Change Indication (see step 21 and step 22) and acted upon it.
  • the mobility related event notifications towards the NF consumers are triggered at the end of this procedure for cases as described in clause 4.15.4.
  • RRC Inactive Assistance Information might be provided to NG-RAN (see 3GPP TS 23.501 clause 5.3.3.2.5) in this step.
  • FIG. 2 is a call-flow diagram illustrating a registration procedure with AMF re-allocation according to one embodiment of the present disclosure. If the UDM intends to indicate the UE that subscription has changed, the Network Slicing Subscription Change Indication is included. If the AMF includes Network Slicing Subscription Change Indication, then the UE shall locally erase all the network slicing configuration for all PLMNs and, if applicable, update the configuration for the current PLMN based on any received information.
  • the AMF may need to reroute the Registration request to another AMF, e.g. when the initial AMF is not the appropriate AMF to serve the UE.
  • the Registration with AMF reallocation procedure described in figure 4.2.2.2.3-1 of 3GPP TS 23.502 V15.3.0, is used to reroute the NAS message of the UE to the target AMF during a Registration procedure.
  • Steps 1 and 2 of Figure 1 have occurred, and the (R)AN sends the Registration request message within an Initial UE message to the initial AMF.
  • the AMF selects a UDM as described in 3GPP TS 23.501 , clause 6.3.8.
  • Nudm_SDM_Get (SUPI, Slice Selection Subscription data).
  • the initial AMF request UE's Slice Selection Subscription data from UDM by invoking the Nudm_SDM_Get (see clause 5.2.3.3.1 of 3GPP TS 23.502 V15.3.0) service operation.
  • UDM may get this information from UDR by Nudr_DM_Query(SUPI, Subscribed S-NSSAIs).
  • UDM to initial AMF Response to Nudm_SDM_Get.
  • the AMF gets the Slice Selection Subscription data including Subscribed S-NSSAIs.
  • the UDM may provide indication that the subscription data for network slicing is updated for the UE.
  • UDM responds with slice selection data to initial AMF.
  • the initial AMF cannot serve all the S-NSSAI(s) from the Requested NSSAI permitted by the subscription information, the initial AMF invokes the Nnssf_NSSelection_Get service operation from the NSSF by including Requested NSSAI, optionally Mapping Of Requested NSSAI, Subscribed S-NSSAIs with the default S-NSSAI indication, Allowed NSSAI for the other access type (if any), Mapping of Allowed NSSAI, PLMN ID of the SUPI and the TAI of the UE.
  • NSSF to Initial AMF Response to Nnssf_NSSelection_Get (AMF Set or list of AMF addresses, Allowed NSSAI for the first access type, [Mapping Of Allowed NSSAI], [Allowed NSSAI for the second access type], [Mapping of Allowed NSSAI], [NSI ID(s)], [NRF(s)], [List of rejected (S-NSSAI(s), cause value(s))], [Configured NSSAI for the Serving PLMN and/or other PLMNs], [Mapping Of Configured NSSAI]).
  • the NSSF performs the steps specified in point (B) in clause 5.15.2.1 of 3GPP TS 23.501.
  • the NSSF returns to initial AMF the Allowed NSSAI for the first access type, optionally the Mapping Of Allowed NSSAI, the Allowed NSSAI for the second access type (if any), optionally the Mapping of Allowed NSSAI and the target AMF Set or, based on configuration, the list of candidate AMF(s).
  • the NSSF may return NSI ID(s) associated to the Network Slice instance(s) corresponding to certain S-NSSAI(s).
  • the NSSF may return the NRF(s) to be used to select NFs/services within the selected Network Slice instance(s).
  • the NSSF may return Configured NSSAI for the Serving PLMN, and possibly the associated mapping of the Configured NSSAI.
  • the NRF(s) returned by the NSSF if any, belong to any level of NRF (see clause 6.2.6 of 3GPP TS 23.501) according to the deployment decision of the operator.
  • the initial AMF decides to reroute the NAS message to another AMF.
  • the initial AMF sends a reject indication to the old AMF telling that the UE Registration procedure did not fully complete at the initial AMF.
  • the old AMF continues as if the Namf_Communication_UEContextTransfer had never been received.
  • Nnrf_NFDiscovery_Request (NF type, AMF Set). If the initial AMF does not locally store the target AMF address, and if the initial AMF intends to use direct reroute to target AMF or the reroute via (NG-R)AN message needs to include AMF address, then the initial AMF invokes the
  • Nnrf_NFDiscovery_Request service operation from the NRF to find a proper target AMF which has required NF capabilities to serve the UE.
  • the NF type is set to AMF.
  • the AMF Set is included in the Nnrf_NFDiscovery_Request.
  • NRF to AMF Response to Nnrf_NFDiscovery_Request (list of (AMF pointer, AMF address, plus additional selection rules and NF capabilities)). The NRF replies with the list of potential target AMF(s).
  • the NRF may also provide the details of the services offered by the candidate AMF(s) along with the notification endpoint for each type of notification service that the selected AMF had registered with the NRF, if available. As an alternative, it provides a list of potential target AMFs and their capabilities, and optionally, additional selection rules.
  • a target AMF is selected by the initial AMF.
  • the initial AMF shall forward the NAS message to the target AMF via (R)AN executing step 7(B); the Allowed NSSAI and the AMF Set are included to enable the (R)AN to select the target AMF.
  • the initial AMF invokes the Namf_Communication_N1 MessageNotify to the target AMF, carrying the rerouted NAS message.
  • the Namf_Communication_N1 MessageNotify service operation includes the information enabling (R)AN to identify the N2 terminating point and the NAS message carried at step 1 , and the UE's SUPI and MM Context if available. If the initial AMF has obtained the information from the NSSF as described at step 4b, that information except the AMF Set or list of AMF addresses is included. The target AMF then updates the (R)AN with a new updated N2 termination point for the UE in the first message from target AMF to RAN in step 8.
  • the initial AMF decides to forward the NAS message to the target AMF via (R)AN
  • the initial AMF sends a Reroute NAS message to the (R)AN (7a).
  • the Reroute NAS message includes the information about the target AMF and the Registration Request message carried at step 1. If the initial AMF has obtained the information as described at step 4b, that information is included.
  • the (R)AN sends the Initial UE message to the target AMF (7b) indicating reroute due to slicing including the information from step 4b that the NSSF provided.
  • the target AMF After receiving the Registration Request message transmitted at step 7(A)a or step 7(B)b, if no UE context is received from the initial AMF, the target AMF, based on rerouting due to slicing, continues with the Registration procedure from step 4 until 22 of Figure 1 (with the target AMF corresponding to the new AMF). If the UE context is received from the initial AMF, the target AMF continues with the Registration procedure from step 8 or 9b (depending on whether it decides to reauthenticate the UE) until step 22 of Figure 1 , skipping step 10. If the initial AMF decides to forward the NAS message to the target AMF (step 7(A), the first message from the target AMF to RAN (either Initial Context Setup Request, or Downlink NAS Transport) contain the AMF name of the initial AMF.
  • the initial AMF decides to forward the NAS message to the target AMF (step 7(A)
  • the first message from the target AMF to RAN either Initial Context Setup Request, or Down
  • Nnssf_NSSelection service The following describes one or more services that may be used to implement the functionality described above.
  • the following describes a Nnssf_NSSelection service.
  • This service operation enables Network Slice selection in both the Serving PLMN and HPLMN. It also enables the NSSF to provide to the AMF the Allowed NSSAI and the Configured NSSAI for the Serving PLMN.
  • Requested NSSAI Subscribed S-NSSAI(s) with the indication if marked as default S-NSSAI, PLMN ID of the SUPI, TAI, NF type of the NF service consumer, Requester ID.
  • S-NSSAIs for the HPLMN associated with established PDN connection PLMN ID of the SUPI, NF type of the NF service consumer, Requester ID.
  • S-NSSAI non-roaming/LBO roaming/HR roaming indication
  • PLMN ID of the SUPI PLMN ID of the SUPI
  • TAI NF type of the NF service consumer
  • Requester ID PLMN ID of the SUPI
  • HPLMN S-NSSAI that maps to the S-NSSAI from the Allowed NSSAI of the Serving PLMN.
  • S-NSSAIs for the HPLMN associated with established PDN connection Mapping of S-NSSAIs associated with established PDN connection in the Serving PLMN.
  • Network Slice instance(s) and NRF to be used to determine the list of candidate AMF(s) from the AMF
  • a wireless network such as the example wireless network illustrated in Figure 3.
  • the wireless network of Figure 3 only depicts a network QQ106, network nodes QQ160 and QQ160B, and Wireless Devices (WDs) QQ110, QQ110B, and QQ110C.
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • the network node QQ160 and the WD QQ110 are depicted with additional detail.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards; Wireless Local Area Network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN Wireless Local Area Network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave
  • ZigBee ZigBee
  • the network QQ106 may comprise one or more backhaul networks, core networks, Internet Protocol (IP) networks, Public Switched Telephone Networks (PSTNs), packet data networks, optical networks, Wide Area Networks (WANs), Local Area Networks (LANs), WLANs, wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • IP Internet Protocol
  • PSTNs Public Switched Telephone Networks
  • WANs Wide Area Networks
  • LANs Local Area Networks
  • WLANs wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • the network node QQ160 and the WD QQ110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • network node refers to equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, Access Points (APs) (e.g., radio APs), Base Stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and New Radio (NR) Node Bs (gNBs)).
  • APs Access Points
  • BSs Base Stations
  • gNBs New Radio
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs Remote Radio Heads
  • Parts of a distributed radio base station may also be referred to as nodes in a Distributed Antenna System (DAS).
  • DAS Distributed Antenna System
  • network nodes include Multi- Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell/Multicast Coordination Entities (MCEs), core network nodes (e.g., Mobile Switching Centers (MSCs), Mobility Management Entities (MMEs)), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Center (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR Multi- Standard Radio
  • RNCs Radio Network Controllers
  • BSCs Base Transceiver Stations
  • MCEs Multi-Cell/Multicast Coordination Entities
  • core network nodes e.g., Mobile Switching Centers (MSCs), Mobility Management Entities (
  • a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • the network node QQ160 includes processing circuitry QQ170, a device readable medium QQ180, an interface QQ190, auxiliary equipment QQ184, a power source QQ186, power circuitry QQ187, and an antenna QQ162.
  • the network node QQ160 illustrated in the example wireless network of Figure 3 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions, and methods disclosed herein.
  • a network node may comprise multiple different physical components that make up a single illustrated component (e.g., the device readable medium QQ180 may comprise multiple separate hard drives as well as multiple Random Access Memory (RAM) modules).
  • RAM Random Access Memory
  • the network node QQ160 may be composed of multiple physically separate components (e.g., a Node B component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node QQ160 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple Node Bs.
  • each unique Node B and RNC pair may in some instances be considered a single separate network node.
  • the network node QQ160 may be configured to support multiple Radio Access Technologies (RATs).
  • RATs Radio Access Technologies
  • the network node QQ160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into the network node QQ160, such as, for example, GSM, Wideband Code Division Multiple Access (WCDMA), LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or a different chip or set of chips and other components within the network node QQ160.
  • WCDMA Wideband Code Division Multiple Access
  • LTE Long Term Evolution
  • NR Fifth Generation
  • WiFi Wireless Fidelity
  • Bluetooth wireless technologies may be integrated into the same or a different chip or set of chips and other components within the network node QQ160.
  • the processing circuitry QQ170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by the processing circuitry QQ170 may include processing information obtained by the processing circuitry QQ170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by the processing circuitry QQ170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • the processing circuitry QQ170 may comprise a combination of one or more of a microprocessor, a controller, a microcontroller, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ160 components, such as the device readable medium QQ180, network node QQ160 functionality.
  • the processing circuitry QQ170 may execute instructions stored in the device readable medium QQ180 or in memory within the processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • the processing circuitry QQ170 may include a System on a Chip (SOC).
  • SOC System on a Chip
  • the processing circuitry QQ170 may include one or more of Radio Frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174.
  • RF Radio Frequency
  • the RF transceiver circuitry QQ172 and the baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of the RF transceiver circuitry QQ172 and the baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units.
  • some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by the processing circuitry QQ170 executing instructions stored on the device readable medium QQ180 or memory within the processing circuitry QQ170.
  • some or all of the functionality may be provided by the processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • the processing circuitry QQ170 can be configured to perform the described functionality.
  • the benefits provided by such functionality are not limited to the processing circuitry QQ170 alone or to other components of the network node QQ160, but are enjoyed by the network node QQ160 as a whole, and/or by end users and the wireless network generally.
  • the device readable medium QQ180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, Read Only Memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or nonvolatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry QQ170.
  • volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, Read Only Memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)
  • the device readable medium QQ180 may store any suitable instructions; data or information, including a computer program; software; an application including one or more of logic, rules, code, tables, etc.; and/or other instructions capable of being executed by the processing circuitry QQ170 and utilized by the network node QQ160.
  • the device readable medium QQ180 may be used to store any calculations made by the processing circuitry QQ170 and/or any data received via the interface QQ190.
  • the processing circuitry QQ170 and the device readable medium QQ180 may be considered to be integrated.
  • the interface QQ190 is used in the wired or wireless communication of signaling and/or data between the network node QQ160, a network QQ106, and/or WDs QQ110. As illustrated, the interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from the network QQ106 over a wired connection.
  • the interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, the antenna QQ162.
  • the radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196.
  • the radio front end circuitry QQ192 may be connected to the antenna QQ162 and the processing circuitry QQ170.
  • the radio front end circuitry QQ192 may be configured to condition signals communicated between the antenna QQ162 and the processing circuitry QQ170.
  • the radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • the radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters QQ198 and/or the amplifiers QQ196.
  • the radio signal may then be transmitted via the antenna QQ162.
  • the antenna QQ162 may collect radio signals which are then converted into digital data by the radio front end circuitry QQ192.
  • the digital data may be passed to the processing circuitry QQ170.
  • the interface QQ190 may comprise different components and/or different combinations of components.
  • the network node QQ160 may not include separate radio front end circuitry QQ192; instead, the processing circuitry QQ170 may comprise radio front end circuitry and may be connected to the antenna QQ162 without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ172 may be considered a part of the interface QQ190.
  • the interface QQ190 may include the one or more ports or terminals QQ194, the radio front end circuitry QQ192, and the RF transceiver circuitry QQ172 as part of a radio unit (not shown), and the interface QQ190 may communicate with the baseband processing circuitry QQ174, which is part of a digital unit (not shown).
  • the antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna QQ162 may be coupled to the radio front end circuitry QQ192 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna QQ162 may comprise one or more omni-directional, sector, or panel antennas operable to transmit/receive radio signals between, for example, 2 gigahertz (GHz) and 66 GHz.
  • GHz gigahertz
  • An omni-directional antenna may be used to transmit/receive radio signals in any direction
  • a sector antenna may be used to transmit/receive radio signals from devices within a particular area
  • a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line.
  • MIMO Multiple Input Multiple Output
  • the antenna QQ162 may be separate from the network node QQ160 and may be connectable to the network node QQ160 through an interface or port.
  • the antenna QQ162, the interface QQ190, and/or the processing circuitry QQ170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data, and/or signals may be received from a WD, another network node, and/or any other network equipment. Similarly, the antenna QQ162, the interface QQ190, and/or the processing circuitry QQ170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data, and/or signals may be transmitted to a WD, another network node, and/or any other network equipment.
  • the power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of the network node QQ160 with power for performing the functionality described herein.
  • the power circuitry QQ187 may receive power from the power source QQ186.
  • the power source QQ186 and/or the power circuitry QQ187 may be configured to provide power to the various components of the network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source QQ186 may either be included in, or be external to, the power circuitry QQ187 and/or the network node QQ160.
  • the network node QQ160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to the power circuitry QQ187.
  • the power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, the power circuitry QQ187.
  • the battery may provide backup power should the external power source fail.
  • Other types of power sources such as photovoltaic devices, may also be used.
  • Alternative embodiments of the network node QQ160 may include additional components beyond those shown in Figure 3 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node QQ160 may include user interface equipment to allow input of information into the network node QQ160 and to allow output of information from the network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ160.
  • WD refers to a device capable, configured, arranged, and/or operable to communicate wirelessly with network nodes and/or other WDs.
  • the term WD may be used interchangeably herein with User Equipment (UE).
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • UE User Equipment
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a Voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a Personal Digital Assistant (PDA), a wireless camera, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), a smart device, a wireless Customer Premise Equipment (CPE), a vehicle mounted wireless terminal device, etc.
  • VoIP Voice over IP
  • PDA Personal Digital Assistant
  • PDA Personal Digital Assistant
  • a wireless camera a gaming console or device
  • music storage device a playback appliance
  • a wearable terminal device a wireless endpoint
  • a mobile station a tablet, a laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), a smart device, a wireless Customer
  • a WD may support Device-to- Device (D2D) communication, for example by implementing a 3G Partnership Project (3GPP) standard for sidelink communication, Vehicle-to-Vehicle (V2V), Vehicle-to-lnfrastructure (V2I), Vehicle-to-Everything (V2X), and may in this case be referred to as a D2D communication device.
  • D2D Device-to- Device
  • 3GPP 3G Partnership Project
  • V2V Vehicle-to-Vehicle
  • V2I Vehicle-to-lnfrastructure
  • V2X Vehicle-to-Everything
  • a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD may in this case be a Machine-to-Machine (M2M) device, which may in a 3GPP context be referred to as a Machine-Type Communication (MTC) device.
  • M2M Machine-to-Machine
  • MTC Machine-Type Communication
  • the WD may be a UE implementing the 3GPP Narrowband loT (NB-loT) standard.
  • NB-loT 3GPP Narrowband loT
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • a WD QQ110 includes an antenna QQ111 , an interface QQ114, processing circuitry QQ120, a device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, a power source QQ136, and power circuitry QQ137.
  • the WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by the WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within the WD QQ110.
  • the antenna QQ111 may include one or more antennas or antenna arrays configured to send and/or receive wireless signals and is connected to the interface QQ114. In certain alternative embodiments, the antenna QQ111 may be separate from the WD QQ110 and be connectable to the WD QQ110 through an interface or port.
  • the antenna QQ111 , the interface QQ114, and/or the processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data, and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or the antenna QQ111 may be considered an interface.
  • the interface QQ114 comprises radio front end circuitry QQ112 and the antenna QQ111.
  • the radio front end circuitry QQ112 comprises one or more filters QQ118 and amplifiers QQ116.
  • the radio front end circuitry QQ112 is connected to the antenna QQ111 and the processing circuitry QQ120 and is configured to condition signals communicated between the antenna QQ111 and the processing circuitry QQ120.
  • the radio front end circuitry QQ112 may be coupled to or be a part of the antenna QQ111.
  • the WD QQ110 may not include separate radio front end circuitry QQ112; rather, the processing circuitry QQ120 may comprise radio front end circuitry and may be connected to the antenna QQ111.
  • RF transceiver circuitry QQ122 may be considered a part of the interface QQ114.
  • the radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • the radio front end circuitry QQ112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters QQ118 and/or the amplifiers QQ116.
  • the radio signal may then be transmitted via the antenna QQ111.
  • the antenna QQ111 may collect radio signals which are then converted into digital data by the radio front end circuitry QQ112.
  • the digital data may be passed to the processing circuitry QQ120.
  • the interface QQ114 may comprise different components and/or different combinations of components.
  • the processing circuitry QQ120 may comprise a combination of one or more of a microprocessor, a controller, a microcontroller, a CPU, a DSP, an ASIC, a FPGA, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD QQ110 components, such as the device readable medium QQ130, WD QQ110 functionality.
  • Such functionality may include providing any of the various wireless features or benefits discussed herein.
  • the processing circuitry QQ120 may execute instructions stored in the device readable medium QQ130 or in memory within the processing circuitry QQ120 to provide the functionality disclosed herein.
  • the processing circuitry QQ120 includes one or more of the RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126.
  • the processing circuitry QQ120 may comprise different components and/or different combinations of components.
  • the processing circuitry QQ120 of the WD QQ110 may comprise a SOC.
  • the RF transceiver circuitry QQ122, the baseband processing circuitry QQ124, and the application processing circuitry QQ126 may be on separate chips or sets of chips.
  • part or all of the baseband processing circuitry QQ124 and the application processing circuitry QQ126 may be combined into one chip or set of chips, and the RF transceiver circuitry QQ122 may be on a separate chip or set of chips.
  • part or all of the RF transceiver circuitry QQ122 and the baseband processing circuitry QQ124 may be on the same chip or set of chips, and the application processing circuitry QQ126 may be on a separate chip or set of chips.
  • part or all of the RF transceiver circuitry QQ122, the baseband processing circuitry QQ124, and the application processing circuitry QQ126 may be combined in the same chip or set of chips.
  • the RF transceiver circuitry QQ122 may be a part of the interface QQ114.
  • the RF transceiver circuitry QQ122 may condition RF signals for the processing circuitry QQ120.
  • some or all of the functionality described herein as being performed by a WD may be provided by the processing circuitry QQ120 executing instructions stored on the device readable medium QQ130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, the processing circuitry QQ120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry QQ120 alone or to other components of the WD QQ110, but are enjoyed by the WD QQ110 as a whole, and/or by end users and the wireless network generally.
  • the processing circuitry QQ120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by the processing circuitry QQ120, may include processing information obtained by the processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by the WD QQ110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by the processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by the WD QQ110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • the device readable medium QQ130 may be operable to store a computer program; software; an application including one or more of logic, rules, code, tables, etc.; and/or other instructions capable of being executed by the processing circuitry QQ120.
  • the device readable medium QQ130 may include computer memory (e.g., RAM or ROM), mass storage media (e.g., a hard disk), removable storage media (e.g., a CD or a DVD), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry QQ120.
  • the processing circuitry QQ120 and the device readable medium QQ130 may be considered to be integrated.
  • the user interface equipment QQ132 may provide components that allow for a human user to interact with the WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc.
  • the user interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to the WD QQ110.
  • the type of interaction may vary depending on the type of user interface equipment QQ132 installed in the WD QQ110.
  • the interaction may be via a touch screen; if the WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • the user interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. The user interface equipment QQ132 is configured to allow input of information into the WD QQ110, and is connected to the processing circuitry QQ120 to allow the processing circuitry QQ120 to process the input information.
  • the user interface equipment QQ132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a Universal Serial Bus (USB) port, or other input circuitry.
  • the user interface equipment QQ132 is also configured to allow output of information from the WD QQ110 and to allow the processing circuitry QQ120 to output information from the WD QQ110.
  • the user interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry.
  • the WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • the auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications, etc. The inclusion and type of components of the auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario.
  • the power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices, or power cells may also be used.
  • the WD QQ110 may further comprise the power circuitry QQ137 for delivering power from the power source QQ136 to the various parts of the WD QQ110 which need power from the power source QQ136 to carry out any functionality described or indicated herein.
  • the power circuitry QQ137 may in certain embodiments comprise power management circuitry.
  • the power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source, in which case the WD QQ110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • the power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to the power source QQ136. This may be, for example, for the charging of the power source QQ136.
  • the power circuitry QQ137 may perform any formatting, converting, or other modification to the power from the power source QQ136 to make the power suitable for the respective components of the WD QQ110 to which power is supplied.
  • Figure 4 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point/interface.
  • Figure 4 can be viewed as one particular implementation of the system QQ100 of Figure 3.
  • the 5G network architecture shown in Figure 4 comprises a plurality of User Equipment (UEs) connected to either a Radio Access Network (RAN) or an Access Network (AN) as well as an Access and Mobility Management Function (AMF).
  • the R(AN) comprises base stations, e.g. such as evolved Node Bs (eNBs) or 5G base stations (gNBs) or similar.
  • the 5G core NFs shown in Figure 4 include a Network Slice Selection Function (NSSF), an Authentication Server Function (AUSF), a Unified Data Management (UDM), an AMF, a Session Management Function (SMF), a Policy Control Function (PCF), and an Application Function (AF).
  • NSSF Network Slice Selection Function
  • AUSF Authentication Server Function
  • UDM Unified Data Management
  • AMF Application Function
  • SMF Session Management Function
  • PCF Policy Control Function
  • AF Application Function
  • the N1 reference point is defined to carry signaling between the UE and AMF.
  • the reference points for connecting between the AN and AMF and between the AN and UPF are defined as N2 and N3, respectively.
  • N4 is used by the SMF and UPF so that the UPF can be set using the control signal generated by the SMF, and the UPF can report its state to the SMF.
  • N9 is the reference point for the connection between different UPFs
  • N14 is the reference point connecting between different AMFs, respectively.
  • N15 and N7 are defined since the PCF applies policy to the AMF and SMP, respectively.
  • N12 is required for the AMF to perform authentication of the UE.
  • N8 and N10 are defined because the subscription data of the UE is required for the AMF and SMF.
  • the 5G core network aims at separating user plane and control plane.
  • the user plane carries user traffic while the control plane carries signaling in the network.
  • the UPF is in the user plane and all other NFs, i.e., the AMF, SMF, PCF, AF, AUSF, and UDM, are in the control plane. Separating the user and control planes guarantees each plane resource to be scaled independently. It also allows UPFs to be deployed separately from control plane functions in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency.
  • RTT Round Trip Time
  • the core 5G network architecture is composed of modularized functions.
  • the AMF and SMF are independent functions in the control plane. Separated AMF and SMF allow independent evolution and scaling.
  • Other control plane functions like the PCF and AUSF can be separated as shown in Figure 4.
  • Modularized function design enables the 5G core network to support various services flexibly.
  • Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF.
  • a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity.
  • the user plane supports interactions such as forwarding operations between different UPFs.
  • Figure 5 illustrates a 5G network architecture using service-based interfaces between the NFs in the control plane, instead of the point-to-point reference points/interfaces used in the 5G network architecture of Figure 4.
  • the NFs described above with reference to Figure 4 correspond to the NFs shown in Figure 5.
  • the service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface.
  • the service based interfaces are indicated by the letter“N” followed by the name of the NF, e.g. Namf for the service based interface of the AMF and Nsmf for the service based interface of the SMF etc.
  • the Network Exposure Function (NEF) and the Network Repository Function (NRF) in Figure 5 are not shown in Figure 4 discussed above. However, it should be clarified that all NFs depicted in Figure 4 can interact with the NEF and the NRF of Figure 5 as necessary, though not explicitly indicated in Figure 4. [0153] Some properties of the NFs shown in Figures 4 and 5 may be described in the following manner.
  • the AMF provides UE-based authentication, authorization, mobility management, etc. A UE even using multiple access technologies is basically connected to a single AMF because the AMF is independent of the access technologies.
  • the SMF is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF for data transfer.
  • IP Internet Protocol
  • the AF provides information on the packet flow to the PCF responsible for policy control in order to support Quality of Service (QoS). Based on the information, the PCF determines policies about mobility and session management to make the AMF and SMF operate properly.
  • the AUSF supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM stores subscription data of the UE.
  • the Data Network (DN) not part of the 5G core network, provides Internet access or operator services and similar.
  • An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.
  • Figure 6 illustrates one embodiment of a UE in accordance with various aspects described herein.
  • a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • a UE QQ200 may be any UE identified by 3GPP, including a NB-loT UE, a MTC UE, and/or an enhanced MTC (eMTC) UE.
  • the UE QQ200 as illustrated in Figure 6, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by 3GPP, such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • the term WD and UE may be used interchangeable. Accordingly, although Figure 6 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
  • the UE QQ200 includes processing circuitry QQ201 that is operatively coupled to an input/output interface QQ205, an RF interface QQ209, a network connection interface QQ211 , memory QQ215 including RAM QQ217, ROM QQ219, and a storage medium QQ221 or the like, a communication subsystem QQ231 , a power source QQ213, and/or any other component, or any combination thereof.
  • the storage medium QQ221 includes an operating system QQ223, an application program QQ225, and data QQ227. In other embodiments, the storage medium QQ221 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 6, or only a subset of the components.
  • the processing circuitry QQ201 may be configured to process computer instructions and data.
  • the processing circuitry QQ201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware- implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored programs, general purpose processors, such as a microprocessor or DSP, together with appropriate software; or any combination of the above.
  • the processing circuitry QQ201 may include two CPUs. Data may be information in a form suitable for use by a computer.
  • the input/output interface QQ205 may be configured to provide a
  • the UE QQ200 may be configured to use an output device via the input/output interface QQ205.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from the UE QQ200.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • the UE QQ200 may be configured to use an input device via the input/output interface QQ205 to allow a user to capture information into the UE QQ200.
  • the input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • the RF interface QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • the network connection interface QQ211 may be configured to provide a communication interface to a network QQ243A.
  • the network QQ243A may encompass wired and/or wireless networks such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • the network QQ243A may comprise a WiFi network.
  • the network connection interface QQ211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, Transmission Control Protocol (TCP) / IP, Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), or the like.
  • the network connection interface QQ211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like).
  • the transmitter and receiver functions may share circuit components, software, or firmware, or alternatively may be implemented separately.
  • the RAM QQ217 may be configured to interface via a bus QQ202 to the processing circuitry QQ201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • the ROM QQ219 may be configured to provide computer instructions or data to the processing circuitry QQ201.
  • the ROM QQ219 may be configured to store invariant low-level system code or data for basic system functions such as basic Input and Output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • the Storage medium QQ221 may be configured to include memory such as RAM, ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • the storage medium QQ221 may be configured to include the operating system QQ223, the application program QQ225 such as a web browser application, a widget or gadget engine, or another application, and the data file QQ227.
  • the storage medium QQ221 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.
  • the storage medium QQ221 may be configured to include a number of physical drive units, such as a Redundant Array of Independent Disks (RAID), a floppy disk drive, flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a High-Density Digital Versatile Disc (HD-DVD) optical disc drive, an internal hard disk drive, a Blu-Ray optical disc drive, a Holographic Digital Data Storage (HDDS) optical disc drive, an external mini-Dual In-Line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a Subscriber Identity Module (SIM) or a Removable User Identity (RUIM) module, other memory, or any combination thereof.
  • RAID Redundant Array of Independent Disks
  • HD-DVD High-Density Digital Versatile Disc
  • HDDS Holographic Digital Data Storage
  • DIMM Digital Data Storage
  • DIMM
  • the storage medium QQ221 may allow the UE QQ200 to access computer- executable instructions, application programs, or the like, stored on transitory or non-transitory memory media, to off-load data or to upload data.
  • An article of manufacture, such as one utilizing a communication system, may be tangibly embodied in the storage medium QQ221 , which may comprise a device readable medium.
  • the processing circuitry QQ201 may be configured to communicate with a network QQ243B using the communication subsystem QQ231.
  • the network QQ243A and the network QQ243B may be the same network or networks or different network or networks.
  • the communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with the network QQ243B.
  • the communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a Radio Access Network (RAN) according to one or more communication protocols, such as IEEE 802.
  • RAN Radio Access Network
  • Each transceiver may include a transmitter QQ233 and/or a receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, the transmitter QQ233 and the receiver QQ235 of each transceiver may share circuit components, software, or firmware, or alternatively may be implemented separately.
  • the communication functions of the communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof.
  • the communication subsystem QQ231 may include cellular communication, WiFi communication, Bluetooth communication, and GPS communication.
  • the network QQ243B may encompass wired and/or wireless networks such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, another like network, or any combination thereof.
  • the network QQ243B may be a cellular network, a WiFi network, and/or a near-field network.
  • a power source QQ213 may be configured to provide Alternating Current (AC) or Direct Current (DC) power to components of the UE QQ200.
  • the features, benefits, and/or functions described herein may be implemented in one of the components of the UE QQ200 or partitioned across multiple components of the UE QQ200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software, or firmware.
  • the communication subsystem QQ231 may be configured to include any of the components described herein.
  • the processing circuitry QQ201 may be configured to communicate with any of such components over the bus QQ202.
  • any of such components may be represented by program instructions stored in memory that, when executed by the processing circuitry QQ201 , perform the corresponding functions described herein.
  • any of such components may be partitioned between the processing circuitry QQ201 and the communication subsystem QQ231.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • FIG. 7 is a schematic block diagram illustrating a virtualization environment QQ300 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices, and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a WD, or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executing on one or more physical processing nodes in one or more networks).
  • a node e.g., a virtualized base station or a virtualized radio access node
  • a device e.g., a UE, a WD, or any other type of communication device
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300 hosted by one or more of hardware nodes QQ330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications QQ320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • the applications QQ320 are run in the virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390.
  • the memory QQ390 contains instructions QQ395 executable by the processing circuitry QQ360 whereby the application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • the virtualization environment QQ300 comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, which may be Commercial Off-the-Shelf (COTS) processors, dedicated ASICs, or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device QQ330 may comprise memory QQ390-1 which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by the processing circuitry QQ360.
  • Each hardware device QQ330 may comprise one or more Network Interface Controllers (NICs) QQ370, also known as network interface cards, which include a physical network interface QQ380.
  • NICs Network Interface Controllers
  • Each hardware device QQ330 may also include non-transitory, persistent, machine-readable storage media QQ390-2 having stored therein software QQ395 and/or instructions executable by the processing circuitry QQ360.
  • the software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340, as well as software allowing it to execute functions, features, and/or benefits described in relation with some embodiments described herein.
  • the virtual machines QQ340 comprise virtual processing, virtual memory, virtual networking or interface, and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor.
  • Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of the virtual machines QQ340, and the implementations may be made in different ways.
  • the processing circuitry QQ360 executes the software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a Virtual Machine Monitor (VMM).
  • VMM Virtual Machine Monitor
  • the virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to the virtual machine QQ340.
  • the hardware QQ330 may be a standalone network node with generic or specific components.
  • the hardware QQ330 may comprise an antenna QQ3225 and may implement some functions via virtualization.
  • the hardware QQ330 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via a Management and Orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of the applications QQ320.
  • MANO Management and Orchestration
  • NFV Network Function Virtualization
  • NFV Network Function Virtualization
  • the virtual machine QQ340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the virtual machines QQ340, and that part of the hardware QQ330 that executes that virtual machine QQ340 be it hardware dedicated to that virtual machine QQ340 and/or hardware shared by that virtual machine QQ340 with others of the virtual machines QQ340, forms a separate Virtual Network Element (VNE).
  • VNE Virtual Network Element
  • Virtual Network Function is responsible for handling specific network functions that run in one or more virtual machines QQ340 on top of the hardware networking infrastructure QQ330 and corresponds to the application QQ320 in Figure 7.
  • one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to the one or more antennas QQ3225.
  • the radio units QQ3200 may communicate directly with the hardware nodes QQ330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signaling can be effected with the use of a control system QQ3230, which may alternatively be used for communication between the hardware nodes QQ330 and the radio unit QQ3200.
  • a method performed by a wireless device comprising:
  • PLMN public land mobile network
  • NSSAI network slice selection assistance information
  • NSSAI network slice selection assistance information
  • the information identifying the one or more network slices includes information identifying a first network slice defined for the serving PLMN and information identifying a second network slice defined for the one or more other PLMNs.
  • a wireless device comprising:
  • a base station comprising:
  • a User Equipment, UE comprising:
  • radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;
  • processing circuitry being configured to perform any of the steps of any of the Group A embodiments;
  • an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry
  • a battery connected to the processing circuitry and configured to supply power to the UE.
  • a communication system including a host computer comprising:
  • UE User Equipment
  • the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • GSM Global System for Mobile

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 un procédé et un dispositif sans fil et un nœud d'accès radioélectrique permettant de mettre en œuvre le procédé. Le procédé mis en œuvre par le dispositif sans fil comprend : la réception en provenance d'un nœud d'accès radioélectrique dans un réseau mobile terrestre public de desserte (PLMN) d'informations identifiant une ou plusieurs tranches de réseau définies pour le PLMN de desserte et un ou plusieurs autres PLMN. Le procédé mis en œuvre par le nœud d'accès radioélectrique comprend : l'envoi par le nœud d'accès radioélectrique dans un réseau mobile terrestre public de desserte (PLMN) d'informations identifiant une ou plusieurs tranches de réseau définies pour le PLMN de desserte et un ou plusieurs autres PLMN.
PCT/EP2019/077268 2018-10-09 2019-10-08 Nssai configurées pour d'autres plmn WO2020074542A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862742980P 2018-10-09 2018-10-09
US62/742980 2018-10-09

Publications (1)

Publication Number Publication Date
WO2020074542A1 true WO2020074542A1 (fr) 2020-04-16

Family

ID=68210797

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2019/077268 WO2020074542A1 (fr) 2018-10-09 2019-10-08 Nssai configurées pour d'autres plmn

Country Status (1)

Country Link
WO (1) WO2020074542A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021215227A1 (fr) * 2020-04-24 2021-10-28 シャープ株式会社 Ue (équipement utilisateur)
CN113676904A (zh) * 2020-04-30 2021-11-19 华为技术有限公司 切片认证方法及装置
CN113905337A (zh) * 2020-06-22 2022-01-07 华为技术有限公司 通信方法、装置及系统
EP3968570A1 (fr) * 2020-09-09 2022-03-16 Hewlett Packard Enterprise Development LP Contrôle d'accès d'équipement à des tranches dans un réseau 5g
WO2022253004A1 (fr) * 2021-05-31 2022-12-08 华为技术有限公司 Procédé de communication et appareil de communication
WO2023205454A1 (fr) * 2022-04-21 2023-10-26 Dish Wireless L.L.C. Système de communication sans fil mis en œuvre à l'aide d'un procédé de découpage en tranches de réseau
US11979807B2 (en) 2021-07-30 2024-05-07 Hewlett Packard Enterprise Development Lp Automatic notifications for expired subscriptions

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170303259A1 (en) * 2016-04-18 2017-10-19 Electronics And Telecommunications Research Institute Communication method and apparatus using network slicing

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170303259A1 (en) * 2016-04-18 2017-10-19 Electronics And Telecommunications Research Institute Communication method and apparatus using network slicing

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.501, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V15.3.0, 17 September 2018 (2018-09-17), pages 1 - 226, XP051487016 *
MOTOROLA MOBILITY ET AL: "Slicing configuration update", vol. SA WG2, no. Gothenburg, Sweden; 20180122 - 20180126, 26 January 2018 (2018-01-26), XP051390383, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fsa/WG2%5FArch/TSGS2%5F125%5FGothenburg/Docs/> [retrieved on 20180126] *
QUALCOMM INCORPORATED ET AL: "TS 23.501: Applicability of UE slicing configuration in roaming scenarios", vol. SA WG2, no. Ljubljana, Slovenia; 20171023 - 20171027, 30 October 2017 (2017-10-30), XP051360647, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_123_Ljubljana/Docs/> [retrieved on 20171030] *
SHARP: "Clarification on configured S-NSSAI not associated with a PLMN_Alt3", vol. CT WG1, no. Vilnius (Lithuania); 20181015 - 20181019, 7 October 2018 (2018-10-07), XP051571532, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fct/WG1%5Fmm%2Dcc%2Dsm%5Fex%2DCN1/TSGC1%5F112bis%5FVilnius/docs/C1%2D186415%2Ezip> [retrieved on 20181007] *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021215227A1 (fr) * 2020-04-24 2021-10-28 シャープ株式会社 Ue (équipement utilisateur)
CN113676904A (zh) * 2020-04-30 2021-11-19 华为技术有限公司 切片认证方法及装置
CN113676904B (zh) * 2020-04-30 2023-02-03 华为技术有限公司 切片认证方法及装置
CN113905337A (zh) * 2020-06-22 2022-01-07 华为技术有限公司 通信方法、装置及系统
EP3968570A1 (fr) * 2020-09-09 2022-03-16 Hewlett Packard Enterprise Development LP Contrôle d'accès d'équipement à des tranches dans un réseau 5g
US11546833B2 (en) 2020-09-09 2023-01-03 Hewlett Packard Enterprise Development Lp Controlling equipment access to slices in a 5G network
WO2022253004A1 (fr) * 2021-05-31 2022-12-08 华为技术有限公司 Procédé de communication et appareil de communication
US11979807B2 (en) 2021-07-30 2024-05-07 Hewlett Packard Enterprise Development Lp Automatic notifications for expired subscriptions
WO2023205454A1 (fr) * 2022-04-21 2023-10-26 Dish Wireless L.L.C. Système de communication sans fil mis en œuvre à l'aide d'un procédé de découpage en tranches de réseau

Similar Documents

Publication Publication Date Title
US11671952B2 (en) Frequency or radio access technology (RAT) selection based on slice availability
US20230156580A1 (en) Session mangement function service area information provision
EP3697062B1 (fr) Autorisation secondaire lors de l&#39;établissement d&#39;une session de pdu pour itinérance routée domestique
AU2019265694B2 (en) UE behavior with rejection of resume request
WO2020074542A1 (fr) Nssai configurées pour d&#39;autres plmn
US20210329444A1 (en) Incrementally Distributing User Equipment Capability Information Using a Model Identifier
EP3837814B1 (fr) Procédé de notification d&#39;avance de changements dans des capacités de qos de réseau
WO2019097498A1 (fr) Procédés et appareil de transfert ou de redirection
US11140598B2 (en) Network initiated inter-RAT handover
US20230232356A1 (en) Storage of network slice authorization status
US11051161B1 (en) Key maerial generation optimization for authentication and key management for applications
WO2021209379A1 (fr) Poussée de fonction de serveurs d&#39;authentification (ausf) de contenus d&#39;authentification et de gestion de clés (akma)
WO2021164659A1 (fr) Procédé et appareil de protection de la confidentialité
WO2019197282A1 (fr) Gestion commandée par amf de la politique de sécurité pour une protection de plan d&#39;utilisateur dans des systèmes 5g
US20230171598A1 (en) Secondary or Splice-Specific Access Control in a Wireless Communication Network
US20230254680A1 (en) Methods providing flexible communication between radio access and core networks and related nodes
US20240114444A1 (en) Network slice isolation via network slice lists
US20240080650A1 (en) Discovery key handling for ue-to-network relay discovery
WO2024012064A1 (fr) Procédé et appareil de rapport d&#39;événement
US11445474B2 (en) Mobile switching node and mobility management node to page terminal device
US20230328677A1 (en) Handling registrations of a user equipment in different communication networks
US20240179507A1 (en) Proximity services discovery user equipment identifier provisioning
WO2024022278A1 (fr) Procédé et appareil de gestion de mobilité
WO2022106067A1 (fr) Abonnement explicite à des changements dans une ressource non existante, mais valide dans un référentiel de données unifié

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: 19786549

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: 19786549

Country of ref document: EP

Kind code of ref document: A1