WO2023216019A1 - Gestion de ressources radio avec une fréquence dédiée tenant compte d'un ou de plusieurs identifiants de zone de suivi valides dans un découpage de réseau d'accès radio - Google Patents

Gestion de ressources radio avec une fréquence dédiée tenant compte d'un ou de plusieurs identifiants de zone de suivi valides dans un découpage de réseau d'accès radio Download PDF

Info

Publication number
WO2023216019A1
WO2023216019A1 PCT/CN2022/091404 CN2022091404W WO2023216019A1 WO 2023216019 A1 WO2023216019 A1 WO 2023216019A1 CN 2022091404 W CN2022091404 W CN 2022091404W WO 2023216019 A1 WO2023216019 A1 WO 2023216019A1
Authority
WO
WIPO (PCT)
Prior art keywords
slice group
frequency priority
priority configuration
slice
dedicated frequency
Prior art date
Application number
PCT/CN2022/091404
Other languages
English (en)
Inventor
Yuqin Chen
Peng Cheng
Haijing Hu
Original Assignee
Apple Inc.
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 Apple Inc. filed Critical Apple Inc.
Priority to PCT/CN2022/091404 priority Critical patent/WO2023216019A1/fr
Publication of WO2023216019A1 publication Critical patent/WO2023216019A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel

Definitions

  • This application relates generally to wireless communication systems, including wireless communications systems using slice-based frequency priority configuration information and related methods.
  • Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless communication device.
  • Wireless communication system standards and protocols can include, for example, 3rd Generation Partnership Project (3GPP) long term evolution (LTE) (e.g., 4G) , 3GPP new radio (NR) (e.g., 5G) , and IEEE 802.11 standard for wireless local area networks (WLAN) (commonly known to industry groups as ) .
  • 3GPP 3rd Generation Partnership Project
  • LTE long term evolution
  • NR 3GPP new radio
  • WLAN wireless local area networks
  • 3GPP radio access networks
  • RANs can include, for example, global system for mobile communications (GSM) , enhanced data rates for GSM evolution (EDGE) RAN (GERAN) , Universal Terrestrial Radio Access Network (UTRAN) , Evolved Universal Terrestrial Radio Access Network (E-UTRAN) , and/or Next-Generation Radio Access Network (NG-RAN) .
  • GSM global system for mobile communications
  • EDGE enhanced data rates for GSM evolution
  • GERAN GERAN
  • UTRAN Universal Terrestrial Radio Access Network
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • NG-RAN Next-Generation Radio Access Network
  • Each RAN may use one or more radio access technologies (RATs) to perform communication between the base station and the UE.
  • RATs radio access technologies
  • the GERAN implements GSM and/or EDGE RAT
  • the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3GPP RAT
  • the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE)
  • NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR)
  • the E-UTRAN may also implement NR RAT.
  • NG-RAN may also implement LTE RAT.
  • a base station used by a RAN may correspond to that RAN.
  • E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) .
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • eNodeB enhanced Node B
  • NG-RAN base station is a next generation Node B (also sometimes referred to as a g Node B or gNB) .
  • a RAN provides its communication services with external entities through its connection to a core network (CN) .
  • CN core network
  • E-UTRAN may utilize an Evolved Packet Core (EPC)
  • EPC Evolved Packet Core
  • NG-RAN may utilize a 5G Core Network (5GC) .
  • EPC Evolved Packet Core
  • 5GC 5G Core Network
  • FIG. 1 illustrates a diagram showing the use of network slicing methods within a UE registration area, according to an embodiment.
  • FIG. 2 illustrates a CellReselectionPriorities information element, according to an embodiment.
  • FIG. 3 illustrates a diagram showing the use of network slicing methods within a UE registration area, according to an embodiment.
  • FIG. 4 illustrates a diagram corresponding to the use of network slicing methods, according to an embodiment.
  • FIG. 5 illustrates a method of a UE, according to an embodiment.
  • FIG. 6 illustrates a method of a UE, according to an embodiment.
  • FIG. 7 illustrates a method of a UE, according to an embodiment.
  • FIG. 8 illustrates an example architecture of a wireless communication system, according to embodiments disclosed herein.
  • FIG. 9 illustrates a system for performing signaling between a wireless device and a network device, according to embodiments disclosed herein.
  • a UE Various embodiments are described with regard to a UE. However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and/or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component.
  • a wireless communication system may use network slicing.
  • Network slicing organizes resources of the wireless communication system (e.g., associated units of CN resources and/or RAN resources) into “slices. ”
  • some wireless communications systems may organize these slices into one or more groups (each having one or more slices) . Such groups may be referred to herein as "slice groups. " The use of slice groups may be beneficial in wireless communications systems that, for example, support a large number of slices (and thus where slice groups, rather than individual slices, may be indicated between a RAN and a UE, in cases where a large signaling overhead might be needed in order to otherwise indicate any individual slice) .
  • slice groups may correspond to one or more particular use case (s) within the network.
  • a first network slice group may be intended (e.g., from a network configuration perspective) for ultra-reliable low latency communications (URLLCs)
  • a second network slice group may be intended for non-URLLC and/or more general use.
  • URLLCs ultra-reliable low latency communications
  • the network may which to associate the a UE that could benefit from URLLC service with a slice group intended for URLLC.
  • the network may provide a UE with slice-based frequency priority configuration information.
  • the network may use a system information block (SIB) for this purpose. It is contemplated that in some wireless communication systems (e.g., in NR systems) , a SIB16 may be used for this purpose.
  • SIB system information block
  • An SIB may provide the UE with slice-based frequency priority configuration information in the following format:
  • F1 a list of one or more items having information items ⁇ slice group x, frequency priority for slice group x, slice allowed cells or slice excluded cells ⁇
  • F2 a list of one or more items having information items ⁇ slice group x, frequency priority for slice group x, slice allowed cells or slice excluded cells ⁇
  • Fn a list of one or more items having information items ⁇ slice group x, frequency priority for slice group x, slice allowed cells or slice excluded cells ⁇
  • F1 through Fn represent different frequencies, each having an associated list of (one or more) information items relevant for selecting to that frequency.
  • the content in “ ⁇ ” for each of the frequencies F1 through Fn describes the (same) format for individual list items within the associated list for that frequency.
  • Each list item may include a “slice group x” identifier information item identifying a slice group, a “frequency priority for slice group x” indication information item that relates a network-assigned priority for using that slice group with the associated frequency, and a “slice allowed cells or slice excluded cells” indication information item that indicates particular cells for which this frequency/slice group information is permitted/excluded to be used, as the case may be.
  • slice-based frequency priority configuration information provided by SIB may include information for any number of frequencies (including one, two, three, four, 10, 15, etc. ) .
  • the slice-based frequency priority configuration information provided by SIB may be understood to be made up of one or more frequency priority configurations for a corresponding one or more slice groups. For example, it may be that any list items (across all frequencies) for a first slice group (e.g., for the same first “slice group x” identifier information item) represent a first frequency priority configuration for that first slice group, and that any list items (across all frequencies) for a second slice group (e.g., for the same second “slice group x” identifier information item) represent a second frequency priority configuration for that second slice group.
  • this SIB-provided slice-based frequency priority configuration information may be common to many/all of the UE that receive the SIB/that are camped on the cell broadcasting the SIB.
  • the network may use a radio resource control (RRC) release message (also referred to as an “RRCRelease” message) to provide dedicated frequency priority information to a UE.
  • RRC radio resource control
  • RRCRelease radio resource control
  • an RRC release message is directed to a particular UE, the use of the RRC release message to deliver frequency priority information allows this information to be dedicated particularly for the UE (e.g., such that may be different from other UEs served on the same cell) .
  • dedicated frequency priority information delivered to the UE may supersede or override any frequency priority information previously delivered to the UE (e.g., using an SIB) .
  • An RRC release message may provide the UE with slice-based frequency priority configuration information in the following format:
  • F1 a list of one or more items having information items ⁇ slice group x, frequency priority for slice group x ⁇
  • F2 a list of one or more items having information items ⁇ slice group x, frequency priority for slice group x ⁇
  • Fn a list of one or more items having information items ⁇ slice group x, frequency priority for slice group x ⁇
  • each list item associated with a frequency may include a “slice group x” identifier information item identifying a slice group and a “frequency priority for slice group x” indication information item that relates a network-assigned priority for using that slice group with the associated frequency.
  • an RRC release message may not indicate a “slice allowed cells or slice excluded cells” indication information item that indicates particular cells for which this frequency/slice group information is permitted/excluded to be used (because the base station performing the RRC release of the UE may not have this knowledge about other cells of the wireless communication system) .
  • slice-based frequency priority configuration information provided by an RRC release message may include information for any number of frequencies (including one, two, three, four, 10, 15, etc. ) .
  • the slice-based frequency priority configuration information provided by an RRC release message may be understood to correspond to one or more frequency priority configurations for a corresponding one or more slice groups. For example, it may be that any list items (across all frequencies) for a first slice group (e.g., for the same first “slice group x” identifier information item) represent a first frequency priority configuration for that first slice group, and that any list items (across all frequencies) for a second slice group (e.g., for the same second “slice group x” identifier information item) represent a second frequency priority configuration for that second slice group. Further, because the RRC release message provides slice-based frequency priority configuration information that is dedicated to the UE undergoing the RRC release, it may be understood that these frequency priority configurations are dedicated frequency priority configurations for their corresponding slice groups.
  • the UE may receive a non-access stratum (NAS) configuration from the CN (e.g., an access and mobility management function (AMF) of the CN) .
  • NAS non-access stratum
  • AMF access and mobility management function
  • This NAS configuration may indicate a slice-to-slice-group mapping to the UE.
  • the NAS configuration may include a slice group priority for the UE.
  • This slice group priority may indicate to the UE a relative priority at the UE of one or more slice group s.
  • the UE may then perform radio resource management (RRM) and/or cell reselection methods according to its slice group priority and in view of received slice-based frequency priority configuration information (e.g., as provided by SIB and/or an RRC release message) .
  • RRM radio resource management
  • cell reselection methods according to its slice group priority and in view of received slice-based frequency priority configuration information (e.g., as provided by SIB and/or an RRC release message) .
  • frequencies of the slice-based frequency priority configuration information that support at least one slice group indicated in the NAS-provided slice group priority for the UE may have a higher re-selection priority than frequencies that do not support any slice groups indicated in the slice group priority for the UE.
  • the frequencies of the slice-based frequency priority configuration information that support at least one slice group indicated in the NAS-provided slice group priority for the UE are prioritized at the UE in the order provided in the NAS-provided slice group priority for the UE.
  • the frequencies of the slice-based frequency priority configuration information that support the same slice group from the NAS-provided slice group priority for the UE are prioritized in the order of the per-slice group sliceSpecificCellReselectionPriority (the priority represented by the “frequency priority for slice group x” information item discussed above) .
  • frequencies that indicate a sliceSpecificCellReselectionPriority for the slice group are prioritized over frequencies that support the slice group but that do not indicate a sliceSpecificCellReselectionPriority for the slice group.
  • the frequencies of the slice-based frequency priority configuration information that support no slice group from the NAS-provided slice group priority for the UE may be prioritized at the UE in order of their cellReselectionPriority (a non-slice-based priority that has been configured to the UE) .
  • a first UE may receive a NAS configuration that configures UE 1 to use a first slice group ( “slice group 1" ) and a second slice group ( “slice group 2" ) .
  • UE 1 determines that slice group 1 has a higher relative priority than slice group 2.
  • a second UE may receive a NAS configuration that configures UE 2 to use slice group 1 and slice group 2.
  • UE 2 that slice group 2 has a higher relative priority than slice group 1.
  • each of UE 1 and UE 2 may receive slice-based frequency priority configuration information from the network.
  • This slice-based frequency priority configuration information may be received in SIB, or may be provided to one or both of the UEs in dedicated RRC release message for that UE, as has been described.
  • each of the UEs understands its relevant slice-based frequency priority configuration information to be as follows:
  • the UEs might use different slice-based frequency priority configuration information (e.g., in the case that at least one of the UEs has been given dedicated slice-based frequency priority configuration information via an RRC release message) .
  • This slice-based frequency priority configuration information may be understood to be made up of two frequency priority configurations for two slice groups (slice group 1 and slice group 2) .
  • a first frequency priority configuration for slice group 1 may be that on frequency 1, slice group 1 has a priority of 7.
  • a second frequency priority configuration for slice group 2 may be that on frequency 1, slice group 2 has a priority of 7 and that on frequency 2, slice group 2 has a priority of 8.
  • Each UE may then proceed to perform RRM and/or cell reselection methods using, among possibly others, one or more of the frequencies configured in the slice-based frequency priority configuration information. This use may occur in an order that is determined according to the UE's NAS-provided slice group priority and in view of the slice based frequency configuration information known to the UE.
  • UE 1 in the case of UE 1, UE 1 first uses F1, because F1 supports slice group 1 (its highest priority slice group from its NAS-provided slice group priority) , while F2 does not. Then, the UE may then use F2 (e.g., because it in the slice-based frequency priority configuration information, albeit without support for slice group 1) . Finally, UE 1 may then proceed to consider frequencies according to a non-slice-based methods.
  • UE 2 In the case of UE 2, UE 2 first uses F2, because F2 supports slice group 2 (its highest priority slice group from its NAS-provided slice group priority) with a higher priority than F1 (8 versus 7) . Then, UE 2 uses F1, because F1 (also) supports slice group 2 (albeit at a lower priority) . Finally, UE 1 may then proceed to consider frequencies according to a non-slice-based methods.
  • FIG. 1 illustrates a diagram 100 showing the use of network slicing methods within a UE registration area 102, according to an embodiment.
  • a registration area 102 may include a first tracking area (TA) 104 and a second TA 106.
  • the first TA 104 may use a first tracking area identifier (TAI) (TAI 1) and the second TA 106 may use a second TAI (TAI 2) .
  • TAI tracking area identifier
  • TAI 2 second TAI
  • a UE may be configured with a number of network slicing access stratum groups (NSAGs) that are usable within the UE's registration area 102.
  • An NSAG may be understood to correspond to a slice group as is discussed herein. It may be that one of these NSAGs as known to the UE may be associated with a particular TAI.
  • the UE understands that the TA corresponding to this TAI supports the slice group represented by the NSAG.
  • a TA may support the NSAG slice group by, for example, providing that slice group in the portion of the network corresponding to the TA, and/or by configuring for that slice group in slice-based frequency priority configuration information provided by SIBs and/or RRC release messages used in that TA.
  • a first TAI ( "TAI 1" ) corresponding to the first TA 104 is a valid TAI for a first network slicing access stratum group ( "NSAG1” ) . Accordingly, it may be understood that the first TA 104 supports the NSAG1 slice group. However, it may be that a second TAI ( "TAI 2" ) corresponding to the second TA 106 is not a valid TAI for NSAG1. Accordingly, the NSAG1 slice group is not available for use within the second TA 106.
  • the UE may be aware of multiple NSAGs associated with corresponding particular TAIs in the registration area 102 in the manner that has been described. For example, in some wireless communication systems up to four such NSAGs may be associated with certain TAI (s) in the registration area 102.
  • FIG. 2 illustrates a CellReselectionPriorities information element 200, according to an embodiment.
  • an RRC release message may provide dedicated slice-based frequency priority configuration information (that provides one or more dedicated frequency priority configurations for one or more corresponding slice groups) using the CellReselectionPriorities information element 200.
  • the CellReselectionPriorities information element 200 may include, among other things, a t320 timer 202.
  • the t320 timer 202 may indicate a duration for which a dedicated slice-based frequency priority configuration information provided in the CellReselectionPriorities information element 200 is valid. Accordingly, a t320 timer 202 may sometimes referred to herein as a “validity timer” or “first validity timer. ”
  • the UE is configured to discard the dedicated slice-based frequency priority configuration information provided in the CellReselectionPriorities information element 200 by an RRC release message after the associated t320 timer 202 expires (and, e.g., revert to the use of (non-dedicated) slice-based frequency priority configuration information provided by SIB) .
  • the t320 timer 202 can have a duration of up to 180 minutes.
  • the t320 timer 202 may be considered to be for (e.g., each of) the individual dedicated frequency priority configurations for corresponding individual slice groups that make up the entire dedicated slice-based frequency priority configuration information.
  • FIG. 3 illustrates a diagram 300 showing the use of network slicing methods within a UE registration area 302, according to an embodiment.
  • a registration area 302 may include a first TA 304, a second TA 306, and a third TA 308.
  • the first TA 304 may use a first TAI ( "TAI 1" )
  • the second TA 306 may use a second TAI ( "TAI 2" )
  • the third TA 308 may use a third TAI ( "TAI 3" ) .
  • a first UE 310 may begin in the first TA 304, which uses a TAI that is valid for a first NSAG ( "NSAG1" ) . Accordingly, the first TA 304 supports the NSAG1 slice group. While in the first TA 304, the first UE 310 may be configured with dedicated slice-based frequency priority configuration information that includes a dedicated frequency priority configuration for the NSAG1 slice group.
  • the first UE 310 moves from the first TA 304 to the second TA 306, which may implement slice-based frequency priority configuration information methods, but which does not support the NSAG1 slice group (e.g., TAI 2 is not valid for NSAG1, as illustrated) .
  • the UE may continue to perform measurements of one or more frequencies determined (at least in part) using a dedicated frequency priority configuration for the NSAG1 slice group from the dedicated slice-based frequency priority configuration information (until the relevant t320 time expires) .
  • the frequencies selected for measurement in view of the use of the dedicated frequency priority configuration for the NSAG1 slice group may not be particularly (or at all) relevant.
  • the second TA 306 does not support NSAG1
  • it may be that the frequency (s) indicated for in the dedicated frequency priority configuration for the NSAG1 slice group are not used, or are not frequently used, within the second TA 306.
  • the UE is in a part of the second TA 306 that is not physically near cells of the first TA 304, and reselection back into the first TA 304 according to frequencies selected in view of the use of the dedicated frequency priority configuration for the NSAG1 slice group is not likely.
  • a prioritization of frequency measurement activities at the UE generated in view of a dedicated frequency priority configuration for the NSAG1 slice group from the dedicated frequency priority configuration information may result in an inefficient use of UE resources.
  • a second UE 312 may begin in the first TA 304. While in the first TA 304, the second UE 312 may be configured with dedicated slice-based frequency priority configuration information that includes a dedicated frequency priority configuration for the NSAG1 slice group.
  • the second UE 312 moves from the first TA 304 to the third TA 308, which may not implement slice-based frequency priority configuration information methods.
  • the UE may continue to perform measurements of one or more frequencies determined (at least in part) using a dedicated frequency priority configuration for the NSAG1 slice group from the dedicated slice-based frequency priority configuration information (until the relevant t320 time expires) .
  • the frequencies selected for measurement in view of the use of the dedicated frequency priority configuration for the NSAG1 slice group may not be particularly (or at all) relevant.
  • the third TA 308 does not support NSAG1
  • it may be that the frequency (s) indicated for in the dedicated frequency priority configuration for the NSAG1 slice group are not used, or are not frequently used, within the third TA 308.
  • the UE is in a part of the third TA 308 that is not physically near cells of the first TA 304, and reselection back into the first TA 304 according to frequencies selected in view of the use of the dedicated frequency priority configuration for the NSAG1 slice group in not likely.
  • a prioritization of frequency measurement activities at the UE generated in view of a dedicated frequency priority configuration for the NSAG1 slice group from the dedicated frequency priority configuration information may result in an inefficient use of UE resources.
  • a UE may be configured with dedicated frequency priority configuration information having a dedicated frequency priority configuration for a slice group. The UE then camps on a new cell. The dedicated frequency priority configuration for the slice group may still be active according to a corresponding t320 timer.
  • the UE may check a SIB of the new cell having slice-based frequency priority configuration information. For example, an SIB16 having a freqPriorityListNRSlicing information object carrying the slice-based frequency priority configuration information (including, in this SIB case, an allowed cell list or an excluded cell list) may be checked. Because this slice-based frequency priority configuration information is being broadcast in the SIB by the new cell, any slice groups indicated therein are relevant corresponding to the present location of the UE. Accordingly, when the UE determines that the SIB's slice-based frequency priority configuration information contains a frequency priority configuration for the slice group, the UE concludes that the slice group remains relevant at the new location. Accordingly, the UE continues to use the previously received dedicated frequency priority configuration for the slice group.
  • an SIB16 having a freqPriorityListNRSlicing information object carrying the slice-based frequency priority configuration information including, in this SIB case, an allowed cell list or an excluded cell list
  • the new cell is part of the same TA as the cell where the dedicated frequency priority configuration for the slice group was configured to the UE.
  • the SIB of the new cell may include a frequency priority configuration for the slice group due to the fact that the slice group is supported throughout the entire TA.
  • the UE continues to use the previously configured dedicated frequency priority configuration for the slice group.
  • an SIB of the new cell may not necessarily include a frequency priority configuration for the slice group for reasons relating to the TA of the new cell.
  • one or more cells of the first TA may be neighbor cells to the new cell, and that the SIB of the new cell includes frequency priority configuration (s) for slice group (s) corresponding to those neighbor cells.
  • the slice-based frequency priority configuration information of the SIB of the current cell would still indicate a dedicated frequency priority configuration for the slice group due to the this neighbor cell relationship.
  • FIG. 4 illustrates a diagram 400 corresponding to the use of network slicing methods, according to an embodiment.
  • the diagram 400 includes the first TA 402, the second TA 404, and the third TA 406.
  • the first TA 402 may use a first TAI ( "TAI 1" )
  • the second TA 404 may use a second TAI ( "TAI 2" )
  • the third TA 406 may use a third TAI ( "TAI 3" ) .
  • a first UE 412 may be configured with a dedicated frequency priority configuration for the slice group (corresponding to NSAG1 in the diagram 400) prior to moving to the first TAI 2 cell 408 of the second TA 404, as illustrated.
  • One or more cells of the first TA 402 may be neighbor cell (s) of the first TAI 2 cell 408. Accordingly, because the first TA 402 supports the slice group, slice-based frequency priority configuration information of an SIB of the first TAI 2 cell 408 indicates a frequency priority configuration for the slice group (at least as corresponding to its neighbor cell (s) from the first TA 402) . Accordingly, upon identifying the presence of a frequency priority configuration for the slice group in the SIB, the first UE 412 may determine to continue using its dedicated frequency priority configuration for the slice group.
  • the UE upon camping on the new cell, the UE checks the SIB of the new cell having slice-based frequency priority configuration information and determines that there is no useable frequency priority configuration for the slice group.
  • Such a case may correspond to the a circumstance where the new cell does not have any first TA cells as neighbor cells (and thus the SIB of the new cell does not include a frequency priority configuration for the slice group based on a neighbor cell relationship) .
  • a second UE 414 may be configured with a dedicated frequency priority configuration for the slice group (corresponding to NSAG1 in the diagram 400) prior to moving to the second TA 404 as illustrated.
  • the second UE 414 moves to camp on a second TAI 2 cell 410 of the second TA 404 that does not have any cells of the first TA 402 as neighbors. Note that this may occur in stages (e.g., the second UE 414 may have first camped on the first TAI 2 cell 408, and/or on some other cell (s) , prior to camping on the second TAI 2 cell 410) .
  • slice-based frequency priority configuration information of an SIB of the second TAI 2 cell 410 does not indicate a useable frequency priority configuration for the slice group. This may be because, for example, the second TA 404 does not support the slice group (represented in FIG. 4 as “NSAG1” ) . Further, it may be that no cell of the first TA 402 (which does support the NSAG1 slice group) is a neighbor cell to the second TAI 2 cell 410.
  • the second UE 414 may determine to stop the use of the previously configured dedicated frequency priority configuration for the slice group. For example, the UE may prioritize frequencies for its RRM and/or cell reselection methods without reference to the dedicated frequency priority configuration for the slice group. This may result in the UE dropping a frequency measurement for RRM and/or cell re-selection corresponding to the dedicated frequency priority configuration for the slice group (e.g., that would have otherwise been performed according to a use of the dedicated frequency priority configuration for the slice group) .
  • the stopping of the use of the previously configured dedicated frequency priority configuration for the slice group may occur prior to an expiration of any t320 timer for the dedicated frequency priority configuration for the slice group.
  • slice-based frequency priority configuration information of an SIB of the new cell indicates a frequency priority configuration for the slice group, but only for a public land mobile network (PLMN) (e.g., a registered PLMN (RPMLN) and/or an equivalent PLMN (EPMLN) ) that is not used by the UE.
  • PLMN public land mobile network
  • RPMLN registered PLMN
  • EPMLN equivalent PLMN
  • the UE will fail to identify the presence of a usable frequency priority configuration for the slice group in the SIB of the new cell (with the result that the UE determines to stop the use of the previously configured dedicated frequency priority configuration for the slice group) .
  • a UE determination to stop the use of the previously configured dedicated frequency priority configuration for one slice group does not cause the UE to stop the use of other dedicated frequency priority configuration (s) for other slice group (s) (if any) that are also found in the dedicated frequency priority configuration information as was provided in the RRC release message. These may remain valid (but may also be subject to individualized determinations regarding each of these other dedicated frequency priority configuration (s) for other slice group (s) in the manner discussed herein, and to any t320 timer that may apply) .
  • the UE upon determining to stop the use of the dedicated frequency priority configuration for a slice group, the UE starts a second validity timer (e.g., a timer that is different than a t320 timer as discussed herein) . Then, whenever UE moves to camp on a new cell prior to the expiration of this second validity timer, the UE may check to determine whether it has re-entered the TA in which the dedicated frequency priority configuration information was originally provided, and/or if an SIB of the new cell provides slice-based frequency priority configuration information indicating a usable frequency priority configuration for the slice group (e.g., due to a neighbor cell relationship between the new cell and a cell of the TA in which the dedicated frequency priority configuration information was originally provided, or due to the new cell being in the TA in which the dedicated frequency priority configuration information was originally provided) . If so, the UE may resume or restart the use of the dedicated frequency priority configuration for the slice group.
  • a second validity timer e.g., a timer that is
  • This resumed/restarted use may still be subject to the duration of a first validity/t320 timer as originally configured. Accordingly, the duration of a second validity timer as has been described may be less than or equal to any remaining duration for the t320 timer.
  • the UE may then outright discard the dedicated frequency priority configuration for the slice group.
  • FIG. 5 illustrates a method 500 of a UE, according to an embodiment.
  • the method 500 includes receiving 502, while camping on a first cell in a first TA that supports a slice group, a dedicated frequency priority configuration for the slice group.
  • the method 500 further includes camping 504 on a second cell in a second TA that does not support the slice group.
  • the method 500 further includes determining 506 that slice-based frequency priority configuration information in a SIB of the second cell does not include a usable frequency priority configuration for the slice group.
  • the method 500 further includes stopping 508 a use of the dedicated frequency priority configuration for the slice group in response to the determining that the slice-based frequency priority configuration information in the SIB of the second cell does not include a usable frequency priority configuration for the slice group.
  • the stopping the use of the dedicated frequency priority configuration for the slice group occurs prior to an expiration of a first validity timer for the dedicated frequency priority configuration for the slice group.
  • the stopping the use of the dedicated frequency priority configuration for the slice group comprises dropping a frequency measurement for cell re-selection corresponding to the dedicated frequency priority configuration for the slice group.
  • the method 500 further includes starting a second validity timer upon stopping the use of the dedicated frequency priority configuration for the slice group, re-entering the first TA prior to an expiration of the second validity timer, and resuming the use of the dedicated frequency priority configuration for the slice group in response to the re-entering the first TA prior to the expiration of the second validity timer.
  • the method 500 further includes starting a second validity timer upon stopping the use of the dedicated frequency priority configuration for the slice group, camping on third cell having a neighbor cell that is from the first TA, determining that an SIB of the third cell indicates a useable frequency priority configuration for the slice group, and resuming the use of the dedicated frequency priority configuration for the slice group in response to the determining that the SIB of the third cell indicates a useable frequency priority configuration for the slice group.
  • the determining that the slice-based frequency priority configuration information in the SIB of the second cell does not include a usable frequency priority configuration for the slice group comprises determining that a provided frequency priority configuration for the slice group in the slice-based frequency priority configuration information in the SIB of the second cell is for a PLMN that is not used by the UE.
  • the slice group is prioritized at the UE according to a slice group priority for the UE.
  • the method 500 further includes receiving the dedicated frequency priority configuration for the slice group in a RRC release message.
  • Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method 500.
  • This apparatus may be, for example, an apparatus of a UE (such as a wireless device 902 that is a UE, as described herein) .
  • Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 500.
  • This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 906 of a wireless device 902 that is a UE, as described herein) .
  • Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method 500.
  • This apparatus may be, for example, an apparatus of a UE (such as a wireless device 902 that is a UE, as described herein) .
  • Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 500.
  • This apparatus may be, for example, an apparatus of a UE (such as a wireless device 902 that is a UE, as described herein) .
  • Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 500.
  • Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method 500.
  • the processor may be a processor of a UE (such as a processor (s) 904 of a wireless device 902 that is a UE, as described herein) .
  • These instructions may be, for example, located in the processor and/or on a memory of the UE (such as a memory 906 of a wireless device 902 that is a UE, as described herein) .
  • a UE may be configured with dedicated frequency priority configuration information having a dedicated frequency priority configuration for a slice group. The UE then camps on a new cell. The dedicated frequency priority configuration for the slice group may still be active according to a corresponding t320 timer.
  • the UE may check whether any SIB of the new cell provides slice-based frequency priority configuration information (e.g., such as in an SIB16 of some wireless communication systems) .
  • the UE may determine to stop the use of the previously configured dedicated frequency priority configuration for the slice group. For example, the UE may prioritize frequencies for its RRM and/or cell reselection methods without reference to the dedicated frequency priority configuration for the slice group. This may result in the UE dropping a frequency measurement for RRM and/or cell re-selection corresponding to the dedicated frequency priority configuration for the slice group (e.g., that would have otherwise been performed according to a use of the dedicated frequency priority configuration for the slice group) .
  • the stopping of the use of the previously configured dedicated frequency priority configuration for the slice group may occur prior to an expiration of any t320 timer for the dedicated frequency priority configuration for the slice group.
  • the UE accordingly stops the use of all dedicated frequency priority configuration (s) for all slice group (s) that are present in dedicated frequency priority configuration information as provided by the RRC release message.
  • the UE upon determining to stop the use of the dedicated frequency priority configuration for a slice group, the UE starts a second validity timer (e.g., a timer that is different than a t320 timer as discussed herein) . Then, whenever the UE moves to camp on a new cell prior to the expiration of this second validity timer, the UE may check to determine whether it has re-entered the TA in which the dedicated frequency priority configuration information was originally provided, and/or if an SIB of the new cell provides slice-based frequency priority configuration information indicating a useable frequency priority configuration for the slice group (e.g., due to a neighbor cell relationship between the new cell and a cell of the TA in which the dedicated frequency priority configuration information was originally provided, or due to the new cell being in the TA in which the dedicated frequency priority configuration information was originally provided) . If so, the UE may resume or restart the use of the dedicated frequency priority configuration for the slice group.
  • a second validity timer e.g., a timer that
  • This resumed/restarted use may still be subject to the duration of a first validity/t320 timer as originally configured. Accordingly, the duration of a second validity timer as has been described may be less than or equal to any remaining duration for the t320 timer.
  • the UE may then outright discard the dedicated frequency priority configuration for the slice group.
  • FIG. 6 illustrates a method 600 of a UE, according to an embodiment.
  • the method 600 includes receiving 602, while camping on a first cell in a first TA that supports a slice group, a dedicated frequency priority configuration for the slice group.
  • the method 600 further includes camping 604 on a second cell in a second TA that does not support the slice group.
  • the method 600 further includes determining 606 that no SIB of the second cell provides slice-based frequency priority configuration information.
  • the method 600 further includes stopping 608 a use of the dedicated frequency priority configuration for the slice group in response to the determining that no SIB of the second cell provides slice-based frequency priority configuration information.
  • the stopping a use of the dedicated frequency priority configuration for the slice group occurs prior to an expiration of a first validity timer for the dedicated frequency priority configuration for the slice group.
  • the stopping the use of the dedicated frequency priority configuration for the slice group comprises dropping a frequency measurement for cell re-selection corresponding to the dedicated frequency priority configuration for the slice group.
  • the method 600 further includes starting a second validity timer upon stopping the use of the dedicated frequency priority configuration for the slice group, re-entering the first TA prior to an expiration of the second validity timer, and resuming the use of the dedicated frequency priority configuration for the slice group in response to the re-entering the first TA prior to the expiration of the second validity timer.
  • the method 600 further includes starting a second validity timer upon stopping the use of the dedicated frequency priority configuration for the slice group, camping on third cell having a neighbor cell that is from the first TA, determining that an SIB of the third cell indicates a useable frequency priority configuration for the slice group, and resuming the use of the dedicated frequency priority configuration for the slice group in response to the determining that the SIB of the third cell indicates a useable frequency priority configuration for the slice group.
  • the slice group is prioritized at the UE according to a slice group priority for the UE.
  • the method 600 further includes receiving the dedicated frequency priority configuration for the slice group in a RRC release message.
  • Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method 600.
  • This apparatus may be, for example, an apparatus of a UE (such as a wireless device 902 that is a UE, as described herein) .
  • Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 600.
  • This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 906 of a wireless device 902 that is a UE, as described herein) .
  • Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method 600.
  • This apparatus may be, for example, an apparatus of a UE (such as a wireless device 902 that is a UE, as described herein) .
  • Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 600.
  • This apparatus may be, for example, an apparatus of a UE (such as a wireless device 902 that is a UE, as described herein) .
  • Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 600.
  • Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method 600.
  • the processor may be a processor of a UE (such as a processor (s) 904 of a wireless device 902 that is a UE, as described herein) .
  • These instructions may be, for example, located in the processor and/or on a memory of the UE (such as a memory 906 of a wireless device 902 that is a UE, as described herein) .
  • a UE may be configured with dedicated frequency priority configuration information having a dedicated frequency priority configuration for a slice group. The UE then camps on a new cell. The dedicated frequency priority configuration for the slice group may still be active according to a corresponding t320 timer.
  • the UE may check whether the new cell is in a TA that supports the slice group. To perform this check, the UE may determine a TAI for the TA of the new cell based on TA information in an SIB broadcast by the new cell. In some wireless communication systems, this SIB may be an SIB1, and the TA information may include a trackingareacode information item that is used by the UE to determine the TAI corresponding to the TA of the new cell.
  • the UE may then proceed to determine, based on the TAI of the second TA, that the second TA does not support the slice group. For example, the UE may identify that the NSAG for the slice group is not associated with the TAI of the of the second TA (e.g., that the TAI for the second TA is not valid for the NSAG for the slice group) .
  • the UE may determine to stop the use of the previously configured dedicated frequency priority configuration for the slice group. For example, the UE may prioritize frequencies for its RRM and/or cell reselection methods without reference to the dedicated frequency priority configuration for the slice group. This may result in the UE dropping a frequency measurement for RRM and/or cell re-selection corresponding to the dedicated frequency priority configuration for the slice group (e.g., that would have otherwise been performed according to a use of the dedicated frequency priority configuration for the slice group) .
  • the stopping of the use of the previously configured dedicated frequency priority configuration for the slice group may occur prior to an expiration of any t320 timer for the dedicated frequency priority configuration for the slice group.
  • TAIs identified using an SIB in the manner described herein are PLMN specific.
  • the UE using the SIB, identifies a same TAI for the new cell as the TAI for the TA where the UE received the dedicated frequency priority configuration for a slice group, but that the TAI for the new cell is only valid for a PLMN that is not used by the UE.
  • the UE will determine that the second TA does not support the slice group (with the result that the UE determines to stop the use of the previously configured dedicated frequency priority configuration for the slice group) .
  • a UE determination to stop the use of the previously configured dedicated frequency priority configuration for one slice group does not cause the UE to stop the use of other dedicated frequency priority configuration (s) for other slice group (s) (if any) that are also found in the dedicated frequency priority configuration information as was provided in the RRC release message. These may remain valid (but may also be subject to individualized determinations regarding each of these other dedicated frequency priority configuration (s) for other slice group (s) in the manner discussed herein, and to any t320 timer that may apply) .
  • the UE upon determining to stop the user of the dedicated frequency priority configuration for a slice group, the UE starts a second validity timer (e.g., a timer that is different than a t320 timer as discussed herein) . Then, whenever UE moves to camp on a new cell prior to the expiration of this second validity timer, the UE may check to determine whether it has re-entered the TA in which the dedicated frequency priority configuration information was originally provided, and/or if an SIB of the new cell provides slice-based frequency priority configuration information indicating a useable frequency priority configuration for the slice group (e.g., due to a neighbor cell relationship between the new cell and a cell of the TA in which the dedicated frequency priority configuration information was originally provided, or due to the new cell being in the TA in which the dedicated frequency priority configuration information was originally provided) . If so, the UE may resume or restart the use of the dedicated frequency priority configuration for the slice group.
  • a second validity timer e.g., a timer that is
  • This resumed/restarted use may still be subject to the duration of a first validity/t320 timer as originally configured. Accordingly, the duration of a second validity timer as has been described may be less than or equal to any remaining duration for the t320 timer.
  • the UE may then outright discard the dedicated frequency priority configuration for the slice group.
  • FIG. 7 illustrates a method 700 of a UE, according to an embodiment.
  • the method 700 includes receiving 702, while on a first cell in a first TA that supports a slice group, a dedicated frequency priority configuration for the slice group.
  • the method 700 further includes camping 704 on a second cell in a second TA that does not support the slice group.
  • the method 700 further includes determining 706 a TAI for the second TA based on TA information in a SIB of the second cell.
  • the method 700 further includes determining 708, based on the TAI of the second TA, that the second TA does not support the slice group.
  • the method 700 further includes stopping 710 a use of the dedicated frequency priority configuration for the slice group in response to the determining that the second TA does not support the slice group.
  • the stopping the use of the dedicated frequency priority configuration for the slice group occurs prior to an expiration of a first validity timer for the dedicated frequency priority configuration for the slice group.
  • the stopping the use of the dedicated frequency priority configuration for the slice group comprises dropping a frequency measurement for cell re-selection corresponding to the dedicated frequency priority configuration for the slice group.
  • the method 700 further includes starting a second validity timer upon stopping the use of the dedicated frequency priority configuration for the slice group, re-entering the first TA prior to an expiration of the second validity timer, and resuming the use of the dedicated frequency priority configuration for the slice group in response to the re-entering the first TA prior to the expiration of the second validity timer.
  • the method 700 further includes starting a second validity timer upon stopping the use of the dedicated frequency priority configuration for the slice group, camping on third cell having a neighbor cell that is from the first TA, determining that an SIB of the third cell indicates a useable frequency priority configuration for the slice group, and resuming the use of the dedicated frequency priority configuration for the slice group in response to the determining that the SIB of the third cell indicates a useable frequency priority configuration for the slice group.
  • the slice group is prioritized at the UE according to a slice group priority for the UE.
  • the method 700 further includes receiving the dedicated frequency priority configuration for the slice group in a RRC release message.
  • Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method 700.
  • This apparatus may be, for example, an apparatus of a UE (such as a wireless device 902 that is a UE, as described herein) .
  • Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 700.
  • This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 906 of a wireless device 902 that is a UE, as described herein) .
  • Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method 700.
  • This apparatus may be, for example, an apparatus of a UE (such as a wireless device 902 that is a UE, as described herein) .
  • Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 700.
  • This apparatus may be, for example, an apparatus of a UE (such as a wireless device 902 that is a UE, as described herein) .
  • Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 700.
  • Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method 700.
  • the processor may be a processor of a UE (such as a processor (s) 904 of a wireless device 902 that is a UE, as described herein) .
  • These instructions may be, for example, located in the processor and/or on a memory of the UE (such as a memory 906 of a wireless device 902 that is a UE, as described herein) .
  • FIG. 8 illustrates an example architecture of a wireless communication system 800, according to embodiments disclosed herein.
  • the following description is provided for an example wireless communication system 800 that operates in conjunction with the LTE system standards and/or 5G or NR system standards as provided by 3GPP technical specifications.
  • the wireless communication system 800 includes UE 802 and UE 804 (although any number of UEs may be used) .
  • the UE 802 and the UE 804 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) , but may also comprise any mobile or non-mobile computing device configured for wireless communication.
  • the UE 802 and UE 804 may be configured to communicatively couple with a RAN 806.
  • the RAN 806 may be NG-RAN, E-UTRAN, etc.
  • the UE 802 and UE 804 utilize connections (or channels) (shown as connection 808 and connection 810, respectively) with the RAN 806, each of which comprises a physical communications interface.
  • the RAN 806 can include one or more base stations, such as base station 812 and base station 814, that enable the connection 808 and connection 810.
  • connection 808 and connection 810 are air interfaces to enable such communicative coupling, and may be consistent with RAT (s) used by the RAN 806, such as, for example, an LTE and/or NR.
  • the UE 802 and UE 804 may also directly exchange communication data via a sidelink interface 816.
  • the UE 804 is shown to be configured to access an access point (shown as AP 818) via connection 820.
  • the connection 820 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 818 may comprise a router.
  • the AP 818 may be connected to another network (for example, the Internet) without going through a CN 824.
  • the UE 802 and UE 804 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 812 and/or the base station 814 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications) , although the scope of the embodiments is not limited in this respect.
  • OFDM signals can comprise a plurality of orthogonal subcarriers.
  • the base station 812 or base station 814 may be implemented as one or more software entities running on server computers as part of a virtual network.
  • the base station 812 or base station 814 may be configured to communicate with one another via interface 822.
  • the interface 822 may be an X2 interface.
  • the X2 interface may be defined between two or more base stations (e.g., two or more eNBs and the like) that connect to an EPC, and/or between two eNBs connecting to the EPC.
  • the interface 822 may be an Xn interface.
  • the Xn interface is defined between two or more base stations (e.g., two or more gNBs and the like) that connect to 5GC, between a base station 812 (e.g., a gNB) connecting to 5GC and an eNB, and/or between two eNBs connecting to 5GC (e.g., CN 824) .
  • the RAN 806 is shown to be communicatively coupled to the CN 824.
  • the CN 824 may comprise one or more network elements 826, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UE 802 and UE 804) who are connected to the CN 824 via the RAN 806.
  • the components of the CN 824 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) .
  • the CN 824 may be an EPC, and the RAN 806 may be connected with the CN 824 via an S1 interface 828.
  • the S1 interface 828 may be split into two parts, an S1 user plane (S1-U) interface, which carries traffic data between the base station 812 or base station 814 and a serving gateway (S-GW) , and the S1-MME interface, which is a signaling interface between the base station 812 or base station 814 and mobility management entities (MMEs) .
  • S1-U S1 user plane
  • S-GW serving gateway
  • MMEs mobility management entities
  • the CN 824 may be a 5GC, and the RAN 806 may be connected with the CN 824 via an NG interface 828.
  • the NG interface 828 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 812 or base station 814 and a user plane function (UPF) , and the S1 control plane (NG-C) interface, which is a signaling interface between the base station 812 or base station 814 and access and mobility management functions (AMFs) .
  • NG-U NG user plane
  • UPF user plane function
  • S1 control plane S1 control plane
  • an application server 830 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 824 (e.g., packet switched data services) .
  • IP internet protocol
  • the application server 830 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc. ) for the UE 802 and UE 804 via the CN 824.
  • the application server 830 may communicate with the CN 824 through an IP communications interface 832.
  • FIG. 9 illustrates a system 900 for performing signaling 932 between a wireless device 902 and a network device 918, according to embodiments disclosed herein.
  • the system 900 may be a portion of a wireless communications system as herein described.
  • the wireless device 902 may be, for example, a UE of a wireless communication system.
  • the network device 918 may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system.
  • the wireless device 902 may include one or more processor (s) 904.
  • the processor (s) 904 may execute instructions such that various operations of the wireless device 902 are performed, as described herein.
  • the processor (s) 904 may include one or more baseband processors implemented using, for example, a central processing unit (CPU) , a digital s ignal processor (DSP) , an application specific integrated circuit (ASIC) , a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
  • CPU central processing unit
  • DSP digital s ignal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the wireless device 902 may include a memory 906.
  • the memory 906 may be a non-transitory computer-readable storage medium that stores instructions 908 (which may include, for example, the instructions being executed by the processor (s) 904) .
  • the instructions 908 may also be referred to as program code or a computer program.
  • the memory 906 may also store data used by, and results computed by, the processor (s) 904.
  • the wireless device 902 may include one or more transceiver (s) 910 that may include radio frequency (RF) transmitter and/or receiver circuitry that use the antenna (s) 912 of the wireless device 902 to facilitate signaling (e.g., the signaling 932) to and/or from the wireless device 902 with other devices (e.g., the network device 918) according to corresponding RATs.
  • RF radio frequency
  • the wireless device 902 may include one or more antenna (s) 912 (e.g., one, two, four, or more) .
  • the wireless device 902 may leverage the spatial diversity of such multiple antenna (s) 912 to send and/or receive multiple different data streams on the same time and frequency resources.
  • This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and a receiving device that enable this aspect) .
  • MIMO multiple input multiple output
  • MIMO transmissions by the wireless device 902 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 902 that multiplexes the data streams across the antenna (s) 912 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream) .
  • Certain embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and/or multi user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain) .
  • SU-MIMO single user MIMO
  • MU-MIMO multi user MIMO
  • the wireless device 902 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna (s) 912 are relatively adjusted such that the (joint) transmission of the antenna (s) 912 can be directed (this is sometimes referred to as beam steering) .
  • the wireless device 902 may include one or more interface (s) 914.
  • the interface (s) 914 may be used to provide input to or output from the wireless device 902.
  • a wireless device 902 that is a UE may include interface (s) 914 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and/or output to the UE by a user of the UE.
  • Other interfaces of such a UE may be made up of made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver (s) 910/antenna (s) 912 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., and the like) .
  • the wireless device 902 may include a dedicated frequency priority configuration verification module 916.
  • the dedicated frequency priority configuration verification module 916 may be implemented via hardware, software, or combinations thereof.
  • the dedicated frequency priority configuration verification module 916 may be implemented as a processor, circuit, and/or instructions 908 stored in the memory 906 and executed by the processor (s) 904.
  • the dedicated frequency priority configuration verification module 916 may be integrated within the processor (s) 904 and/or the transceiver (s) 910.
  • the dedicated frequency priority configuration verification module 916 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor (s) 904 or the transceiver (s) 910.
  • the dedicated frequency priority configuration verification module 916 may be used for various aspects of the present disclosure, for example, aspects of FIG. 1 through FIG. 7.
  • the dedicated frequency priority configuration verification module 916 may be configured to determine whether to stop the use of dedicated frequency priority configuration (s) of corresponding slice groups, to determine whether to resume the use of a dedicated frequency priority configuration (s) of corresponding slice group (s) , and/or to determine whether to discard a dedicated frequency priority configuration (s) of corresponding slice group (s) , as described herein.
  • the network device 918 may include one or more processor (s) 920.
  • the processor (s) 920 may execute instructions such that various operations of the network device 918 are performed, as described herein.
  • the processor (s) 920 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
  • the network device 918 may include a memory 922.
  • the memory 922 may be a non-transitory computer-readable storage medium that stores instructions 924 (which may include, for example, the instructions being executed by the processor (s) 920) .
  • the instructions 924 may also be referred to as program code or a computer program.
  • the memory 922 may also store data used by, and results computed by, the processor (s) 920.
  • the network device 918 may include one or more transceiver (s) 926 that may include RF transmitter and/or receiver circuitry that use the antenna (s) 928 of the network device 918 to facilitate signaling (e.g., the signaling 932) to and/or from the network device 918 with other devices (e.g., the wireless device 902) according to corresponding RATs.
  • transceiver (s) 926 may include RF transmitter and/or receiver circuitry that use the antenna (s) 928 of the network device 918 to facilitate signaling (e.g., the signaling 932) to and/or from the network device 918 with other devices (e.g., the wireless device 902) according to corresponding RATs.
  • the network device 918 may include one or more antenna (s) 928 (e.g., one, two, four, or more) .
  • the network device 918 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.
  • the network device 918 may include one or more interface (s) 930.
  • the interface (s) 930 may be used to provide input to or output from the network device 918.
  • a network device 918 that is a base station may include interface (s) 930 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver (s) 926/antenna (s) 928 already described) that enables the base station to communicate with other equipment in a core network, and/or that enables the base station to communicate with external networks, computers, databases, and the like for purposes of operations, administration, and maintenance of the base station or other equipment operably connected thereto.
  • circuitry e.g., other than the transceiver (s) 926/antenna (s) 928 already described
  • At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth herein.
  • a baseband processor as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.
  • circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.
  • Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system.
  • a computer system may include one or more general-purpose or special-purpose computers (or other electronic devices) .
  • the computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and/or firmware.
  • personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users.
  • personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Landscapes

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

Abstract

Des systèmes et des procédés pour déterminer une utilisation d'une ou plusieurs configurations de priorité de fréquence dédiée pour un ou plusieurs groupes de tranches correspondants sont évoqués. Un cœur de réseau (CN) du système de communication sans fil peut configurer un équipement utilisateur (UE) avec une priorité de groupe de tranches. L'UE peut ensuite être pourvu d'une ou de plusieurs configurations de priorité de fréquence dédiées pour un ou plusieurs groupes de tranches correspondants par l'intermédiaire d'un bloc d'informations de système (SIB) et/ou d'un message de libération de gestion des ressources radio (RRC). L'UE peut être permettre de hiérarchiser des actions de mesure de fréquence (par exemple, selon des procédés de gestion de ressources radio [RRM] et/ou de resélection de cellule) sur la base de ces ensembles d'informations. Des circonstances relatives à un changement de zone de suivi (TA) au niveau de l'UE où un UE peut s'arrêter avantageusement à l'aide d'une ou de plusieurs des configurations de priorité de fréquence dédiée pour le ou les groupes de tranches correspondants (par exemple, avant leur expiration selon un temporisateur de validité) sont évoquées.
PCT/CN2022/091404 2022-05-07 2022-05-07 Gestion de ressources radio avec une fréquence dédiée tenant compte d'un ou de plusieurs identifiants de zone de suivi valides dans un découpage de réseau d'accès radio WO2023216019A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/091404 WO2023216019A1 (fr) 2022-05-07 2022-05-07 Gestion de ressources radio avec une fréquence dédiée tenant compte d'un ou de plusieurs identifiants de zone de suivi valides dans un découpage de réseau d'accès radio

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/091404 WO2023216019A1 (fr) 2022-05-07 2022-05-07 Gestion de ressources radio avec une fréquence dédiée tenant compte d'un ou de plusieurs identifiants de zone de suivi valides dans un découpage de réseau d'accès radio

Publications (1)

Publication Number Publication Date
WO2023216019A1 true WO2023216019A1 (fr) 2023-11-16

Family

ID=88729384

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/091404 WO2023216019A1 (fr) 2022-05-07 2022-05-07 Gestion de ressources radio avec une fréquence dédiée tenant compte d'un ou de plusieurs identifiants de zone de suivi valides dans un découpage de réseau d'accès radio

Country Status (1)

Country Link
WO (1) WO2023216019A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210037455A1 (en) * 2019-07-30 2021-02-04 Qualcomm Incorporated Mobility enhancement with network slicing
WO2022027166A1 (fr) * 2020-08-03 2022-02-10 Zte Corporation Schémas de configuration de cellule dans des communications sans fil
WO2022082628A1 (fr) * 2020-10-22 2022-04-28 Apple Inc. Améliorations de connectivité de réseau d'accès radio pour découpage en tranches de réseau

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210037455A1 (en) * 2019-07-30 2021-02-04 Qualcomm Incorporated Mobility enhancement with network slicing
WO2022027166A1 (fr) * 2020-08-03 2022-02-10 Zte Corporation Schémas de configuration de cellule dans des communications sans fil
WO2022082628A1 (fr) * 2020-10-22 2022-04-28 Apple Inc. Améliorations de connectivité de réseau d'accès radio pour découpage en tranches de réseau

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "On slice priority for cell reselection", 3GPP DRAFT; R2-2108316, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20210809 - 20210827, 5 August 2021 (2021-08-05), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052032545 *
SAMSUNG: "Remaining issues on slice priority for cell reselection", 3GPP TSG-RAN WG2 MEETING #116-E R2-2110522, 12 November 2021 (2021-11-12), XP052066968 *

