EP4413770A1 - Calcul d'état de mobilité de dispositif de communication à l'aide d'une fréquence de référence - Google Patents

Calcul d'état de mobilité de dispositif de communication à l'aide d'une fréquence de référence

Info

Publication number
EP4413770A1
EP4413770A1 EP22772621.3A EP22772621A EP4413770A1 EP 4413770 A1 EP4413770 A1 EP 4413770A1 EP 22772621 A EP22772621 A EP 22772621A EP 4413770 A1 EP4413770 A1 EP 4413770A1
Authority
EP
European Patent Office
Prior art keywords
communication device
network node
mobility state
network
message
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
EP22772621.3A
Other languages
German (de)
English (en)
Inventor
Sakib BIN REDHWAN
Pradeepa Ramachandra
Marco BELLESCHI
Angelo Centonza
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
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 AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of EP4413770A1 publication Critical patent/EP4413770A1/fr
Pending legal-status Critical Current

Links

Classifications

    • 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
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic

Definitions

  • the present disclosure is related to wireless communication systems and more particularly to calculating communication device mobility state using reference frequency.
  • FIG. 1 illustrates an example of a new radio (“NR”) network (e.g., a 5th Generation (“5G”) network) including a 5G core (“5GC”) network 130, network nodes 120a-b (e.g., 5G base station (“gNB”)), multiple communication devices 110 (also referred to as user equipment (“UE”)).
  • NR new radio
  • 5G 5th Generation
  • 5GC 5G core
  • gNB 5G base station
  • UE user equipment
  • a UE can move at different speeds; estimation of which can be beneficial to network.
  • a UE mobility state can be classified as one of several different mobility states such as a Normal, a Medium, or a High mobility state.
  • the UE mobility state can be determined based on the number of cell-reselections performed by the UE while in a radio resource control (“RRC”) Idle state. Modification of cell reselection parameters based on UE speed are allowed and transmitted to UE via speedStateReselectionPars as part of system information block 2 (“SIB2”) in NR.
  • SIB2 system information block 2
  • a UE determines its mobility state and logs as mobilitystate in RRCSetupComplete or RRCResumeComplete messages.
  • a network can configure speedStateReselectionPars as part of system information block 3 (“SIB3”), which are used by a UE in RRC IDLE state or speedStatePars as part of measConfig, which is used by UE in RRC Connected state to evaluate its mobility state.
  • SIB3 system information block 3
  • measConfig measConfig
  • Mobility state evaluation in UE is based on combining number of cell reselection performed in RRC Idle state and number of handovers performed in RRC Connected state by the UE. However, the evaluation is performed at the serving frequency of the UE. Cells at a lower frequency have a larger coverage area than cells at a higher frequency. Accordingly, if a UE is connected or camped normally to a cell in low frequency, it would perform less handover or cell- reselection and thus may evaluate itself as a low-speed UE while another UE in the same geographical area might be served by smaller cells at high frequency and perform frequent cell reselection or handover and may evaluate itself as a highspeed UE. Therefore, two UEs moving at a similar speed, in the same geographical area, can report being in different mobility states to the network.
  • a method of operating a communication device of a communications network includes receiving a message from a first network node of the communications network including a reference frequency and an evaluation parameter. The method further includes determining information associated with the reference frequency. The method further includes determining a mobility state of the communication device based on the information and the evaluation parameter. The method further includes transmitting an indication of the mobility state to a second network node of the communications network.
  • a method of operating a network node of a communications network includes transmitting a message to a communication device including a reference frequency and an evaluation parameter.
  • the message configures the communication device to determine a mobility state of the communication device relative to the reference frequency based on the evaluation parameter.
  • a communication device operating in a communications network is provided.
  • the communication device is adapted to perform operations.
  • the operations include receiving a message from a first network node of the communications network including a reference frequency and an evaluation parameter.
  • the operations further include determining information associated with the reference frequency.
  • the operations further include determining a mobility state of the communication device based on the information and the evaluation parameter.
  • the operations further include transmitting an indication of the mobility state to a second network node of the communications network.
  • a communication device operating in a communications network is provided.
  • the communication device includes processing circuitry and memory coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the communication device to perform operations.
  • the operations include receiving a message from a first network node of the communications network including a reference frequency and an evaluation parameter.
  • the operations further include determining information associated with the reference frequency.
  • the operations further include determining a mobility state of the communication device based on the information and the evaluation parameter.
  • the operations further include transmitting an indication of the mobility state to a second network node of the communications network.
  • a computer program including program code to be executed by processing circuitry of a communication device operating in a communications network. Execution of the program code causes the communication device to perform operations.
  • the operations include receiving a message from a first network node of the communications network including a reference frequency and an evaluation parameter.
  • the operations further include determining information associated with the reference frequency.
  • the operations further include determining a mobility state of the communication device based on the information and the evaluation parameter.
  • the operations further include transmitting an indication of the mobility state to a second network node of the communications network.
  • a computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry of a communication device operating in a communications network. Execution of the program code causes the communication device to perform operations. The operations include receiving a message from a first network node of the communications network including a reference frequency and an evaluation parameter. The operations further include determining information associated with the reference frequency. The operations further include determining a mobility state of the communication device based on the information and the evaluation parameter. The operations further include transmitting an indication of the mobility state to a second network node of the communications network. [0013] According to other embodiments, a non-transitory computer-readable medium having instructions stored is provided.
  • the instructions are executable by processing circuitry of a communication device operating in a communications network to cause the communication device to perform operations.
  • the operations include receiving a message from a first network node of the communications network including a reference frequency and an evaluation parameter.
  • the operations further include determining information associated with the reference frequency.
  • the operations further include determining a mobility state of the communication device based on the information and the evaluation parameter.
  • the operations further include transmitting an indication of the mobility state to a second network node of the communications network.
  • a network node operating in a communications network is provided.
  • the network node is adapted to perform operations.
  • the operations include transmitting a message to a communication device including a reference frequency and an evaluation parameter, the message configuring the communication device to determine a mobility state of the communication device relative to the reference frequency based on the evaluation parameter.
  • a network node operating in a communications network includes processing circuitry and memory coupled to the processing circuitry and having instructions stored therein that are executable by the processing circuitry to cause the network node to perform operations.
  • the operations include transmitting a message to a communication device including a reference frequency and an evaluation parameter, the message configuring the communication device to determine a mobility state of the communication device relative to the reference frequency based on the evaluation parameter.
  • a computer program including program code to be executed by processing circuitry of a network node operating in a communications network. Execution of the program code causes the network node to perform operations. The operations include transmitting a message to a communication device including a reference frequency and an evaluation parameter, the message configuring the communication device to determine a mobility state of the communication device relative to the reference frequency based on the evaluation parameter.
  • a computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry of a network node operating in a communications network. Execution of the program code causes the network node to perform operations. The operations include transmitting a message to a communication device including a reference frequency and an evaluation parameter, the message configuring the communication device to determine a mobility state of the communication device relative to the reference frequency based on the evaluation parameter.
  • a non-transitory computer-readable medium having instructions stored is provided.
  • the instructions are executable by processing circuitry of a network node operating in a communications network to cause the network node to perform operations.
  • the operations include transmitting a message to a communication device including a reference frequency and an evaluation parameter, the message configuring the communication device to determine a mobility state of the communication device relative to the reference frequency based on the evaluation parameter.
  • the UE can calculate its mobility states based on provided parameters for provided frequencies and report its mobility states to network. Such a report can provide multiple advantages to network.
  • a network can avoid misclassification of UEs.
  • the network may setup a single frequency layer as a reference frequency and optimize mobility state evaluation parameters for that layer. Thus, UEs can report uniform mobility state irrespective of their serving frequency. If a UE connected to high frequency layer reports being a high-speed UE based on the serving frequency, but a low-speed UE based on a reference frequency, the network can be aware of the situation and thus can adjust Mobility state evaluation parameters.
  • the network can configure optimal parameters for the UE.
  • a network needs to switch UEs to a different frequency layer, it can optimize UE configuration (e.g., speed-based scaling of Handover parameters) based on UE speed evaluated on the target frequency layer.
  • UE configuration e.g., speed-based scaling of Handover parameters
  • FIG. 1 is a schematic diagram illustrating an example of a 5 th generation (“5G”) network
  • FIG. 2 is a diagram illustrating an example of a MobilityStateParametersPSCell information element according to some embodiments of inventive concepts
  • FIG. 3 is a table illustrating an example of MobilityStateParametersPSCell field descriptions according to some embodiments of inventive concepts
  • FIG. 4 is a diagram illustrating an example of a
  • MobilityStateParametersSCell information element according to some embodiments of inventive concepts
  • FIG. 5 is a table illustrating an example of MobilityStateParametersSCell field descriptions according to some embodiments of inventive concepts
  • FIG. 6 is a flow chart illustrating examples of operations of a communication device according to some embodiments of inventive concepts
  • FIG. 7 is a flow chart illustrating examples of operations of a network node according to some embodiments of inventive concepts
  • FIG. 8 is a block diagram of a communication system in accordance with some embodiments.
  • FIG. 9 is a block diagram of a user equipment in accordance with some embodiments
  • FIG. 10 is a block diagram of a network node in accordance with some embodiments.
  • FIG. 11 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments.
  • FIG. 12 is a block diagram of a virtualization environment in accordance with some embodiments.
  • FIG. 13 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments in accordance with some embodiments.
  • a network node provides a communication device with a set of reference information to calculate its mobility state.
  • the network node can transmit a set of reference information to the communication device to calculate its mobility state via dedicated message or broadcasting for multiple UEs in the coverage region.
  • the UE can be configured to report its mobility state and the network node can receive the mobility state report from the UE.
  • the set of reference information can include a reference frequency or a set of reference frequencies based on which the UE needs to calculate its mobility state.
  • the set of reference information can further include mobility state evaluation parameters associated with each of the reference frequencies.
  • a UE can store mobility state information based on reference information provided by the network.
  • the UE can monitor mobility state evaluation related parameters broadcasted by the network (or received in a dedicated message from the network node).
  • the UE can evaluate its mobility state based on the received parameters.
  • the mobility state can include speed information for the UE.
  • the UE can transmit the mobility state report to network node [0038]
  • operations can be performed by a network node to provide a UE with a reference frequency or a range of frequencies and associated parameters and operations can be preformed by the UE to calculate its mobility states and report the mobility states to the network node.
  • the UE can calculate its mobility states based on provided parameters for provided frequencies and report its mobility states to network. Such a report can provide multiple advantages to network.
  • a network can avoid misclassification of UEs.
  • the network may setup a single frequency layer as a reference frequency and optimize mobility state evaluation parameters for that layer.
  • UEs can report uniform mobility state irrespective of their serving frequency. If a UE connected to high frequency layer reports being a high-speed UE based on the serving frequency, but a low-speed UE based on a reference frequency, the network can be aware of the situation and thus can adjust Mobility state evaluation parameters.
  • the network can configure optimal parameters for the UE. If a network needs to switch UEs to a different frequency layer, it can optimize UE configuration (e.g., speed-based scaling of Handover parameters) based on UE speed evaluated on the target frequency layer.
  • a first network node and a second network node are used interchangeably.
  • a first network node and a second network node can be the same node or different nodes.
  • operations performed by a first network node allow a UE to calculate a UE mobility state using a reference frequency.
  • the operations include the first network node providing the UE a set of reference information to calculate its mobility state.
  • the network can transmit a set of information to the UE in order for the UE to calculate its mobility states.
  • the set of information can be provided via dedicated message to the UE or broadcasted to multiple UEs in the coverage region.
  • the network may provide the UE with a reference frequency and associated parameters with it.
  • the network may provide the UE with a set of frequencies or range of frequencies and associated parameters for each of the frequencies.
  • the network may provide the UE with a set of frequencies and one or more sets of parameters.
  • Each set of parameters may be applicable to different subsets of the set of frequencies.
  • the same set of mobility state parameters may be configured for different frequencies, or for a range of frequencies.
  • the network may provide the UE with an indicator to a set of frequencies and mobility state evaluation parameter applicable for each of the frequencies.
  • the network may provide the UE with an indicator to a set of frequencies or to a subset of the set of frequencies and one set of mobility state evaluation parameter applicable to all frequencies in the set or subset.
  • the network may configure a separate set of mobility state evaluation parameters, which is not associated to any specific frequency.
  • the UE may use this configuration in case the UE did not visit in a given time window (configured by the network for mobility state evaluation) any cell associated to any of the reference frequency(ies) configured as per the above embodiments.
  • the network can configure the UE to calculate mobility state based on one or more frequencies on which the Primary Cell (PCell) is serving the UE and additionally indicate to the UE to calculate its mobility state on the basis of one or more of the following: a number of PSCell changes; and a number of SCell changes.
  • PCell Primary Cell
  • the UE can count the number of PSCell changes and derive its mobility state based on the number of PSCell changes.
  • Configuration parameters form the RAN to the UE for mobility state derivation based on PSCell changes can follow the format in FIG. 2, which is provided as an example.
  • the IE MobilityStateParametersPSCell includes parameters to determine UE mobility state.
  • FIG. 3 illustrates an example of MobilityStateParametersPSCell field descriptions.
  • the UE can count the number of SCell changes and derive its mobility state based on the number of SCell changes.
  • an SCell change can include an addition and/or a removal of an SCell as part of the configuration to the UE.
  • an SCell change can also include starting data transmission from a new SCell not used within a past time window and/or stopping of data transmission from an SCell previously used.
  • Configuration parameters form the RAN to the UE for mobility state derivation based on SCell changes can follow the format in FIG. 4, which is provided as an example.
  • the IE MobilityStateParametersSCell includes parameters to determine UE mobility state.
  • FIG. 5 illustrates an example of MobilityStateParametersSCell field descriptions.
  • the PSCell or SCell changes used to calculate the mobility state are considered only if the PSCells serve the UE on one of the frequencies signalled by the RAN to the UE for mobility state calculation.
  • the PSCell or SCell changes used to calculate the mobility state are considered independently of the frequencies signalled by the RAN to the UE for mobility state calculation.
  • the network can configure the UE using broadcast messages. It can include an indication in one of the broadcasted SIBs to provide UE with the information. In additional or alternative embodiments, the network can configure the UE with dedicated messages.
  • the network can configure the UE with a RRCReconfigurationComplete message. Such configuration can be applicable to RRC Connected and RRC IDLE UEs. In additional or alternative embodiments, the network can configure the UE in a RRCRelease message. Such configuration can be applicable to RRC IDLE UEs. In additional or alternative embodiments, the network can configure the UE in a LoggedMDTConfiguration message. Such configuration can be applicable to RRC IDLE UEs.
  • the network configures the UE to report its mobility sate.
  • a first network node configures the UE to report its mobility state to the first network node.
  • a first network node configures the UE to report its mobility state to a second network node that is different than the first network node.
  • a network may request the UE to report a mobility state evaluated on a certain frequency. For example, the network may have configured the UE to evaluate mobility state based on frequencies, f 1 , f2, f3; however, it may configure the UE to report its mobility state based on f2 only.
  • the existing UElnformationRequest message can be used for reporting a mobility state evaluated on a certain frequency.
  • a new message can be used for reporting a mobility state evaluated on a certain frequency.
  • a network may request a UE to report mobility state information as part of a logged MDT report.
  • a network may request a UE to report mobility state information as a new report.
  • a network may receive the mobility state report from the UE.
  • the network receives a mobility state report from the UE in a message based on its configuration. The network may use this report for any optimization purpose.
  • a UE can store detailed information regarding its state change and transmit the information to a wireless network.
  • the UE can monitor mobility state evaluation related parameters that were broadcasted by the network (or received in a dedicated message from a network node). In some examples, the UE monitors mobility state evaluation related parameters broadcasted by the network or receives it in a dedicated manner.
  • the UE evaluates its mobility state based on the received parameters. In some examples, the UE evaluates its mobility states based on the received parameters. In additional or alternative examples, its mobility state evaluation may be different for different reference frequencies if a set of reference frequencies is configured by the network as per the previous embodiments.
  • the UE transmits the mobility state report towards the network.
  • the UE transmits the mobility state reports to the network (e.g., a first network node that transmitted the parameters or a second network node that is different than the first network node) based on network configuration.
  • Each report may be associated to different mobility state evaluation, and hence separate reports may be provided for different reference frequencies if a set of reference frequencies is configured by the network.
  • the UE includes the mobility state information as part of UElnformationResponse message.
  • the network may request the UE report mobility state information as part of logged MDT report.
  • the network may request the UE report mobility state information as a new report.
  • the UE for each reported mobility state information including a specific mobility state (e.g. a normal, a medium, or a high mobility state), the UE also reports an indication (e.g., an absolute radio-frequency channel number (“ARFCN”) value or an indicator provided in the configuration) of the frequencies or range of frequencies associated to each reported mobility state information. Since, as per configuration, one mobility state information may be associated to multiple frequencies, the UE indicates all the frequencies in which that concerned mobility state information was evaluated. The UE may also include the number of cell reselections performed for each of the frequencies associated to this mobility state report.
  • ARFCN absolute radio-frequency channel number
  • the UE may indicate that in the mobility state information. For example, the UE may indicate that for the certain reference frequency or for the specific set/subset/range of frequencies no cell reselection was performed, and that mobility state evaluation is not available/applicable.
  • the UE may apply the mobility state parameters configuration provided by the network.
  • the UE may perform the mobility state evaluation just on the basis of the visited cells irrespective of the operating frequencies of those visited cells.
  • the UE for each reported mobility state information including a specific mobility state (e.g., normal/medium/high mobility state), the UE also reports an indication of whether the mobility state was derived by taking PSCell changes and/or SCell changes into account. The UE may also indicate whether the mobility state was derived by taking into account only PSCell changes events and/or SCell change events.
  • a specific mobility state e.g., normal/medium/high mobility state
  • the communication device may be any of the UE 812A-D, 900, hardware 1204, or virtual machine 1208A, 1208B
  • the UE 900 (also referred to herein as communication device 900) shall be used to describe the functionality of the operations of the communication device.
  • Operations of the communication device 900 (implemented using the structure of FIG. 9) will now be discussed with reference to the flow chart of FIG. 6 according to some embodiments of inventive concepts.
  • modules may be stored in memory 910 of FIG. 9, and these modules may provide instructions so that when the instructions of a module are executed by respective communication device processing circuitry 902, processing circuitry 902 performs respective operations of the flow chart.
  • FIG. 6 illustrates operations performed by a communication device of a communications network.
  • the communications network includes a fifth generation (“5G”) network.
  • 5G fifth generation
  • processing circuitry 902 receives, via communication interface 912, a message from a first network node including a reference frequency and an evaluation parameter.
  • the reference frequency includes a plurality of reference frequencies and the evaluation parameter includes a plurality of evaluation parameters.
  • Each evaluation parameter of the plurality of evaluation parameters can be associated with a reference frequency of the plurality of reference frequencies.
  • receiving the message includes receiving at least one of: a broadcast message; a direct message; a radio resource control (“RRC”) reconfiguration complete message; a RRC release message; and a logged minimization of drive tests (“MDT”), configuration message.
  • RRC radio resource control
  • MDT logged minimization of drive tests
  • processing circuitry 902 determines information associated with the reference frequency.
  • processing circuitry 902 determines a mobility state of the communication device based on the information and the evaluation parameter.
  • the reference frequency includes a frequency on which a primary cell is serving the communication device
  • the evaluation parameter includes a threshold number of primary secondary cell (“PSCell”) changes. Determining the information can include determining a number of PSCell changes associated with the communication device. Determining the mobility state of the communication device includes comparing the number of PSCell changes associated with the communication device with the threshold number of PSCell changes.
  • the reference frequency includes a frequency on which a primary cell is serving the communication device
  • the evaluation parameter includes a threshold number of secondary cell (“SCell”) changes. Determining the information can include determining a number of SCell changes associated with the communication device. Determining the mobility state of the communication device includes comparing the number of SCell changes associated with the communication device with the threshold number of SCell changes.
  • the reference frequency includes a frequency of a cell in which the communication device has camped while the communication device was in an IDLE mode
  • the evaluation parameter includes a threshold number of cell reselections. Determining the information can include determining a number of cell reselections associated with the communication device. Determining the mobility state of the communication device includes comparing the number of cell reselections associated with the communication device with the threshold number of cell reselections.
  • processing circuitry 902 receives, via communication interface 912, a request from the first network node or a second network node requesting an indication of the mobility state be transmitted to the second network node.
  • the first network node and the second network node are different entities.
  • the first network node includes the second network node.
  • processing circuitry 902 transmits, via communication interface 912, the indication of the mobility state to the second network node of the communications network.
  • transmitting the indication of the mobility state further includes transmitting a portion of the information to the second network node.
  • the first network node and the second network node include radio access network, RAN, nodes.
  • FIG. 6 may be optional with respect to some embodiments.
  • block 640 may be optional.
  • the network node may be any of the network node 810A, 810B, 1000, 1304, hardware 1204, or virtual machine 1208A, 1208B
  • the network node 1000 shall be used to describe the functionality of the operations of the network node. Operations of the network node 1000 (implemented using the structure of FIG. 10) will now be discussed with reference to the flow chart of FIG. 7 according to some embodiments of inventive concepts.
  • modules may be stored in memory 1004 of FIG. 10, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 1002, processing circuitry 1002 performs respective operations of the flow chart.
  • FIG. 7 illustrates operations performed by a network node of a communications network.
  • the communications network includes a fifth generation, 5G, network
  • the network node includes a radio access network, RAN, node.
  • processing circuitry 1002 transmits, via communication interface 1006, a message to a communication device including a reference frequency and an evaluation parameter.
  • the reference frequency includes a plurality of reference frequencies and the evaluation parameter includes a plurality of evaluation parameters. Each evaluation parameter of the plurality of evaluation parameters can be associated with a reference frequency of the plurality of reference frequencies.
  • the message configures the communication device to determine a mobility state of the communication device relative to the reference frequency based on the evaluation parameter.
  • the reference frequency includes a frequency on which a primary cell is serving the communication device and the evaluation parameter includes a threshold number of primary secondary cell, PSCell, changes.
  • the message can configure the communication device to determine the mobility state of the communication device by comparing a number of PSCell changes associated with the communication device with the threshold number of PSCell changes.
  • the reference frequency includes a frequency on which a primary cell is serving the communication device and the evaluation parameter includes a threshold number of secondary cell, SCell, changes.
  • the message can configure the communication device to determine the mobility state of the communication device by comparing a number of SCell changes associated with the communication device with the threshold number of SCell changes.
  • the reference frequency includes a frequency of a cell in which the communication device has camped while the communication device was in an IDLE mode
  • the evaluation parameter includes a threshold number of cell reselections.
  • the message can configure the communication device to determine the mobility state of the communication device by comparing with a number of cell reselections associated with the threshold number of cell reselections.
  • the message further includes a default evaluation parameter and instructs the communication device to use the default evaluation parameter to determine the mobility state of the communication device if the communication device avoids using the reference frequency within a period of time.
  • transmitting the message includes transmitting at least one of: a broadcast message; a direct message; a radio resource control, RRC, reconfiguration complete message; a RRC release message; and a logged minimization of drive tests, MDT, configuration message.
  • processing circuitry 1002 transmits, via communication interface 1006, a request to the communication device requesting that the communication device transmit an indication of the mobility state to a second network node.
  • the network node (a first network node) is the same as the second network node. In other embodiments, the network node (the first network node) is separate and distinct from the second network node.
  • processing circuitry 1002 receives, via communication interface 1006, an indication of the mobility state of the communication device.
  • processing circuitry 1002 adjusts operation of the communications network based on the mobility state of the communication device.
  • Various operations of FIG. 7 may be optional with respect to some embodiments. For example, in some embodiments, blocks 720, 730, and 740 may be optional.
  • FIG. 8 shows an example of a communication system 800 in accordance with some embodiments.
  • the communication system 800 includes a telecommunication network 802 that includes an access network 804, such as a radio access network (RAN), and a core network 806, which includes one or more core network nodes 808.
  • the access network 804 includes one or more access network nodes, such as network nodes 810a and 810b (one or more of which may be generally referred to as network nodes 810), or any other similar 3 rd Generation Partnership Project (3GPP) access node or non-3GPP access point.
  • 3GPP 3 rd Generation Partnership Project
  • the network nodes 810 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 812a, 812b, 812c, and 812d (one or more of which may be generally referred to as UEs 812) to the core network 806 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 800 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 800 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 812 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 810 and other communication devices.
  • the network nodes 810 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 812 and/or with other network nodes or equipment in the telecommunication network 802 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 802.
  • the core network 806 connects the network nodes 810 to one or more hosts, such as host 816. 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 806 includes one more core network nodes (e.g., core network node 808) 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 808.
  • 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 816 may be under the ownership or control of a service provider other than an operator or provider of the access network 804 and/or the telecommunication network 802, and may be operated by the service provider or on behalf of the service provider.
  • the host 816 may host a variety of applications to provide one or more service. Examples of such applications include live and prerecorded 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 800 of FIG. 8 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, 4G, 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 802 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 802. For example, the telecommunications network 802 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 812 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 804.
  • 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 814 communicates with the access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812c and/or 812d) and network nodes (e.g., network node 810b).
  • the hub 814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 814 may be a broadband router enabling access to the core network 806 for the UEs.
  • the hub 814 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 814 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 814 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 814 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 814 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 814 may have a constant/persistent or intermittent connection to the network node 810b.
  • the hub 814 may also allow for a different communication scheme and/or schedule between the hub 814 and UEs (e.g., UE 812c and/or 812d), and between the hub 814 and the core network 806.
  • the hub 814 is connected to the core network 806 and/or one or more UEs via a wired connection.
  • the hub 814 may be configured to connect to an M2M service provider over the access network 804 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 810 while still connected via the hub 814 via a wired or wireless connection.
  • the hub 814 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 810b.
  • the hub 814 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 810b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIG. 9 shows a UE 900 in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • 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), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE 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).
  • 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, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • the UE 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input/output interface 906, a power source 908, a memory 910, a communication interface 912, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in FIG. 9. 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 902 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 910.
  • the processing circuitry 902 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 902 may include multiple central processing units (CPUs).
  • the input/output interface 906 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 900.
  • 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 908 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 908 may further include power circuitry for delivering power from the power source 908 itself, and/or an external power source, to the various parts of the UE 900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 908.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 908 to make the power suitable for the respective components of the UE 900 to which power is supplied.
  • the memory 910 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 910 includes one or more application programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916.
  • the memory 910 may store, for use by the UE 900, any of a variety of various operating systems or combinations of operating systems.
  • the memory 910 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 910 may allow the UE 900 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 910, which may be or comprise a device-readable storage medium.
  • the processing circuitry 902 may be configured to communicate with an access network or other network using the communication interface 912.
  • the communication interface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 922.
  • the communication interface 912 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 918 and/or a receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., antenna 922) and may share circuit components, software or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 912 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, nearfield 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 912, 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. In response to the received wireless input 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 Internet of Things
  • Non-limiting examples of such an 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-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot.
  • 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. 10 shows a network node 1000 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 1000 includes a processing circuitry 1002, a memory 1004, a communication interface 1006, and a power source 1008.
  • the network node 1000 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 1000 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 1000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs).
  • the network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, 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 1000.
  • RFID Radio Frequency Identification
  • the processing circuitry 1002 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 1000 components, such as the memory 1004, to provide network node 1000 functionality.
  • the processing circuitry 1002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1002 includes one or more of radio frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014. In some embodiments, the radio frequency (RF) transceiver circuitry 1012 and the baseband processing circuitry 1014 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 1012 and baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.
  • SOC system on a chip
  • the processing circuitry 1002 includes one or more of radio frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014.
  • the radio frequency (RF) transceiver circuitry 1012 and the baseband processing circuitry 1014 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 1004 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 nonvolatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1002.
  • 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 nonvola
  • the memory 1004 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 1002 and utilized by the network node 1000.
  • the memory 1004 may be used to store any calculations made by the processing circuitry 1002 and/or any data received via the communication interface 1006.
  • the processing circuitry 1002 and memory 1004 is integrated.
  • the communication interface 1006 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE.
  • the communication interface 1006 comprises port(s)/terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 1006 also includes radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, the antenna 1010.
  • Radio front-end circuitry 1018 comprises filters 1020 and amplifiers 1022.
  • the radio front-end circuitry 1018 may be connected to an antenna 1010 and processing circuitry 1002.
  • the radio front-end circuitry may be configured to condition signals communicated between antenna 1010 and processing circuitry 1002.
  • the radio front-end circuitry 1018 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 1018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1020 and/or amplifiers 1022. The radio signal may then be transmitted via the antenna 1010. Similarly, when receiving data, the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018. The digital data may be passed to the processing circuitry 1002.
  • the communication interface may comprise different components and/or different combinations of components.
  • the network node 1000 does not include separate radio front-end circuitry 1018, instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communication interface 1006. In still other embodiments, the communication interface 1006 includes one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012, as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).
  • the antenna 1010 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 1010 may be coupled to the radio front-end circuitry 1018 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 1010 is separate from the network node 1000 and connectable to the network node 1000 through an interface or port.
  • the antenna 1010, communication interface 1006, and/or the processing circuitry 1002 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 1010, the communication interface 1006, and/or the processing circuitry 1002 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 1008 provides power to the various components of network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1000 with power for performing the functionality described herein.
  • the network node 1000 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 1008.
  • the power source 1008 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 1000 may include additional components beyond those shown in FIG. 10 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 1000 may include user interface equipment to allow input of information into the network node 1000 and to allow output of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000.
  • FIG. 11 is a block diagram of a host 1100, which may be an embodiment of the host 816 of FIG. 8, in accordance with various aspects described herein.
  • the host 1100 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 1100 may provide one or more services to one or more UEs.
  • the host 1100 includes processing circuitry 1102 that is operatively coupled via a bus 1104 to an input/output interface 1106, a network interface 1108, a power source 1110, and a memory 1112.
  • 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 FIGS. 9 and 10, such that the descriptions thereof are generally applicable to the corresponding components of host 1100.
  • the memory 1112 may include one or more computer programs including one or more host application programs 1114 and data 1116, which may include user data, e.g., data generated by a UE for the host 1100 or data generated by the host 1100 for a UE.
  • Embodiments of the host 1100 may utilize only a subset or all of the components shown.
  • the host application programs 1114 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), 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 1114 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 1100 may select and/or indicate a different host for over-the-top services for a UE.
  • the host application programs 1114 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. 12 is a block diagram illustrating a virtualization environment 1200 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 1200 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 1202 (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 1204 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 1206 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1208a and 1208b (one or more of which may be generally referred to as VMs 1208), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1206 may present a virtual operating platform that appears like networking hardware to the VMs 1208.
  • the VMs 1208 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1206.
  • a virtualization layer 1206 Different embodiments of the instance of a virtual appliance 1202 may be implemented on one or more of VMs 1208, 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 1208 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, nonvirtualized machine.
  • Each of the VMs 1208, and that part of hardware 1204 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 1208 on top of the hardware 1204 and corresponds to the application 1202.
  • Hardware 1204 may be implemented in a standalone network node with generic or specific components. Hardware 1204 may implement some functions via virtualization. Alternatively, hardware 1204 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 1210, which, among others, oversees lifecycle management of applications 1202.
  • hardware 1204 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 1212 which may alternatively be used for communication between hardware nodes and radio units.
  • FIG. 13 shows a communication diagram of a host 1302 communicating via a network node 1304 with a UE 1306 over a partially wireless connection in accordance with some embodiments.
  • host 1302 Like host 1100, embodiments of host 1302 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1302 also includes software, which is stored in or accessible by the host 1302 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 1306 connecting via an over-the-top (OTT) connection 1350 extending between the UE 1306 and host 1302.
  • OTT over-the-top
  • the network node 1304 includes hardware enabling it to communicate with the host 1302 and UE 1306.
  • the connection 1360 may be direct or pass through a core network (like core network 806 of FIG. 8) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1306 includes hardware and software, which is stored in or accessible by UE 1306 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 1306 with the support of the host 1302.
  • 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 1306 with the support of the host 1302.
  • an executing host application may communicate with the executing client application via the OTT connection 1350 terminating at the UE 1306 and host 1302.
  • 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 1350 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
  • the OTT connection 1350 may extend via a connection 1360 between the host 1302 and the network node 1304 and via a wireless connection 1370 between the network node 1304 and the UE 1306 to provide the connection between the host 1302 and the UE 1306.
  • the connection 1360 and wireless connection 1370, over which the OTT connection 1350 may be provided, have been drawn abstractly to illustrate the communication between the host 1302 and the UE 1306 via the network node 1304, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • the host 1302 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 1306.
  • the user data is associated with a UE 1306 that shares data with the host 1302 without explicit human interaction.
  • the host 1302 initiates a transmission carrying the user data towards the UE 1306.
  • the host 1302 may initiate the transmission responsive to a request transmitted by the UE 1306.
  • the request may be caused by human interaction with the UE 1306 or by operation of the client application executing on the UE 1306.
  • the transmission may pass via the network node 1304, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1312, the network node 1304 transmits to the UE 1306 the user data that was carried in the transmission that the host 1302 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1314, the UE 1306 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1306 associated with the host application executed by the host 1302.
  • the UE 1306 executes a client application which provides user data to the host 1302.
  • the user data may be provided in reaction or response to the data received from the host 1302.
  • the UE 1306 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 1306. Regardless of the specific manner in which the user data was provided, the UE 1306 initiates, in step 1318, transmission of the user data towards the host 1302 via the network node 1304.
  • the network node 1304 receives user data from the UE 1306 and initiates transmission of the received user data towards the host 1302.
  • the host 1302 receives the user data carried in the transmission initiated by the UE 1306.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1306 using the OTT connection 1350, in which the wireless connection 1370 forms the last segment. More precisely, the teachings of these embodiments may allow a UE to calculate its mobility states based on provided parameters for provided frequencies and report its mobility states to network. Such a report can provide multiple advantages to network. In some examples, a network can avoid misclassification of UEs. The network may setup a single frequency layer as a reference frequency and optimize mobility state evaluation parameters for that layer. Thus, UEs can report uniform mobility state irrespective of their serving frequency.
  • the network can be aware of the situation and thus can adjust Mobility state evaluation parameters.
  • the network can configure optimal parameters for the UE. If a network needs to switch UEs to a different frequency layer, it can optimize UE configuration (e.g., speed-based scaling of Handover parameters) based on UE speed evaluated on the target frequency layer.
  • factory status information may be collected and analyzed by the host 1302.
  • the host 1302 may process audio and video data which may have been retrieved from a UE for use in creating maps.
  • the host 1302 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights).
  • the host 1302 may store surveillance video uploaded by a UE.
  • the host 1302 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 1302 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 1302 and/or UE 1306.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1350 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 1350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1304. 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 1302.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1350 while monitoring propagation times, errors, etc.
  • computing devices described herein may include the illustrated combination of hardware components
  • 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.

