WO2023146453A1 - Journalisation d'ue et notification de propriétés de hsdn - Google Patents

Journalisation d'ue et notification de propriétés de hsdn Download PDF

Info

Publication number
WO2023146453A1
WO2023146453A1 PCT/SE2023/050052 SE2023050052W WO2023146453A1 WO 2023146453 A1 WO2023146453 A1 WO 2023146453A1 SE 2023050052 W SE2023050052 W SE 2023050052W WO 2023146453 A1 WO2023146453 A1 WO 2023146453A1
Authority
WO
WIPO (PCT)
Prior art keywords
wireless device
given time
time instance
speed
mobility state
Prior art date
Application number
PCT/SE2023/050052
Other languages
English (en)
Inventor
Mattias BERGSTRÖM
Pradeepa Ramachandra
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 WO2023146453A1 publication Critical patent/WO2023146453A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0083—Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
    • H04W36/00835—Determination of neighbour cell lists
    • H04W36/008357—Determination of target cell based on access point [AP] properties, e.g. AP service capabilities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H04W36/324—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data by mobility data, e.g. speed data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H04W64/006—Locating users or terminals or network equipment for network management purposes, e.g. mobility management with additional information processing, e.g. for direction or speed determination

Definitions

  • This document is generally directed to wireless communications and is more directly related to the configuration and use of high-speed-dedicated network cells in wireless communication networks.
  • the high speed dedicated network is a feature allowing an operator to define cells to be so- called high-speed cells, in comparison to normal cells (i.e., non-high-speed cells).
  • the feature also comprises that UEs will determine their speed.
  • a UE may consider itself to be a high-speed UE or a normal UE (i.e., a non-high-speed UE), depending on its mobility.
  • speed refers to the velocity of a moving UE.
  • high-speed dedicated network refers to features specifically designed and provided (“dedicated”) for UEs moving at high velocities, and the term should not be confused with other network features that use the term “high speed” to refer to high data rates (such as high-speed downlink packet access, or HSDPA).
  • a UE that considers itself to be a high-speed UE will give priority to high-speed cells in the sense that if the UE finds both a high-speed cell and a normal cell, the UE gives the high-speed cell the highest priority when selecting or reselecting cells.
  • a non-high-speed UE on the other hand, will give the highest priority to non-high-speed cells.
  • a high-speed UE that only finds normal cells would select those normal speed cells, as there is no other option available for the UE.
  • This feature could be used in a high-speed train scenario, for example, where there are network cells deployed along a train track, meant to provide an increased capacity for UEs traveling in the trains.
  • the feature ensures that potential non-high-speed UEs (e.g., one carried a person walking along the train tracks), would not select the cells if there are non-high-speed cells that can be selected.
  • the feature has been implemented in the LTE and NR specifications, where the network can configure the UEs in the cell to operate in a mode that is more suitable if the UEs are traveling at high speed.
  • These features include, for example, the high-speed measurement feature and high-speed demodulation feature as configured by these parameters in 3GPP TS 38.331 version 16.6.0:
  • HighSpeedConfig-r16 SEQUENCE ⁇ highSpeedMeasFlag-r16 ENUMERATED ⁇ true ⁇ OPTIONAL, - Need R highSpeedDemodFlag-r16 ENUMERATED ⁇ true ⁇ OPTIONAL, - Need R
  • a HSDN cell can configure the UE with additional parameters that can aid the UE to classify itself as a high-speed UE, so that the cell reselection parameters can take this into account.
  • An HSDN cell can broadcast a ‘cellEquivalentSize’ parameter, which indicates the number of equivalent cells that the UE can count for its stay in the current cell.
  • CellReselectionlnfoHSDN-r15 SEQUENCE ⁇ cellEquivalentSize-r15 INTEGER(2..16)
  • the UE Based on this broadcasted parameter, the UE performs mobility state-based cell reselection as captured in 3GPP TS 36.304 v16.5.0:
  • a High-mobility and a Medium-mobility state are applicable if the parameters (TcRmax, NCR_H, NCR_M, TcRmaxHyst and cellEquivalentSize) are sent in the system information broadcast of the serving cell.
  • the UE shall not count consecutive reselections between same two cells into mobility state detection criteria if same cell is reselected just after one other reselection. If the UE is capable of HSDN and the cellEquivalentSize is configured, the UE counts the number of cell reselections for this cell as cellEquivalentSize configured for this cell.
  • Absolute priorities of different E-UTRAN frequencies or inter-RAT frequencies may be provided to the UE in the system information, in the RRCConnectionRelease or RRCEarlyDataComplete message, or by inheriting from another RAT at inter-RAT cell (re)selection.
  • an E- UTRAN frequency or inter-RAT frequency may be listed without providing a priority (i.e. the field cellReselectionPriority is absent for that frequency).
  • the UE shall ignore all the priorities provided in system information. If UE is in camped on any cell state, UE shall only apply the priorities (i.e.
  • the UE preserves priorities provided by dedicated signalling, deprioritisationReq received in RRCConnectionReject and altFreqPriorities provided by dedicated signalling unless specified otherwise.
  • the UE shall consider the current frequency to be the lowest priority frequency (i.e. lower than any of the network configured values).
  • the UE While the UE is camped on a suitable CSG cell in normal coverage, the UE shall always consider the current frequency to be the highest priority frequency (i.e. higher than any of the network configured values), irrespective of any other priority value allocated to this frequency.
  • the UE When the HSDN capable UE is in High-mobility state, the UE shall always consider the HSDN cells to be the highest priority (i.e. higher than any other network configured priorities). When the HSDN capable UE is not in High- mobility state, the UE shall always consider HSDN cells to be the lowest priority (i.e. lower than network configured priorities). If the UE capable of sidelink communication is configured to perform sidelink communication and can only perform the sidelink communication while camping on a frequency, the UE may consider that frequency to be the highest priority. If the UE capable of V2X sidelink communication is configured to perform V2X sidelink communication and can only perform the V2X sidelink communication while camping on a frequency, the UE may consider that frequency to be the highest priority.
  • the UE capable of V2X sidelink communication is configured to perform V2X sidelink communication and can only use pre-configuration while not camping on a frequency
  • the UE may consider the frequency providing inter-carrier V2X sidelink configuration to be the highest priority. If the UE is configured to perform both V2X sidelink communication and NR sidelink communication, the UE may consider the frequency providing both V2X sidelink communication and NR sidelink communication configuration to be the highest priority. If the UE is configured to perform V2X sidelink communication and not perform NR sidelink communication, the UE may consider the frequency providing V2X sidelink communication configuration to be the highest priority.
  • the UE may consider the frequency providing NR sidelink communication configuration to be the highest priority. If the UE capable of sidelink discovery is configured to perform Public Safety related sidelink discovery and can only perform the Public Safety related sidelink discovery while camping on a frequency, the UE may consider that frequency to be the highest priority.
  • a HSDN- capable UE that is connected to a HSDN cell properly classifies itself as a high-mobility state UE.
  • the HSDN capable UE always prioritizes HSDN cells for cell reselection.
  • the HSDN specific cell reselection parameters e.g., cellEquivalentSize
  • This disclosure also describes some explicit configurations from the network side to request the UEs to collect HSDN-specific information described herein, and still further includes some additional dedicated configurations (UE specific configurations) to indicate the HSDN-specific parameters and/or mobility state parameters.
  • UE specific configurations UE specific configurations
  • An example method described herein is implemented in/by a wireless device operating in a wireless network, where the wireless device is capable of selectively operating in a high-speed state, such that it prioritizes cells designated as high-speed cells for selection or reselection, when available.
  • the example method comprises the step of logging information indicating, for a given time instance, one or more selected from the following: whether the wireless device has classified itself in a highspeed mobility state; one or more high-speed cell operation parameters for a cell in which the wireless device is camping or to which the wireless device is connected, at the given time instance; one or more mobility state classification parameters applicable to the wireless device at the given time instance; cell reselection statistics and/or handover statistics for the wireless device for a predetermined time interval preceding the given time instance; and an indication of whether the wireless device was in connected mode at the given time instance.
  • Another example method described herein is implemented in/by a network node operating in or in association with a wireless network, and complements the method summarized above.
  • This example method comprises the step of receiving a report from each of a plurality of wireless devices operating in the wireless network, where each report comprises, for each of one or more given time instances, one or more of any one of: whether the wireless device has classified itself in a high-speed mobility state; one or more high-speed cell operation parameters for a cell in which the wireless device is camping or to which the wireless device is connected, at the given time instance; one or more mobility state classification parameters applicable to the wireless device at the given time instance; cell reselection statistics and/or handover statistics for the wireless device for a predetermined time interval preceding the given time instance; and an indication of whether the wireless device was in connected mode at the given time instance.
  • This example method further comprises modifying one or more operational parameters in the wireless network, based on the reports.
  • the network can collect information about the optimality of the configured HSDN parameters and the network can tune these parameters accordingly.
  • Figure 1 is a process flow diagram illustrating an example method in a wireless device.
  • Figure 2 is a process flow diagram illustrating an example method in a network node.
  • Figure 3 shows an example of a communication system in accordance with some embodiments.
  • Figure 4 shows a wireless device in accordance with some embodiments.
  • Figure 5 shows a network node in accordance with some embodiments.
  • Figure 6 is a block diagram of a host.
  • Figure 7 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.
  • Figure 8 shows a communication diagram of a host communicating via a network node with a wireless device over a partially wireless connection in accordance with some embodiments.
  • high-speed cell will herein be used to refer cells that are indicated to be cells which UEs moving at high speed shall prioritize selecting or re-selecting.
  • highspeed UE will herein be used to refer to UEs that are moving in such a manner that they enter a state wherein it should prioritize high-speed cells for selection or re-selection.
  • high-speed features refers to features that the UE can apply which ensures that the communication between the UE and network is more reliable in scenarios when the UE is moving at a high speed (relative to the network node). These features may put stricter requirements on the UE and may waste the power of the UE, in some cases, thus, it will be generally expected that it is desirable for a UE to avoid using these features except when actually in a high-speed state.
  • the term “speed” as used herein refers to the velocity of a moving UE.
  • the term “high-speed dedicated network” refers to features specifically designed and provided (“dedicated”) for UEs moving at high velocities, and the term should not be confused with other network features that use the term “high speed” to refer to high data rates (such as high-speed downlink packet access, or HSDPA).
  • HSDPA high-speed downlink packet access
  • this disclosure may refer to a UE that “is capable of HSDN” - this refers to a UE that is configured (whether through programming alone or through programming plus activation of the feature by network signaling, for example) to classify itself as high-speed or not, according to the HSDN features described herein.
  • both UE1 and UE2 are HSDN-capable, and are thus required to count reselection to the current cell, which identifies itself as a high-speed cell, according to the cellEquivalentSize parameter.
  • UE1 is not in the high-speed train but UE2 is.
  • scenario 1 and scenario 2 both UE1 and UE2 would be classified as highspeed UEs, which is incorrect.
  • the UEs in scenario 3 will properly classify themselves, but scenario 4 would again end up with both UEs classifying themselves as high-speed UEs and both of them would end up prioritizing the HSDN frequencies/cells from here on.
  • the above table shows the sensitivity of the cellEquivalentSize and mobilityStateParameters (n- CellChangeHigh and t-Evaluation) parameters, along with the past UE mobility history. Thus, there need to be mechanisms to optimize these parameters’ configurations.
  • a HSDN-capable UE logs and reports one or more of the following parameters, in various embodiments:
  • the HSDN-capable UE determines whether it is classified as a high-mobility state UE or not. In some embodiments of the techniques described herein, the outcome of this determination is logged by the UE in a report and this report is later sent to the network node. In some embodiments, the UE logs a one-bit flag, where, for example, if the flag is set to TRUE then it indicates that the UE was classified as a high-mobility state UE and if the flag is set to FALSE then it indicates that the UE was classified in either medium-mobility state or a low-mobility state.
  • the UE logs the actual outcome of the classification of the mobility state i.e., the UE sets a field to HighMobilityState if the UE was classified as a high-mobility state, the UE sets a field to MediumMobilityState if the UE was classified as a medium-mobility state and the UE sets a field to LowMobilityState if the UE was classified as a low-mobility state.
  • the classification of mobility state is performed based on the method specified in section 5.2.4.3 of 3GPP TS 36.304 v16.5.0.
  • the UE logs the cellEquivalentSize parameter in a report and this report is later sent to the network node. This may be logged (and subsequently reported) on a per cell basis.
  • An idle or inactive UE finds this parameter in the broadcasted system information, specifically in SystemlnformationBlockType3 in 3GPP TS 36.331 v 16.7.0.
  • a connected UE might find this parameter either from the broadcasted information or this information can be delivered to the UE as part of the dedicated configuration.
  • RRCConnectionReconfiguration message might include the cellEquivalentSize parameter and a UE upon receiving this information, logs this information in a report.
  • a UE in idle/inactive state includes the mobility state parameters as broadcasted in SystemlnformationBlockType3, in a report, and this report is later sent to the network node.
  • “idle/inactive state” here refers to an RRC state other than RRC connected state, in the context of operation in a 3GPP network.
  • the included parameters may comprise one or more of the following:
  • n-CellChangeMedium The number of cell changes to enter medium mobility state - from SystemlnformationBlockType3 in 3GPP TS 36.331 v16.7.0
  • a UE in RRC Connected state includes the mobility state parameters as provided in a dedicated message like RRCConnectionReconfiguration (measConfig IE), in a report, and this report is later sent to the network node.
  • the included parameters may comprise one or more of the following:
  • n-CellChangeMedium The number of cell changes to enter medium mobility state - from measConfig in 3GPP TS 36.331 v16.7.0
  • n-CellChangeHigh The number of cell changes to enter high mobility state - from measConfig in 3GPP TS 36.331 v16.7.0.
  • the NR specifications (specifications for the 5 th -generation 3GPP network widely referred to as “NR”) might include these mobility state parameters in a different RRC message for the dedicated delivery to the UE.
  • the UE includes the number of cell reselections that it has performed in the last ‘X’ seconds in a report, and this report is later sent to the network node.
  • the UE identifies the value of ‘X’ based on the value of t-Evaluation, i.e., the UE uses the same value.
  • the value of ‘X’ is explicitly hardcoded in the specification.
  • the UE may include a flag indicating whether the UE was in connected mode in the cell (e.g., an HSDN cell), in a report, and this report is later sent to the network node. Based on this information, the network node may be able to determine whether the RRC state has had any effect on the mobility state classification.
  • the cell e.g., an HSDN cell
  • the UE includes an indication indicating whether the UE entered this HSDN cell via handover or via cell reselection. This is useful information, as this cell change would not be part of the mobility state estimation as per the current specification. Based on the current specification (3GPP TS 36.304 v 16.5.0), a UE uses only the past cell reselections in the computation of the mobility state estimation:
  • the UE may include the number of handovers that the UE has performed in the last ‘X’ seconds, in a report, and this report is later sent to the network node.
  • the UE identifies the value of ‘X’ based on the value of t-Evaluation, i.e., the UE uses the same value.
  • the value of ‘X’ is explicitly hardcoded in the specification.
  • a HSDN UE that is configured with a Minimization of Drive Time (MDT) configuration shall always perform the logging of measurements according to any of the various techniques discussed above.
  • a HSDN UE that is configured with an MDT configuration with a flag or flags indicating the UE to log one or more of the measurements discussed above shall perform the corresponding logging.
  • a HSDN UE shall include one or more parameters mentioned above in the mobility history information.
  • a HSDN UE that has information associated to one or more of the measurements described above may transmit an indication to the network node indicating the availability of such HSDN specific measurements. In some embodiments, this indication could be specific to any one of the measurements discussed above, individually. In some other embodiments, there could be a single indication for a group of measurements.
  • the network node Upon receiving such an indication, the network node might request the UE to transmit the stored measurements and upon receiving such a request, the UE starts transmitting the stored report.
  • the UE appends the information as part of the logged MDT reporting and thus reporting of such information follows the same method as that of reporting logged MDT reports. In some embodiments, the UE appends the information as part of the mobility history reporting and thus reporting of such information follows the same method as that of reporting mobility history reports.
  • the network can optimize the configuration of the HSDN specific parameter configuration and/or the configuration of the mobility state parameter configurations.
  • Figure 1 illustrates an example method, as implemented by a wireless device operating in a wireless device.
  • wireless device may be considered a generalization of “UE,” the method illustrated here is a generalization of several of the techniques described above and should be understand as encompassing those techniques.
  • the terms used in connection with Figure 1 should be understood as generalizations or synonyms of the terms used in describing the detailed examples above.
  • the term “wireless device” is a generalization of the 3GPP-specific term “UE.”
  • variations and modifications described in connection with the examples above are applicable to the method shown in Figure 1 , even if those variations are not explicitly discussed below.
  • the wireless device carrying out the method shown in Figure 1 is capable of selectively operating in a high-speed state, such that it prioritizes cells designated as high-speed cells for selection or reselection, when available.
  • “capable of” is meant that the wireless device is designed and implemented with support for those features, such that it may operate in the high-speed operational state described herein.
  • Some embodiments may require that the network “configure” the wireless device to operate in such a state, e.g., by sending a flag or other indication in configuration information or broadcast information received by the device.
  • the method comprises the step of logging information regarding high-speed operation, where this information comprises information indicating, for a given time instance, one or more selected from the following: whether the wireless device has classified itself in a high-speed mobility state; one or more high-speed cell operation parameters for a cell in which the wireless device is camping or to which the wireless device is connected, at the given time instance; one or more mobility state classification parameters applicable to the wireless device at the given time instance; cell reselection statistics and/or handover statistics for the wireless device for a predetermined time interval preceding the given time instance; and an indication of whether the wireless device was in connected mode at the given time instance.
  • This logging may be selectively performed, responsive to receiving some indication that such logging should be performed.
  • the method may further comprises receiving, from the wireless network, configuration information indicating that the wireless device is to log said information, where the logging information is responsive to receiving this configuration information.
  • This might be an HSDNFlag, for example. This is shown at block 110 in Figure 1 , which is illustrated with a dashed outline to indicate that it may not be present in all embodiments or instances of the illustrated method.
  • the logging comprises logging a binary indication of whether the wireless device has classified itself in the high-speed mobility state.
  • the logging may comprise logging an indicator of which, of at least three mobility states including the high-speed mobility state, the wireless device was classified at the given time instance.
  • the logging may comprise logging the value of a cellEquivalentSize parameter applicable to the wireless device at the given time instance. In some of these and in some other embodiments or instances, the logging comprises logging the value of each of any one or more of the following mobility state classification parameters: t-Evaluation t- HystNormal n-CellChangeMedium n-CellChangeHigh. Various embodiments may log equivalents to these 3GPP parameters, in other systems.
  • the logging may comprise logging an indication of the difference between (a) the number of reselections or equivalent reselections for the wireless device in a predetermined time interval preceding the given time instance and (b) a number of reselections or equivalent reselections necessary for a mobility state classification of high-speed mobility state.
  • the logging may comprise logging the information to a mobility history information log. In some of these or in other embodiments or instances, the logging may comprise logging the information to a Minimization of Drive Time (MDT) log.
  • MDT Minimization of Drive Time
  • the logging is performed (further) in response to the wireless device calculating its mobility state classification. In some embodiments or instances, the logging is in response to determining that a triggering event has occurred, the triggering event comprising any one of: a radio link failure; a handover failure; a random access procedure; a connection establishment failure; a failure in a secondary cell group leg; and a request from the wireless network. In some of these embodiments or instances, the logging may comprise logging an indication of the triggering event.
  • the method may further comprise reporting the logged information to the wireless network. This is shown at block 140 in Figure 1 . In some embodiments, this reporting may be in response to a request received from the wireless network - the receipt of such a request is shown in Figure 1 as block 135. In some embodiments, this request is in turn responsive to an indication that the information is available. Thus, as shown at block 130, the method may comprise sending an indication of the availability of logged information, where the request received from the wireless network is responsive to said indication.
  • Figure 2 illustrates another example method, this one as implemented by a network node operating in or associated with a wireless network. Again, this method is a generalization of several of the techniques described above and should be understand as encompassing those techniques. So, wherever there are differences in terminology, the terms used in connection with Figure 2 should be understood as generalizations or synonyms of the terms used in describing the detailed examples above. Furthermore, variations and modifications described in connection with the examples above are applicable to the method shown in Figure 2, even if those variations are not explicitly discussed below.
  • the method illustrated in Figure 2 comprises receiving a report from each of a plurality of wireless devices operating in the wireless network.
  • Each of these reports comprises, for each of one or more time instances, one or more of any one of: whether the wireless device has classified itself in a high-speed mobility state; one or more high-speed cell operation parameters for a cell in which the wireless device is camping or to which the wireless device is connected, at the given time instance; one or more mobility state classification parameters applicable to the wireless device at the given time instance; cell reselection statistics and/or handover statistics for the wireless device for a predetermined time interval preceding the given time instance; and an indication of whether the wireless device was in connected mode at the given time instance.
  • the method further comprises modifying one or more operational parameters in the wireless network, based on the reports, as shown at block 220.
  • modifying one or more operational parameters may comprise the value of one or more of any of the following parameters, for a given cell: cellEquivalentSize t-Evaluation t-HystNormal n-CellChangeMedium and n-CellChangeHigh.
  • FIG. 3 shows an example of a communication system 300 in accordance with some embodiments.
  • the techniques described above may be implemented in such a communication system, in various embodiments.
  • the communication system 300 includes a telecommunication network 302 that includes an access network 304, such as a radio access network (RAN), and a core network 306, which includes one or more core network nodes 308.
  • the access network 304 includes one or more access network nodes, such as network nodes 310a and 310b (one or more of which may be generally referred to as network nodes 310), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3rd Generation Partnership Project
  • the network nodes 310 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 312a, 312b, 312c, and 312d (one or more of which may be generally referred to as UEs 312) to the core network 306 over one or more wireless connections.
  • UE user equipment
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 300 may include any number of wired or wireless networks, network nodes, UEs, 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.
  • the communication system 300 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 312 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 310 and other communication devices.
  • the network nodes 310 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 312 and/or with other network nodes or equipment in the telecommunication network 302 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 302.
  • the core network 306 connects the network nodes 310 to one or more hosts, such as host 316. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 306 includes one more core network nodes (e.g., core network node 308) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 308.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 316 may be under the ownership or control of a service provider other than an operator or provider of the access network 304 and/or the telecommunication network 302 and may be operated by the service provider or on behalf of the service provider.
  • the host 316 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 300 of Figure 3 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 3G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the telecommunication network 302 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 302 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 302. For example, the telecommunications network 302 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • the UEs 312 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 304.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e., being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).
  • MR-DC multi-radio dual connectivity
  • the hub 314 communicates with the access network 304 to facilitate indirect communication between one or more UEs (e.g., UE 312c and/or 312d) and network nodes (e.g., network node 310b).
  • the hub 314 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 314 may be a broadband router enabling access to the core network 306 for the UEs.
  • the hub 314 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 314 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 314 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 314 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 314 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 314 may have a constant/persistent or intermittent connection to the network node 310b.
  • the hub 314 may also allow for a different communication scheme and/or schedule between the hub 314 and UEs (e.g., UE 312c and/or 312d), and between the hub 314 and the core network 306.
  • the hub 314 is connected to the core network 306 and/or one or more UEs via a wired connection.
  • the hub 314 may be configured to connect to an M2M service provider over the access network 304 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 310 while still connected via the hub 314 via a wired or wireless connection.
  • the hub 314 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 310b.
  • the hub 314 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 310b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs, and may thus be referred to as a “wireless device.”
  • Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptopmounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehiclemounted or vehicle embedded/integrated wireless device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • gaming console or device gaming console or device
  • music storage device playback appliance
  • wearable terminal device wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptopmounted equipment (LME), smart device, wireless customer-premise equipment (
  • UEs identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-loT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to- vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to- vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a 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,
  • the UE 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input/output interface 406, a power source 408, a memory 410, a communication interface 412, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 4. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 402 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine- readable computer programs in the memory 410.
  • the processing circuitry 402 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 402 may include multiple central processing units (CPUs).
  • the input/output interface 406 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include 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.
  • An input device may allow a user to capture information into the UE 400.
  • Examples of an input device 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, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • USB Universal Serial Bus
  • the power source 408 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 408 may further include power circuitry for delivering power from the power source 408 itself, and/or an external power source, to the various parts of the UE 400 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 408.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 408 to make the power suitable for the respective components of the UE 400 to which power is supplied.
  • the memory 410 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 410 includes one or more application programs 414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 416.
  • the memory 410 may store, for use by the UE 400, any of a variety of various operating systems or combinations of operating systems.
  • the memory 410 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, 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 external mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • the memory 410 may allow the UE 400 to access instructions, application programs and 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 as or in the memory 410, which may be or comprise a device-readable storage medium.
  • the processing circuitry 402 may be configured to communicate with an access network or other network using the communication interface 412.
  • the communication interface 412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 422.
  • the communication interface 412 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 418 and/or a receiver 420 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 418 and receiver 420 may be coupled to one or more antennas (e.g., antenna 422) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 412 may include cellular communication, Wi-Fi communication, LPWAN communication, 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.
  • GPS global positioning system
  • Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR New Radio
  • UMTS Worldwide Interoperability for Microwave Access
  • WiMax Ethernet
  • TCP/IP transmission control protocol/internet protocol
  • SONET synchronous optical networking
  • ATM Asynchronous Transfer Mode
  • QUIC Hypertext Transfer Protocol
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 412, via a wireless connection to a network node.
  • Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected, an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare.
  • loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-t
  • AR Augmented
  • a UE 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 UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3GPP NB-loT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.
  • FIG. 5 shows a network node 500 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • Node Bs Node Bs
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may 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 remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • 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 multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, SelfOrganizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • OFDM Operation and Maintenance
  • OSS Operations Support System
  • SON SelfOrganizing Network
  • positioning nodes e.g., Evolved Serving Mobile Location Centers (E-SMLCs)
  • the network node 500 includes a processing circuitry 502, a memory 504, a communication interface 506, and a power source 508.
  • the network node 500 may be composed of multiple physically separate components (e.g., a NodeB 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 500 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 NodeBs.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • the network node 500 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components may be duplicated (e.g., separate memory 504 for different RATs) and some components may be reused (e.g., a same antenna 510 may be shared by different RATs).
  • the network node 500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 500, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 500.
  • RFID Radio Frequency Identification
  • the processing circuitry 502 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, 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 500 components, such as the memory 504, to provide network node 500 functionality.
  • the processing circuitry 502 includes a system on a chip (SOC). In some embodiments, the processing circuitry 502 includes one or more of radio frequency (RF) transceiver circuitry 512 and baseband processing circuitry 514. In some embodiments, the radio frequency (RF) transceiver circuitry 512 and the baseband processing circuitry 514 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 512 and baseband processing circuitry 514 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 502 includes one or more of radio frequency (RF) transceiver circuitry 512 and baseband processing circuitry 514.
  • the radio frequency (RF) transceiver circuitry 512 and the baseband processing circuitry 514 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of
  • the memory 504 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, random access memory (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 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 502.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (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 non-
  • the memory 504 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 502 and utilized by the network node 500.
  • the memory 504 may be used to store any calculations made by the processing circuitry 502 and/or any data received via the communication interface 506.
  • the processing circuitry 502 and memory 504 is integrated.
  • the communication interface 506 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 506 comprises port(s)/terminal(s) 516 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 506 also includes radio front-end circuitry 518 that may be coupled to, or in certain embodiments a part of, the antenna 510. Radio front-end circuitry 518 comprises filters 520 and amplifiers 522. The radio front-end circuitry 518 may be connected to an antenna 510 and processing circuitry 502. The radio front-end circuitry may be configured to condition signals communicated between antenna 510 and processing circuitry 502.
  • the radio front-end circuitry 518 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 518 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 520 and/or amplifiers 522.
  • the radio signal may then be transmitted via the antenna 510.
  • the antenna 510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 518.
  • the digital data may be passed to the processing circuitry 502.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 500 does not include separate radio front-end circuitry 518, instead, the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510.
  • the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510.
  • all or some of the RF transceiver circuitry 512 is part of the communication interface 506.
  • the communication interface 506 includes one or more ports or terminals 516, the radio front-end circuitry 518, and the RF transceiver circuitry 512, as part of a radio unit (not shown), and the communication interface 506 communicates with the baseband processing circuitry 514, which is part of a digital unit (not shown).
  • the antenna 510 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 510 may be coupled to the radio front-end circuitry 518 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 510 is separate from the network node 500 and connectable to the network node 500 through an interface or port.
  • the antenna 510, communication interface 506, and/or the processing circuitry 502 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 510, the communication interface 506, and/or the processing circuitry 502 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.
  • the power source 508 provides power to the various components of network node 500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 508 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 500 with power for performing the functionality described herein.
  • the network node 500 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 508.
  • the power source 508 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry.
  • the battery may provide backup power should the external power source fail.
  • Embodiments of the network node 500 may include additional components beyond those shown in Figure 5 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 500 may include user interface equipment to allow input of information into the network node 500 and to allow output of information from the network node 500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 500.
  • FIG 6 is a block diagram of a host 600, which may be an embodiment of the host 316 of Figure 3, in accordance with various aspects described herein.
  • the host 600 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 600 may provide one or more services to one or more UEs.
  • the host 600 includes processing circuitry 602 that is operatively coupled via a bus 604 to an input/output interface 606, a network interface 608, a power source 610, and a memory 612.
  • processing circuitry 602 that is operatively coupled via a bus 604 to an input/output interface 606, a network interface 608, a power source 610, and a memory 612.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 4 and 5, such that the descriptions thereof are generally applicable to the corresponding components of host 600.
  • the memory 612 may include one or more computer programs including one or more host application programs 614 and data 616, which may include user data, e.g., data generated by a UE for the host 600 or data generated by the host 600 for a UE.
  • Embodiments of the host 600 may utilize only a subset or all of the components shown.
  • the host application programs 614 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems).
  • the host application programs 614 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network.
  • the host 600 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 614 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG- DASH), etc.
  • HLS HTTP Live Streaming
  • RTMP Real-Time Messaging Protocol
  • RTSP Real-Time Streaming Protocol
  • MPEG- DASH Dynamic Adaptive Streaming over HTTP
  • FIG. 7 is a block diagram illustrating a virtualization environment 700 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 any device described herein, 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.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 700 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • Applications 702 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 704 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 706 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 708a and 708b (one or more of which may be generally referred to as VMs 708), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 706 may present a virtual operating platform that appears like networking hardware to the VMs 708.
  • the VMs 708 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 706.
  • Different embodiments of the instance of a virtual appliance 702 may be implemented on one or more of VMs 708, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • NFV network function virtualization
  • a VM 708 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 VMs 708, and that part of hardware 704 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 708 on top of the hardware 704 and corresponds to the application 702.
  • Hardware 704 may be implemented in a standalone network node with generic or specific components. Hardware 704 may implement some functions via virtualization. Alternatively, hardware 704 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 management and orchestration 710, which, among others, oversees lifecycle management of applications 702.
  • hardware 704 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes 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 provided with the use of a control system 712 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 8 shows a communication diagram of a host 802 communicating via a network node 804 with a UE 806 over a partially wireless connection in accordance with some embodiments.
  • host 802 Like host 600, embodiments of host 802 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 802 also includes software, which is stored in or accessible by the host 802 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 806 connecting via an over-the-top (OTT) connection 850 extending between the UE 806 and host 802.
  • OTT over-the-top
  • the network node 804 includes hardware enabling it to communicate with the host 802 and UE 806.
  • the connection 860 may be direct or pass through a core network (like core network 306 of Figure 3) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • a core network like core network 306 of Figure 3
  • an intermediate network may be a backbone network or the Internet.
  • the UE 806 includes hardware and software, which is stored in or accessible by UE 806 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 806 with the support of the host 802.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 806 with the support of the host 802.
  • an executing host application may communicate with the executing client application via the OTT connection 850 terminating at the UE 806 and host 802.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 850 may transfer both the request data and the user data.
  • the UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 850.
  • the OTT connection 850 may extend via a connection 860 between the host 802 and the network node 804 and via a wireless connection 870 between the network node 804 and the UE 806 to provide the connection between the host 802 and the UE 806.
  • the connection 860 and wireless connection 870, over which the OTT connection 850 may be provided, have been drawn abstractly to illustrate the communication between the host 802 and the UE 806 via the network node 804, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 802 provides user data, which may be performed by executing a host application.
  • the user data is associated with a particular human user interacting with the UE 806.
  • the user data is associated with a UE 806 that shares data with the host 802 without explicit human interaction.
  • the host 802 initiates a transmission carrying the user data towards the UE 806.
  • the host 802 may initiate the transmission responsive to a request transmitted by the UE 806.
  • the request may be caused by human interaction with the UE 806 or by operation of the client application executing on the UE 806.
  • the transmission may pass via the network node 804, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 812, the network node 804 transmits to the UE 806 the user data that was carried in the transmission that the host 802 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 814, the UE 806 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 806 associated with the host application executed by the host 802.
  • the UE 806 executes a client application which provides user data to the host 802.
  • the user data may be provided in reaction or response to the data received from the host 802.
  • the UE 806 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 806. Regardless of the specific manner in which the user data was provided, the UE 806 initiates, in step 818, transmission of the user data towards the host 802 via the network node 804.
  • the network node 804 receives user data from the UE 806 and initiates transmission of the received user data towards the host 802.
  • the host 802 receives the user data carried in the transmission initiated by the UE 806.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 806 using the OTT connection 850, in which the wireless connection 870 forms the last segment. More precisely, the techniques described herein can be used to ensure that UE 806 properly prioritizes high-speed cells or non-high-speed cells under various circumstances, thus allowing the network to provide appropriate capacity for high-speed UEs, reducing dropped connections and over-crowded cells, thereby improving data rate and latency and providing benefits such as reduced user waiting time.
  • factory status information may be collected and analyzed by the host 802.
  • the host 802 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 802 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 802 may store surveillance video uploaded by a UE.
  • the host 802 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs.
  • the host 802 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 802 and/or UE 806.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 850 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 850 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 804. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 802.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 850 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information 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 circuitry may process information 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.
  • computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.
  • Embodiments of the techniques, apparatuses, and systems described herein include, but are not limited to, the following enumerated examples.
  • the method comprises receiving, from the wireless network, configuration information indicating that the wireless device is to log said information, wherein said logging information is responsive to receiving said configuration information.
  • logging comprises logging an indication of the difference between (a) the number of reselections or equivalent reselections for the wireless device in a predetermined time interval preceding the given time instance and (b) a number of reselections or equivalent reselections necessary for a mobility state classification of high-speed mobility state.
  • a wireless device comprising transceiver circuitry configured to communicate with a wireless network and processing circuitry operatively coupled to the transceiver circuitry, wherein the processing circuitry is configured to carry out a method according to any one of example embodiments 1-15.
  • a wireless device adapted to carry out a method according to any one of example embodiments 1-15.
  • a method in a network node operating in or in association with a wireless network comprising: receiving a report from each of a plurality of wireless devices operating in the wireless network, each report comprising, for each of one or more given time instances, one or more of any one of: whether the wireless device has classified itself in a high-speed mobility state; one or more high-speed cell operation parameters for a cell in which the wireless device is camping or to which the wireless device is connected, at the given time instance; one or more mobility state classification parameters applicable to the wireless device at the given time instance; cell reselection statistics and/or handover statistics for the wireless device for a predetermined time interval preceding the given time instance; and an indication of whether the wireless device was in connected mode at the given time instance; and modifying one or more operational parameters in the wireless network, based on the reports.
  • modifying comprises modifying the value of one or more of any of the following parameters, for a given cell: cellEquivalentSize t-Evaluation t-HystNormal n-CellChangeMedium and n-CellChangeHigh.
  • a network node comprising interface circuitry configured to communicate with one or more other nodes of a wireless network and/or configured to communicate with one or more wireless devices served by the network node and further comprising processing circuitry operatively coupled to the interface circuitry, wherein the processing circuitry is configured to carry out a method according to example embodiment 18 or 19.
  • a network node adapted to carry out a method according to example embodiment 18 or 19.

Landscapes

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

Abstract

La présente invention concerne des techniques d'amélioration du fonctionnement dans des scénarios à haute mobilité comprenant un procédé mis en œuvre dans/par un dispositif sans fil capable de fonctionner sélectivement dans un état à grande vitesse de sorte qu'il donne la priorité à des cellules désignées en tant que cellules à grande vitesse pour une sélection ou une resélection, lorsqu'elles sont disponibles. Le procédé comprend la journalisation (120) d'informations indiquant, pour une instance de temps donnée, un ou plusieurs éléments parmi les suivants : si le dispositif sans fil s'est classé lui-même dans un état de mobilité à grande vitesse ; un ou plusieurs paramètres de fonctionnement de cellule à grande vitesse pour une cellule dans laquelle le dispositif sans fil est en attente ou à laquelle le dispositif sans fil est connecté, à l'instance de temps donnée ; un ou plusieurs paramètres de classification d'état de mobilité applicables au dispositif sans fil à l'instance de temps donnée ; des statistiques de resélection de cellule et/ou des statistiques de transfert pour le dispositif sans fil pendant un intervalle de temps prédéterminé précédant l'instance de temps donnée ; et une indication du fait que le dispositif sans fil était en mode connecté ou non à l'instance de temps donnée.
PCT/SE2023/050052 2022-01-31 2023-01-20 Journalisation d'ue et notification de propriétés de hsdn WO2023146453A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263304853P 2022-01-31 2022-01-31
US63/304,853 2022-01-31

Publications (1)

Publication Number Publication Date
WO2023146453A1 true WO2023146453A1 (fr) 2023-08-03

Family

ID=87472377

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050052 WO2023146453A1 (fr) 2022-01-31 2023-01-20 Journalisation d'ue et notification de propriétés de hsdn

Country Status (1)

Country Link
WO (1) WO2023146453A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015063371A1 (fr) * 2013-11-01 2015-05-07 Nokia Technologies Oy Signalisation de mobilité et estimation d'un état de mobilité
WO2019148313A1 (fr) * 2018-01-30 2019-08-08 北京小米移动软件有限公司 Procédé de gestion de réseau, dispositif, système et support de stockage lisible par ordinateur
US20210099942A1 (en) * 2019-09-26 2021-04-01 Samsung Electronics Co., Ltd. Context-specific customization of handover parameters using characterization of a device's radio environment
US11102694B2 (en) * 2017-03-03 2021-08-24 Apple Inc. High speed train in new radio (NR)

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015063371A1 (fr) * 2013-11-01 2015-05-07 Nokia Technologies Oy Signalisation de mobilité et estimation d'un état de mobilité
US11102694B2 (en) * 2017-03-03 2021-08-24 Apple Inc. High speed train in new radio (NR)
WO2019148313A1 (fr) * 2018-01-30 2019-08-08 北京小米移动软件有限公司 Procédé de gestion de réseau, dispositif, système et support de stockage lisible par ordinateur
US20210099942A1 (en) * 2019-09-26 2021-04-01 Samsung Electronics Co., Ltd. Context-specific customization of handover parameters using characterization of a device's radio environment

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CATT: "Cell Re-selection in HSDN Station", 3GPP DRAFT; R2-1811376 CELL RE-SELECTION IN HSDN STATION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Gothenburg, Sweden; 20180820 - 20180824, 10 August 2018 (2018-08-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051521032 *
INTEL CORPORATION: "Cell reselection for the UE on high-speed-dedicated network", 3GPP DRAFT; R2-1802897, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Athens, Greece; 20180226 - 20180302, 16 February 2018 (2018-02-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051400274 *

Similar Documents

Publication Publication Date Title
EP4381884A1 (fr) Partitionnement d'accès aléatoire et rapport d'accès aléatoire
WO2023203240A1 (fr) Cas d'utilisation du découpage du réseau pour l'accès sans fil fixe (fwa)
WO2023022642A1 (fr) Signalisation de surchauffe prédite d'ue
WO2023043360A1 (fr) Améliorations de rapport de défaillance de liaison radio en cas d'échec de transfert
WO2022243850A1 (fr) Mobilité centrée l1/l2 par reconfiguration légère avec synchronisation
WO2022240334A1 (fr) Reconfigurations conditionnelles de cellules dans des groupes de cellules secondaires
WO2023146453A1 (fr) Journalisation d'ue et notification de propriétés de hsdn
US20240214849A1 (en) Relaxed Measurement Mode of Operation when UE Performs High-Priority Actions
WO2023121533A1 (fr) Enregistrement et rapport de propriétés de réseau dédié à grande vitesse (hsdn)
WO2023059238A1 (fr) Calcul d'état de mobilité de dispositif de communication à l'aide d'une fréquence de référence
EP4381812A1 (fr) Approches de signalisation pour plmn de catastrophe
WO2023068983A1 (fr) Rapport de mesurage basé sur des configurations de mesurage utilisant des indications de priorité spécifiques à la fréquence
WO2024035309A1 (fr) Procédés, appareil et support lisible par ordinateur associés à un changement conditionnel de cellule
WO2023068977A1 (fr) Rapport de mesurage de mdt pour équipements utilisateurs se trouvant dans n'importe quel état de sélection de cellule
WO2023152043A1 (fr) Mesure et notification efficaces de l1-rsrp entre cellules
WO2023152683A1 (fr) Changement de pscell conditionnel initié par un nœud secondaire
WO2023153978A1 (fr) Informations d'historique d'eu (uhi) et informations d'historique de mobilité (mhi) pendant l'activation/désactivation de scg
WO2023084464A1 (fr) Systèmes et procédés d'interdiction d'itinérance en cas de sinistre par des équipements d'utilisateur dans des cellules réservées à une utilisation par un opérateur
WO2024099949A1 (fr) Inclusion d'identité de pcell (cellule primaire) dans un rapport ra tout en effectuant une procédure ra vers une cellule scg
WO2023152704A1 (fr) Gestion d'identités de nœud local pour récupération de contexte de dispositif de communication
WO2023075672A1 (fr) Procédés et systèmes pour indiquer des fréquences mesurées dans un rapport de mesure
WO2024035305A1 (fr) Rapport de réussite de changement ou d'ajout de pscell
WO2023166448A1 (fr) Rapport de mesurage b1/a4 optimisé
WO2024072306A1 (fr) Surveillance de détection de défaillance de faisceau
WO2024035287A1 (fr) Évitement de situations de concurrence entre mobilité l1/l2 et l3

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

Country of ref document: EP

Kind code of ref document: A1