Similar Documents

Publication Publication Date Title
US20230362787A1 (en) Apparatus and method in a radio communications network
WO2023216019A1 (fr) Gestion de ressources radio avec une fréquence dédiée tenant compte d'un ou de plusieurs identifiants de zone de suivi valides dans un découpage de réseau d'accès radio
WO2024026727A1 (fr) Amélioration de la sélection des cellules ntn et tn pour l'économie d'énergie
WO2023010468A1 (fr) Modes de fonctionnement permettant des améliorations associées à un train de transmission à vitesse élevée
KR102230149B1 (ko) 주파수 대역 결정 방법 및 그 장치
WO2024060189A1 (fr) Nouvelle conception de srb pour transmission de message rrc de groupe
WO2024007259A1 (fr) Réalisation d'opérations de mesure de couche 1 (l1) pour des porteuses de desserte sur la base d'une priorité attribuée à un groupe de porteuses parmi de multiples groupes de porteuses
WO2024031231A1 (fr) Procédure de transfert dans une communication sans fil
WO2023151032A1 (fr) Amélioration par assouplissement de rrm en mode edrx
US20240137819A1 (en) Cross layer optimization for selection of a best cell from conditional special cell change candidate cells
US20230319671A1 (en) Handover between terrestrial network and nonterrestrial network
WO2023130255A1 (fr) Gestion de ressources radio pour équipement utilisateur à capacité réduite
WO2024026821A1 (fr) Appareil et procédé de mesure de qoe
WO2023201622A1 (fr) Mise a jour de l'indicateur de configuration de transmission et commutation partielle de la bande passante pour les porteuses composantes multiples
WO2023010300A1 (fr) Systèmes et procédés pour indication de faisceau pour une mobilité intercellulaire centrique l1/l2
WO2023065307A1 (fr) Détection et mesure de cellule pour un équipement d'utilisateur à capacité réduite avec edrx en mode veille et inactif
WO2024092621A1 (fr) Amélioration apportée à la prise en charge de petit intervalle commandé par réseau (ncsg)
WO2024092643A1 (fr) Systèmes et procédés de systèmes de communication sans fil utilisant des modèles multicouches
WO2024020917A1 (fr) Procédés et systèmes de rapport de mesure de couche d'application par un équipement utilisateur fonctionnant dans un mode à double connectivité
WO2023230762A1 (fr) Capacités hybrides d'intervalle de mesure par équipement utilisateur et par plage de fréquences
WO2023230755A1 (fr) Réglage de longueur d'interruption visible spécifique à une plage de fréquences ou à une bande de fréquences pour petit espace commandé par réseau pour une mesure d'équipement utilisateur
WO2024092615A1 (fr) Amélioration de transfert conditionnel avec priorisation de cellules cibles candidates
US20240089837A1 (en) Capability based cell selection and cell reselection
WO2024060210A1 (fr) Configuration pour un intervalle pour un ue à capacité musim
WO2023230944A1 (fr) Mobilité accélérée basée sur une liste de priorités de fréquence dédiée

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

Country of ref document: EP

Kind code of ref document: A1