Landscapes

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

Abstract

Un dispositif de communication d'un réseau de communication peut recevoir, d'un premier nœud de réseau du réseau de communication, un message comprenant une fréquence de référence et un paramètre d'évaluation. Le dispositif de communication peut déterminer des informations associées à la fréquence de référence. Le dispositif de communication peut en outre déterminer un état de mobilité du dispositif de communication sur la base des informations et du paramètre d'évaluation. Le dispositif de communication peut en outre transmettre une indication de l'état de mobilité à un second nœud de réseau du réseau de communication.
EP22772621.3A 2021-10-08 2022-09-06 Calcul d'état de mobilité de dispositif de communication à l'aide d'une fréquence de référence Pending EP4413770A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163253795P 2021-10-08 2021-10-08
PCT/SE2022/050789 WO2023059238A1 (fr) 2021-10-08 2022-09-06 Calcul d'état de mobilité de dispositif de communication à l'aide d'une fréquence de référence

Publications (1)

Publication Number Publication Date
EP4413770A1 true EP4413770A1 (fr) 2024-08-14

Family

ID=83355192

Family Applications (1)

Application Number Title Priority Date Filing Date
EP22772621.3A Pending EP4413770A1 (fr) 2021-10-08 2022-09-06 Calcul d'état de mobilité de dispositif de communication à l'aide d'une fréquence de référence

Country Status (2)

Country Link
EP (1) EP4413770A1 (fr)
WO (1) WO2023059238A1 (fr)

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102148335B1 (ko) * 2012-02-06 2020-08-26 삼성전자 주식회사 이동통신 시스템에서 복수의 캐리어를 이용해서 데이터를 송수신하는 방법 및 장치

Also Published As

Publication number Publication date
WO2023059238A1 (fr) 2023-04-13

Similar Documents

Publication Publication Date Title
WO2022240334A1 (fr) Reconfigurations conditionnelles de cellules dans des groupes de cellules secondaires
EP4381884A1 (fr) Partitionnement d'accès aléatoire et rapport d'accès aléatoire
EP4381790A1 (fr) Mode de fonctionnement de mesure relâché lorsqu'un ue effectue des actions de haute priorité
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
EP4413770A1 (fr) Calcul d'état de mobilité de dispositif de communication à l'aide d'une fréquence de référence
US20240259921A1 (en) Signalling Approaches for Disaster PLMNS
US20240306038A1 (en) Seamless Broadcast Segments Acquisition during Mobility
US20240323995A1 (en) Secondary node requested measurement gaps at secondary node addition
US20240298203A1 (en) Signalling based minimization of drive test configuration availability
WO2023146453A1 (fr) Journalisation d'ue et notification de propriétés de hsdn
WO2023152043A1 (fr) Mesure et notification efficaces de l1-rsrp entre cellules
WO2024035309A1 (fr) Procédés, appareil et support lisible par ordinateur associés à un changement conditionnel de cellule
WO2023121533A1 (fr) Enregistrement et rapport de propriétés de réseau dédié à grande vitesse (hsdn)
EP4420388A1 (fr) Rapport de mesurage basé sur des configurations de mesurage utilisant des indications de priorité spécifiques à la fréquence
WO2024035305A1 (fr) Rapport de réussite de changement ou d'ajout de pscell
WO2024072306A1 (fr) Surveillance de détection de défaillance de faisceau
EP4381779A1 (fr) Réduction de rapports de relaxation de mesure radio inutile
WO2024099949A1 (fr) Inclusion d'identité de pcell (cellule primaire) dans un rapport ra tout en effectuant une procédure ra vers une cellule scg
WO2023153978A1 (fr) Informations d'historique d'eu (uhi) et informations d'historique de mobilité (mhi) pendant l'activation/désactivation de scg
WO2024035311A1 (fr) Minimisation de portée de configuration de tests de disque pour différents types de réseau
WO2023068977A1 (fr) Rapport de mesurage de mdt pour équipements utilisateurs se trouvant dans n'importe quel état de sélection de cellule
WO2023152683A1 (fr) Changement de pscell conditionnel initié par un nœud secondaire
WO2024210787A1 (fr) Informations de capacité d'équipement utilisateur relatives à un temps de syntonisation de fréquence radio

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: UNKNOWN

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20240326

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR